You are currently reviewing an older revision of this page.

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.

Cube Processing Errors

Error in PROCESS_CUBES step:

Contributions cube build unsuccessful, the cube does not exist 

Check errors in Sisense log folders:

On Sisense Web Application server:

  • C:\ProgramData\Sisense\PrismWeb\Logs (web server logs)
  • C:\ProgramData\Sisense\PrismWeb\Repository\Logs (MongoDB logs)

On Sisense cube server:

  • C:\ProgramData\Sisense\PrismServer\PrismServerLogs (Cube server logs)
  • C:\ProgramData\Sisense\PrismServer\ElastiCubeProcessLogs (limited usability, not human readable text)

In Sisense web server log:

<Exception handler="Maestro.Exception" type="EndpointNotFoundException" msg="Could not connect to net.tcp://fcsql02.bard.edu:811/CloudManagementService. The connection attempt lasted for a time span of 00:00:21.0019839. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.20.10.46:811. " thread="(110)" date="31-01-2020" time="15:17:08:415" log_level="ERROR">

A connection cannot be made to port 811 on the cube server. Re-check that services are running and that firewall ports are open. Follow troubleshooting steps in Tessitura Analytics Setup documentation. Don't forget about the ElastiCubeManagementService!

You should also be able to manually log in to the Sisense web interface as admin (using your org credential at host:port/app/account#/login) and check Admin/Data Sources to verify that all cubes are accessible.

When the PROCESS_CUBES job is run in debug mode, you will see calls and responses to the sisense api/elasticubes/servers/YOURSERVER/status?q=CubeName. Status codes 1 mean stopped and 2 means running. Other status codes like 514 indicate that the cube is currently processing or being built.