Planning Analytics
Planning Analytics Workspace 63
Microsoft Windows 2019 server

In PAW, when you create a new book, and insert a Websheet from a TM1 application, you only get a blank box after a long time. This is in a new installation, where you are using the new TM1WEB service (IBM Planning Analytics Spreadsheet Services).


You need to in IBM Planning Analytics Workspace Administration Tool ensure that the TM1 Application Server Gateway URI point to the new TM1WEB server and it correct port.

Change and save. Then restart the PAW from inside the status tab.

If you click validate you will still get the 404 error on this line, this is OK, as they validate try to find pmhub parts that is not in PAL at this later versions.

This value is also in the paw.env file, on your PAW linux server. You can edit direct in the file, too.

Change value export TM1ApplicationsLocation=”″
The file is in your /ibm/paw/config folder.

Stop PAW with command (from your /paw/scripts/ folder):

sudo ./ stop

Check if PAW is stopped with command:

sudo docker ps

Start PAW with command:

sudo ./

Wait 10 min before you test to browse, to your paw installation in chrome.

More information:

Cognos Analytics 11.1.7
Microsoft Windows 2019 Server

After change to use HTTPS in Cognos Configuration, you get a error when you save.

[Populate authentication settings] [ WARNING ] Failed to populate the authentication settings to server

When change values in Cognos Configuration that have with certificates, you need to first stop the “IBM Cognos” windows service.
Then you can save the configuration without warnings.


More Information:

To active Cognos internal certificate, you need to inside Cognos Configuration on your Content Manager server change HTTP to HTTPS under environment – group properties.
Check that server FQDN is at Cognos – Cryptography ;DNS names and Server common name.
Save will create the certificate files.

Start CMD, and move to folder C:\Program Files\ibm\cognos\analytics\bin
Run this to export the Cognos certificate
ThirdPartyCertificateTool.bat -E -T -p NoPassWordSet -r ca.cer

Start MMC on your Windows server where Cognos Gateway is installed, and certificates and go to “Trusted Root Certification Authority”. Right click to Import certs.
Select the ca.cer file and import it.

Inside IIS manager, go to \ibmcognos\bi folder and click on URL Rewrite icon.
Click on Reverse proxy Rules to edit.
At action properties – Rewrite URL: change the http to https{R:0}
Click apply in the right corner.
Exit IIS manager.

On PA server open Command Prompt as an Administrator and navigate to the \bin64\ directory.

Execute the following command to import/trust the certificate for Tm1 admin:
gsk8capicmd_64 -cert -add -db “C:\Program Files\ibm\cognos\tm1_64\bin64\ssl\ibmtm1.kdb” -stashed -label caRoot -file “C:\Program Files\ibm\cognos\tm1_64\bin64\ssl\ca.cer” -format ascii -trust enable

Go to \bin64\jre\bin\ to import it to PMPSVC java keystore.
keytool.exe -import -trustcacerts -file “C:\Program
Files\ibm\cognos\tm1_64\bin64\ssl\ca.cer” -keystore “C:\Program
Files\ibm\cognos\tm1_64\bin64\ssl\tm1store” -alias caRoot -storepass applix

You need also to add the ca.cer file to the correct keystore for TM1WEB.

Configure Planning Analytics 2.0 TM1 Server with SSL Cognos BI Dispatcher (

How to Configure Planning Analytics to Connect to an SSL Secured Cognos Dispatcher (

Configuring TM1 Server to trust the SSL certificate on CA Side (

Microsoft Windows 2019 server

Problem to connect to Remote Desktop from old laptop.


Newer Microsoft Windows server has the possible to harden the communication, to not use old security protocols, then it will not allow connections from Windows 2012 or Windows 7 computers.

Try to connect from a Windows 10 computer with the latest service packs.


More information:

Planning Analytics 2.0.9
Cognos Analytics 11.1.7
Microsoft Windows 2019 server

After import of the full content store to a new installed Cognos server, the icons for Tm1 App Web (PMPSVC) is not working.

The old Cognos BI 10 solution may have used SKINS for the users.
Check the old server in folder d:\program files\ibm\cognos\c10_64\webcontent\skins for any unique folders that you do not have in your new cognos server. Copy that unique folder over to d:\program files\cognos\tm1_64\webapps\pmpsvc\skins folder.
Looks like the new TM1 needs the old custom skins files to work.

You can also click on icon for My Preferences and change Style to “modern” and click OK.

Below the default style skins that come with the product. If you have more folders in your Cognos BI installation, then they should be copied over to the new cognos server.

More information:
Inside Cognos Analytics – Administrator page – if you are only see text and miss the icons and color, it is possible the same issue, you need to copy the company unique skins folder to the new server.

What you’re seeing is related to content (images and css files) not being found.
The person who has selected a custom skin as their default will get this.

If your custom skin is named MyCustomSkin, which doesn’t exist on the Cognos Analytics server.

On the Cognos Analytics server…
Copy <install_location>\webcontent\skins\corporate to <install_location>\webcontent\skins\MyCustomSkin.
Copy <install_location>\webcontent\bi\skins\corporate to <install_location>\webcontent\bi\skins\MyCustomSkin.

No restart is required. Once these are in place, the browser will find the styles and images and Cognos Analytics will be functional and more aesthetically pleasing.

Planning Analytics 2.0.97  (file tm1_winx64h_2.0.97.6_ml.tar)
Microsoft Windows 2019 server

Error when installing PA on Windows server.


Uninstall Planning Analytics.

Go to control panel – administrative tools – services.

Go to Printer Spooler service, right click and select properties and change it to Automatic.

Click to start the Printer Spooler.

Run the installation of Planning Analytics again.

More information:

Cognos Controller 10.4.2
Microsoft Windows 2012 R2 Server

In Cognos Controller the IBM license is for users and servers. The user part is divided in Administrators and Standard Users.  The limit is that the Standard Users should not have access to all the menu points on the Maintain menu. How do we set this up?

Create a security group called ST = standard user, and limit access to menu items as shown below.

Then use this menu group as template when you create other menu security groups in Cognos Controller- if you want the data entry people only to have access to less number of menus.

Log into Cognos Controller Client as a administrator (ADM) user.

Go to maintain – rights – security groups.

Create a new security group, by click on new icon.

Name it ST, Standard User and scroll down to select all menu points that should be set to Not Available.

Then for each menu a standard user, should not see, you need to select it and click “Not Available”.

Important, that Jobs menu above is set to red “Not Available”.

When all fields need are set to “Not Available” click save icon.

Now click on save as icon to create a new security group with this as base;

Give it a good name, and then select the menu points your data entry users should not see, and also mark them as Not Available.

Here you need to decide what menu point your different users groups need. Save the new group.

Then you go to Maintain – Rights – Users.
On each user go to limitations and select your new security group.

Click on Save icon.
Now it may be needed, that you run a optimization of the database for the changes to take affect.

Go to maintain – rights – reports and click on Generate (to get a License Management Report as PDF)

Save the pdf to a folder you can find.
Open the UserReport.pdf file in your Adobe reader or web browser.

Now you should have more standard active users in the report.

The information is also stored in a SLMT tag file for each database, in a unique folder for each database, on the Cognos Controller main server.

C:\Program Files\ibm\cognos\ccr_64\SLMTagData\UK, is the folder for the UK database.

Where you can see historical values from your Controller installation.

In folder C:\Program Files\ibm\cognos\ccr_64\swidtag you find the file that the ILMT tool should check to find what version of Cognos Controller you have installed.


More Information:


Cognos Controller web 10.4.2
Microsoft Windows 2012 R2 server

Upgrade of controller web to later version with SSO (CAM login), you get a error after you select the database in the controller web page.

Error message:

The website declined to show this webpage
Most Likely causes:
This website requires you to login.

This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.


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

may contain the wrong information.

Open variables_CCRWeb.xml in Notepad++

Change line <CRNenv c_cmd=”!/CamLogin”>


<CRNenv c_cmd=”!/CamLogin”>
<param name=”cam_passport”/>

The extra fcm.web is from the old version of Controller web.

Save the file again.

Restart the 3 Cognos Controller Web services.

Try to browse to to see if Controller Web works.

More Information:

The log files for controller web is found in folders:

D:\Program Files\ibm\cognos\ccr_64\frontend\logs\fcmwebui-stdout.2021-04-23.log

D:\Program Files\ibm\cognos\ccr_64\fcmweb\wlp\usr\servers\fcm.web\logs\fcmweb-stdout.2021-04-23.log

Linux Centos

How create a SSL (TLS) request for a server that need a certificate?

Suggested Solution:

Install openssl on your Centos Linux with command:

yum install openssl

Create a folder to work in mkdir /ibm

Go to that folder cd /ibm

Create a text file with a text editor like; nano san.txt

[ req ]
default_bits       = 2048
distinguished_name = req_distinguished_name
req_extensions     = req_ext
prompt             = no
[ req_distinguished_name ]
countryName                = Country Name (2 letter code)
stateOrProvinceName        = State or Province Name (full name)
localityName               = Locality Name (eg, city)
organizationName           = Organization Name (eg, company)
commonName                 = Common Name (e.g. server FQDN or YOUR name)
[ req_ext ]
subjectAltName = @alt_names
DNS.1   = servername
DNS.2   =
DNS.3   =

Save above text in the file after you change to your server-names.
openssl  req  -out /ibm/request.csr  -newkey rsa:2048 -nodes -keyout /ibm/privateKey.pem -config /ibm/san.txt
Above will give a new server private key and a certificate request for a cert.

Check the request with command:

openssl req -text -noout -verify -in request.csr

Check the private key with command:

openssl rsa -in privateKey.pem -check

The private-key should only be stored on the server where it should be used.
The certificate request you copy and paste to your Certificate Authority to generate your certificate.

SSL Experten

newkey rsa:2048

This option creates a new certificate request and a new private key.



More information: 

Managing Certs with Windows Certificate Manager and PowerShell [Tutorial]

Windows certificate stores

IBM License Metric Tool on Linux
Red Hat Enterprise Linux 7.5 or a higher 7.x version
How install ILMT on Linux in one step
Suggested Solution:
You need to install on Red Hat Enterprise Linux 7.5 or a higher 7.x version, but for this test we will use CentOS Linux
Install CentOS with a fix IP address, so you can easy connect to the Linux server.

Download the installation file “ILMT_Install_Lnx-x86-64_V9222.tar.gz”

Copy the file to your linux server with WinSCP program.

Check disk space with command df  -h

Install the needed programs

yum install byobu

yum install libnsl

yum install libstdc++

yum install ksh

yum install pam*i686

yum install numactl*x86_64

yum install libstdc++*i686

yum install libpng12.x86_64

yum install fontconfig.x86_64

yum install libXext.x86_64

yum install libXrender.x86_64

yum install unixODBC.x86_64

yum install nano

yum install wget*x86_64

Unzip the tar file with command:  tar  zxvf  ILMT_Install_Lnx-x86-64_V9222.tar.gz

Copy the install_response.txt to a new file with command: cp install_response.txt response.txt
Edit that file in nano response.txt

Change the following values;




#RSP_DB2_ROOT=/opt/ibm/db2/V11.5  (if you want DB2 installed in a different folder)


#RSP_IEM_WR_WWW_PORT=8083 (if you want to change the port number used by BigFix)

#RSP_TLM_ROOT=/opt/ibm/LMT (if you want ILMT installed to other folder)

#RSP_TLM_HTTPS_PORT=9081 (if you want to change The port for administration server web UI)

Save the file, and run below command to start the installation:

./ -i silent -f /ibm/response.txt

You must install to Red Hat.  For this test we enter export disable_platform_check=true

Then the check in the script file will skip the check (if [ “$disable_platform_check” != “true” ]

Go to /root folder and enter command to unzip the log files:

tar zxvf LMT_9.2.22.0_20210514-113503_16243_logs.tar.gz

Check the log file with commando:

tail  LMT_9.2.22.0_20210514-113503_16243_logs/LMT9.2.22.0/Server.log

Solve the issue and run the ./ -i silent -f /ibm/response.txt again.

Add the BigFix port and ILMT port to the firewall on Linux server with commands:

firewall-cmd --permanent --add-port=52311/tcp

firewall-cmd --permanent --add-port=9081/tcp

firewall-cmd --reload


Copy windows client files to your windows share for clients with winSCP

Create a CMD file with this text to run the installation locally on the windows clients:

BigFix-BES-Client- /s /v”/L*vx! \”C:\temp\ClientInstallLog.txt\” SETUPEXE=1 REBOOT=ReallySuppress MSIRESTARTMANAGERCONTROL=Disable /qn”

Check the client windows services for “BES Client”, to see that it was installed.

Copy BIGFIX console files to your windows computer with winSCP

The files are in folder /var/opt/BESInstallers/ directory.

Run the BigFix console setup on a computer, and ensure the clients are listed in the Go to Sites – External Sites – IBM License Reporting (ILMT) – Fixlets and tasks – Install or Upgrade Scanner, task.

Browse to https://yourservername:9081/ in Chrome.

First time you log into ILMT webpage you should get above dialog, to import the data from BigFix server.

For more help contact your IBM partner.

Vår nya ILMT expert – Christer Borg

More information: