Cognos Controller 11.0.1


Do you have a checklist of what is needed to do a upgrade to Cognos controller 11?


Best is if you create a own checklist for your environment, that you can use at every upgrade. Below is a suggested 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
Run the setup program from IBM Cognos Analytics Server
Run the setup program from ( CA 11.2.4 FP3)  
Open Cognos Configuration and click save  
Ensure the SQL driver is in the folder D:\Program Files\ibm\cognos\analytics\drivers  
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
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:

Cognos Controller 10.4.2
Microsoft Windows 2022 server


Users are prompted with the native login dialog, instead of the SSO (single sign on), that should be using the CAM (Cognos Analytics login).

This happens after the Cognos Controller Windows server was restarted last night.


Ensure that the Component service (found under Administrative Tools) have the COM+ component IBM Cognos Controller Consolidation running. Right click on IBM Cognos Controller Consolidation and select Start, if they are not running.

Ensure that the Cognos Controller Configuration, is set to CAM Authentication in the Server Authentication dialog. Even if it is correct set, change to native, and then back to CAM authentication. Then click on save icon in Controller Configuration.

If above works, then it can be that when the Windows server was restarted, and some of the controller configuration values was not picked up by the system.



More information: 

Cognos Controller 10.4.2
Microsoft Windows 2012 Server


When run a standard report, the BI session start, but you get a error that you do not have rights to the package.


/messageString></message></messages> Spåra bakåt:RSReportService.cpp(734): QFException: CCL_CAUGHT: RSReportService::processImpl()RSReportServiceMethod.cpp(254): QFException: CCL_RETHROW: RSReportServiceMethod::process(): asynchRunSpecification_RequestRSASyncExecutionThread.cpp(887): QFException: RSASyncExecutionThread::checkExceptionRSASyncExecutionThread.cpp(331): QFException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): asynchRunSpecification_RequestRSASyncExecutionThread.cpp(932): QFException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): asynchRunSpecification_RequestRSRequest.cpp(1656): QFException: CCL_THROW: RSRequest::executeInteractivePrompting()RSQueryMgr.cpp(840): QSModelNotFound: CCL_RETHROW: RSQueryMgr::getListIteratorRSQueryMgr.cpp(912): QSModelNotFound: CCL_RETHROW: RSQueryMgr::getResultSetIteratorRSQueryMgr.cpp(1020): QSModelNotFound: CCL_RETHROW: RSQueryMgr::createIteratorRSQueryMgrBasic.cpp(296): QSModelNotFound: CCL_RETHROW: RSQueryMgrBasic::executeRsapiCommandRSQueryMgrBasic.cpp(669): QSModelNotFound: CCL_THROW: RSQueryMgrBasic::processExceptionRSQueryMgrExecutionHandlerImpl.cpp(167): QSModelNotFound: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()RSFaultHandler.cpp(193): QSModelNotFound: RSFaultHandler::handleNonCriticalExceptionQFSSession.cpp(1190): QSModelNotFound: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1188): QSModelNotFound: CCL_CAUGHT: QFSSession::ProcessDoRequest()QFSSession.cpp(723): QSModelNotFound: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSXQEModelChecker.cpp(90): QSModelNotFound: CCL_RETHROW: QFSXQEModelChecker::IsModelPointingToTheNewStack()Source/QECMAuthentication_4.cpp(6149): QSModelNotFound: CCL_THROW: QE


The Cognos Controller server have lost the knowledge of that the package name is “Controller”, go into the Cognos Controller configuration.

Go to report server tab.

Ensure the package name is Controller.

And press SAVE anyway to ensure the settings are saved.

Exit Cognos Controller Configuration.

Start Cognos Controller Client and test the standard report again.

More Information:


Cognos Controller 10.4.2 fix pack 2
CONTRL_UPDATE_name=IBM Cognos Controller Update
Microsoft Windows 2019 server


When run a standard report in Cognos Controller program, the adobe program starts up and give an error message.


Change the Cognos Controller server to use the internal pdf viewer.

1. Obtain a short amount of downtime (nobody logged onto Controller)
2. Logon to the Controller application server
3. Browse to the folder C:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer
4. As a precaution, create a backup copy of the file:  web.config
5. Use Notepad to edit the file   web.config
6. Locate the section   <appSettings>
7. Add the following line into that section:
    <add key="useInternalPdfViewer" value="true" />
Save the file, and restart the server to test again.
More Information:

Cognos Controller 10.4.2 fix pack 2
CONTRL_UPDATE_name=IBM Cognos Controller Update
Microsoft Windows 2019 server


After the upgrade to the controller fix pack, how do i change to get standard reports to show in HTML as they did before?

Before it looked like this:

after upgrade it look like this:


You don’t. As the use of WebView2 from Cognos Controller 10.4.2 fp1 there is only possible to see reports in PDF or XLS.


Other information:

Change to use Cognos Controller own pdf viewer:

1. Obtain a short amount of downtime (nobody logged onto Controller)
2. Logon to the Controller application server
3. Browse to the folder ‘ControllerProxyServer’
  • TIP: By default this is located here: C:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer
4. As a precaution, create a backup copy of the file:  web.config
5. Use Notepad to edit the file   web.config
6. Locate the section   <appSettings>
7. Add the following line into that section:
    <add key=”useInternalPdfViewer” value=”true” />
To change the order of report generation in Cognos Controller client:
The following must be done on a per-user basis:

  1. Launch Controller
  2. Click ‘Maintain – Installation – Local Preferences
  3. Add a new key called ‘StandardReportPreviewFormat‘, with a value of either ‘html‘ or ‘pdf‘ or ‘xls‘ or ‘xml
  4. Click ‘save’

