Cognos Controller 11.0.1200
Windows Server 2022


When press the excel icon in Cognos Controller, excel starts but there is no controller toolbar inside.


Check that you have two lines for cognos controller in options-add in.

if not, ensure that one is not disabled.

1. Launch Excel

2. Click “File – Options”

3. Click “Add-ins”:

4. Change “Manage” to “Disabled Items” and click ‘Go’:

5. Highlight the Controller add-in (“cognos controller link for Microsoft excel (adxloader.Controller.ExcelLink.dll)”), and click “Enable“:

6. Test.

If that not helps, try to add the add-in manually.

More information: 


Cognos Controller 11.0.12
Microsoft Windows 1016 server


Error message about missing files when doing a upgrade installation of Cognos Controller 11.

Failed to copy file “d:\cognos controller upgrade\cntrl_11.0.1_win_ml\winx64h\./resource/utf-8\is_en_rc.txt” to destination “d:\program files\ibm\cognos\ccr_64\uninstall\./resource/utf-8\is_en_rc.txt”: No such file or directory.

If you press skip, you get a new message for other missing file.


Check the size of the cntrl_11.0.1_win_ml.tar.gz   file – if it is less than 2 326 187 KB, you have the wrong file. Download again from IBM.

Parts and platforms Details eImage
IBM Cognos Controller 11.0.1 Microsoft Windows Multilingual Required M0DH2ML


A zip file of the size 409 587 KB is wrong.

More information:

To log a ticket with IBM support go to:

IBM Documentation:

Cognos Controller 11.0.12

Microsoft Windows 2022 server


User get a error when they try to login to Cognos Controller after you have upgraded the software on the server.


Ask the user to install the new Cognos Controller client that match the version you have installed on the windows server.

This is often done by central distribution system, like Software center.

IBM Cognos Controller Version 11.0.1200.28
Integration Version 11.0.1200.8
Install/Updater Kit Version 11.0.1200.36


More information:


Cognos Controller 11
Microsoft Windows 2022 server


Error when you try to setup the Cognos Controller web, by running bat command to add the databases.

D:\Program Files\ibm\cognos\ccr_64\fcmweb>SyncDBConf.bat ..\data wlp\user\shared\config\datasources
Found 6 udl files in ..\data

FATAL ERROR: ‘ D:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\user\shared\config\datasources\datasources.xml (The system cannot find the path specified.)’
:D:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\user\shared\config\datasources\datasources.xml (The system cannot find the path specified.)
Datasources updated.


Try to Find the config.js file in C:\Program Files\IBM\cognos\ccr_64\frontend folder
Open the file in a text editor and make the following changes:


* =====================================================================

* IBM Confidential


* IBM Cognos Products: ccr


* © Copyright IBM Corp. 2023


* The source code for this program is not published or otherwise

* divested of its trade secrets, irrespective of that has been

* deposited with the U.S. Copyright Office.

* =====================================================================


var fs = require('fs');

module.exports =


