Cognos TM1 10.1.1
Microsoft Windows 2012 server

Error when saving in TM1 Cognos Configuration, after adding a new TM1 server.

Error message:
[ ERROR ] The cryptography information was not generated.
[ ERROR ] CAM-CRP-1064 Unable to process the PKCS #7 data because of an internal error. Unable to find the encryption certificate with alias ‘encryption’ in the keystore ‘D:/Program Files/ibm/cognos/tm1_64/configuration/encryptkeypair\jEncKeystore’.
The parameter named ‘User ID and password’ located in ‘TM1 Application Server’ is currently invalid.

Possible solution:
In the Cognos configuration, remove the TM1 server you are trying to add…or re-add.

This is for TM1 10.1.1
Then save the configuration in plain text.
Select File – Export to clear text file
Select a folder to save the file in, like d:\temp
Name the file to cogstartup_backup.xml
Stop the Cognos TM1 servers (including IBM Cognos TM1 Application Server) on that physical server.
Close the TM1 configuration.
Go to the following install folder: Driver_letter:\Program Files\ibm\cognos\tm1_64\configuration.
Rename the CSK, SIGNKEYPAIR, and ENCRYPTKEYPAIR folders (add _old after the name).
Rename the cogstartup.xml to cogstartup.xml.old
Copy the file d:\temp\cogstartup_backup.xml to folder \Program Files\ibm\cognos\tm1_64\configuration\
Rename cogstartup_backup.xml to cogstartup.xml
Open the Configuration tool.
Click save, to test that it works now.
This should allow the encryption files to be recreated.
Then add your TM1 server and save your settings.

Below how to update the keys for CA11 or PA2 Local:

Steps to regenerate the cryptographic keys are as follows:
1. Stop the running of your service in Cognos Configuration.

2. On the Content Manager computer, click ‘File > Export As’.

3. Choose ‘Yes’ at the prompt and save the file. For example, name it ‘backup.xml’ which will be stored in the c11\configuration folder.

4. Close Cognos Configuration.

5. On the Content Manager computer, create a backup of the following files and directories before moving them to a different, secure location (as during the cryptographic keys regeneration process they will be re-created):

The files are:

· c11/configuration/cogstartup.xml

· c11/configuration/caSerial

· c11/configuration/certs/CAMCrypto.status

· c11/configuration/certs/CAMKeystore

· c11/configuration/certs/CAMKeystore.lock

· c11/temp/cam/freshness
The directory is

· c11/configuration/csk

6. In the c11\configuration folder, rename ‘backup.xml’ to ‘cogstartup.xml’.

7. Open Cognos Configuration, save the configuration and start the services.

More Information

Cognos TM1 10.2.2
Windows 2012 R2 server

When try to login to TM1 Application web (pmpsvc) you get an error 500 message.
To surf to TM1WEB is works fine, and you can enter the TM1 application from TM1 architect.

Error message:
HTTP Status 500 –
type Exception report
message java.lang.NullPointerException
description The server encountered an internal error () that prevented it from fulfilling this request.
org.apache.jasper.JasperException: java.lang.NullPointerException

root cause

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.35 logs.
Apache Tomcat/6.0.35

On the TM1 server – stop the IBM Cognos TM1 Application server.
In windows explorer go to folder C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration\

Rename the file fpmsvc_config.xml to fpmsvc_config.xml.old
Rename the file to fpmsvc_config.xml
Start the IBM Cognos TM1 Application server.

Surf to http://localhost:9510/pmpsvc
And enter new TM1 applications to the server.

The file fpmsvc_config.xml can have been corrupt when you added a new TM1 instance.

IBM Cognos TM1 10.2.2
Microsoft Windows 2012 R2 Server
Sterling Integrator / Connect Direct

When calling a BAT file from a TM1 TI process, to call other program, to send files or other systems task.
You get not the result you wanted.
The BAT file works fine when run direct in DOS prompt, and then the job get done.
But when called from a TI process – there are no errors – but the job is not executed.

Example of TI code to call a BAT file:
SIpath = ‘C:\cdroot\processer\PW188\PW188.bat’;
ExecuteCommand ( SIpath, 0);

Possible solution:
On the Microsoft Windows 2012 server create this two folders (if they do not exist):

This folders are needed when you run Applications without a user logged in, in Windows.

Cognos TM1 10.2.2
Microsoft Windows 2012 R2 Server

Error message when surf to PMHUB at

Error message:
HTTP Status 500 – Servlet.init() for servlet equinoxbridgeservlet threw exception

Go to IBM Cognos Configuration for TM1 on the server.
Right click on TM1 Applications server and select STOP.
(You can also stop the IBM Cognos TM1 Application server from the Windows Services)
Delete folder pmhub at C:\Program Files\IBM\cognos\tm1_64\tomcat\work\Catalina\localhost\pmhub
Start TM1 Applications Server from inside IBM Cognos Configuration program.

This will recreate the application in TOMCAT and it will work again.

When you apply a FIX PACK to TM1 you must;
Stop the services.
Delete the config.ini file found in folder C:\Program Files\IBM\cognos\tm1_64\tomcat\work\Catalina\localhost\pmhub\eclipse\configuration\
Open Cognos Configuration and click SAVE.
Then you can start the TM1 services again.

Cognos Controller 10.2.1
Microsoft Windows 2008 R2 Server

In the list of data sources in Cognos Controller Configuration is more databases than in the list that is shown for the Cognos Controller user when he log on to the Cognos Controller application with his Cognos Controller client program.
The Controller Configuration program was started on server as a normal user.
When you start Controller Configuration program on the Windows server, you must start it with “Run as Administrator” to make it read the udl file from folder C:\Program Files\ibm\cognos\ccr_64\data\
Otherwise it will read the files from folder (and that can be different content):
C:\Users\%user%\AppData\Local\VirtualStore\Program Files\ibm\cognos\ccr_64\data\
The Controller services will only read the UDL files from the real C:\Program Files\ibm\cognos\ccr_64\data\ folder.
For security, New Windows OS forbids programs from writing to a variety of “sensitive” areas, among them the Windows folder and the Program Files folder. That includes all subfolders of Program Files, so this ban would be a hardship on older programs that store INI files or data files along with the program itself. To avoid disabling these programs, Windows OS lies to them. When they try to write to a banned location, it says “Sure, no problem!” but actually saves the data in a holding area called the Virtual Store. And when the program tries to read back the data it wrote, Windows Operating System slips in the data from the Virtual Store. The old program works fine, and other programs aren’t affected. A similar process handles programs that write to now-forbidden areas of the Registry.
Start – run command and enter %localappdata%\VirtualStore\ to see this users store.,2817,2325762,00.asp

Cognos Controller 10.2.1
Cognos TM1 10.2.2
Cognos BI 10.2.1

When publish from FAP program to TM1 cube with a Windows account you cannot login. But same account work when you access the TM1 cube from TM1 Architect.

TM1 and Controller are using CAM authentication against a BI server that is connected to the Company’s Active Directory.
The windows user account is in a different sub domain, than the TM1 and Controller servers, that are in an other sub domain in the Company Active Directory.
The FAP program cannot add sub domain information at login, as you can when you login to TM1 Architect.
If you use a Windows account that is in the same sub domain as the TM1 server, then the login works.

Check the name space connection string at the Cognos Configuration on the BI server. It should point to the top of the AD domain. If it point to a single AD server in the domain, that server cannot have access of the whole AD, and therefor miss the account. This because the sub domain info is not passed on from the FAP program.
Ensure that the AD connection point to the top of the domain, or to a load balancer in front of the AD servers.

Cognos Controller 10.2.1 fix pack 4
Windows 2012 R2 server

How install the Cognos Controller client on a Citrix server?

Fix pack downloaded from here

The IBM Cognos Controller client has the following 3rd party dependencies that needs to be satisfied:
1. Microsoft .net Framework 2.0SP2 (Present in Windows 7 and Windows Server 2008 R2 from start).
2. In the case where IBM Cognos Controller 10.2.1FP4 is installed to run as a local client on a Windows 10 client machine, it is required that Microsoft .NET Framework 3.5 Service Pack 1 is installed.
3. Acrobat Reader 9.3 or ‘X’.
4. Microsoft Excel 2007 or 2010, 2013, 2016.
5. Internet Explorer 8 or 9 or 10 or 11.

Copy the ccrlocalclient.msi file from folder c:\program files\ibm\cognos\ccr_64\webcontent\ccr
To a share you created for the installation.
In that share create a text file called EXCEL.EXE.CONFIG with this content:

     <supportedRuntime version=”v2.0.50727″/>
 <generatePublisherEvidence enabled=”false”/>                           

Then you can install Controller program from the share to the local computer.

The Controller client installation in Citrix is performed in a similar way to any local installation. There are however a few things to observe in the installation process as Controller is installed in a shared Citrix environment.

The installation steps in Citrix are as follows:
1. Copy the ‘Excel.exe.config’ file to the Office installation folder (needs to be in the same location as excel.exe.)
2. Set terminal server in install mode, at the command prompt type:

change user /install

3. Run the installation from the command-line (convenient way to supply configuration parameters):

msiexec /i ccrlocalclient.msi WSSURL= HELPURL=

4. Change back to execute mode:

change user /execute

5. Check the following registry key to ensure that not all users get the Controller Excel-link loaded from start:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\14.0\Excel\Options

There are different ways to check this, however, at the lowest level of this key there should not be an ‘OPEN’ value pointing to ‘/R \controllerxl.xll’ present!

