Reasons why Pulse can’t connect to an instance

This article explains the different reasons why Pulse can’t connect to a TM1 instance.

If Pulse can’t connect to a TM1 instance, the Pulse Live Monitor is going to hide some components and it will show the warning message below:

In the example above, the TM1 instance CRM_DEV is still Running, the Pulse Monitor can see the status from the Windows Service but the Pulse Application Server can’t connect via the TM1 REST API.

The main reasons why the Pulse Application Server can’t connect to a TM1 instance are:

• The TM1 REST API is not enabled

• The TM1 user credentials are not valid

• The TM1 server’s REST API is not responding

• The TM1 server’s REST API Port is not reachable

The following article explains how to check if the TM1 REST API is enabled:

• Enabling the TM1 REST API

To connect to the TM1 instance via the TM1 REST API, Pulse is going to authenticate using the TM1 user credentials defined in the Pulse instance settings.

To check if the credentials are correct, go to Administration > Instance Settings and click the Save button as below:

If you see a green tick box, it means that Pulse was able to authenticate with a TM1 Admin user.

If you are getting a red cross, you should reenter the TM1 user credentials. If you are using CAM security, check the CAM Namespace (it is case sensitive).