Troubleshooting Application Availability

Nick Reilingh — Mon, 06 Apr 2020 05:55:22 GMT

Current Revision posted to Wiki by Nick Reilingh on 4/6/2020 5:55:22 AM

Some procedures and information for issues where Tessitura Analytics does not load inside the Tessitura Application.

Could not connect to Tessitura Analytics: The remote server returned an error: (400) Bad Request. Please contact your system administrator.

The Analytics services may not be running. Start any service starting with Sisense.* with a startup type of Automatic. Also start ElastiCubeManagementService.

Try accessing the Sisense application outside of TessituraWeb or Tessitura Client. This can be done by manually accessing <server:port>/app/account#/login

If SiSense is running, then the issue has to do with the way Tessitura connects to it.

Consider verifying that the TessituraWeb Web.config appSettings configuration key for analyticsUrl is correct and has the correct port number.

Inspect TessituraWeb logs:

Could not retrieve access token from Sisense.

Try switching nlog.config for TessituraWeb to log Trace level instead of Error — you will see the GET HTTP request that is being attempted.

Verify that the HTTP request URL is valid — you should be able to access it in a browser. Be mindful of port numbers.

Data cube availability:

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

Most likely scenario for this error appearing in the Analytics application is that the ElastiCubeManagementService is not running.

Or, just log in to the Analytics application as an administrator, go to the Admin settings for Data Sources, and start all of the cubes.

Tags: Tessitura Analytics

Troubleshooting Application Availability

Nick Reilingh — Sun, 02 Feb 2020 00:17:08 GMT

Revision 4 posted to Wiki by Nick Reilingh on 2/2/2020 12:17:08 AM

Some procedures and information for issues where Tessitura Analytics does not load inside the Tessitura Application.

Could not connect to Tessitura Analytics: The remote server returned an error: (400) Bad Request. Please contact your system administrator.

The Analytics services may not be running. Start any service starting with Sisense.* with a startup type of Automatic. Also start ElastiCubeManagementService.

Try accessing the Sisense application outside of TessituraWeb or Tessitura Client. This can be done by manually accessing <server:port>/app/account#/login

If SiSense is running, then the issue has to do with the way Tessitura connects to it.

Inspect TessituraWeb logs:

Could not retrieve access token from Sisense.

Try switching nlog.config for TessituraWeb to log Trace level instead of Error — you will see the GET HTTP request that is being attempted.

Verify that the HTTP request URL is valid — you should be able to access it in a browser. Be mindful of port numbers.

Data cube availability:

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

Most likely scenario for this error appearing in the Analytics application is that the ElastiCubeManagementService is not running.

Tags: Tessitura Analytics

Troubleshooting Application Availability

Nick Reilingh — Fri, 31 Jan 2020 21:07:53 GMT

Revision 3 posted to Wiki by Nick Reilingh on 1/31/2020 9:07:53 PM

Some procedures and information for issues where Tessitura Analytics does not load inside the Tessitura Application.

Could not connect to Tessitura Analytics: The remote server returned an error: (400) Bad Request. Please contact your system administrator.

The Analytics services may not be running. Start any service starting with Sisense.* with a startup type of Automatic. Also start ElastiCubeManagementService.

Try accessing the Sisense application outside of TessituraWeb or Tessitura Client. This can be done by manually accessing <server:port>/app/account#/login

If SiSense is running, then the issue has to do with the way Tessitura connects to it.

Inspect TessituraWeb logs:

Could not retrieve access token from Sisense.

Try switching nlog.config for TessituraWeb to log Trace level instead of Error — you will see the GET HTTP request that is being attempted.

Verify that the HTTP request URL is valid — you should be able to access it in a browser. Be mindful of port numbers.

Tags: Tessitura Analytics

Troubleshooting Application Availability

Nick Reilingh — Thu, 30 Jan 2020 23:14:26 GMT

Revision 2 posted to Wiki by Nick Reilingh on 1/30/2020 11:14:26 PM

Some procedures and information for issues where Tessitura Analytics does not load inside the Tessitura Application.

Could not connect to Tessitura Analytics: The remote server returned an error: (400) Bad Request. Please contact your system administrator.

The Analytics services may not be running. Start any Sisense with a startup type of Automatic.

Try accessing the Sisense application outside of TessituraWeb or Tessitura Client. This can be done by manually accessing <server:port>/app/account#/login

If SiSense is running, then the issue has to do with the way Tessitura connects to it.

Inspect TessituraWeb logs:

Could not retrieve access token from Sisense.

Try switching nlog.config for TessituraWeb to log Trace level instead of Error — you will see the GET HTTP request that is being attempted.

Verify that the HTTP request URL is valid — you should be able to access it in a browser. Be mindful of port numbers.

Tags: Tessitura Analytics

Troubleshooting Application Availability

Nick Reilingh — Thu, 30 Jan 2020 21:03:48 GMT

Revision 1 posted to Wiki by Nick Reilingh on 1/30/2020 9:03:48 PM

Some procedures and information for issues where Tessitura Analytics does not load inside the Tessitura Application.

Could not connect to Tessitura Analytics: The remote server returned an error: (400) Bad Request. Please contact your system administrator.

The Analytics services may not be running. Start any Sisense with a startup type of Automatic.

Try accessing the Sisense application outside of TessituraWeb or Tessitura Client. This can be done by manually accessing <server:port>/app/account#/login

If SiSense is running, then the issue has to do with the way Tessitura connects to it.

Tags: Tessitura Analytics