/
Reasons Why Pulse Can't Connect to a TM1 Instance

Reasons Why Pulse Can't Connect to a TM1 Instance

Reasons Why Pulse Can't Connect to a TM1 Instance

This article covers the most common reasons why Pulse fails to connect to a TM1 instance and how to resolve each one.

Reason 1 — TM1 REST API Is Not Enabled

Pulse v6+ connects exclusively via the TM1 REST API. If the REST API is not enabled on the TM1 instance, Pulse cannot connect.

Resolution:
Add or verify the following in tm1s.cfg:

HTTPPortNumber=8010

Restart the TM1 instance after making this change.

Reason 2 — REST API Port Is Blocked by a Firewall

Even with the REST API enabled, a firewall may be blocking the port between the Pulse server and the TM1 server.

Resolution:

  • From the Pulse server, test connectivity: http://<TM1Server>:8010/api/v1/$metadata

  • If unreachable, open the REST API port in the firewall rules between the two servers.

Reason 3 — Incorrect Credentials in Pulse Instance Settings

The username or password configured in Pulse Instance Settings may be wrong or expired.

Resolution:

  1. Go to Administration → Instance Settings.

  2. Select the instance and verify the User Name and Password.

  3. For CAM-secured instances, also verify the CAM Namespace (case-sensitive).

  4. Click Save and check connectivity.

Reason 4 — The TM1 Instance Is Not Running

Pulse cannot connect to a TM1 instance that is stopped or starting up.

Resolution:

  • Verify the TM1 service is running via Windows Services on the TM1 server.

  • Check TM1 logs for startup errors.

Reason 5 — Invalid SSL Certificate

If TM1 uses HTTPS with a self-signed or internally-signed certificate, Pulse may reject the connection.

Resolution:
Import the TM1 server's certificate into the Pulse Java truststore. See Considerations When Enabling SSL to TM1 with Custom Certificates for steps.

Reason 6 — The User Account Is Not a TM1 Admin

Pulse requires a TM1 Admin account to connect. Non-admin accounts will be rejected.

Resolution:
Ensure the account configured in Pulse Instance Settings has ADMIN security in TM1 (}ElementAttributes_}Clients cube or TM1 security cube).

Reason 7 — CAM Passport Expired (Security Mode 3 Only)

For TM1 instances using CAM security, an expired CAM Passport prevents connection.

Resolution:

  • Reduce CAMKeepAliveInterval in Pulse.cfg to renew the passport more frequently.

  • Verify the Cognos Dispatcher URL is accessible from the Pulse server.

Reason 8 — Account Locked in TM1

TM1 may lock an account after repeated failed login attempts.

Resolution:
Unlock the account in TM1 security or restart the TM1 instance to clear the lock.

Diagnostic Tips

  • Check pulse.log for specific error messages related to the instance connection attempt.

  • Enable the Pulse REST API Tool (EnableRESTAPITool = true in Pulse.cfg) to send test requests directly to the TM1 instance from the Pulse interface.