Cognos Controller 10.4
Microsoft Windows 2016 server

How do i now the number of Administration license i use in my Cognos Controller installation?

There is a text file that list this for each controller database, you can look into this file to find out.
The number of administrators, is not the number of users that you add to the Cognos Controller Administrators role.
Administrative User
A Controller administrative user can have access to all menu items.

Standard User
A Controller Standard User may have access to all menus in Controller with the exception of financial change/write access to menus in the ‘Maintain’ menu.

You can go to this folder on your Controller server to check.
C:\Program Files\ibm\cognos\ccr_64\SLMTagData\default\*.slmtag
This file is only updated on production servers. Default it is updated every 24 hours.

The initial generation of SLMT files is determined by the settings in the Web.config file at C:\Program Files\IBM\cognos\ccr_64\ControllerProxyServer. If a parameter is not specified in the Web.config file, then its default value is used.

SLMTag_PeriodMinuteLength 1440 Frequency of logging SLMT information (StartTime, EndTime interval). Defaults to 24 hours (1440 minutes).

More Information:

Cognos Controller 10.4
Microsoft Windows 2016 server

New install of Cognos Controller on server. When you open Cognos Controller Configuration, you get a error on the Client Distribution Server Configuration.


Close the Controller Configuration program, and start the Controller Configuration program again. Now it should look normal and you can fill in the information.

More Information:

Cognos Controller 10.4
Microsoft Windows 2016 server
Oracle 12c database

New installed Cognos Controller server. You get a error when you do a optimization of the Cognos Controller database from the Cognos Controller client.

Error message:

If you look into the installation log file, in folder c:\program files\ibm\cognos\ccr_64\instlog\tl-CNTRL-10.4-0.101-yymmdd-hhmm.txt and search for error during install, you will find this lines:
Successfully copied file “C:\Users\L-CTRL~1\AppData\Local\Temp\COG_2\server\vfp9r.dll” to file “C:\Windows\system32\server\vfp9r.dll”.
Self registration of file using command line “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfp9r.dll””.
Error: Failed system command “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfp9r.dll””.
Error: Application has returned exit code “3”.
Successfully deleted file “C:\Users\L-CTRL~1\AppData\Local\Temp\COG_2\server\vfp9r.dll”.
Successfully set value “C:\Windows\system32\server\vfp9r.dll” for key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs”.


Successfully copied file “C:\Users\L-CTRL~1\AppData\Local\Temp\COG_2\server\vfp9t.dll” to file “C:\Windows\system32\server\vfp9t.dll”.
Self registration of file using command line “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfp9t.dll””.
Error: Failed system command “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfp9t.dll””.
Error: Application has returned exit code “3”.
Successfully deleted file “C:\Users\L-CTRL~1\AppData\Local\Temp\COG_2\server\vfp9t.dll”

Uninstall Cognos Controller from the server.
Then reinstall it again to the same directory.
Check the log file again, now the above two files are installed correct.
Update Controller Configuration with correct report server values again.

Suggestion, always install cognos controller – then uninstall it, and install cognos controller again. This to prevent this and you have to update the Cognos Controller Configuration again.

More information:

Cognos Controller 10.4
Microsoft Windows 2016 server

New installed Cognos Controller client on citrix/terminal server give error when open a standard report in PDF.

Error message:

Suggested Solution:
Check that the user logged in to citrix, have access rights to run the program Adobe Reader. Can be limited by group polices in Windows.

Cognos Controller 10.4
Microsoft Windows 2016
Oracle database 12c

Get a error message when open Command Center dialog inside Cognos Controller client , in a new installation.

Error Messages examples:
Caused by: Unable to find instance of model of type: configproperty[ConfigPropertyModel]…….
Caused by: Failed to rollback transaction….

Solutions to check:

Workaround is to use OJDBC5.JAR file in this locations on the Controller server:
c:\Program Files\ibm\cognos\ccr_64
c:\Program Files\ibm\cognos\ccr_64\server\integration
c:\Program Files\ibm\cognos\ccr_64\server\FAP\lib
Even do CA11 can work with OJDBC7.JAR file, it may not be that Cognos Controller can it.

Check that file and
in folder c:\Program Files\ibm\cognos\ccr_64\server\integration
are updated with Oracle information.

Setup a TNS_ADMIN windows system variable to point to the TNSNAMES.ORA file

Oracle driver OJDBC7.JAR file, will work for Cognos Controller, if you do not edit the file – leave it as default.

Cognos Controller 10.4
Microsoft Windows 2016

How create one silent install package, that can install to different environments. If the install script run in DEV it should point to the DEV controllerserver (e.g. by updating the ccr.exe.config file), same script should work for PROD.

Suggested Solution:
In case your terminal servers host name point out if it is DEV or PROD, like this;
DEV servers have TT in there servername like TT2345.
PROD servers have SRV in there servername like SRV2345, and PPE have PP in the servername.
Then you can create 3 uniq ccr.exe.config files, with a predefined line for each environment;
<add key=”WSSUrl” value=”http://DEVSERVER.COMPANY.COM/ibmcognos/controllerserver”/>

Place all files in the same folder on the server. 3 files of ccr.exe.config, with the middle part replaced with the environment tag. The client ccrlocalclient64.msi file and a BAT file with below code;
REM=================replace italic with your values=========
cd /D %~dp0
msiexec /qb /i CCRLocalClient64.Msi IBM_COGNOS_CONTROLLER=”C:\Program Files\IBM\IBM Cognos Controller Local Client” WSSURL= HELPURL=

@setlocal enableextensions enabledelayedexpansion
@echo off
call :CheckEnv %COMPUTERNAME%
call :CopyFile

Goto ScriptEND

echo %1
set str1=%1
if not x%str1:tt=%==x%str1% set COGNOSVAL=DEV
if not x%str1:pp=%==x%str1% set COGNOSVAL=PPE
if not x%str1:srv=%==x%str1% set COGNOSVAL=PROD
Goto END

copy /Y ccr.%COGNOSVAL%.config “C:\Program Files\IBM\IBM Cognos Controller Local Client\CCR.exe.config”
copy /Y CognosController.ps1 “C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\CognosController.ps1”
Goto END

REM=====================end of code==============

We also copy a ps1 file to the startup folder of Windows 2016.
The powershell cognoscontroller.ps1 file is run when a user logon to the terminal server, in that ps1 script you can have code to set that excel can open XLT files, and other things.

Update the BAT file with the your prod servers WSSURL and HELPURL, if the servername does not match Controller client is installed with this values.

Above show the line to update in the ccr.exe.config file.
The content of this file is copied to the users windows profile C:\Users\username\AppData\Roaming\Cognos\ccr\ccr.config, when they start Cognos Controller Client for the first time.
To make above work, the Terminal Servers should not use a roaming profile.
Run the BAT file to install Cognos Controller, and it will copy the correct ccr.exe.config file to your program files folder.

More Information:

Cognos Controller 10.3.1
Microsoft Windows 2012 R2 (Windows NT 6.2)

What are the recommended settings for IIS Application Pools?

For cognos controller and ICAPool that are used with Cognos Controller, recommended timeout is 600 minutes.
Login to the Cognos Controller Server.
Open Internet Information Services (IIS) Manager
Click on Applications Pools
Click on NET v4.5 or the one created for Controller.

Change Idle Time-Out (minutes) to 600.
Click OK.
Do the same for the other Applications Pool used by Cognos.

Cognos Controller Applications Pool should use the local system account.

Set the Cognos BI timeout value to same, open Cognos Configuration, and go to Security – Authentication, and change to 36000 seconds.

Save and restart your Cognos services in correct order. Cognos Content Manager service first.

Then you should change recycling of Application Pool for Cognos Controller to be at a defined time, and not after 29 hours.

Change this to it to be recycled at 1 AM at night, like below.

Also ensure that the logging of the recycling is active, this is not default in Windows 2012, see below to have it active.

More Information:

Cognos Controller 10.3.1
Cognos Analytics 11.0.12
Planning Analytics 2.0.5

What places should i change in Cognos in case i replace my Microsoft SQL database host to a new server?

Stop all Cognos windows services.
Take a backup of the databases and copy them over to the new database server.
Ensure that the collation settings (sort order) is the same on old and new database instances.
Ensure that the SQL login have the correct dbowner rights on the database tables.
Start up the new database server.

Cognos BI have connections to content store, and other databases you have setup from Cognos Configuration.
Start Cognos Configuration.
Go to Environment – Logging – Audit – Audit and change database server with port numbers value to the new SQL server.
Go to Data Access – Content Manager – Content Store, and change database server name value to the new SQL server.

Repeat the change for notification database,and any other database you have setup in Cognos configuration.
Save the changes and start the CA11 services, in case you have more than one BI server, start with the primary content manager first.

