Cognos Controller Web 10.4.2
Microsoft Windows 2016 Server

User can not login to Cognos Controller Web after update to HTTPS.

In folder D:\Program Files\ibm\cognos\ccr_64\frontend\logs

error in log file can be;

error from web proxy: { Error: Client network socket disconnected before secure TLS connection was established at TLSSocket.onConnectEnd (_tls_wrap.js:1088:19)
at Object.onceWrapper (events.js:277:13)
at TLSSocket.emit (events.js:194:15)


Check that the local windows firewall allow connections on port 3443.

Add a inbound rule that allow communications on port 9080,9081,3443,3000.

Controller web ports are set in the config.js and server.xml file.

<httpEndpoint host="*" httpPort="3000" httpsPort="3443" id="defaultHttpEndpoint">
<httpOptions removeServerHeader="true" />

More information:


Cognos Controller Web 10.4.2

Microsoft Windows 2016 server


When change Controller Web configuration, user can not login to Controller web. You get a error in the log file that it does not work.  There could be error like this:

[ERROR   ] CWPKI0033E: The keystore located at d:/Program Files/ibm/cognos/ccr_64/fcmweb/wlp/usr/servers/fcm.web/resources/security/key.jks did not load because of the following error: Keystore was tampered with, or password was incorrect…

Check log file D:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\logs\messages.log

Check log file D:\Program Files\ibm\cognos\ccr_64\frontend\logs\fcmwebui-stderr.2022-09-13.log

Server ip written in backend-url.js!
Express server listening on port 9080
error from web proxy: { Error: connect ECONNREFUSED
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)
syscall: ‘connect’,



Check that you use the same password for your PFX file you import certificate from as you use for the key.jks file you created for the Controller Web setup.

Update the file config.js in folder D:\Program Files\ibm\cognos\ccr_64\frontend to correct password


“secure”: false //set this to false when you use custom certificates for Controller Web

“ssl”: {
// certificates
“key”: fs.readFileSync(__dirname+”/keyfile.key”), //__dirname points to ccr_64\frontend
“cert”: fs.readFileSync(__dirname+”/cert.crt”),

Update the file server.xml in folder D:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web to correct password


<keyStore id=”defaultKeyStore” password=”TheNewPasswordHere” sslProtocol=”SSL_TLS” />

Save the changes and restart all 3 IBM Cognos Controller Web services.

Wait at least 20 minutes for it to load fully, before you test.


More information:


Cognos Controller 10.4.2
Microsoft Excel 2013
Microsoft Windows 2019 server


Data entry does not work in Cognos Controller Client for a few users on the Citrix platform.

Error message:

ControllerForms12 … Object variable or With block variable Object reference not set … ActivateDataEntryForm…

Error launching menu item “Controller Link”

Unable to get the FullName property of the addin class at System.Runtime.Type.ForwardCallToInvokeMember .. a WrapperTypes.

Suggested solution:

Open Excel that is used with Cognos Controller for the user who have issues.

Go to Options – Add-ins, click on the Go button at the bottom for Excel Add-Ins.

Uncheck the link for “Cognos Controller Link for Microsoft Excel” add-in, press OK, and exit excel.
Log off Citrix session and log off Citrix Connection Center.
Log out from your computer and log in again.
Start Excel in Citrix as before.

Go to Options – Add-ins – Go button for Excel Add-ins.

Click on Browse

Find C:\Program Files\ibm\IBM Cognos Controller Local Client\adxloader.Controller.ExcelLink.dll
Click Open.
On question that “a file named C:\Program Files\ibm\IBM Cognos Controller Local Client\adxloader.Controller.ExcelLink.dll  already exists in this location. Do you want to replace it?” Click YES.
Remove any other add in, that can interfere, like Thinkcell.
Click OK
Exit Excel.

Start Cognos Controller client and try again.

Ensure the user have the same version of Excel on Citrix as on other Citrix servers or on her laptop.

More Information:

Cognos Controller Web 10.4.2
Microsoft Windows 2019 server


After applied a DNS alias to the Cognos Controller server, the users can not login to the Controller Web.

They get a error like Server is not reachable or still initializing, please refresh the page in a few seconds


You must update the D:\Program\ibm\cognos\ccr_64\frontend\config.js file with the URL the end user will use to access Cognos Controller Web.

If you change it from a server-name to a DNS alias, then open config.js in notepad++

 //Details for Controller UI service 
"expressJs": {
"host": "", //interface used by Controller Web UI Service
"port": "9080", //port used by Controller Web UI Service
"options": {

Change the interface value to your DNS alias. The controller web backend connection at line 14 can be left with the server host name.

Save the file.

Restart the 3 Controller web services.

More Information:

Cognos Controller 10.4.2
Microsoft Windows 2019 server

After upgrade of Cognos Controller to a new version, the users get a error message when they start Cognos Controller Client program.

“The version of Controller requires database version 992.”


Wait for the IT department to upgrade the Cognos Controller Client installation on the Citrix server you are using. Cognos Controller 10.4.2 use database version 1010.

More Information:

Cognos Controller 10.4.2
Microsoft Windows 2019 server

When you login to cognos controller client, you get a error message of this kind;

Number: 76
Source: mscorlib
Description: Could not find a part of the path ‘C:\Users\nnnnn\AppData\Roaming\Cognos\CCR\ADMdb_cognoscontroller.local,1433CognosControllerdatabase’.
at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)
at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)
at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc)

Suggested Solution:

Click OK to get past the error message, and still login to Cognos Controller Client program.

Clear the local cache by going to Maintain – Special Utilities – Clear Local Cache.

Close Cognos Controller program and try to login again. Did the error go away?

Can be garbage in the cache of files in folder C:\Users\nnnn\AppData\Roaming\Cognos\ccr, that are cleared by this action.

More Information:

Cognos Controller 10.4.2
Microsoft Windows 2019 server

When open FAP.UDL file with DBCONV.exe program to upgrade the database you get a error.

ERROR: java.lang.NullPointerException

Possible solution:

The UDL file does not contain a password.

Copy the fap.uld file to folder D:\Program files\ibm\cognos\ccr_64\Data

Open the file in Cognos Controller configuration and add a password.

Click on test connection icon.

Click on arrow to start the Database conversion program.

Select FAP DB.

Click Connect.

Check if the numbers are different, then you need to click on Upgrade button.

Close the program.

Remove the fap.udl file from the \ibm\cognos\ccr_64\Data folder.

Also, ensure the SQLJDBC42.JAR file is in the folder D:\Program files\ibm\cognos\ccr_64

More Information:

Cognos Controller 10.4.2 if8 CONTRL_UPDATE_version=CCR-AW64-ML-RTM-10.4.2000.1064-0
Microsoft Windows 2016 server
Planning Analytics  TM1-AW64-ML-RTM-11.0.911.20-0

After upgrade of TM1 (Planning Analytics) to a newer version than then the Cognos Controller FAP does not work.
The FAP IP stop with a error.

The TM1ProcessError can be:

Cannot convert field number 17, value “123456” to a real number

Error: Data procedure line (0): 01004[Microsoft][ODBC SQL Server Driver]String data, right truncation


Upgrade Cognos Controller software to a later version.

  1. Install Controller 10.4.2 IF 17
  2. Stop the Windows service of the TM1 server that is connected to FAP.
  3. Stop the Windows service IBM Cognos FAP Service.
  4. Manually delete the existing <…>MonthlyCompanyDetails_TextImportData TI process from inside TM1 Architect.
  5. Start the Windows service of the TM1 server that is connected to FAP.
  6. Start the Windows service IBM Cognos FAP Service.
  7. Do a full FAP IP.


More information:

These errors occur because Planning Analytics and later does not support FAP jobs with comments containing more than 2047 characters.  The existing <…>MonthlyCompanyDetails_TextImportData TI process that you upgraded from your previous TM1 environment does not adhere to this new limitation.

If you upgrade Planning Analytics 2.0.9, you must upgrade Cognos Controller 10.4.2 to a later version.

Cognos Controller 10.4.2
Microsoft Windows 2016 server


We need to install a fix pack/interim fix to cognos controller – do we also need to upgrade the cognos controller client?

Suggested solution:

Do a test upgrade in your test environment, and see if the client works without upgrade the Cognos Controller client.

When you do a installation of a new version, you must upgrade the cognos controller client. But if you only install a Interim fix then the client installed can be used without upgrading.

Any fixes that are in the client side, like help – content issues, will not be solved.

Recommendation is to always upgrade the cognos controller client too.

Before installation we had in the client this version:

IBM Cognos Controller Version 10.4.2000.293
Integration Version 10.4.2000.145
Installer/Updater Kit Version 10.4.2000.1064

after installation we had this in cognos controller client – help – system info:

IBM Cognos Controller Version 10.4.2000.293
Integration Version 10.4.2000.145
Installer/Updater Kit Version 10.4.2000.1111

The client looks like it is working, but not any bugfixes that are in the Cognos Controller client code is not part of the solution.

Supported is to have both cognos controller client and cognos controller server at the same version.

You can check the version of cognos installed in the cmplst.txt file, often found in folder D:\Program Files\ibm\cognos\ccr_64

CONTRL_UPDATE_name=IBM Cognos Controller Update
[Main Applications]

When doing a upgrade of cognos controller to a interimfix it is important that you;

Note down cognos controller configuration for report server URL.

Specifically, stop the following Windows services:

  • IBM Cognos
  • IBM Cognos Controller Batch Service
  • IBM Cognos Controller Consolidation
  • IBM Cognos Controller Java Proxy
  • IBM Cognos Controller Reports
  • IBM Cognos Controller Web
  • IBM Cognos Controller Web Spreadsheet Service
  • IBM Cognos Controller Web UI
  • IBM Cognos FAP Service
  • WWW service

Stop COM+ object for Cognos Controller.

Backup the controller web folder

D:\Program Files\ibm\cognos\ccr_64\fcmweb and D:\Program Files\ibm\cognos\ccr_64\frontend

Check that no JAVA processes is running, before you start the upgrade.

After upgrade, Cognos Controller Web need to be reconfigured.

More information:

Currently Supported Versions of Controller (incl. Interim Fixes):

Updater Kit Build CCR Version DB Version Comment
10.4.2000.1111 10.4.2000.311 10.4.2 IF17 1010 Generally available (FixCentral)
10.4.2000.1108 10.4.2000.300 10.4.2 IF16 1010 Generally available (FixCentral)
10.4.2000.1098 10.4.2000.300 10.4.2 IF15 1010 Generally available (FixCentral)
10.4.2000.1079 10.4.2000.300 10.4.2 IF14 1010
10.4.2000.1078 10.4.2000.300 10.4.2 IF13 1010
10.4.2000.1076 10.4.2000.300 10.4.2 IF12 1010
10.4.2000.1073 10.4.2000.300 10.4.2 IF11GA 1010 Generally available (FixCentral)
10.4.2000.1070 10.4.2000.296 10.4.2 IF10 1010
10.4.2000.1067 10.4.2000.296 10.4.2 IF9 1010
10.4.2000.1064 10.4.2000.293 10.4.2 IF8 1010
10.4.2000.1063 10.4.2000.292 10.4.2 IF7GA 1010 Generally available (FixCentral)
10.4.2000.1018 10.4.2000.270 10.4.2 IF3 1010  
10.4.2000.1013 10.4.2000.267 10.4.2 IF2 1010  
10.4.2000.1002 10.4.2000.259 10.4.2 IF1GA 1010 Generally available (FixCentral)
10.4.2000.185 10.4.2000.252 10.4.2 RTM 1010 Available via Passport Adv. (full install)


Cognos Controller 10.4.2

Microsoft Windows 2019 server


At new installation, i after selection of database, in cognos controller client, are then stuck.

No more information.


The cognos controller client uses port 80 to talk to the cognos controller server, but after the selection of database, it will if SSO is active, connect to Cognos BI to validate the user.

This happens on the port listed in Cognos Controller Configuration as Report Server.

If this is port 9300, then port 9300 need to be open in firewall between server and client. This is not the normal case.

You should instead change the Cognos Controller Configuration for Report server to use port 80.

Wrong line at report server:

Correct line at report server:

More information: