analytic Coffee!
  • Topical Tessitura Community Groups
  • More
analytic Coffee!
Wiki Troubleshoot Data Warehouse Load
  • Discussions
  • Files
  • Wiki
  • Members
  • Mentions
  • Tags
  • Events
  • More
  • Cancel
  • New
analytic Coffee! requires membership for participation - click to join
  • analytic Coffee! Wiki
  • +Tessitura Analytics Shared Dashboards
  • +Data Analysis Training Opportunities
  • -Analytics Tips & Trouble shooting
    • Analytics Scripts not Saving
    • Auto-Zoom Scatter Map
    • Changing Labels on a Graph
    • Conditionally format the color of text
    • First Time Buyers and Subsequent Buying
    • Fixing Tessitura Analytic Emails after an upgrade
    • Joining Isolated Data-points, Removing Data Markers, Interpolating Last Point
    • Milestones: Labelled Data Points on Analytics Charts
    • RSUM continuous chart, remove gaps
    • Scatter Map Widget tips - Heat Map of postal codes
    • Sorting First Performance Name by Date Instead of Alphabetically
    • Troubleshoot Data Warehouse Load
    • Troubleshooting Application Availability
  • Jupyter Notebooks
  • Learning about AI
  • +Learning about Python
  • +Power BI & Tessitura

You are currently reviewing an older revision of this page.

  • History View current version

Troubleshoot Data Warehouse Load

The Dashboard requires ElastiCube <cubename> to run. It wasn't found on <servername>.

Verify that the Load Data Warehouse (FULL) job can run successfully.

The Load Data Warehouse (FULL) job can be run manually and in debug mode by impersonating the Analytics login in an SSMS session. For example:

EXECUTE AS LOGIN = 'Analytics';

EXEC dbo.LOAD_TABLES @mode='F', @debug = 'Y';

EXEC dbo.PROCESS_CUSTOMIZATIONS @timeout_seconds = 120, @debug = 'Y';

EXEC dbo.PROCESS_CUBES @delayseconds = 20, @debug = 'Y';

Errors may occur during the data load if there is a misconfiguration. For example:

Executed as user: Analytics. pre_load: Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 42000] (Error 50001) OLE DB provider "SQLNCLI11" for linked server "Analytics_FCSQL02\TESSNEXT" returned message "Communication link failure". [SQLSTATE 01000] (Error 7412) OLE DB provider "SQLNCLI11" for linked server "Analytics_FCSQL02\TESSNEXT" returned message "Invalid connection string attribute". [SQLSTATE 01000] (Error 7412). The step failed.

Or:

Executed as user: Analytics. pre_load: Cannot open database "impresario" requested by the login. The login failed. [SQLSTATE 42000] (Error 50001) OLE DB provider "SQLNCLI11" for linked server "Analytics_FCSQL02\TESSNEXT" returned message "Invalid connection string attribute". [SQLSTATE 01000] (Error 7412). The step failed.

In the event of a linked server error, you can test the linked server connection from your Analytics SQL Server in SSMS, found in Server Objects/Linked Servers -> Right click, Test Connection. However, this will only work if you are logged in to SSMS using the [Analytics] SQL credential. In order for the linked server to work, the TessituraAnalytics user must exist in the impresario DB being connected to. This user can be created using a script included with TIM at \TessituraInstaller\Components\TessituraAnalytics\Database\ConfigScripts\CreateAnalyticsUserOnTessitura.sql.

Error in PROCESS_CUBES step:

Contributions cube build unsuccessful, the cube does not exist 

... To be continued...