NOTE: If you change the setting so that the default report is ‘pdf’, then be aware that the report will take longer to view (longer to initially display). This is because there is more workload that the Controller application/report server must perform, in order to generate a ‘pdf’ report (compared with the default ‘html’ format). In other words, the end user(s) may perceive this as a performance loss.

Use the undocumented local preference ‘StandardReportBackProc‘ which will stop the PDF rendition in Cognos Controller client.

Each individual end user must perform the following themselves:

1. Launch Controller and logon as normal
2. Click ‘Maintain – Installation – Local Preferences
3. Inside the ‘key‘ column, create a new entry called: StandardReportBackProc
4. Click ‘Save’
5. Exit Controller
6. Re-launch Controller and test
  • Inside the corresponding ‘value‘ column, create a new entry: false

Adobe Reader X . to make the pdf show up inside the cognos controller report window:

1. Launch Adobe Reader
2. Click “Edit – Preferences”
3. Click on “Internet” section
4. TICK “Display PDF in browser

The Adobe Reader client installs both the ‘main’ PDF reader tool (the full client application) and also a smaller ‘web client’.

  • This Adobe Reader web client is installed as a plugin in Microsoft Internet Explorer
  • By default, this ‘web client’ is what gets activated inside the Cognos report display box.

Unfortunately, in some environments this ‘web client’ suffers from an inability to save more than one PDF file.


Cognos Controller 10.4.2 fix pack 2
CONTRL_UPDATE_name=IBM Cognos Controller Update
Microsoft Windows 2019 server


Inside Cognos Controller Client, when using java menu like jobs – define or command center, you get a error.

Caused by: Failed to launch!

When try to connect to database in DBconv program, you get a error.


Internal Exception: java.sql.SQLException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: “The server selected protocol version TLS10 is not accepted by client preferences [TLS12]”. ClientConnectionId:ab713261-e19e-4c2d-b02b-8e7bce540fae DSRA0010E: SQL State = 08S01, Error Code = 0

Error Code: 0

You can check controller web error in files in folder C:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\logs


The java version that is shipped with Cognos Controller 10.4.2 fp2, is set default to only allow TLS 1.2 communication.

Upgrade SQL server to support TLS 1.2 or as a workaround change the java 8 system to support TLS 1.0 and TLS 1.1

Go into the folder C:\Program Files\ibm\cognos\ccr_64\bin64\jre\8.0\lib\security open the file in notepad++

Change this line:

jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, DH keySize < 1024, DESede, \
EC keySize < 224, 3DES_EDE_CBC, anon, NULL, DES_CBC

To this line:

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, DESede, \
EC keySize < 224, 3DES_EDE_CBC, anon, NULL, DES_CBC

by remove the TLSv1, TLSv1.1 value, the system will support TLS 1, TLS 1.1.

Also go into the Controller Web folder, and do the same change.

Open C:\Program Files\ibm\cognos\ccr_64\fcmweb\jre\lib\security\ file in notepad++

# In some environments, certain algorithms or key lengths may be undesirable
# when using SSL/TLS. This section describes the mechanism for disabling
# algorithms during SSL/TLS security parameters negotiation, including
# protocol version negotiation, cipher suites selection, signature schemes
# selection, peer authentication and key exchange mechanisms.
# Disabled algorithms will not be negotiated for SSL/TLS connections, even
# if they are enabled explicitly in an application.
# For PKI-based peer authentication and key exchange mechanisms, this list
# of disabled algorithms will also be checked during certification path
# building and validation, including algorithms used in certificates, as
# well as revocation information such as CRLs and signed OCSP Responses.
# This is in addition to the jdk.certpath.disabledAlgorithms property above.
# See the specification of “jdk.certpath.disabledAlgorithms” for the
# syntax of the disabled algorithm string.
# Note: The algorithm restrictions do not apply to trust anchors or
# self-signed certificates.
# Note: This property is currently used by the JDK Reference implementation.
# It is not guaranteed to be examined and used by other implementations.
# Example:
# jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048, \
# rsa_pkcs1_sha1
jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, DH keySize < 1024, DESede, \
EC keySize < 224, 3DES_EDE_CBC, anon, NULL, DES_CBC

# Legacy algorithms for Secure Socket Layer/Transport Layer Security (SSL/TLS)
# processing in JSSE implementation.

Save the file.

Reboot the windows controller server to make the change take effect.

More information:

Cognos Controller 10.4.2
Microsoft Windows 2019 server


Scheduled optimization of the cognos controller database does not work from inside the cognos controller program. If you run it manually direct, then it works.

Error message: Session Manager login failed – unable to connect to the remote server


When change Cognos Controller to use HTTPS, you must update all files to have it. The Controller Batch Service look into the file CCRBatch.exe.config at D:\Program Files\ibm\cognos\ccr_64\server folder.

Open file in notepad and edit the line WSSurl;

<add key="numberOfThreads" value="1" />
<add key="dbPollingFrequency" value="20" />
<add key="WSSUrl" value="" />

Save the file, reboot the windows server for the change to take affect.

You may need to update this files when you change to HTTPS;

D:\Program Files\ibm\cognos\ccr_64\server\CCRProxy.options

D:\Program Files\ibm\cognos\ccr_64\ControllerProxyServer\web.config

C:\Program Files\ibm\IBM Cognos Controller Local Client\ccr.exe.config

D:\Program Files\ibm\cognos\analytics\templates\ps\portal\variables_CCRWeb.xml



More Information: