Cognos Controller 10.4.2 IF7

CONTRL_UPDATE_name=IBM Cognos Controller Update

CCRPORTAL_name=IBM Cognos Controller Portal

Microsoft Windows 2019 server

One a fresh new Windows server, after installation of Cognos Controller program for the first time, there is missing COM+ applications for Cognos Controller in Component Services.

Uninstall Cognos Controller from the server, leave a few files left, as below picture show.

Then run the installation again. Select everything.
This can help in many cases.

Other things to check;
Run below power shell command to check that NET framework 4.7.2 is installed:

(Get-ItemProperty “HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full”).Release -ge 461808

More information:

Cognos Analytics 11.0.12
kit_name=IBM Cognos Analytics
Microsoft Windows 2016 server

After restart of servers the Cognos BI system does not respond. The users see this message:

The IBM Cognos gateway is unable to connect to the IBM Cognos BI server. The server may be unavailable or the gateway may not be correctly configured.

Error in cognosserver.log file:

com.cognos.accman.jcam.crypto.CAMCryptoException: CAM-CRP-1093 Unable to read the contents of the keystore ‘D:/Program Files/ibm/cognos/analytics/configuration/certs\CAMKeystore’. Reason: stream does not represent a PKCS12 key store


First, try to restart the IIS server on the Cognos Gateway with the dos command: IISRESET

If that does not help, create new cryptographic keys;
“C:\Program Files\ibm\cognos\analytics\bin64\cogconfigw.exe” open to start cognos configuration.

Stop the running of Cognos BI in Cognos Configuration.

From inside Cognos Configuration, click ‘File > Export As’.

Choose ‘Yes’ at the prompt and save the file.  Name it ‘cogstartup backup.xml’ which will be stored in the analytics\configuration folder.

Close Cognos Configuration.

Moving this files to a different, secure location e.g. c:\temp\backup (they should during the cryptographic keys regeneration process be re-created):

· analytics/configuration/cogstartup.xml

· analytics/configuration/caSerial

· analytics/configuration/certs/CAMCrypto.status

· analytics/configuration/certs/CAMKeystore

· analytics/configuration/certs/CAMKeystore.lock

· analytics/temp/cam/freshness

Moving this folder to a different, secure location e.g. c:\temp\backup

· analytics/configuration/csk

In the analytics\configuration folder, rename ‘cogstartup backup.xml’ to ‘cogstartup.xml’.

Go in to Cognos Configuration and click SAVE, and then start.

To test, you can browse to http://ca11servername:9300/p2pd/servlet

Repeat all the above steps on all the Cognos servers, starting with the Content Manager server and take the Cognos Gateway servers last.


If you see the message “CM-CFG-5069 A serious error occurred while committing a delete operation” when starting up the Cognos Analytics service, it can be a temporary error when CA11 try to clean up its own cache.  Restart the CA11 server again and see if the error goes away.

Misleading Error in cognosserver.log at first logon of any user after a Cognos restart:
“/v1/identity bi-service Can not retrieve the password from configuration.”
Solved in later versions of CA11.

More information:

By default, the cryptographic keys are valid for 365 days.

  • This value is configured inside Cognos Configuration
  • Specifically, browse to “Local Configuration -> Security -> Cryptography” and modify the value for: Common symmetric key lifetime in days

Each time you open Cognos configuration and click the save button, it resets the clock on your 365 days. Therefore, if you installed the software and didn’t save the configuration for 365 days, they would expire and you’d need to manually regenerate them.

You must restart the services every so often to ensure the new keys are actually being used.

  • If you think you won’t be opening and saving your configuration at any point in the next year or two, you can change the expiration date to 8 years and re-encrypt everything.

Planning Analytics Workspace 2.0.
Linux Red Hat 7

After change/crash of PAW, the system is starting but user can not login. They get the message “Planning Analytics Workspace is unavailable. Try again in a few minutes”
On the Linux server you run command to check that all containers are up, and they all show the same number of seconds to be up. This make it look like the PAW is working.
sudo docker ps

If you check the logs for a container, with below command, you can see if there are any errors giving more information.

sudo docker logs share-platform

cp: failed to extend ‘’: No space left on device

cp: error writing ‘’: No space left on device

Check the date before in log file, above can be a fill up disk of log files that have crashed the PAW before.

Check space with command: df -h

sudo docker logs pa-gateway

This may show AH01114: HTTP: failed to make connection to backend: share-platform, that tell us that it does not speak with the share-platform container, who had a problem before.


Recreate the images, they can have been corrupted of the space outage you had earlier. This may remove the books you have inside PAW, so take a backup first by run script /ibm/paw/scripts/ to create a backup file under backup folder.

Go to the /ibm/paw/scripts folder on Linux server. Enter below command to stop PAW

./ stop

Backup the config folder and it sub-folders;   cp -ivR config  /tmp/cognos  (will copy all files in config folder to /tmp/cognos folder)

Kill all running containers
docker kill $(docker ps -q)
Delete all stopped containers
docker rm $(docker ps -a -q)
Delete all images
docker rmi $(docker images -q)

Then go to the PAW folder of your installation on the Linux server and run to create the images/containers from scratch.


Answer YES on both questions.

You can in Linux test that the PAW is up by entering command (replace with your server DNS alias):

curl -k

this will return the html page as plain text – check for errors.

More Information:

To limit docker log files you can edit the daemon.json file in folder /etc/docker

This sample configuration will limit the json log files to 10 megabytes, and will only keep the 5 most recent logs:


“log-opts”: {

“max-size”: “10m”,

“max-file”: “5”


Planning Analytics Workspace 2.0.39
Microsoft Windows 2016 server

After restart/upgrade of PAW – when going to the administrator tab over databases, some show “Threads blocked: unavailable”

Clear the cache in the web browser first, or try with a different web browser (chrome).

It can be that the account you logged in to PAW is not administration in the TM1 instance, then the threads info will not be shown.

More information:

Planning Analytics 2.0.9
TM1SERVER_APP_name=IBM Cognos TM1 Server Application
Microsoft Windows 2019 server

Company have moved from NATIVE TM1 security to Active Directory security – where all users have got a new ID in Cognos Connection. That means that inside Planning Analytics (Tm1) the user is a new person with a new ID, so all private views are lost.

When user Donald login with his new AD ID, he does not see his old private views in Tm1 Architect.


Stop the TM1 service for that instance.

Good that TM1 use a file system to store information.
All private views and data are stored under the user name folder in \data — in above case that should be in folder \data\donald\.
You can then copy the vue files from C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Rules_Guide_Data\donald\Currency}vues\testview1.vue to folder C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Rules_Guide_Data\Currency}vues to make the testview1 public by place it direct under the cube view folder.

We login to TM1 application RulesGuide as Admin in native mode, and create a private view called testview1.

This view is saved under the Tm1 application data folder “rules_guide_data” under the user name and cube name as shown above.

If we copy only the testview1.vue file to the cube folder direct under data e.g. Currency}vues then the view becomes public.
To copy it from NATIVE user Admin to AD user Admin, you have to go under the folder with the same name as the Cognos Namespace, in our example AD. Under the user there you have to copy both the cube folder and the cubeview file.

Folder AD will be different in your environment, as it is the Cognos Namespace name.

You need to copy both cube name folder – in our example Currency}vues and the vue file there under to move the private view to a different user as a private view.

Start the TM1 server after you have copied the files and you should now see the views as other user.

More information:



Cognos Analytics 11.1.7
Microsoft Windows 2019 server
In a multi-server environment, when the second CA11 service is started, then not all the java processes needed for DQM reports is running. There should be 3 java process on a Cognos Analytics server.

The Cognos Configuration say that CA11 is up and running, but if you look into the Cognos Administration you find that the QueryService is not working (as its java process is not started).

Check the cognosserver.log file to find out that the file is damage.

Error you find in the cognosserver.log file are:

ERROR [pool-79-thread-19] NA problem reconfiguring handler queryServiceHandler
com.cognos.xqe.config.ConfigFileException: XQE-CFG-0003 Failed to load configuration file file:/D:/Program%20Files/ibm/cognos/analytics/configuration/xqe.config.xml.
at com.cognos.xqe.config.XQEConfiguration.loadConfiguration( ~[xqeService.jar:?]

Stop the IBM Cognos service from inside Cognos Configuration.
Copy the file xqe.config.xml from the working CA11 server to the none-working CA11 server.
Start the IBM Cognos service from inside Cognos Configuration.

Wait 8 minutes until it starts up. Test to run the reports now.
If no other working Cognos installation is around, you may need to reinstall Cognos to get correct files.

More information:

  1. Stop Dispatcher (that in turn will stop Query service).
  2. Assuming <cognos_home> is home directory of that specific dispatcher delete everything from <cognos_home>\wlp\usr\servers\dataset-service\workarea\*  (i.e. keep the workarea directory, but delete everything in it, including subdirectories)
  3. Delete everything from <cognos_home>\wlp\usr\servers\cognosserver\workarea\*
  4. Delete everything from <cognos_home>\javasharedresources\*
  5. Start Dispatcher (Query service will start automatically)

Planning Analytics 2.0.7
Microsoft Windows 2016 server

How to make the log files not so big for TM1?
Can i have tm1top data logged to a file?


Create the file in the same folder as your tm1s.cfg file.
log4j.appender.S1.MaxFileSize=10 MB tells how big your tm1server.log file will be, default is much larger.
log4j.appender.S1.MaxBackupIndex=40 is the number of files that will be kept. Increase this to the value you need.

To enable TM1TOP data, without using the tm1top utility, add to your tm1s.cfg file
Then active and set the filename with this parameters in file:

log4j.logger.Top=INFO, S_Top
log4j.appender.S_Top.MemorySize=5 MB



Then in the file you adjust the size with the parameters:

log4j.appender.S_Top.MaxFileSize=10 MB

This is a great example of a file that is copied from

# main logging file
log4j.logger.TM1=INFO, S1
# it's good to have Locks details -- provides the names of the locked objects
log4j.logger.TM1.Lock.Exception=DEBUG, S1
# S1 is set to be a SharedMemoryAppender
# Specify the size of the shared memory segment
log4j.appender.S1.MemorySize=5 MB
# Specify the max filesize
log4j.appender.S1.MaxFileSize=10 MB
# Specify the max backup index
# Specify GMT or Local timezone

# event logging configuration
# Meeds EventLogging=T in the tm1s.cfg
log4j.logger.Event=INFO, S_Event
log4j.appender.S_Event.MemorySize=1 MB
log4j.appender.S_Event.MaxFileSize=10 MB

# tm1top logging configuration
# Set up TopLogging=T in the tm1s.cfg
log4j.logger.Top=INFO, S_Top
log4j.appender.S_Top.MemorySize=5 MB
log4j.appender.S_Top.MaxFileSize=10 MB

# Logins file -- records every time a user logins, can be used for license evaluation or just checking user activity
log4j.logger.TM1.Login=DEBUG, S_Login
log4j.appender.S_Login.MemorySize=5 MB
log4j.appender.S_Login.MaxFileSize=10 MB

More Information: