Product:

Cognos TM1 10.1.1 Perspective

PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7101.108-0

Windows 2008 R2 server

Microsoft Office 2010 32 bit  version 14.0.6023.1000

Symptom:

When you start TM1 perspective on a new computer you get a error message, and can not load TM1 perspective into Microsoft Excel 2010.

Error Message:

Could not load an object because it is not available on this machine.

Compile error in hidden module: MenuFuncs.

This error commonly occurs when code is incompatible with the version, platform, or architecture of this application. Click “Help” for information on how to correct this error.

 

Cause:

http://support.microsoft.com/kb/2597986

 

Solution:

Find the correct MSCOMCTL.OCX file from a different computer, where TM1 perspective is working with Microsoft Excel 2010.

 

Correct version is dated 2012-06-06 8:49 AM and 1046 KB in size.

File version 6.1.98.34

Product version 6.01.9834

 

On the computer where you have the problem.

Exit Excel

Go to folder %systemroot%\sysWOW64

Rename file mscomctl.ocx to mscomctl.ocx.old.txt

Copy the correct mscomctl.ocx fil to folder c:\windows\syswow64

Start a cmd prompt with “run as administrator”

Enter cd %systemroot%

Enter cd syswow64

Enter regsvr32 /u mscomctl.ocx

Click OK on dialog

Enter regsvr32  mscomctl.ocx

Click OK on dialog

 

Start Tm1 Perspective again and test.

Product:

IBM Cognos TM1 10.1.1

PLANANALYTICS_Update_version=PLANANALYTICS-AW64-ML-RTM-10.1.7101.108-0

Performance Modeler

Windows 2008 R2 server

Symptom:

When adding CAM users in Cognos TM1 Performance Modeler, you get a error message when you click on CANCEL in the add user dialog (this is the dialog showing the Cognos and namespace groups from the Cognos connection portal security tab).

Error message:

Internal Application Problem

There was an internal application problem. Try to save your work and exit the application. Check console for complete stack trace.

java.lang.NullPointerException

at

com.ibm.mdt.widgets.cube.actions.AddGroupAction.run(AddGroupAction.java:110)

at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)

 

Solution:

Instead of adding user by right click on the list of users inside Performance Modeler, use the icon in the toolbar at the top to add users, or add groups.

By using the icon for this function, it will work better.

The context menu can in some cases give errors.

Product:

TM1 10.1.1

Operations Console

Windows 2008 R2 server

 

Symptom:

Try to login to a Operations Console session, you have enter the following:

adminhost: localhost

servername: planning sample

group: cognos\admin

username: admin

password: apple

 

Error message:

The specified group does not exist on the server

 

Cause:

Operations Console may have problems with group names that contain a \ backslash or other characters. Recommendation to use simple group names like  MONITOR or ADMIN.

 

Solution:

Start TM1 Architect and add a group with name MONITOR

Add users to this group MONITOR that should be allowed to MONITOR the TM1 application.

Exit Architect.

 

Update the D:\Program Files\ibm\cognos\tm1_64\webapps\tm1operationsconsole\WEB-INF\configuration\ OpsConfig.xml file to reflect the change of group.

 

<?xml version=”1.0″ encoding=”UTF-8″?>

<Ops>

<AdminHost name=”localhost”>

<Server name = “Planning Sample”>

<Group>MONITOR</Group>

</Server>

</AdminHost>

<DashboardRefreshRate>5</DashboardRefreshRate>

<EnhancedStatusDetail>true</EnhancedStatusDetail>

</Ops>

 

Opsconfig.xml should look like above. Save the file.

You may need to change localhost with your servername, and planning sample if you want to use a different TM1 application as security container for Operation Console.

 

Go to Windows services and restart the “IBM Cognos TM1 Application Server” to make changes take affect.

Surf to http://localhost:9510/tm1operationsconsole/ to test the change.

Product:
Cognos TM1 10.1.1
Operations Console
Windows 2008 R2 Server

Symptom:
Can not login to Operations Console using a CAM id.

