IBM Support

Unable to log in to Operations Console - may get two different errors.



A user attempting to log in to the TM1 Operations Console may encounter errors.


"An error occured in authentication"
"The specified group does not exist on the server"

Resolving The Problem

For the error "An error occured in authentication", if the user does not have enough free connections this error will be generated. Operations Console (OpsConsole) takes up an extra port, so if the user only has, let's say 2 connections allowed, and they are already logged in to Perspectives and also to TM1Web, then their 2 connections are used up so they will get this error when attempting to log in to OpsConsole. Check the MaximumPorts for the user in the }ClientProperties cube to verify if this is the problem. If not practical to increase the maximum number of ports, then the user will need to log out of one of the other applications in order to log into OpsConsole.

That error can also be caused if the user is not using the correct namespace. This should be the Namespace ID that is noted in Configuration Manager, not the name of the namespace that is outside of Cognos BI. For example, if there is an AD namespace (outside of Cognos) and the Namespace ID is Cognos, the login to use would be Cognos\username (Cognos\jdoe) not AD\username.

For "The specified group does not exist on the server", this would only be an issue if using CAM authentication. There is a defect where this error occurs if the group being used is the alias for the group rather than the actual name of the group - doing this will generate this error.

For example, if the group Cognos\Everyone (the alias name) is used in the OpsConfig.xml and then used to attempt to log in to OpsConsole, this error will be encountered. Instead, it is necessary to use CAMID(""), which should not generate the error. The defect asks for this to function the same as the username, which requires the alias and not the actual name (just the opposite). At this writing there is no target date as to when this may be fixed, and no APAR was generated because this was detected in-house, not through a customer. The workaround suggested should allow functionality.

For TM1 10.2:

If using a group created in CAM for example Cognos\Monitor, then in the pmhub/pm/admin the default group name should be entered as CAMID(":Monitor").

[{"Product":{"code":"SS9RXT","label":"Cognos TM1"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"TM1 Operations Console","Platform":[{"code":"PF033","label":"Windows"}],"Version":"10.1.0;10.1.1;10.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2018