Products | Versions |
---|---|
Spotfire Analyst | All versions |
Error message: Unable to import data. See the details for more information. ImportException at Spotfire.Dxp.Data: An internal connector error has occurred. Internal error: The CustomQuery: 'QueryName' was not allowed to execute because it is not trusted. Data connection: DataConnectionName Server: server.address Database: DatabaseName (HRESULT: 80131500) Stack Trace: at Spotfire.Dxp.Data.Producers.ConnectorImportColumnProducer.GetColumnsAndProperties() at Spotfire.Dxp.Data.Persistence.DataItem.PerformUpdate(DataColumnProducer producer, Boolean forceUpdate) at Spotfire.Dxp.Data.Persistence.DataItem.Update(DataColumnProducer producer, Boolean forceUpdate) at Spotfire.Dxp.Data.Persistence.DataPool.GetDerivedData(DataColumnProducer producer, Boolean loadingPre50CalculatedColumnProducer) at Spotfire.Dxp.Data.Persistence.DataPool.GetData(DataColumnProducer producer, Boolean loadingPre50CalculatedColumnProducer) ...
Each installation of TIBCO Spotfire (Analyst / Desktop / Professional) client has a local trust cache available for the Windows users executing the client. This cache works in the same manner as the trust hash in the library, but is saved locally on the computer instead of in the library database. To trust the custom query locally, follow the below steps:
If it is saved as part of a report
If the connection is saved in the library
The custom query should now be trusted in your local trust cache.
NOTE: This Custom Query is trusted for a specific user on the local machine. If another user tries to open on the same machine, they need to have Spotfire Analyst>>Custom Query in Connections License
From TIBCO Spotfire 7.0 and higher
For TIBCO Spotfire 6.5 and lower
In TIBCO Spotfire 6.5 and prior, the steps provided for 7.0 and onward are not sufficient. To ensure that the custom query is trusted in the library, it needs to be saved as part of a report. If you want it to be trusted as it's own library item, you need to:
This will then trust both the custom query in the report but also the custom query saved in the library prior to using it in the report.