Surf to Cognos Connection, go to manage – administration console. Click on configuration tab. Go to Data Source Connections and in the right side click on the database link name. Then click on more in the right side.

Click on Set properties. Click on Connection tab. Click on pencil icon to edit the data source.

Change the server name to the new server, click on JDBC tab, and change Server name and port number to the new values. Click OK twice to save changes.
Test if the connection works.
Repeat for any data source you have here, that have changed database server.

Cognos Controller have database access that is stored in udl files, and is changed with IBM Cognos Controller Configuration program.
Start Controller Configuration on the Cognos Controller server.

Go to Database Connections – and for each database change the Data Source and click save.

Go to Report Server tab. Click on the check icon.
Press the REPAIR button, to update the data sources in Cognos Analytics.
Ensure that the windows user you are logged in to the Cognos Controller server, is system admin in CA11 Cognos connection, to make the update possible.

Go to Enhanced Reporting Optimizations tab – change the server name here. In most cases the file share for the ERO function is on the SQL server, and therefor need to be changed when you change your database server. Click save after each change, and you need to update each connection.

Ask the cognos controller users to test, by run a excel report with the ERO function active.

If the ERO share is on a file server (or the cognos controller server) you need to add the windows service account that the new SQL server is using to the file share, so the SQL server process have access to the files in this share.

The FAP service is configured in the C:\Program Files\ibm\cognos\ccr_64\server\FAP\ file. Open it in notepad++.

Host should be servername\\instancename or servername:port if the port is correct.
Save the file and start the IBM Cognos FAP Service.
Check the C:\Program Files\ibm\cognos\ccr_64\server\FAP\error.log file for errors.

On the TM1 server there are ODBC connections to the SQL database, one is called FAP. All ODBC connections need to be updated to point to the new database server.
Export the values from registry and edit the server name in notepad.
Start Regedit program.
Right click and select Export.
Save the file as ODBC_64.REG

Repeat the same for [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI] to get the 32 bit ODBC drivers exported to a text file, like odbc_32.reg.
The file can look like below;
Windows Registry Editor Version 5.00

Open the file in notepad and change the server to the new database server, save the file.
Double click on the reg file to register the new value for the ODBC connection.

Start the FAP client connect, and enter the new server name and any new username or password, step through the database on the source tab to ensure it point correct. Edit as below if needed.

You need to edit the server for the cognos controller database, on the source tab.

You need to update the Controller Web to the new database. Stop the IBM Controller Web service.
Start a CMD prompt and go to folder; cd d:\Program Files\IBM\cognos\ccr_64\fcmweb
Enter the following command:
SyncDBConf.bat    ..\Data    wlp\usr\shared\config\datasources

Start the IBM Controller web service.

More information:

Cognos Controller 10.4
Microsoft Windows 2016 Server

After upgrade to a later version of Cognos Controller 10.4, where also BI 10 have been replaced by CA11, the PDF shown inside Cognos Controller client is small. HTML reports works fine.

The user profile of the user executing the report is referencing a style (also known as skin) from IBM Cognos Business Intelligence 10.

In IBM® Cognos® Analytics, in the lower-left corner, click icon for administration, select Administration Console.
On the Security tab, click Users, Groups, and Roles.
Click the namespace that contains the user.
Find the user whose preferences you want to view or change. You can use the Search feature to find a user Searching for entries using name, description, and name or description.
For that user – in the Actions column, click More.
Click Set preferences.
Click the different tabs to view or change the settings.
In the Preferences tab, choose Style Corporate.
Make the change and click OK.

Test again to run a report in Cognos Controller as PDF.

More Information:

Cognos Controller 10.4
Microsoft Windows 2016 server

When doing currency conversation in a consolidation you get a error “ActiveX component can’t create object”.

When you check the Windows event log you find a error similar to this:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
to the user DOMAIN\USERNAME SID (S-1-5-21-55472620-132315974-3481569866-49656) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Service

Suggested Solution:
Login to the Cognos Controller Window server.
Go into IIS Manager
Go to the application pools.
Select the application pool for controller, can be NET v4.5 or Controller (depending what you have named it), and click advanced settings.

Under Process Model, change Identity from ApplicationPoolIdentity to LocalSystem.
Also ensure the Idle Time-out is 600 minutes, and not the default 20 minutes.
Click OK
Restart the IIS service.

You need also go into Controller Configuration
Change COM+ server to us Local System Account
Save the changes.

Retry the currency conversation.

More information: