Cognos Controller 10.1
Microsoft Windows 2008 R2 server

When try to convert a older cognos controller database, you get a error when you run the DbConv program from the folder D:\Program Files (x86)\ibm\cognos\c10\legacy.

Error Message:
DbConv Error
ERROR 429 (Hex 1AD):
ActiveX component can’t create object

Database Upgrade is aborted due to error in processing Step 755.
Error – 429 ActiveX component can’t create object
Current DB Version is 754

During the install of Cognos Controller 10.1 on the Microsoft Windows 2008 R2 server some files was not correct registered.


1. Logon to the Controller application server as an administrator
2. Launch Windows Explorer, and navigate to the folder: C:\Windows\SysWOW64\common
3. Right-click on the file “Xceedzip.dll” and choose “properties”. Check the file size. It should be approximately 278 KB. If it is 0 Kb then the file is corrupt and will need to be replaced.
4. Navigate to the folder: \Common (this can be: D:\Program Files (x86)\ibm\cognos\c10\common)
5. Right-click on the file “FrCrypto.dll” and choose “properties”. Check the file size. It should be approximately 29 KB. If it is 0 Kb then the file is corrupt and will need to be replaced.
6. Launch a command prompt by clicking “Start” – “Run” and then typing in “CMD”
7. Change directory using: cd C:\Windows\SysWOW64\common
8. Register the file using: regsvr32.exe xceedzip.dll
9. Change directory to the c8\common folder (for example using: cd “D:\Program Files (x86)\ibm\cognos\c10\common”)
10. Register the file using: regsvr32.exe FrCrypto.dll

Cognos Controller 10.1
Microsoft Windows 2008 R2

Open Cognos Controller Configuration hang when you select the Report Server section.
In some cases you get a error message.
You can only kill the Controller Configuration program from Windows Task Manager, and when you go into Controller Configuration again it will hang.

Error message:
File Download
Do you want to save this file, or find a program online to open it?
Name: cognosisapi.xts&h_CAM_action=logon
Type: Unknown File Type, 252KB
From: servername

You have changed the Controller Configuration to use cognosisapi.dll but not changed on the Windows 2008 iis to handle isapi for cognos controller. You need to change the IIS settings before you change in Controller Configuration.

Can also happens when you enter a none valid Report Server URL in Controller Configuration.

1) In IIS select the server node, then double-click ISAPI and CGI Restrictions in the right pane, Under Actions on the right hand screen select Edit Feature Settings and make sure Allow unspecified ISAPI modules is selected.
In the Left Connection pane select the cgi-bin virtual directory, then double-click Handler Mappings in the right pane.
In the Actions pane click Add Module Mapping, the settings should be similar to:

Request path: cognosisapi.dll
Module: IsapiModule
Executable (optional): C:\Program Files (x86)\ibm\cognos\c10\cgi-bin\cognosisapi.dll
Name: ISAPI-cognos

Click OK and Yes to allow this ISAPI extension

2) If running 64-bit In iis under Application Pools, select your application pool for the ibmcognos virtual directories i.e. DefaultAppPool, on the right-hand side click Set Application Pool Defaults and change Enable 32-Bit Applications to True

3) Edit the file /c10/cgi-bin/web.config and add:
to the following entry:

To become:

4) Restart iis

5) In Cognos Configuration under Environment change Gateway URI to reference cognosisapi.dll instead

(Leave Cognos Configuration open for the moment)

In the /webcontent directory, edit the index.htm and default.htm files and change

In Cognos Configuration save you settings and restart the services.

6) In Controller Configuration under Report server change Report server to cognosisapi.dll instead of cognos.cgi

When the user surf to http://servername/ibmcognos, will cognosisapi.dll be used as default.

Cognos Controller 10.1
Microsoft Windows 2008 R2

When starting Cognos Controller client, it will hang and not show up.

This happens on a client computer (citrix server) that run a 64 bit operation system.

Possible error:
Microsoft IE Execute shell
Microsoft IE Execute shell has encountered a problem and needs to close.
We are sorry for the inconvenience.

Cognos Controller is a 32 bit application, and will not execute in a 64 bit Internet Explorer.

Possible Solution:
Set the Client computer (citrix server) to process all NET framework code as 32 bit.

start cmd by select “run as administrator” from start menu on client computer.
go to c: drive
change to folder with command: cd %windir%\Microsoft.NET\Framework64\v2.0.50727
Enter command: Ldr64.exe setwow

More information:
On Windows 2008 R2 server when running Controller Configuration, you must right click the program and select Run as Administrator.

Ensure that the client have trust to the Cognos Controller server.
Check by running CASPOL -LG from the Microsoft.NET\Framework\v2.0.50727 folder on the client. This will list the servers that the NET framework client trust.

When you run the caspol command, you must start the command prompt/bat file by right clicking the program and selecting Run as Administrator.

start cmd run as administrator
cd C:\%windir%\Microsoft.NET\Framework\v2.0.50727
caspol -q -m -ag “All_Code” -url http:// SERVERNAME /* FullTrust -name “Controller_ SERVERNAME ” -d “Controller_ SERVERNAME ”

(replace SERVERNAME with the name of your server NetBios or FQDN depending what you have setup)
Run the CASPOL command once for FQDN and once for the NetBios Servername to ensure the clients access to the server.

Cognos Controller 10.1
Microsoft Windows 2008 R2

The Cognos Controller client freeze (hang) after you have selected the database to use. The login dialog is not showing up. There are no error messages in windows event log.

If you run Controller Client direct on the Controller Application server – it works fine.
But from all client computers the Controller Client will hang.

When Cognos Controller client start it will contact Cognos connection to check if it is there, even if you use native controller security. When report server setting is http://localhost/ibmcognos/cgi-bin/cognosisapi.dll , this will not work – Cognos connection can not be found on the local client.

You can sometimes get a Internet Explorer 404 error in Controller before the login dialog.

After you have applied the Cognos Controller hot fix, the settings in Controller configuration is reverted back to default values. Therefore the Report server value is localhost and not the server name.

Open Controller Configuration on your Controller server.
Go to the Report Server tab.
Change the url from localhost to the servername

Report server should be:

Dispatcher URI should be:

(change srv001 to your server name)

Click save and close.
Test again.

Cognos Controller 10.1
Microsoft Windows 2008 server

How automatic set the background picture in Cognos controller for all clients on a Citrix server?

Inside Cognos Controller client, you can define a BMP file to be used as background picture.
Recommended is to have a different background picture for your test environment.
To make Controller Client color different from the productions clients.

In Cognos Controller client go to
Maintain – Installation – Local Preferences
Here you can enter the key app_background
And a value that points to a local BMP file.

Local Preferences values are stored in the ccr.config file for each user in there windows profile.
You need to populate this file for each user when they logon to the Terminal Server.

On citrix server create a folder called d:\script
On citrix server create a BMP file and save it as c:\windows\background.bmp
On citrix server download AUTOIT3:EXE from
And place it in folder d:\script

Create a text file in folder d:\script named replaceccr.au3 with this content:

$TextFileName = @UserProfileDir & “\AppData\Roaming\Cognos\ccr\ccr.config”

$FindText = “”
$ReplaceText = ‘ ‘

$FileContents = FileRead($TextFileName)
$Check = StringInStr( $FileContents, “” )

if $Check = 0 Then

$FileContents = StringReplace($FileContents,$FindText,$ReplaceText)


Create a text file in folder d:\script named updateccr.cmd with this content:
d:\script\autoit3.exe d:\script\replaceccr.au3

In folder d:\script these files should now be:
Autoit3.exe = used to process au3 script files
Replaceccr.au3 = will check the users ccr.config file and add the “app_background” if it does not already have a “LocalPref” value.
Updateccr.cmd = file to run to active the script

You may then add the updateccr.cmd file to your C:\Windows\System32\usrlogon.cmd, to make it run when anyone logon to the Windows Server.

More information about Terminal Server logon script

More information about Autoit3:

Cognos Controller 10.1

Error before login to Cognos Controller you get an error message. You get the message after you have selected the controller database to use.

Error message:
Log On IBM Cognos Controller

Invalid namespace was selected

Cognos Controller 10 is setup to talk to a Cognos BI 8 installation.

The Dispatcher URI in Controller Configuration Report Server is not only used when you run the standard reports – it is also used when validate the login when using Server Authentication. The Report Server Dispatcher value is inherited to Server Authentication.

The values for Report Server will be reset to default values when you install the Cognos Controller Update Components Fix Pack on a existing Cognos Controller installation.

On the Cognos Controller application server
Start IBM Cognos Controller Configuration
Select Report Server in the list
Change the Dispatcher URI to be a valid URL

To something like this

Click Save
Exit Controller Configuration
Start Cognos Controller client and test again.

More Information:
If the Cognos BI service is not available you will get an error of this kind instead:
IBM Cognos Business Intelligence
Error executing request. Please verify that the target URI is valid and that IBM Cognos is online.

Below error message in Swedish:

”IBM Cognos-gatewayen kan inte ansluta till IBM Cognos BI-servern. Servern kan vara otillgänglig eller så kan gatewayen vara felaktigt konfigurerad.”
”Försök igen eller kontakta administratören.”

Cognos Controller 8.5

How to install the Cognos Controller client automatic?

Sometimes the IT department want to automate the installation of the Cognos Controller Client on the client computer or Citrix server.

You can from a script start the CCRLOCALCLIENT.MSI file and add parameters that will respond to the questions you get when you install.

Copy first the CCRLOCALCLIENT.MSI file to the Client Computer.
You can download it from

Enter below on ONE row in a DOS prompt on the client computer:
msiexec.exe /qb /i ccrlocalclient.msi WSSURL=http://servername/cognos8/controllerserver HELPURL=http://servername/cognos8/controllerhelp

Replace servername above with the name of your Cognos Controller server.

Cognos TM1 9.5

After installing a new TM1 instance – the new TM1 server is not shown in the drop down list for the TM1Web login. It only shows the login dialog for user name and password.

The web.config file in the tm1web folder is configured to only talk to one tm1server.

Open the web.config file from folder
Search the file for TM1ServerName (it is close to the end of the file)

Change the line from
<add key=”TM1ServerName” value=”tm1servername” />
to this
<add key=”TM1ServerName” value=”” />
save the file.

Then surf to the TM1web and select the server you want to login to from the list.

Cognos TM1 9.5.2 portlets
Cognos BI 10.1

You can not get a TM1 cube viewer to show up in your Cognos Connection Page.

Error message:
The file “portal/variables_TM1.xml” could not be opened.

The variables_tm1.xml file is installed to the Cognos Gateway folder, should be installed to folder C:\Program Files\ibm\cognos\c10_64\templates\ps\portal on the Cognos BI server.

Error message:
The forward URL does not exist or it has failed validation. Ensure that a valid forward URL is specified.

The URL in the variables_tm1.xml file is wrong. Ensure it is correct, by compare it to a variables_tm1.xml file from a working Cognos BI server.

Note that you must always restart the Cognos BI service, after changes to variables_tm1.xml file for the change to take affect.

The variables_TM1.xml file should look like this; replace SRV001 with your TM1 server name.

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


IBM Confidential

OCO Source Materials

BI and PM: tm1fragments

(C) Copyright IBM Corp. 2008, 2009

The source code for this program is not published or otherwise

divested of its trade secrets, irrespective of what has been

deposited with the U.S. Copyright Office.




<url is-regex=”true”>http://srv001/TM1Web/TM1WebLogin.aspx</url>

<url is-regex=”true”>http://srv001/TM1Web/TM1WebLoginHandler.aspx</url>

<url is-regex=”true”>http://srv001/TM1Web/TM1WebMain.aspx</url>



<param name=”cam_passport”/>



Cognos TM1 contributor version 9.5.1

Can not logon and access a previous working TM1 Contributor application.
User surf to http://tm1servername:8080/pmpsvc
Is prompted with TM1 Login dialog that ask for user name and password
No matter what you enter – you get a error message.

Error message:
Could not logon to any available servers with the provided credentials.

The TM1 Contributor is tie to a TM1 Application that use CAM security.
But the TM1 application was not using CAM security when you setup TOMCAT and TM1 Contributor – you have change the TM1 application later to use CAM (Cognos 8 logon) and therefore the TM1 Contributor ask for a TM1 login- but can not find any TM1 application that supports that logon method.

Suggested Solution:
(There may be other way to solve this)

You need to setup TM1 Contributor again.
Logon to your TM1 Contributor windows server.
Stop Apache Tomcat 6 service.
Remove the values for server name and admin_host in the pmpsvc_config.xml file.
Start the Apache Tomcat 6 service again.
Surf to http://localhost:8080/pmpsvc

You will be prompted with the TM1 Contributor Configuration page again.

Enter the TM1 server name at Admin Host:
(this can be a different server than the TM1WEB – it should be the server that runs the TM1 admin service)

The TM1 Web Client URL should be:
(this should point to the server that runs the tm1web portal – often the same server as the Cognos gateway server)

In the server drop down list you should select your previous selected tm1planning server.
Now you will get two new lines to enter information (for the CAM security)

IBM Cognos 8 Gateway URI: enter here a value like this;

IBM Cognos 8 Dispatcher URI: enter here a value like this;

Click OK to save.
Now you will be prompted with the Cognos 8 logon page.
Then you are back in the TM1 Contributor page with your application.