Problem:
An error occurred in authentication

Solution:
You must enter the namespace id before the username;
like this LDAP\kalle instead of entering kalle
You can check the namespace spelling inside TM1 Architect:
Login to TM1 application from Architect
Right click and select security – client/groups
Then in the left username field you see how you should write the username to operations console.
LDAP\kalle

LDAP is replaced by the Cognos BI namespace name you created in Cognos Configuration for BI.
kalle have to be replaced by your user name.

More information from IBM:
The current documentation on installing and using the Cognos TM1 Operations Console 10.1 does not explicitly state that CAM is not supported for authentication when logging on to the Operations Console. You must use native TM1 authentication to log on to the Operations Console.

However, though native TM1 authentication is required to log on to the Operations Console, the Operations Console can monitor any TM1 server that is configured to use CAM to manage user access.

Additionally, though you can monitor a TM1 server that is configured to use CAM, you cannot use the Operations Console to kill a thread for such a server. The Operations Console allows you to kill threads only for servers that use native TM1 authentication.

“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(“xxxxx.com:x:xxxxxxEveryone”), 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.”

http://www-01.ibm.com/support/docview.wss?uid=swg27034273

http://www-01.ibm.com/support/docview.wss?uid=swg21610251

http://www-01.ibm.com/support/docview.wss?uid=swg21620207

Product:

Cognos TM1 10.1.1

Microsoft Windows 2008 R2 Server

 

Symptom:

How do I get the TM1 Operations Console to work on my TM1 server ?

 

Solution:

Install cognos TM1 64 version (tm1_64b_10.1.1_win_ml.tar) to default folder, including the operations console to get the war file in place.

 

Do the Configuration of Cognos Configuration to test the TM1 installation.

 

Stop the TM1 Admin services and TM1 applications services.

 

Start CMD (commando prompt)

Go to C: drive.

Enter

cd c:\Program Files\IBM\cognos\tm1_64\bin64\jre\6.0\bin

to move to that folder.

 

Note:  On 64-bit computers, be sure to add the certificates to the bin64 folder.

 

Enter this to register the keystore:

keytool -import -file “C:\Program Files\IBM\cognos\tm1_64\bin64\ssl\applixca.pem” -keystore “C:\Program Files\IBM\cognos\tm1_64\bin64\jre\6.0\lib\security\cacerts” -storepass “changeit”

 

Start the TM1 Admin services and TM1 applications services.

 

Start TM1 Architect

Go into a TM1 application (  planning sample )

Double-click on TM1 application to login.

Right-click and select security  – clients/groups

Click “Add new group” from the groups menu.

Enter name of group to be: Monitor.

Click OK

Mark the users that should be able to run Operations Console to be part of this group; Monitor.

At least add the ADMIN user to the Monitor group.

Click OK and exit architect.

 

The IBM Cognos TM1 Operations Console uses an .xml file to identify the user

group, server, and admin host to use. Before you can run the Operations

Console, you need to update this configuration file with the information that

describes your new monitoring group.

 

Start Windows Explorer

Go to folder C:\Program Files\ibm\cognos\tm1_64\webapps\tm1operationsconsole\WEB-INF\configuration.

Open OpsConfig.xml in Notepad.

You want to add the admin host, TM1 server, and security group names to this

file. Enter values like this;

 

<?xml version=”1.0″ encoding=”UTF-8″?>

<ops>

<adminhost name=”localhost”>

<server name = “planning sample”>

<group>Monitor</group>

</server>

</adminhost>

<DashboardRefreshRate>5</DashboardRefreshRate>

<EnhancedStatusDetail>true</EnhancedStatusDetail>

</ops>

 

Save the file after your changes.

 

Start the TMI Operations Console from the URL:

http://serverName:portNumber/tm1operationsconsole

 

serverName: computer where you have the TM1

Operations Console and Web application server

installed.

portNumber: port number where your Web

application server is running. Apache Tomcat

provided with the IBM Cognos TM1 installation

uses the default port number 9510.

 

If you start operations console direct on the TM1 server you should enter like this:

http://localhost:9510/tm1operationsconsole/

 

From the log in dialog enter values for

Adminhost:       localhost

Servername:      planning sample

Group:     Monitor

Username:          admin

Password:         apple

 

Click Log in.

 

More information

http://pic.dhe.ibm.com/infocenter/ctm1/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.tm1_inst.10.1.1.doc%2Ft_tm1_inst_installingopsconcole.html

Product:

Cognos TM1 10.1

Windows 2008 R2 Server

Symptom:

TM1 architect show dialogs and error message in local language.

Want it to be in English instead.

Cause:

TM1 Architect will check the users windows setting for region and use that language if it is supported by the program.

Solution:

You can force TM1 Architect to use English by entering  the line

Language = ENG

in the file c:\users\username\AppData\Roaming\Applix\TM1\tm1p.ini

Stop TM1 Architect

Open TM1P.INI in notepad

Add the line

Language = ENG

Save the file

Start TM1 Architect

Now the menus should be in English

The tm1p.ini is create from this file c:\programdata\applix\tm1\tm1p.ini
when a user log in to that server the first time. Add Language = ENG to above file to ensure that new users also get TM1 architect menus in English.

Other language is possible;

http://pic.dhe.ibm.com/infocenter/ctm1/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.ba.cognos.tm1_inst.10.1.0.doc%2Fc_tm1_inst_tm1languageconfiguration.html

The following table summarizes the language codes for the supported languages in IBM® Cognos® TM1®.

Language	Code
Brazilian Portuguese	bra
Croatian	hry
Czech	csy
Chinese (Simplified)	sch
Chinese (Traditional)	tch
Danish	dan
German	deu
Spanish	esp
Finnish	fin
French	fra
Hungarian	hun
Italian	ita
Japanese	jpn
Kazakh	kaz
Korean	kor
Norwegian	nor
Polish	pol
Romanian	rom
Russian	rus
Swedish	sve
Turkish	trk

 

When you add the line Language = ENG to TM1S.CFG file, the error message in the tm1server.log will be in English. But you must update the TM1p.ini file to change language in TM1 Architect.

 

• • The server checks the Language parameter in the Tm1s.cfg configuration file. If a valid language code is configured, that language is used for the server messages.
  • The client components check the Language parameter in the Tm1p.ini configuration file. If a valid language code is configured, that language is used in the user interface.
• If the language configured in any of the above does not match a valid supported language, English is used.

https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_tm1_inst_tm1languageconfiguration.html

If no Language =  parameter is set, then TM1 will use the Windows regional setting for that user running the program.

 

Product:

Cognos TM1 9.5.2

Windows XP

Symptom:

TM1 architect is started on the Windows XP client, but disappears then.

If you start TM1 architect on the server, it starts and show the available TM1 servers.

Error message in windows event log:

Description:

Generate Activation Context failed for C:\Program Files\Cognos\TM1\bin\tm1p.dll. Reference error message: The operation completed successfully.

 

Description:

Syntax error in manifest or policy file “C:\WINDOWS\WinSxS\Policies\x86_Policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773\8.0.50727.762.policy” on line 12. The root or application manifest contains the noInherit element but the dependent assembly manifest does not contain the noInheritable element. Application manifests which contain the noInherit element may only depend on assemblies which are noInheritable.

 

Cause:

The client default settings are stored in this folder:

C:\Documents and Settings\All Users\Application Data\Applix\TM1\tm1p.ini

These settings are copied to new users who start TM1 Architect on the client computer.

 

TM1P.INI contains:

 

[TM1]

UseHttpConnector=F

HttpProxyServerPort=

IntegratedLogin=F

UseHttpProxyServer=

#AllowImportCAMClients=T

DataBaseDirectory=C:\Program Files\Cognos\TM1\Custom\TM1Data\PData

#CognosGatewayURI= http://FRANGOPC/cognos8/cgi-bin/cognos.cgi

AdvancedRulesEditor=F

HttpConnectorUrl=http://youraddress.com/tm1HttpProxy

HttpProxyServerHost=

AdminHost=ServerTM1

Language=ENG

UseExcelCubeViewer=F

InProcessLocalServer=T

ConnectLocalAtStartup=F

LocalServerNetworkProtocol=tcp

 

Possible Solution:

Ensure the Adminhost value is the correct Tm1 servername.

 

Recommendation is also to set AdvancedRulesEditor to true so it will show the new editor for the users, this editor demands that you have NET framework 3.5 installed on the client computer.

AdvancedRulesEditor=T

Ensure that the client can read this file from the hard disc.

 

If there is on a Microsoft Windows XP computer you need to have installed Service Pack 2.

Product:

Cognos TM1 10.1.1  (this will work with other versions of TM1 also)

Microsoft Windows 2008 R2 server

Problem:

How create a dump file of TM1 application crash and send it to Cognos Support ?

Solution:

In Windows 2008 you can change registry values to active the creation of a complete dump file, that you can then send to Cognos supports FTP site.

 

Login to your TM1 server as administrator

Create a folder to save the dump files in e.g. d:\crashdumps, need free space equal to size of TM1 application in memory (RAM).

Start Registry editor by enter regedit on the RUN line from the start menu.

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft

\Windows\Windows Error Reporting\

Right click and select create a new key under Windows Error Reporting

Create the key Localdumps, if it does not already exists.

Right click and select create a new key under Windows Error Reporting\Localdumps.

Name the key tm1sd.exe

Right click on tm1sd.exe and select new – expandable string value.

Name it DumpFolder

Double click on it and enter the value of the folder e.g. d:\crashdumps

Right click on tm1sd.exe again and create a new DWORD 32bit value

Name it DumpType

Double click on it and enter the value of 2 for a full dump file.

Exit RegEdit program to save the changes.

 

To kill a TM1 process in task manager will not trigger the dump file, so you need to test the

dump create process in a different way.

This registry changes will work on both 32 and 64 bit versions of applications.

 

A other way to create the values in registry to active dumps for TM1 applications are to;

Copy and paste the following command into the Administrator command prompt window, and then press Enter to execute the command:

 

reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\tm1sd.exe” /v DumpType /t REG_DWORD /d “2” /f

 

You should see a message like “The operation completed successfully.” after completion of the command.

 

Paste this line in the dos prompt to set the folder to store the dump file:

reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\tm1sd.exe”  /v DumpFolder /t REG_EXPAND_SZ /d “d:\crashdumps” /f

 

You should see a message like “The operation completed successfully.” after completion of the command.

 

Collect also the listed log files and send to Cognos Support.

The Tm1server.log file. This file is located in the TM1 server data directory.

All TM1ProcessError.log files generated during the TM1 server session that crashed.  Check the name of the file for date and time when it was created. File names are assigned using the convention TM1ProcessError_time stamp_process name.log.

All TM1ProcessError.log files are stored in the TM1 server data directory.

 

Attach the cmplst.txt file from the C:\Program Files\ibm\cognos\tm1_64 folder, found in folder where you have installed your TM1 program.

 

Compress all the files with 7zip.org before you try to send it to Cognos Support.

Name the zip file with the PMR number you have got from Cognos Support.

E.g. cognospmrxxxxxxxxxxx.zip  (do not enter point or dashes in name)

 

You can upload files to the IBM® FTP server from a Web browser.

1. Go to https://testcase.boulder.ibm.com.
2. Log in with user name anonymous. No password is required for an anonymous login.
3. Click the toibm folder.
4. Click the im folder.
5. Click Browse and navigate to the file you want to upload.
6. Click Upload file (binary).

 

More information:

http://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx

Product:

Cognos TM1

Cognos BI

Windows 2008 R2 server

Symptom:

User is unable to deploy a Contributor app due to an error. Can not publish any application from the TM1 application web design in Tm1 performance modeler page to Cognos connection.

Error message:

An error occurred while creating Cognos objects: CAF

Det uppstog ett fel under uppdatering av cognos objektet: cmHeaderFault

 

Possible Solution:

To be able to publish to Cognos Connection you need rights there. If everyone is part of the system administrator group, then there often are no issues. But after you secure the Cognos connection portal, you need to add the users who should publish items to the Cognos connection to the group system administrators or group authors.

 

Surf to Cognos Connection

Go to Administration of Cognos Content

Click on security tab

Click on Cognos namespace

Go to system administrators group

Click more

Click set members

Click add

Click you domain namespace

Click search

Enter the name of the person who uses the tm1 contributor

Click search

When you find the person, select person and click the arrow to add him to the group

Click OK

Click OK

Test again to publish from Tm1 application web.

Product:

Cognos TM1 10.1.1

Windows 7

 

Symptom:

Error when you try to start performance modeler from application portal on a Windows 7 computer. You have installed the complete TM1 10.1.1 (tm1_64b_10.1.1_win_ml.tar ) 64 bit version on you local laptop.

 

Error message:

0% of cogrcpservlet from localhost completed

file download

Do you want to save this file, or find a program online to open it ?

Name: provagent.cogrcp_modeler

Type: unknown file type, 780 bytes

From: localhost

 

When you try to install PerformanceModeler.msi from file you get this error:

Accessing the feature…

Click OK to try again, or enter an alternate path to a folder containing the installation package ‘PerformanceModeler[1].msi’ in the box below.

 

The file ‘c:\program files\ibm\cognos\tm1_64\webapps\rcp_installs\performanceModeler.msi’ is not a valid installation package for the product IBM Cognos Performance Modeler.  Try to find the installation package ‘PerformanceModeler[1].msi’ in a folder from which you can install IBM Cognos Performance Modeler

Possible Solution:

Cognos TM1 is set to use only IP v4 from inside Cognos Configuration by default.

But you Windows 7 computer is setup to use IP v6. This will make it difficult for TM1 to find localhost or the computer name when it try to access it in different parts.

 

If you get this response when you use ping, then the computer is using IP v6.

C:\Users\roger>ping localhost  Pinging computername [::1] with 32 bytes of data:Reply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1msReply from ::1: time<1ms Ping statistics for ::1:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

Recommend to use the IP v4 setting in Cognos Configuration, if you do not have any other program on your computer who demand the use of IP v6.

 

Disable the use of IP v6 on all network connections to you computer.

Go to Windows Control Panel

Go to Network and Sharing Center

Click on Change adapter settings, in the left pane

Right click on “Local Area Connection” and select properties

Untick “Internet Protocol Version 6 (TCP/IPv6)” from the networking tab.

Click OK

Repate above for all adapters, including “Wireless Network Connection”.

 

Update you host file to ensure that 127.0.0.1 is used for localhost.

Go to C:\Windows\System32\drivers\etc folder

Open HOST file in notepad and find below rows:

 

# localhost name resolution is handled within DNS itself.

#          127.0.0.1       localhost

#          ::1             localhost

 

Remove the # in front of localhost line to get this result:

 

# localhost name resolution is handled within DNS itself.

127.0.0.1       localhost

#          ::1             localhost

 

Save the HOST file and exit notepad.

Remove previous installed IBM Cognos Performance Modeler from add/remove programs in windows control panel.

Remove previous saved performanceModeler.msi files from you download folder.

Restart the computer to ensure it get a IP v4 address.

Run ipconfig /flushdns in CMD prompt, to ensure you do not have old IP v6 address in cache.

Restart the IBM Cognos Application server service, to ensure it understand the change of IP.

Surf to Cognos TM1 Applications portal and start Performance modeler again.

( surf to http://localhost:9510/pmpsvc )

Install it and test the TM1 application again.

 

Note: that all TM1 applications (services) that you are going to use in Cognos TM1 applications portal must use the same authentication mode. Recommend IntegratedSecurityMode=1

Also the ADMIN user must have the same password in all the TM1 applications.