"proxies": [{

"urlPath": "fcm.web",  //root context for Controller Web backend

"enabled": true,      //forward requests through UI service

"options": {

"ws": true,

// details for Controller web backend connection

"target": {

"host": "",

"port": 3000,

"protocol": "http:" //set https: for SSL


"secure": true  //set this to false if Controller Web Backend is using Self Signed certificates




"urlPath": "ibmcognos",  //root context for Controller Server Backend

"enabled": true,      //forward requests through UI service

"options": {

"ws": true,

//details for Controller Server connection

"target": {

"host": "",

"port": 80,

"protocol": "http:" //set https: for SSL


"secure": true  //set this to false if Controller Server Backend is using Self Signed certificates



//Details for Controller UI service 

"expressJs": {

"host": "", //interface used by Controller Web UI Service

"port": "9080",              //port used by Controller Web UI Service

"adminContext": "admin",

"enableAdminApp": true,

"enableRemoteExcel": false,

"enableClient": false,

"enableFap": true,

"enableFileSettings": true,

"enableIBMIDAuth": false,

"enableEncryption": false,

"allowedOrigin": '{allowedOrigin}',

"oidcProvider": 'IBMid', //IBMid or google or azure

"options": {

//Add ssl object with path to certificates file below for using HTTPS 

//Note: the protocol in proxies section must also be set to HTTPS


                "ssl": {

// certificates

"key": fs.readFileSync(__dirname+"/keyfile.key"),  //__dirname points to ccr_64\frontend

                    "cert": fs.readFileSync(__dirname+"/cert.crt"),





//false to enable "real time updates" feature for all the users

//true to disable "real time updates" feature for all the users

"disableRealTimeUpdates": false


ibmIDConfig: {

"discoveryEndpoint": "{discoveryEndpoint}",

"client_id": "{client_id}",

"client_secret": "{client_secret}",

"redirect_uris": ["{basePath}/auth/sso/callback"]




"paLink": ""



Reboot the Microsoft Windows Server, and then try to run the SyncDBConf.bat command again.

More Information:


Cognos Controller 11

Microsoft Windows 2022 server


You click on the excel icon in cognos controller to start Excel program. The excel program starts very small.


Remove the ccr.exe properties to adjust screen resolution (change high DPI settings)  or

open a excel document first in excel, before you login to cognos controller from excel, and run a report.

You have change the ccr.exe properties to not make cognos controller shrink when you open a java menu inside the cognos controller program. This is done by go to C:\Program Files\IBM\IBM Cognos Controller Local Client folder.
Right click on CCR.exe > Properties > Compatibility > Change high DPI settings > Check Override high DPI scaling behavior. Scaling performed by: System (Enhanced). 

If user need to send report to Excel, they need to have an Excel book open first before run send to Excel. Otherwise the Excel will shrink after apply setting.

More Information: 

Cognos Controller 11.0.1200
Microsoft Windows 2019 server
Microsoft SQL 2016 server

How install Cognos Controller 11?


This are an example of the steps to install Cognos Controller 11.  (Some information below may be incorrect or not needed)

For best guides follow the IBM documentation.

Before any work with Cognos Controller – take a extra SQL backup of the database.

Download the software from here:

You need to get both the RTM version and any fix pack you need to install.

Install IIS on the server that will run Cognos Controller. Microsoft .NET Framework 4.7.2 must be installed on the Controller Web Services Server computer. Install sqlncli.msi driver version 11.4.7462.6 or later version for SQL server.

Select the following when you add the Web Server (IIS) role to the windows server:

  • .NET Framework 4.5 and 3.5
  • ASP
  • CGI
  • ISAPI Extensions
  • ISAPI Filters
  • .NET Extensibility
  • IIS Management Console
  • IIS Management Scripts and Tools
  • HTTP Activation
  • HTTP Redirection
  • Directory Browsing

Cognos Controller 11 only supports Microsoft SQL server database,  you need to create one database, if you not already have one from an old version of Cognos Controller. Ensure that the database collation sequence is case insensitive, and is the same for both the SQL server (tempdb database) and the Controller database. (Recommended:  SQL_Latin1_General_CP1_CI_AS ) Controller tables owned by dbo are not supported. If you have dbo as the default table owner you must change it, easiest is to create a new database from start in SSMS.

To create a schema named cognos:

IF (NOT EXISTS (SELECT * FROM sys.schemas WHERE name = 'cognos'))

To change schema on one table:

TRANSFER dbo.Employees

To change default schema for a user in SQL:



If you do a upgrade of Cognos Controller 11 on a old server, you need to uninstall the previous Cognos Controller 10 version first.

Check if the anti-virus software on the Windows server is compatible with you installing of software.

Copy the installation media to the server and unzip it.

Run (as a administrator) the issetup.exe from folder C:\install\cntrl_11.0.1_win_ml.tar\winx64h\ to install Cognos Controller.

Click Next

Mark I agree and Click Next

Mark non-production (if not production server) and click Next

Click Yes

Normally you select all. In some cases the FAP is only installed on your TM1 server. Controller Web is only needed if you going to use it.

Click Next.

Click Next

Click Next

Wait until it is done

Click Finish.

In the log file you can find this messages:
Install component: VFP
Component Version: VFP-AW64-ML-RTM-9.0.2120.0
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfp9r.dll” successfully extracted.
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfp9renu.dll” successfully extracted.
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfp9t.dll” successfully extracted.
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfp-winx64h-app-9.0.2120.0-inst.ver” successfully extracted.
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfp-winx64h-app-inst.ver” successfully extracted.
Successfully created directory “C:\Windows\system32\server\”.
Successfully copied file “C:\Users\ADMINI~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\ADMINI~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\ADMINI~1\AppData\Local\Temp\COG_2\server\vfp9renu.dll” to file “C:\Windows\system32\server\vfp9renu.dll”.
Self registration of file using command line “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfp9renu.dll””.
Error: Failed system command “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfp9renu.dll””.
Error: Application has returned exit code “4”.
Successfully deleted file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfp9renu.dll”.
Successfully set value “C:\Windows\system32\server\vfp9renu.dll” for key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs”.
Successfully copied file “C:\Users\ADMINI~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\ADMINI~1\AppData\Local\Temp\COG_2\server\vfp9t.dll”.
Successfully set value “C:\Windows\system32\server\vfp9t.dll” for key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs”.
Successfully deleted file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfp-winx64h-app-9.0.2120.0-inst.ver”.
Successfully deleted file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfp-winx64h-app-inst.ver”.
Successfully added value “1” for key “VFP” under section “Component List” in file “C:\Program Files\ibm\cognos\ccr_64\uninstall\uninst.ini”.

Install component: VFPCOM
Component Version: VFPCOM-AW64-ML-RTM-9.0.2123.0
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfpcom.dll” successfully extracted.
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfpcom-winx64h-app-9.0.2123.0-inst.ver” successfully extracted.
File “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfpcom-winx64h-app-inst.ver” successfully extracted.
Successfully copied file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfpcom.dll” to file “C:\Windows\system32\server\vfpcom.dll”.
Self registration of file using command line “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfpcom.dll””.
Error: Failed system command “C:\Windows\system32\regsvr32.exe /s “C:\Windows\system32\server\vfpcom.dll””.
Error: Application has returned exit code “3”.
Successfully deleted file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\server\vfpcom.dll”.
Successfully set value “C:\Windows\system32\server\vfpcom.dll” for key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs”.
Successfully deleted file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfpcom-winx64h-app-9.0.2123.0-inst.ver”.
Successfully deleted file “C:\Users\ADMINI~1\AppData\Local\Temp\COG_2\vers\vfpcom-winx64h-app-inst.ver”.
Successfully added value “1” for key “VFPCOM” under section “Component List” in file “C:\Program Files\ibm\cognos\ccr_64\uninstall\uninst.ini”.

Above error in log file show that the COM objects for Cognos Controller was not installed. Uninstall cognos controller and do the installation again.


Error: Failed to retrieve environment variable “JAVA_HOME”.
Error: Processing XML file “C:\Program Files\ibm\cognos\ccr_64\bin\wct\ccrconfigwebserver.xml” returned errors. View the file “C:\Program Files\ibm\cognos\ccr_64\instlog\isconfig-CNTRL-20240315_1517.log” for details.
Successfully added value “1” for key “CCRWEBSERVER_VERC” under section “Component List” in file “C:\Program Files\ibm\cognos\ccr_64\uninstall\uninst.ini”.

Above error is common, but should not affect the software performance.


Error: Processing XML file “C:\Program Files\ibm\cognos\ccr_64\frontend\fcmconfigfrontendserver.xml” returned errors. View the file “C:\Program Files\ibm\cognos\ccr_64\instlog\isconfig-CNTRL-20240315_1517.log” for details.
Successfully added value “1” for key “CCRFCMFRONTEND_VERC” under section “Component List” in file “C:\Program Files\ibm\cognos\ccr_64\uninstall\uninst.ini”.

Above error we have no clue what it is.


Run the upgrade/fix pack from folder like C:\install\up_cntrl_winx64h_11.0.1200.36_ml.tar\winx64h\issetup.exe

Click Next

Click Next

Select same path as before and click Next

Click Next


Click Finish.

Reboot the windows server.

Check the cmplst.txt file that the correct controller version is installed:

LICENSE_CONTROLLER_name=IBM Cognos 8 License
CONTRL_name=IBM Cognos Controller
[Product Update Information]

CONTRL_UPDATE_name=IBM Cognos Controller Update
[Main Applications]

Copy the sqljdbc42.jar driver to folders like C:\Program Files\ibm\cognos\ccr_64\server\FAP\lib and C:\Program Files\ibm\cognos\ccr_64\server\integration and C:\Program Files\ibm\cognos\ccr_64

Start Cognos Configuration and setup the values needed, start with the database connection to your Cognos Controller database.

See more details in how to setup old cognos controller here


The provider should be SQLNCLI11.1 and data source is the name of the windows database server. You should use a db server name and not ip address.

Click test connection, click save icon, and then click run icon – to start the DBCONVERT program. Here you need to upgrade your Cognos Controller database to the new version.

Updater Kit Build FCM Web Client (classic) CCR Version DB Version Comment
11.0.1200.1015 11.0.1200.55 11.0.1200.10 11.0.1200.8 IF2 1015
11.0.1200.1002 11.0.1200.37 11.0.1200.10 11.0.1200.8 IF1 1015 Available on Passport Adv. (full installation)
11.0.1200.36 11.0.1200.28 11.0.1200.10 11.0.1200.8 11.0.1 FP2 1015 Generally available (FixCentral)
11.0.1000.8 11.0.1000.6 11.0.1000.1 11.0.1000.2 11.0.1 FP1 1013 Generally available (FixCentral) 11.0.1 1012 Available on Passport Adv. (full installation) IF1 1011 Generally available (FixCentral) RTM 1011 Available on Passport Adv. (full installation)
10.4.2200.222 10.4.2200.228 10.4.2200.79 10.4.2200.77 IF9 1010


If you have a demand for TLS 1.2 in your Windows environment or run old version of Windows, then you can get a error like below when you click “connect”.

** ERROR: Drivrutinen kunde inte upprätta en säker anslutning till SQL Server med SSL-kryptering (Secure Sockets Layer). Fel: “Unexpected rethrowing”.

Can it be that SQL Server 2005 that uses 3DES algorithm in TLS connection and with new versions of JRE, this algorithm is disabled, Or the database is an older database (like SQL Server 2014) which does not allow higher security standards like TLS 1.2.

Then You need to start DBCONV program from a bat file with this settings (save it in a text file called DBCONV.BAT and run it) : 

"C:\Program Files\IBM\cognos\ccr_64\bin\jre\8.0\bin\java.exe" -cp"C:\Program Files\ibm\cognos\ccr_64\bin64\jre\8.0\bin\javaw.exe" -cp "C:\ProgramFiles\ibm\cognos\ccr_64\DbConv.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\antlr-3.2.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\ccr-common.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\ccr-integration-server.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\ccr-integration.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\ccr-xml.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\cglib-nodep-2.1_3.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-beanutils-1.8.3.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-beanutils-bean-collections-1.8.3.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-beanutils-core-1.8.3.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-cli-1.1.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-codec-1.8.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-collections-3.2.1.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-dbcp-1.2.2.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-io-2.4.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-lang-2.3.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-logging-1.1.1.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\commons-pool-1.3.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\db2jcc.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\DBConv.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\icu4j-4_8_1_1.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\jsr173_1.0_api.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\jython.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\log4j-1.2.8.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\ngtm1api.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\ojdbc6.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\resolver.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\spring.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\sqljdbc42.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\stringtemplate-3.2.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\xbean.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\xbean_xpath.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\xmlbeans-qname.jar";"C:\Program Files\ibm\cognos\ccr_64\server\integration\xmlpublic.jar"


If this is a new empty database – you need to click Create DB (this will erase the database, and create a empty controller database).

Then do a upgrade of the cognos controller database.

You should get to above picture without errors, if the upgrade of the cognos controller database was successful.

Click Close


Setup of IIS Manager:

  1. In the Internet Information Services (IIS) Manager,  select Application Pools.
  2. Create a new Controller application pool and then from the Actions pane, select Advanced Settings.
  3. Set the .Net CLR Version to v.4.0.
  4. Set Enable 32-Bit Applications to False.
  5. Set Identity to LocalSystem and time-out to 600.
  6. Click OK.
  7. If you do not have CA11 installed, you can point the ibmcognos virtual directory to a empty folder like webcontent.
  8. Expand Sites and under your web site, create the following virtual directories as shown in the table. If you are installing on the same machine as IBM Cognos Analytics, create the virtual directories under the ibmcognos virtual directory.

    controller controller_install_location\ccrvdir
    controllerbin controller_install_location\webcontent\ccr
  9. Select the controller virtual directory.
  10. double click on HTTP redirect. 
  11. Select Redirect Requests to this destination and enter the following path:

  12. Click Apply.
  13. Right-click your web site and click Add Application.
    1. Set Alias to ControllerServer.
    2. Set Application pool to Controller.
    3. In the PhysicalPath field, enter controller_install_location/ControllerProxyServer.

    4. Click OK.
  14. When you only use native login in Cognos Controller, keep the authentication in IIS to Anonymous Authentication.


On the Cognos Controller server Open C:\Program Files\IBM\cognos\ccr_64\ControllerProxyServer\Web.config and add

<add key="ccrReports" value="http://[servername]:9082/fcm.reports/report" />


Ensure you use space and not tabs inside the config file. Change the localhost settings to the servername in cognos controller configuration, so the client program can find the cognos controller server.

Go to folder C:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\etc\
Open the file server.env inside notepad++
Add the following line:
JAVA_HOME=C:/Program Files/IBM/cognos/ccr_64/fcmweb/jre

Save the changes to the file.


Setup of Cognos Configuration:

Use FQDN server name instead of only the server name.

Above should you not change, it is configured from the report server settings.

Above you must fill out with the full server and domain name.

Start the batch service in Cognos Controller.



When you run a report in Cognos Controller 11 and get a error like:

HTTP Error 404.0 – Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

The value in cognos controller configuration report server (http://localhost/ibmcognos/cgi-bin/cognos.cgi) is pointing to a not working website server. Try to change it to http://cognosanalyticsserver/ibmcognos/bi/v1/disp and ensure that all IIS functions are installed in the Web Server.

HTTP Error 405.0 – Method Not Allowed

The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.

Then you maybe are pointing to a none existent CA11 server in cognos controller configuration report server section. Add the “ccrReports” value in web.config to solve it (this will use the Cognos Controller internal report server).

We can’t open this file

Something went wrong.


This can be that we are using a wrong database connection, try to connect to a other SQL version than 2016.

If you do not have a adobe pdf viewer installed on your laptop. Add the value <add key=”useInternalPdfViewer” value=”true” /> to the servers web.config file. Then cognos controller should use its internal pdfviewer.

You have to reboot the windows server, for the service FCMREPORTS to get any changes to the web.config file to take affect.

You get above error when you run a report in Cognos Controller, when the java is not correct point out in the server.env file for IBM Cognos Controller Reports.


Setup of connection to Cognos Analytics:

If you use CA11 for authentication, then in cognos configuration enter the Report Server to and Dispatcher URI to

You need to create the roles Controller Administrators and Controller Users in CA11 if it is a new installation, then add the users that should use cognos controller to above roles. Follow IBM documentation for more exact steps.

And The Controller Administrators role must be a member of the Controller Users role in Cognos Analytics.

Setup of the Cognos Controller Client:

To install the cognos controller client copy the file ccrlocalclient64.msi to a local folder (c:\install) from C:\Program Files\ibm\cognos\ccr_64\webcontent\ccr folder on the the windows server.

Create a setupccr.bat file with this content:

msiexec.exe /qb /i CCRLocalClient64.msi WSSURL=””

Run the bat file as administrator to install the cognos controller client silent.

After you login to Cognos Controller client, you can check the version in help menu – system info.

If you get a error like WebView is missing, then you must install WebView on the client from  to get the Help menu to work properly inside cognos controller client.

Under Evergreen Standalone Installer, click the x64 download button.

Download and run the installer file MicrosoftEdgeWebView2RuntimeInstallerX64.exe

If you when you test menu – maintain – jobs – define, get a error like this: org.eclipse.core.runtime.adaptor.EclipseStarter failed!
Caused by: Failed to launch!
at Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
… 1 more
Caused by: Unable to find instance of model of type: configproperty[ConfigPropertyModel]

Check if it works better if you use a newer SQL server version, that can communication with the TLS security that the java parts need.

You can try to setup all this:


To setup Controller FAP, there are a few new steps, that is outlined here that you must follow:


More Information:



Cognos Controller 11.0.1


Do you have a checklist of what is needed to do, when you upgrade to Cognos Controller 11?


Best is if you create a own checklist for your environment, that you can use it at every upgrade. Below is a suggested as a starting point, that you can develop further.

Download from here: 

Downloading IBM Cognos Controller 11.0.1 


Parts and platforms Details eImage
IBM Cognos Controller 11.0.1 Microsoft Windows Multilingual Required M0DH2ML
IBM Cognos Analytics Client Multiplatform Multilingual Optional M0BRXML
IBM Cognos Analytics installer 3.6.46 Microsoft Windows Multilingual Optional M0BRWML
IBM Cognos Analytics Server Microsoft Windows Multilingual     Optional M0BRVML


You must download the RTM program and then the fix packs.

IBM Cognos Controller 11.0.x Fix List 

IBM Cognos Analytics Fix Lists 

analytics-installer-3.7.21-win.exe (174.73 MB) (1.49 GB) (6.98 GB)

Get file up_cntrl_winx64h_11.0.1200.36_ml.tar.gz that is for Cognos Controller 11.0.1 fix pack 2.

Detail upgrade instruction here: 

Upgrading IBM Cognos Controller – IBM Documentation 

Installing fix packs – IBM Documentation 

Cognos Analytics 11.2.4 can be installed on top of CA 11.1.7.  The installation will overwrite the images folder, and upgrade the content-store database to a different schema version that will not work with the old CA11 version, therefore you must take a backup of the SQL database before.
Cognos Analytics 11.1.x end of support (EOS) is 2024-04-30 – but you can buy extended support.

Cognos Controller 11 needs to be installed fresh. You need to uninstall and remove the old version of CC 10 on your server before you install Cognos Controller 11.
Cognos Controller 10.4.2 end of support (EOS) is 30-Sep-2024.  Lifecycle policy Standard (S): minimum 3 years support with extension of 2 years.

Cognos Analytics upgrade  (if you decide to upgrade Cognos Analytics) Date
Copy the media to local hard disk on server d:\install
Export configuration from cognos configuration to backup folder d:\temp\backup
Backup the CA11 images folders and any custom images folders you use like D:\Program Files\ibm\cognos\analytics\webcontent\bi\images or D:\Program Files\ibm\cognos\analytics\webcontent\bi\samples\images 
Backup the controller config file D:\Program Files\ibm\cognos\analytics\templates\ps\portal\ variables_CCRWeb.xml 
Backup PA variables_TM1.xml files from D:\Program Files\ibm\cognos\analytics\templates\ps\portal
Backup PA planning.html and PMHub.html files from D:\Program Files\ibm\cognos\analytics\webcontent
Backup PA tm1web.html files from D:\Program Files\ibm\cognos\analytics\webcontent\bi\tm1\web 
Backup web.config from D:\Program Files\ibm\cognos\analytics\webcontent
Backup the SQL database for content store
Backup the SQL database for audit
Take a screenshot of cognos configuration environment page
Take a screenshot of the members of cognos administrator group
Take a screenshot of the members of cognos controller administrator group
Take a screenshot of the members of cognos controller user group
Check that firewall ports are open Port 25, 80, 9300, 9362, 1433, 389 etc for BI.  
Stop the Cognos Services and set them to manual, reboot the windows server to ensure no Cognos processes are running before you start the installation
Run the setup program for IBM Cognos Analytics Server, the installation will take a long time.
Run the setup program from ( CA 11.2.4 FP3). You can install the fix pack media direct, it is a full installation.  
Open Cognos Configuration and click save  
Ensure the SQL driver is in the folder D:\Program Files\ibm\cognos\analytics\drivers Copy back any planning.html files you have backed up  
Start the Cognos BI service
Check that you can login to IBMCOGNOS
Check file exist in D:\Program Files\ibm\cognos\analytics\templates\ps\portal\ variables_CCRWeb.xml 


When CA11 is up and running, then you can install Cognos Controller.

Cognos Controller 11 upgrade Date
Copy media to server d:\install
Backup all Controller database in SQL server
Export configuration from cognos configuration to backup folder d:\temp\backup
Backup the acl files in D:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer 
Backup the web.config file in D:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer
Take screenshots of application pools and iis timeout settings
Take screenshots of every setting in Cognos Controller configuration Controller configuration is erased when installing a new version, so you need to enter the values back
Backup all under D:\Program Files\ibm\cognos\ccr_64\fcmweb
Backup all under D:\Program Files\ibm\cognos\ccr_64\frontend
Backup the udl files in D:\Program Files\ibm\cognos\ccr_64\Data 
Backup properties file from D:\Program Files\ibm\cognos\ccr_64\server\FAP
If HTTPS is used, backup all certificate stores
Stop all IBM Cognos Controller services
Uninstall the previous version of Cognos Controller
Reboot the server
Install the new version of Cognos Controller 
Stop Internet Information Services (IIS) Manager (the Default Web Site)

Stop IBM Cognos Controller Consolidation

Go to the folder C:\Program Files\ibm\cognos\ccr_64

Search recursively for all instances of the subfolder workarea.

Delete all instances of the workarea folder that appear in the search results.

Install the new fix pack of Cognos Controller
Place the SQL driver sqljdbc42.jar in D:\Program Files\ibm\cognos\ccr_64\server\integration 
Place the SQL driver sqljdbc42.jar in D:\Program Files\ibm\cognos\ccr_64
Add back the information in Cognos Controller configuration and click save
Create the virtual directories in WWW for Cognos Controller 
Update the files for Controller Web with old information
Upgrade your Controller application databases
Create a UDL file and Upgrade your FAP database
If FAP service is on other server, install FAP there
Add back the file
Upgrade the Cognos Controller client on the server – can you login?
Start FAP service – any error in log file?
Create the Cognos Controller Client package for silent installation
Reboot windows server and check you can login to cc

More information:

Cognos Controller 10.4.2200.88
Microsoft Excel 64 bit Microsoft® Excel® for Microsoft 365 MSO (Version 2302 Build 16.0.16130.20684) 64-bit
Microsoft Windows 11


After upgrade to Excel 64 bit, Excel crash at start. The add in for Cognos controller can be for the 32 bit version of the Excel program.


Inside Excel, go to file – options.

Go to Add-ins dialog.

Manage‘ is set to ‘Excel Add-ins‘, and click ‘Go’.

Remove the mark for the first Cognos Controller line (adxloader.controller.excellink). Should look like this when it is correct.

Click OK.

Manage‘ is set to ‘COM Add-ins‘, and click ‘Go’.

The Cognos controller link should point to the 64 bit version of the dll, as above.

Click OK.

Recommendation, is to start Cognos Controller program first, and from inside Cognos Controller click on the icon for excel, to start Excel.

Be patient, Excel take a long time to start.

If you check Excel add-ins when Cognos controller is running it can look like this:


More Information:

Cognos Controller 10.4.2
Microsoft Windows Server 2022


Suddenly user can not login to cognos controller.

They get a error like this:

System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.ArgumentNullException: Value cannot be null.
Parameter name: uriString
at System.Uri..ctor(String uriString)
at System.Web.Services.Protocols.WebClientProtocol.set_Url(String value)
at Cognos.Controller.Common.CRNBridge.CRNBridge.set_EndPointURL(String sURL)
at Cognos.Controller.Proxy.CCRWS.GetUserInfo(String sGuid, String sUser, String passportId)
— End of inner exception stack trace —
at Cognos.Controller.Forms.Common.Main.DoLoginCognos8(Form& frm, Boolean runtimCheck)
at CCR.AppContext.DoLogin()
at CCR.AppContext.Login()


Restart the IIS service on the Cognos Controller server.


Steps to check the issue:

Login to the Cognos Controller server (via remote desktop).

Check that all IBM Cognos service are running.

Start IE and browse to CA11 – does it work?

Start IIS manager and check that all application pools are running.

Go to Components service from control panel administration. Expand COM+ components.

Ensure that “IBM Cognos Controller Consolidation” is running. If not, then restart the IIS from inside IIS manager program.

Check the windows event log for any error message, that can explain why any of above processes have stopped.

More Information:

Cognos Controller 10.4.2


After a reboot of the TM1 server where the FAP service is running, the FAP does not connect to the TM1 services with error in D:\Program Files\ibm\cognos\ccr_64\Server\FAP\error.log file.

DEBUG [fap.service.schedule.ConnectionsPoller] [pool-5-thread-2], Starting connection poller for datamart ‘FAP’ with a 3600000 ms timeout.

ERROR [fap.service.schedule.Scheduler] [pool-5-thread-2], Could not find the TM1 server [tm1:FAP]

Suggested solution:

Change the FAP service to have “Automatic (Delayed Start)” in the windows services.

The Tm1 instance must be started before the FAP service is started.

More Information: