Cognos Analytics 11.1.7
Microsoft Windows 2019 server

How do i change CA11 WLP to use balanced in java?

Suggested solution:

The log file cbs_run_WebSphereLiberty.log say “CBSBootstrapService attempt to load config from “C:\Program Files\ibm\cognos\analytics\bin64/bootstrap_wlp_winx64.xml”
This should mean that the WLP is controlled from the file bootstrap_wlp_winx64.xml. Open file in Notepad++
Change line 37 to;

param condName=”${java_vendor}” condValue=”IBM”>-Xgcpolicy:balanced</param>

save the file and restart the server, will give that WLP use garbage collection Balanced instead of default gencon. Then this will not help you, if you not have a big solution that maybe need it.

WLP settings for Planning Analytics is on the other hand stored in file C:\Program Files\ibm\cognos\tm1_64\bin64\bootstrap_wlp_tm1_winx64.xml

Normally you add the line -Xgcpolicy:balanced to the file C:\Program Files\ibm\cognos\tm1_64\wlp\usr\servers\tm1\jvm.options instead, of doing above.

Edit C:\Program Files\ibm\cognos\analytics\wlp\usr\servers\cognosserver\jvm.options to have the line -Xgcpolicy:balanced  will not work with CA11. You may need to do something more….

More information:

Cognos Analytics 11.1.7
Microsoft Windows 2016 server

After upgrade of Cognos and the IIS gateway settings the large dashboard with many columns does not work. If you use less columns the dashboard work. Error like this:

We can’t retrieve the data from data set….

Inside IIS Manager on your Microsoft Windows server, check the values for Maximum URL length.
Go to your ibmcognos\bi folder and click on “request filtering”.

Click on edit feature settings on the right side.
Update to 8192 or 16000. (adjust other values as needed)
Click OK (the values are saved in C:\Program Files\ibm\cognos\analytics\webcontent\bi\web.config)
Restart the IIS service and test again.

The CA_IIS_Config.bat file should set this values in your windows server:

More Information:

Cognos Analytics 11.1.7
Microsoft Windows 2016 server

On a installation where you use SSL only to the IIS gateway, and not to the Cognos dispatchers.
When try to login to Cognos Analytics HTTPS portal you get a error similar to this;
HTTPS Error 404.0 – Not Found…
Requested URL
Physical Path  c:\inetpub\wwwroot\bi\

Run the CA_IIS_Config script with HTTP instead of HTTPS, so you change the Reverse Proxy Inbound Rule to have Rewrite URL http://ca_servers/bi/{R:0} instead of HTTPS.
Add the certificate server name to the IIS manager – Default web site – bindings. Edit the settings for HTTPS port 443, so you have a host name in the host name field.

After any change to IIS, restart it from a DOS prompt with command: iisreset

From your web browser test that you can browse to the Gateway URL;

More Information:

Cognos Analytics 11.1.7
Microsoft Windows 2016 Server

After upgrade to CA 11.1.7 in a Multi server solution the event studio events are not running all the time, and also you get other errors in cogserver.log file.

CNC-ASV-0048 Error building report template: {0} CNC-ASV-0048 Error building report template: PRS-REQ-0760 The operation “/” “” “” is invalid. Certificate for <servername> doesn’t match any of the subject alternative names:…

CNC-SDS-0222 An error occurred while trying to send a message in message manager

Suggested Solution:

Upgrade your installation to the latest Fix Pack of CA11.1.7

If you restart the IBM Cognos windows service by some script, change the script to instead use the Cognos Configuration program to do the restart. Create a CMD file with this content:


call “C:\Program Files\ibm\cognos\analytics\bin64\cogconfig.bat” -stop

PING -n 31>nul

call “C:\Program Files\ibm\cognos\analytics\bin64\cogconfig.bat” -s

Name the file c:\scripts\birestart.cmd and put your schedule software to use that, instead of the NET STOP command, as stopping Cognos BI from windows may corrupt some temp files.

CA 11.1.7 demands that all server names are in FQDN format.
Stop the Cognos BI service on Windows from Cognos Configuration.
Update all the server name in Cognos Configuration to be FQDN and lowercase. Also ensure the Server Common Name, under Security – Cryptography -Cognos, is the FQDN server name.

Gateway URI
External dispatcher URI
Internal dispatcher URI
Dispatcher URI for external applications
Content Manager URIs
Environment > Configuration Group
Group contact host
Member coordination host
Security > Cryptography > Cognos
Server common name
Subject Alternative Name > DNS names
Subject Alternative Name > IP addresses
Note: You must at DNS names enter both the FQDN and HOSTNAME to make the logging to work.
Check that the windows firewall does not block the port used by cognos – particular ports 9300, 9362, 4300, 5701, 9301. They need to be open between Cognos servers.

Before start of the Cognos from Cognos Configuration, clean out some folders to ensure there are no old settings around.
Backup and then remove the analytics/configuration/data/flipper folder
(You need a backup of flipper folder, like file flipper\config\global\, as it will erase your new cognos advance settings, or you need to manually add the values back.)
Backup and then remove the analytics/configuration/data/discovery folder
Backup and then remove the analytics/wlp/usr/servers/cognosserver/workarea folder
Backup and then remove the analytics/wlp/usr/servers/dataset-service/workarea folder
Backup and then remove the analytics/javasharedresources folder
Backup and then remove the analytics/temp folder
Backup and then remove the analytics/logs folder
Backup and then remove the analytics/data folder

You can check the setup of Configuration Group by browse in IE to the server first on
and login, then change the URL in IE, and browse to
This json file can be saved.

If you have old reports that fails, please try to upgrade the reports to the latest version.

  1. Open IBM Cognos Administration.
  2. On the Configuration tab, click Content Administration.
  3. Click the arrow on the new content maintenance button New content maintenance on the toolbar, and then click New Report Upgrade
  4. Type a name for the upgrade task and, if you want, a description and screen tip. Click Next.
  5. Select the packages and locations for the report specification you want to upgrade. Click Next.

    If you upgrade report specifications by folder, all reports in the folder will be upgraded.

  6. Choose one of the following:
    • Save and run once opens the run with options page.
    • Save and schedule opens the scheduling tool.
    • Save only allows you to save the upgrade so that you can run it at a later time.

    Give time to upgrade all reports and all templates in your Cognos solution. To upgrade users my folders, select Directory – My Folder of AD (your namespace).

If schedule or events are not working, try dropping the NC* tables with this script:

1. Stop the Cognos Service
2. Take a physical backup of the Content Store or Notification database
3. Select the appropriate folder for your content store or notification database type ,like C:\Program Files\ibm\cognos\analytics\configuration\schemas\delivery\sqlserver for SQL.
4. Run NC_DROP_MS.sql against the content store or notification database in Microsoft SQL Management Studio.
4. Restart Cognos Services.

Should dropping the NC* tables not resolve the issue, then restore the content or notification store from the last backup version.

CA 11.1.x have made changes to the IIS setup for URL rewrite, manually change IIS settings to the new values or use the script in folder: C:\Program Files\ibm\cognos\analytics\cgi-bin\templates\IIS

Check the rules under ibmcognos and bi folder in IIS manager. Compare yours to the latest webpage

  • Name is Event Studio.
  • Pattern is ^(ags|cr1|prompting|ccl|common|skins|ps|cps4)/(.*)
  • Open the Conditions section.
  • Change the Logical Grouping to Match Any
  • Click Add.
    • Condition input is {HTTP_REFERER}
    • Check if input string is Matches the Pattern
    • Pattern is v1/disp
    • Check Ignore case.
  • Click Add
    • Condition input is {HTTP_REFERER}
    • Check if input string is Matches the Pattern
    • Pattern is (ags|cr1|prompting|ccl|common|skins|ps|cps4)/(.*)\.css
    • Check Ignore case.
  • Action type is Rewrite
  • Rewrite URL is /ibmcognos/{R:0}
  • Check Stop processing of subsequent rules.
  • Click Apply and Back to Rules.

In IIS Manager on the Application Pool for Cognos (ICApool) change to 10 for Maximum Worker Processes, if you have many users in Cognos.


If nothing helps – contact Cognos Support.

More information:

Cognos Controller 10.4.2
Microsoft Windows Server

When a user start Cognos Controller Client on Citrix server a second time they get a error:
System.Unauthorized Access Exception: Access to the path c:\cognos\ccr\ccr.config is denied at System.IO…Error.WinIOError( Int32 errorCode, String maybeFullPath )

Suggested Solution:
Disable the use of FSLogix.
Cognos Controller update the ccr.config file during start of client, and also when the user change personal parameters inside the Cognos Controller client.
Each user of Cognos Controller need there own ccr.config file. If the file is not there, this error can show up.
They are normally in folder c:\users\%username%\appdata\roaming\cognos\ccr
and are created during login from the default file in folder c:\program files\ibm\ibm cognos controller local client\ccr.exe.config

