This document is intended to provide a troubleshooting methodology which incorporates publicly available utilities to diagnose and resolve an issue identified within a specific use case. The use case will be presented as a scenario where an IBM Business Analytics Support Analyst is working with a customer to diagnose and solve a particular issue.
The utilities mentioned in this document can be found at http://www.ibm.com/support/docview.wss?uid=swg24028107.
Although the troubleshooting approach outlined is not IBM Cognos TM1 version specific, some of the diagnostic utilities used are. The version of the utility to be downloaded may be specific to the IBM Cognos TM1 version that is experiencing the issue. Please check the compatibility of the version in the Document Information section of the link provided above.
Use Case Description
A customer calls IBM Business Analytics Support and indicates that they have deployed IBM Cognos TM1 as a part of an IBM Cognos Controller FAP (Financial Analytics Publisher) implementation. The customer has added the IBM Cognos BI namespace user CorpNS\Administrator to the list of users in IBM Cognos TM1 (CorpNS is the IBM Cognos BI namespace ID). The customer launches TM1 Architect and inside the Server Explorer they double-click on the TM1 Server they want to explore. The customer is prompted for a username and password, enters the credentials for the IBM Cognos BI namespace user and they receive the error message Client name does not exist on the server.
Gathering Information for this Use Case
The Support Analyst asks the customer about the operating system used in the environment and what machine the TM1 Architect client is being run on. The customer indicates that the TM1 components are installed on a single server and the server is running a Microsoft Windows Server 2003 SP2 operating system.
The Support Analyst then requests that the customer download and run the IBM Cognos TM1 Diagnostic tool. This tool is located at the following URL:
The diagnostic tool is run on the IBM Cognos TM1 server and by default, it will save its output files under the IBM Cognos TM1 Server install location at .\Temp\IBMCognos_Diagnostic\IBMCognos_TM1\TM1_<Date & Timestamp>.
The IBM Cognos TM1 Diagnostic Tool will gather the following information from the customer’s IBM Cognos TM1 environment:
- Operating System type and version
- Total physical memory
- IBM Cognos TM1 processes
- Software version information for Microsoft Excel and IBM Lotus Notes
- License file
- User configuration files
- Admin server logs
- IBM Cognos TM1 Microsoft Excel service logs
- Database directory files
- IBM Cognos BI files
- Web configuration files
- User specified files
The customer compresses and sends the output files created by the diagnostic tool to the Support Analyst for review.
Indicating Considerations and Precautions
The Support Analyst reviews the output files from the diagnostic tool and while looking in the IBMCognos_Planning_FilesCopied folder, notices that the tm1s.cfg file contains the line IntegratedSecurityMode=4.
The Support Analyst informs the customer that in order to use the IBM Cognos Controller FAP functionality with IBM Cognos TM1, IntegratedSecurityMode must be set to a value of 5. This is because FAP publishes security to native TM1 Groups and hence a combination of IBM Cognos BI CAM users and native TM1 Groups are required.
The Support Analyst offers a suggestion on how to remedy the situation.
- The customer should navigate to the tm1s.cfg file for the IBM Cognos TM1 server they wish to integrate with FAP.
- Open the tm1s.cfg file in a text editor such as Notepad.
- Modify the setting for IntegratedSecurityMode to a value of 5.
- Save the file.
- Restart the Windows service “TM1 Admin Server”.
- Test the IBM Cognos BI namespace logon in TM1 Architect.
Resolving the Issue
After the customer followed the recommended steps provided by the Support Analyst, the customer is now able to successfully logon to the IBM Cognos TM1 Server being used in the IBM Cognos Controller FAP process with the credentials of the IBM Cognos BI namespace user.