In Internet Explorer the Cognos Controller server must be with the local sites to allow SSO login.
Go to Internet Options
Click Security tab
Select Local Intranet and click Sites button
Click Advanced button
Enter the url for the server ( ) and click ADD
Repeat for only server name ( http://servername ) and click ADD
Click Close
Click OK
Click OK

More information

Cognos Controller 10.2.1
Microsoft Windows 2012 R2
Microsoft SQL 2012 database in cluster setup

After the SQL cluster have rolled from Node A to Node B, then the first Controller user to login and run a standard report get an error message. He run the report a second time and it gives the same error message. The third time he run the report it works fine. Same issue for other reports.
Thereafter the reports work fine inside Cognos Controller, until next time you role the Cluster.

Error Message:
Ett fel inträffade när åtgärden ‘sqlStart’ status=’-121’ utfördes.
UDA-SQL0564 [Microsoft OLE DB Provdier for SQL Server][DBNETLIB]
General network error.

After you have shifted the SQL cluster, restart the Cognos BI service on the Application server.
Wait the 5 minutes it takes to restart the IBM Cognos service, and then login to Cognos Controller client and test again to run report. Now it should work the first time.

The Cognos BI service check if it have contact with the database, if it loose contact – it will not use that node for some time.

More information:

Cognos Controller 10.2.5130.56
Microsoft Windows 2012 R2 standard Server
Microsoft SQL 2008 R2 database Server 10.50.4000.0

One user cannot login in to Cognos Controller over VPN connection.
Single Sign On is active with use of CAM users. After select the database to use the error message appears.

Error message:
An error occurred while trying to access the server
Invalid URI: The hostname could not be parsed.

Change Cognos Controller Configuration to use FQDN instead of only hostname in all places.
Special at Client Distribution Server configuration, ensure that CASURL and WSSURL point to
instead of only servername.

Ensure that in Cognos BI Configuration Environment, that all references to localhost is replaced with the FQDN name of the servers.

Also on server and client ensure that server is part of local intranet.
Go to Windows Control panel.
Go to Internet Options.
Select Security tab.
Click on local Intranet.
Click on Sites button.
Click on Advance button.
Enter the * ( the company domain ) to the “add this website to the zone:” and click ADD button.
Now the server name or the last part of FQDN should show in the list of websites for Local Intranet.
Click OK to leave Internet Options.
Restart IE and try to surf to
– If it works without login message, then it is correct setup.

More information:

IBM Cognos Controller 10.2.1 fix pack 3
Microsoft Windows 2012 Server
Microsoft SQL database

How do I upgrade the Cognos Controller Client to newer fix pack?

If you get error message like this when you start Cognos Controller, then you are missing some step in the client upgrade.
“invalid database version.
This version of Controller requires database version: 949”

“System.Web.Services.Protocols.SoapException: Server was unable to process request. –>
“System.Exception: Invalid column name ‘ExcelFileFormat'”

On the Cognos Controller server you have to first install the Fix Pack.
You download the fix pack from IBM site:

On the Controller server stop all services and run the setup as of this instructions

Then you need to go into Cognos Configuration and click save, and start to start the Cognos BI services.
Then you need to go into Cognos Controller Configuration and on the databases, you need to click RUN. This will start the DBCONV program.
Here you click CONNECT to see the version of the database.
And if needed you click on UPGRADE, more info here:

Click OK and close.
After database is update and Cognos BI services is started, it is recommended that you restart the physical Windows server where you have Cognos Controller installed, to ensure update of COM packages.
You can run command: SHUTDOWN /R /T 10 /F
to force a restart of the server. (check with IT department before you do this).

Then you need to copy the CCRLOCALCLIENT.MSI file from server to a share so you can install the client on your workstation or citrix servers. You find the file in folder;
\program files\ibm\cognos\ccr_64\webcontent\ccr

If you have a packaged installation of the Cognos Controller client in you organization then this is the MSI file you need to give them from the server, to update there package to the new version of the Cognos Controller client.

On client workstation you need first uninstall the previous version of Cognos Controller from the add/remove program dialog in the Windows Control panel.
The New version of Cognos Controller will be listed in Control panel as:
Name: IBM Cognos Controller Local Client
Author: IBM
Size: 234 MB
Version: 10.2.5130.56

Run CCRLOCALCLIENT.MSI to install the Cognos Controller client program.
Click NEXT on “welcome to the IBM cognos Controller Local Client Setup Wizard”
Enter the WSSURL to be the same as the value you have in Cognos Controller Configuration on the Controller server, in tab “client distribution server configuration”. Normal it is a value like this:
And for the HelpURL you need to make a entry like this;
The servername you can find in the Controller Configuration on the Server itself.

Leave the cache dir blank (if you not have used it before).
Click NEXT

You get a new group on the start menu, called: IBM Cognos Controller
and under there you have icon for IBM Cognos Controller
click on it to start the program.

If you get error AAA-AUT-0013 when you try to login, then is the Windows user not added to the Cognos Controller program.
You need to add the windows user to the Cognos Connection group Controller users,
Surf to http://servername/ibmcognos
go to Administration page.
Select Security tab.
Click on Cognos
find the group Controller Users and click on MORE on the right side
click Set Members
click ADD on the right side
Click on your namespace name e.g. AD
Click search
Enter the name of the user, can be only lastname
Set Find text in: Name or description field
Click on Advance, to set:
Method: Contains the exact string
Type: Any
Scope: This folder and its subfolders
Click on SEARCH
if no match found with name try the user network login short name, e.g ROOS
Mark the user name and click on the arrow to add it the list of selected users.
Click OK
Click OK

Then you need to ask a Cognos Controller Administrator to login into the Cognos Controller client, and create an account for you windows user.
Select Create New: User
In the CAM user field. Click on the … to get a list of available users to add.
Select the user to ADD and click on the green icon.
Now the user name and email should be automatic populated inside Cognos Controller.
Ensure the user have the needed rights inside Cognos Controller Limitations tab.
Click SAVE.
Click CLOSE.
Exit Cognos Controller.

Now the new user can start the new Cognos Controller client and try to login again.

More Information: