Troubleshooting
Problem
Collect troubleshooting data for problems with IBM Cognos TM1 - determining the build numbers.
Resolving The Problem
|
Instructions for determining the TM1 and related products build numbers
Understanding the Build Number String |
All TM1 build strings are formatted as A.B.CDDEE.xxxxx.
- A is the first section (usually 1 digit)
- B is the second section (usually 1 digit)
- CDDEE is the third section (always 5 digits)
- xxxxx is the fourth section (usually 4 or 5 digits, but can be anywhere between 1 - 5 digits)
Example 9.4.10304.3790 = 9.4 Maintenance Release 1 Fix Pack 3 Hot Fix 4 build 3790 9.5.10000.5424 = 9.5 Refresh Pack 1 build 5424 |
Find the Build Number for Core TM1 |
Problems with the Common Location for Build Number String |
In the past, the most common location to look for the build string was on the server application itself, however, we have seen problems in the past where the third octet digits get truncated when there are leading zeros. This has been identified as a Microsoft OS issue, and as such is not under our control.
DO NOT log a PMR regarding this known issue.
If the third octet is not displaying 5 digits, the field has been truncated. Follow the steps below in Steps to Get the Build Number String to get the correct build number string.
Recommended Location For Build Number String |
The recommended location to find the TM1 build number string is to look at the file properties.
- For Perspective or Architect - look in the tm1api.dll
- For TM1 server - look in tm1s.exe or tm1sd.exe
Note: if you have taken a Hot Fix, you may have a different version strings for these two files. Use the file for the type of issue you are logging.
- For Architect issue - tm1api.dll
- For Tm1 server issue - tm1s.exe or tm1sd.exe
Steps to Get the Build Number String |
Method 1 - Using File Properties |
1. Select a file.
2. Right click on toolbar menuitem File > Properties.
3. Click on the Version tab.
4. Under item name, highlight Product Version.
5. The value shown is the correct build number string.
Method 2 - Using Windows Explorer |
1. In Windows Explorer, navigate to the bin directory.
2. Click toolbar menuitem View > Choose Details...
3. Scroll down the list and tick the box Product Version.
4. Click OK.
5. A new column is displayed showing the product version information.
Find the Build Number for Contributor (Planning Service). |
When you have a TM1 issue related to Contributor, you need to report the Planning Service build number. |
1. Determine the correct TM1 build number as outlined in the section Find the Build Number for Core TM1 .
2. Match the TM1 build number in the table below to determine the corresponding Planning Service build number.
TM1 Version | Planning Service build |
9.5 (9.5.00000.65077) | 8.4.5165.0 |
9.5 SRP (9.5.00100.2380) | 8.4.5165.0 |
9.5.1 (9.5.10000.5424) | 8.4.6095.0 |
Find the Build Number for CQ |
When you have a TM1 issue related to Cognos Query (CQ), you need to report the CQ build number.
1. Determine the correct TM1 build number as outlined in the section Find the Build Number for Core TM1 .
2. The CQ version is equal to the first two octets in the TM1 build number string.
3. The CQ build number is equal to the third and fourth octet in the TM1 build number string.
Example For TM1 build number string 9.5.10000.5424 The CQ build number is 10000.5424 |
If you are unsure of the correct build number for a specific TM1 release, please refer to the table below in section Table of Released TM1 build numbers .
Find the Build Number for TM1 Package Connector (TM1 9.5.1 and up) |
When you have a TM1 issue related to TM1 Package Connector, you need to report the Package Connector build number.
1. Determine the correct TM1 build number as outlined in the section Find the Build Number for Core TM1.
2. Go to the directory <TM1 Package Connector Installation Location>\vers.
3. Look for a file with the name cogtr_tm1integration_LL-win32-app-A.B.CCCC.xxx-inst.ver
- LL = Language version (i.e., en, de, ln …)
- A.B = Version
- CCCC.xxx = Build number
Example For file cogtr_tm1integration_en-win32-app-8.4.6013.183-inst.ver, the TM1 Package Connector build number string is 8.4.6013.183 |
Submit MustGather data to IBM Technical Support |
To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:
1. IBM Support Assistant (ISA)
2. Service Request (SR)
3. FTP to the Enhanced Customer Data Repository (ECuRep)
For information about using each of these services, see Exchanging information with IBM Technical Support.
Collect MustGather data for related products |
MustGather: Read first for Cognos Now!
MustGather: Read first for Cognos Planning
MustGather: Read first for Cognos Software Development Kit (SDK)
MustGather: Read first for Cognos TM1
[{"Product":{"code":"SS9RXT","label":"Cognos TM1"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"TM1","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.5.2;10.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Product Synonym
Cognos TM1
Was this topic helpful?
Document Information
Modified date:
24 February 2020
UID
swg21457063