The understanding of the orchestration of FSlogix with profiles will make logical sense when you look at the pieces and parts that FSLogix puts together.

  • FSLogix apps is an installer that is loaded on WVDSH00 and is part of every deployment done with WVDSH00
  • Registry entry is configured on WVDSH00 to enable FSLogix and point the profile storage to \\FS01\Profiles\%username%
  • There is another registry entry that excludes DESKTOP, DOCUMENTS and FAVORITES folders from FSLogix profile because those are redirected to \\FS01\USERS\%username% folder. This registry entry points at an XML file that tells FSLogix to exclude those folders. This file is \\FS01\Profiles\redirections.xml

More Information:

App-V is not officially supported by IBM. But the following tips helped package/deploy the Controller client successfully:

    • (1) Re-package the Cognos Controller client *without* capturing (saving) the following folder (inside the App-V package):


(2) To avoid an ‘Excel Link is not installed’, configure the setting ‘local interaction’ to ‘FALSE’ (within the OSD file for the main Cognos controller application).

The Controller client reads from and writes to a configuration file called ‘ccr.config’.

  • This is located here: %APPDATA%\Cognos\CCR\ccr.config
  • By default, this is: C:\Users\%USERNAME%\AppData\Roaming\Cognos\CCR\ccr.config

if the I.T. department have modified the value for %APPDATA% (for example redirected user’s profiles to be stored on a remote network file share) then this means that ccr.config reads/writes are slower.

  • In some environments, these are so slow that Controller aborts trying to read/write to that location, and falls back to a default local location (C:\Cognos\ccr\)
  • However, only one person at a time can use that location, therefore errors will occur (when trying to read the configuration file) if a different user tries to read that file.

Use the “CacheDir” parameter to cause the Controller local client to move the storage location of the ‘cache files’ (*.DSS and *.DSD) into subfolders of the CacheDir.


For example, if “CACHEDIR” is configured to be the value “D:\Controller\Cache” then these files will created/stored inside folders such as:


NOTE: The configuration file (CCR.CONFIG) is unaffected by this parameter, and will stay inside the default location (%APPDATA%\Cognos\ccr)


Do NOT modify the location of the “Cache Dir” to either (a) a mapped network drive or (b) a network UNC path.
Doing this will seriously affect the performance/speed of Controller, and also the stability (may create error messages).

Logon to client PC using the *same* Windows user that launches/runs Controller
Create a folder which will be used to store the cache files (for example: D:\Controller\Cache).


Do not choose a network drive letter (or UNC path).
Instead, you MUST choose a location which is on one of the client device’s local hard drives.
This does not need to be its C: drive, although it must be a local hard drive
For example, you could choose: D:\Controller\Cache

3. Launch Windows Explorer
4. Open the folder where Controller is installed.

For example, by default this is here: C:\Program Files\ibm\IBM Cognos Controller Local Client

5. Open the file “CCR.exe.config” inside Notepad
6. Search for the entry similar to the following:

<add key=”CacheDir” value=””/>

7. Modify this entry appropriately, for example similar to the following:

<add key=”CacheDir” value=”D:\Controller\Cache” />

8. Save and test

You will notice that, after launching Controller, now all the cache files are created inside the following folder: D:\Controller\Cache\<Windows_Username>\Cognos\CCR

Cognos Analytics 11.1.7
Microsoft Windows 2016 server

There are 3 jave.exe on the Cognos Analytics server, what are they for?

Java.exe (with most memory usage is Query Service, if you use Dynamic Cubes) command line c:\program files\ibm\cognos\analytics\ibm-jre\jre\bin\java.exe
Java.exe (with command line ..\ibm-jre\jre/bin/java.exe is the Content Manager and WLP service for the cognos portal) it have -Xgcpolicy:gencon
Java.exe (with least memory usage is the exploration engine in CA11) command line c:\program files\ibm\cognos\analytics\ibm-jre\jre\bin\java.exe” -Xms1024m -Xmx8192m -XX:MaxDirectMemorySize=512m

The 3 java.exe process for exploration in CA11 is part of the query service and is configured with advanced parameters in cognos connection;

  1. From Manage > Administration console, open Cognos Administration.
  2. On the Configuration tab, click Dispatchers and Services, and click your dispatcher name.
  3. In the list of services, locate the Query service, and click its properties icon Set properties.
  4. On the Settings tab, under Category, select Environment.
  5. Next to Advanced settings, click Edit.
  6. Select the Override the settings acquired from the parent entry check box.
  7. Type or copy the parameter names and their values, from the Cognos documentation.
  8. Click OK.
  9. Restart the Query service.

The Java.exe for Query Service memory usage is also controlled from cognos connection.

JVM heap size limit for the query service: Specifies the maximum size, in MB, of the JVM heap.

JVM garbage collection policy: Specifies the garbage collection policy used by the JVM.

