Search

Your Notifications (0)

There are currently no notifications. You're all set!

Knowledge Base
ChemDraw and ChemOffice+ Products Signals Notebook E-Notebook and ChemBioOffice Enterprise Spotfire and Signals Spotfire Products Image Artist Spectrus, Percepta, Katalyst, Luminata and more
Downloads
Downloads
Community
Ideas Portal Product Basics
About Support
Legal Resources Support and Maintenance Plans Product Life Cycle Support News
Contact Support

Data source element cannot be located error when opening the default user_actions.dxp imported from logged_user_actions_mssql.part0.zip or logged_user_actions_ora.part0.zip

Franch, Monica
  • Updated
Date Posted:
Product: TIBCO Spotfire®

Problem:

Data source element cannot be located error when opening the default user_actions.dxp imported from logged_user_actions_mssql.part0.zip or logged_user_actions_ora.part0.zip


Solution:

After importing the logged_user_actions_mssql.part0.zip or logged_user_actions_ora.part0.zip file to the library, and editing the data source with the connection information to the action log database/schema, you might encounter the following error while opening the analysis file or information links that are associated with action log database.This may happen even though the user has required library permissions to access it.

ImportException at Spotfire.Dxp.Data:
Failed to execute data query

The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/LOGGED_TIME' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/MACHINE' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/USER_NAME' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ORIGINAL_TIME' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ORIGINAL_IP' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/LOG_CATEGORY' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/LOG_ACTION' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/SUCCESS' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/SESSION_ID' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ID1' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ID2' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ARG1' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ARG2' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ARG3' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ARG4' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ARG5' cannot be located.
The referenced data source element '/logged_user_actions_datasource/spotfire_actionlog/dbo/ACTIONLOG/ARG6' cannot be located.
(HRESULT: 80131500)

Stack Trace:
   at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.DataStream.GetNextBlock()
   at Spotfire.Dxp.Data.InformationModel.InternalInformationModelManager.DataStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at Spotfire.Dxp.Internal.Utilities.SeekableStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.BinaryReader.FillBuffer(Int32 numBytes)
   at System.IO.BinaryReader.ReadUInt16()
   at Spotfire.Dxp.Data.Formats.Sbdf.SbdfSectionHeader.ReadMagicNumber(BinaryReader reader)
   at Spotfire.Dxp.Data.Formats.Sbdf.SbdfSectionHeader.ReadSectionType(BinaryReader reader, SbdfSectionTypeId expectedType)
   at Spotfire.Dxp.Data.Import.SbdfDataRowReader.DelayedInit()
   at Spotfire.Dxp.Data.Import.InformationLinkDataSourceConnection.ExecuteQueryCore2()
   at Spotfire.Dxp.Data.DataSourceConnection.ExecuteQuery2()
   at Spotfire.Dxp.Data.DataFlow.Execute()
   at Spotfire.Dxp.Data.DataFlow.DataFlowConnection.ExecuteQueryCore2()
   at Spotfire.Dxp.Data.DataSourceConnection.ExecuteQuery2()
   at Spotfire.Dxp.Data.Producers.SourceColumnProducer.<>c__DisplayClass27.<CreateView>b__24()
   at Spotfire.Dxp.Framework.ApplicationModel.Progress.ExecuteSubtask(String title, ProgressOperation operation)
   at Spotfire.Dxp.Data.Producers.SourceColumnProducer.CreateView(CxxSession session, DataPropertyRegistry propertyRegistry, GlobalMethodRegistry globalMethodRegistry, DataSourceConnection connection, PartialDataLoadReport& partialLoadReport)
   at Spotfire.Dxp.Data.Producers.SourceColumnProducer.GetColumnsAndProperties(DataSourceConnection connection)?

You may see this error because the data source and/or information links reference to the default Action Log database name "spotfire_actionlog" while the actual installed Action Log database was named something non-default, like "mySpotfireServerActionLog". In order to prevent this from happening, you can remap the information model to use your actual Action Log database name (like the example "mySpotfireServerActionLog"). This can be done following the instructions here:

Doc: Redirecting the Information Model


Alternatively, you can rename the Action Log database name back to the default value "spotfire_actionlog" and keep the information model unmodified.

Doc: Importing a library to Spotfire Analyst for analyzing action logs

Doc: Redirecting the Information Model

Related articles

Comments

0 comments

Article is closed for comments.