Go to Cognos Administration page, and click on System in the left.
Click the arrow at All servers and select Services – Query.
Now you only see the QueryService for each server. Click on arrow and select Set properties.
Change the Initial JVM heap size for the query service to a unique value like 2048, then after a restart it is easier to tell the jave.exe apart from each other.

The Java.exe for content manager and WLP is setup from inside Cognos Configuration.
If you have the RAM in the server, it can be increased to 24576 MB.  The start up time of Cognos will be longer, when the WLP use more memory.

  1. Start IBM Cognos Configuration.
  2. In the Explorer window, expand Environment > IBM Cognos services, and then click IBM Cognos.
  3. In the Properties window, change the value for Maximum memory in MB.
    • To reduce the startup time, memory footprint, and resources that are used, use the default setting of 8192.
    • This value can be adjusted based on available system resources.
  4. From the File menu, click Save.

More information:

Cognos Analytics 11 CP4D

How report on a DB2 database?

Suggested Solution:
Depending on what data source you are going to connect to – the way may be different.

Login to Cloud pak for data to setup the data source (this is only for Cognos Content Store called BLUEDB).

Click on menu icon to get to the connections

Click on new connection

Enter a name for the connection and click on the drop down menu to select type of data source. When you select DB2, you get other fields to complete.

Enter the IP address of the database server host.
Enter the port for the DB2 database, default is 50000 – but this you need to change when you setup your DB2 server, to something else like 50500.
Enter the name of the database.
Enter the name of the user to access the database (can be DB2 default user db2inst1) and enter the password.
Scroll down and click on Test connection.

Click on Create.

You have now a data source in CP4D.

Click on menu and select My instances – to see what applications are running.

Click on the dots to open the menu on the right side of your application, and click on open to go to Cognos Analytics.

If security is setup correct, you should be logged in automatically.

To setup a data source for CA11, you can use the same as you done in CA11 on Windows. Described below;

Setup in Cognos Analytics 11

Click on Manage icon in lower left corner and select Data Server Connections

Click on + to create a new data connection, the dialog will expand to the right.

Select DB2 in this case

First enter the jdbc:db2:// to your database.
Scroll down and click close
Select Use the following signon

Click on ? to create a new signon, enter the user and password that will connect to the DB2 database.
Change the name for the connection to SAMPLE2.

Change the name of the connection and click save.

Click on Test and after success, click on schemas tab.

Click on dots to show the options, and click on Load metadata.

Wait for the metadata to load.

Click on new icon and select Data module.

Click on the data icon and select your data source from the list. New dialog opens automatic.

Click on the schema to work with and click OK.

Click on Discover related tables and click Next

Cognos Analytics will show in word diagram the most popular fields. Select 3 of them and click next.

Table relations is shown, click OK.

Click on save icon in top left corner.
Select to save as.

Click on my content or the folder where you want it to be saved.
Enter a name for the data module.
Click on save.

Click on new icon and exploration.

Select the folder, select the data module and click add.

Enter a table name or click on the boxes to select the data you want to find out about.

Select one of the charts on the right, if they fit your question.

When you are satisfied with your chart, click save icon to store the report in the folders inside Cognos Analytics.

More information:

Cognos Analytics 11.1.6 Product_version=11.1 R6
Microsoft Windows 2016

Error when start cognos from cognos configuration like this;
[Check NIST 131A conformance]
[ WARNING ] CAM-CRP-1632 The selected PDF Confidentiality algorithm is not permitted by the NIST SP 800-131A standard. You must change the selected algorithm to a stronger algorithm such as ‘AES-256’. Note that you may need to install the JRE’s unlimited jurisdiction policy files to enable all of the supported algorithms


Open first Cognos Configuration and check that it says 128 at Cryptography > Cognos > field “PDF Confidentiality Algorithm – Advanced encryption standard with Cipher Block Chaining (CBC) mode 128 bit key”. Stop cognos service and close Cognos Configuration.
Backup the files in folder C:\Program Files\ibm\cognos\analytics\ibm-jre\jre\lib\security\ to c:\temp\security

Download the new policy zip file from
Unzip the file in a new folder (c:\install), creating folder C:\install\unrestricted.

Copy the two new files (US_export_policy.jar and local_policy.jar)to folder C:\Program Files\ibm\cognos\analytics\ibm-jre\jre\lib\security\policy\unlimited

Open Cognos Configuration and go to Cryptography > Cognos. Change PDF Confidentiality Algorithm and Confidentiality Algorithm to Advanced encryption standard with Cipher Block Chaining (CBC) mode 256 bit key.

Right-click on supported ciphersuites and select “Reset to Default”.

Save the configuration and start the Cognos service.


More information: