Product:
Planning Analytics 2.0.91
Linux Centos

Problem:
How install PA to Linux server?
Download latest version from IBM;
https://www.ibm.com/support/pages/ibm-planning-analytics-20-fix-lists

Linux commands:
https://ss64.com/bash/

Solution:
Install the Linux distribution with a GUI.
https://getfedora.org/workstation/download/
https://wiki.centos.org/Download

Setup a static IP address on Linux, so it is easy to connect to it with PUTTY and WINSCP.
https://winscp.net/eng/index.php

(Test this steps in you lab first, they may differ because of your flavor of Linux)

Install simple editor:
yum install nano

Install X11 windows system (if needed) on linux:
yum install xorg-x11-server-Xorg xorg-x11-xauth xorg-x11-apps -y
https://www.osradar.com/configure-x11-forwarding-in-centos-rhel-6-7-8-and-fedora-28-29/
In /etc/ssh/sshd_config file set X11Forwarding=yes
Restart the SSH service with command:
systemctl restart sshd

To use X11 you must install Xming on your Windows laptop:
https://sourceforge.net/projects/xming/

Open file C:\Program Files (x86)\Xming\X0.hosts in notepad++
add the IP address of the linux system you want to work with

Restart the Xming program on your Windows laptop.

Install C++ libraries:
yum -y install libstdc++ libstdc++.i686 motif libXm.so.4 libXtst

Create a installations folder:
mkdir -p /data/installationsmedia

Copy the file tm1_linuxi38664h_2.0.91.41_ml.tar.gz to the linux server with WINSCP.

Change to root user:
su –

Go to the folder where media are:
cd /data/installationsmedia

Unzip the file:
tar -xf tm1_linuxi38664h_2.0.91.41_ml.tar.gz

Go to the linuxi38664h folder:
cd linuxi38664hprof

Check that you have execute permissions on the files:
ls -al

Run the installation:
./issetup


Click next for the installation.

select production if it is a production server.


All components are selected above.

Create a user:
groupadd cognosusers
useradd cognos -g cognosusers -m
passwd cognos

Install java:
Download from here https://developer.ibm.com/javasdk/downloads/sdk8/
Copy file ibm-java-x86_64-jre-8.0-6.10.bin to linux server.
Go to folder where the media is. Copy to data folder with command:
cp ibm-java-x86_64-jre-8.0-6.10.bin /data/
Go to data folder:
cd /data
Change to be able to execute:
chmod 777 ibm-java-x86_64-jre-8.0-6.10.bin
Run install of java with command:
./ibm-java-x86_64-jre-8.0-6.10.bin

Click OK to English as language

Select “i accept..” and click Next

Click Next
Click Next

Click Install

Click Done

Create environment values (only if they are needed):
JAVA_HOME /opt/ibm/java-x86_64-80/jre
LD_LIBRARY_PATH /opt/ibm/cognos/tm1_64/webapps/pmpsvc/WEB-INF/bin64/

Do not edit the /etc/bashrc file, instead create a custom.sh shell script in folder /etc/profile.d/ to make custom changes to your environment for all users

Go to folder /etc/profile.d/ and create a new cognos.sh file to store your variables.

export JAVA_HOME=/opt/ibm/java-x86_64-80/jre
export LD_LIBRARY_PATH=”/opt/ibm/cognos/tm1_64/webapps/pmpsvc/WEB-INF/bin64:$LD_LIBRARY_PATH”
export PATH=”$PATH:/opt/ibm/cognos/tm1_64/bin64″
export DISPLAY=’192.168.1.11:0.0′

You must set the IP of the windows laptop you run Xming on to the export DISPLAY command.

Enter . ./cognos.sh to activate the settings above. In some Linux installations you do not need above values – as they are already configured, then it can be enough to only type JAVA_HOME=/opt/ibm/java-x86_64-80/jre before your command.

Enter env to check the variables values.

Change the file block value:
sysctl -w vm.max_map_count=‭1310600‬

Create a folder for the tm1 applications (tm1 do not work well with long paths):
mkdir -p /data/pa

Change users to have access to the folders:
chmod -R 777  /data/pa
chmod -R 777  /opt/ibm/cognos

Change owner to the cognos account:
chown –R  cognos:cognosusers /data/pa/
chown –R  cognos:cognosusers /opt/ibm/cognos/

 

 

 

To start Cognos Configuration:
LD_LIBRARY_PATH=/opt/ibm/cognos/tm1_64/webapps/pmpsvc/WEB-INF/bin64/ JAVA_HOME=/opt/ibm/java-x86_64-80/jre /opt/ibm/cognos/tm1_64/bin64/cogconfig.sh

Set the memory for the TM1WEB to higher number if TM1WEB is used.

Use only FQDN instead of localhost in TM1 Application.

Only to be sure add the company domain and all tm1 servers to the valid domain list for the Cognos Application Firewall.

Do all configuration and press save icon.

Start the service to see that they do not give errors.

Stop the service in cognos configuration and exit cognos configuration.

Open ports in firewall for TM1 on linux:

firewall-cmd --zone=public --add-port=5495/tcp --permanent 
firewall-cmd --zone=public --add-port=5498/tcp --permanent 
firewall-cmd --zone=public --add-port=12345/tcp --permanent 
firewall-cmd --zone=public --add-port=53333/tcp --permanent
firewall-cmd --zone=public --add-port=5895/tcp --permanent
firewall-cmd --zone=public --add-port=5898/tcp --permanent
firewall-cmd --zone=public --add-port=9510/tcp --permanent
firewall-cmd --reload
firewall-cmd --list-ports

(you may need to open more ports in the Linux firewall for your TM1 applications)

Update the values for TM1WEB if used, in file (nano /opt/ibm/cognos/tm1_64/webapps/tm1web/web-inf/configuration/tm1web_config.xml)

<!– CubeViewerRowPageSize: Number of rows to fetch in a page of cubeviewer –>
<add key=”CubeViewerRowPageSize” value=”200” />

<!– CubeViewerColumnPageSize: Number of columns to fetch in a page of cubeviewer –>
<add key=”CubeViewerColumnPageSize” value=”100” />

Use the scripts to start and stop the PA services.

 

Create unit service files with the configuration to prepare for systemd services, like the tm1 admin service.
nano /usr/lib/systemd/system/tm1adminsrv.service

That have this content:
[Unit]
Description=Cognos TM1 – tm1 admin server.service
After=network.target auditd.service
Documentation=https://www.ibm.com

[Service]
Type=forking
Environment=”LD_LIBRARY_PATH=/opt/ibm/cognos/tm1_64/bin64:/usr/lib:/lib:$LD_LIBRARY_PATH”
Environment=”JAVA_HOME=/opt/ibm/java-x86_64-80/jre”
Environment=”TM1_PATH=/opt/ibm/cognos/tm1_64/bin64″
ExecStart=/opt/ibm/cognos/tm1_64/bin64/startup_tm1admsrv.sh
ExecStop=kill `ps -e | grep “tm1admsrv.exe” | awk ‘{print $1}’`

# the user must have full access to the folders
User=cognos
WorkingDirectory=/opt/ibm/cognos/tm1_64

# Kill root process
KillMode=process

# Wait up to 30 seconds for service to start/stop
TimeoutStartSec=120
TimeoutStopSec=60

# Remove process, file, thread limits
#
LimitNPROC=infinity
LimitNOFILE=infinity
TasksMax=infinity

# Restart on non-successful exits.
Restart=on-failure

# Don’t restart if we’ve restarted more than 3 times in 2 minutes.
StartLimitInterval=120
StartLimitBurst=3

[Install]
WantedBy=multi-user.target

 

To start the service enter (use this first to test and ensure your unit file works):

systemctl start tm1adminsrv.service

To make the service start after a reboot of linux enter:

systemctl enable tm1adminsrv.service

After unit files are created you can stop/start the tm1 services with these commands:

  • Start service: systemctl start [Name of Service]
  • Stop service: systemctl stop [Name of Service]
  • Restart service: systemctl restart [Name of Service]
  • Status of service: systemctl status [Name of Service]

Create the file for TM1 Application web
nano /usr/lib/systemd/system/tm1app.service

That have this content:
[Unit]
Description=Cognos TM1 – Application server
After=network.target auditd.service
Documentation=https://www.ibm.com

[Service]
Type=forking
Environment=”JAVA_HOME=/opt/ibm/java-x86_64-80/jre”
# we use the script to start and stop
ExecStart=/opt/ibm/cognos/tm1_64/bin64/startwlp.sh
ExecStop=/opt/ibm/cognos/tm1_64/bin64/stopwlp.sh
User=cognos
WorkingDirectory=/opt/ibm/cognos/tm1_64/bin64

# Kill root process
# KillMode=process

# Wait up to 30 seconds for service to start/stop
TimeoutStartSec=120
TimeoutStopSec=60

# Remove process, file, thread limits
LimitNPROC=infinity
LimitNOFILE=infinity
TasksMax=infinity

# Restart on non-successful exits.
# Restart=on-failure

# Don’t restart if we’ve restarted more than 3 times in 2 minutes.
# StartLimitInterval=120
# StartLimitBurst=3

[Install]
WantedBy=multi-user.target

 

Create the file for TM1 planning sample (update for your TM1 instance)
nano /usr/lib/systemd/system/tm1plansamp.service

That have this content:
[Unit]
Description=Cognos TM1 – Planning Sample
After=network.target auditd.service tm1adminsrv.service
Documentation=https://www.ibm.com

[Service]
Type=forking
Environment=”LD_LIBRARY_PATH=/opt/ibm/cognos/tm1_64/bin64:/usr/lib:/lib:$LD_LIBRARY_PATH”
Environment=”JAVA_HOME=/opt/ibm/java-x86_64-80/jre”
Environment=”TM1_PATH=/opt/ibm/cognos/tm1_64/bin64″
# the case of the letters in path is important
ExecStart=/opt/ibm/cognos/tm1_64/bin64/tm1s.exe -w -z /opt/ibm/cognos/tm1_64/samples/tm1/PlanSamp
ExecStop=kill -s INT `ps -ef | grep “tm1s.exe -w -z /opt/ibm/cognos/tm1_64/samples/tm1/PlanSamp” | grep -v grep | awk ‘{print $2}’`
# must be root to be able to kill this process
User=root
WorkingDirectory=/opt/ibm/cognos/tm1_64/bin64

# Kill root process
KillMode=process

# Wait up to 30 seconds for service to start/stop
TimeoutStartSec=120
TimeoutStopSec=60

# Remove process, file, thread limits
LimitNPROC=infinity
LimitNOFILE=infinity
TasksMax=infinity

# Restart on non-successful exits.
Restart=on-failure

# Don’t restart if we’ve restarted more than 3 times in 2 minutes.
StartLimitInterval=120
StartLimitBurst=3

[Install]
WantedBy=multi-user.target

You need to test the start and stop a few times to get the commands correct.


Check in TM1 architect that you can reach the TM1 instance from your laptop.

If you edit the unit file, you must run this command to reload the file:
systemctl daemon-reload

To list running TM1 instance on Linux, enter this command:
ps -ef  | grep “tm1s.exe”

To check the service running use this command:
systemctl  list-units  –type=service

To remove failed service enter this command:

systemctl reset-failed

If the TM1 instance is run with systemd, as above, then you must in each TM1s.cfg file have this value:

RunningInBackground=F

More information:
https://www.ibm.com/support/pages/how-install-cognos-analytics-1111-rhel-76-0
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_tm1_instunixlinux.html
https://developer.ibm.com/technologies/linux/tutorials/l-lpic1-106-1/

http://www.geo.mtu.edu/geoschem/docs/putty_install.html
https://cc.jlab.org/windows/X11onWindows

https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files

https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory

https://www.cyberciti.biz/faq/how-to-check-open-ports-in-linux-using-the-cli/

https://www.thegeekdiary.com/how-to-open-a-ports-in-centos-rhel-7/

https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_inst_troubleshooting_timeouts.html

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/managing-services-with-systemd_configuring-basic-system-settings

https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

https://www.cyberciti.biz/tips/understanding-linux-unix-umask-value-usage.html

AWK tutorial: find and kill process use awk

Note that use of ODBC drivers on Linux demand a expensive license. Recommend to only use csv files to transfer data to and from TM1 on Linux.

Example on PA https://www.youtube.com/watch?v=x-VQ0Nr-Pg0

Product:
Planning Analytics 2.0.9
Planning Analytics Workspace 53

Problem:
When run the installation of the PAA agent you get the error: ERROR: PAA Agent not found at the PA installation directory passed as input

Solution:
Enter the path to tm1 folder in quotation mark.
Download the zip file from the Planning Analytics Workspace Administrator database page.
Unzip the file to a empty folder.
Start CMD as administrator.
Enter updatePAAagent.bat “d:\program files\ibm\cognos\tm1_64”

More information:
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/t_paw_download_paa_agent.html

Product:
Planning Analytics 2.0.9 tm1 application web
Microsoft Windows 2016 server
Microsoft Edge Version 83.0.478.58 (Official build) (64-bit)

Problem:
Can not copy and paste between planning analytics application web and excel.
First time you get a error message:

Solution:
For chrome or IE edge install the tm1 plugin from here
https://chrome.google.com/webstore/detail/ibm-cognos-tm1-web-clipbo/pfcpjkoiknombhfcjnjihpafmkhmdcjb

Start new Edge and surf to https://chrome.google.com/webstore/detail/ibm-cognos-tm1-web-clipbo/pfcpjkoiknombhfcjnjihpafmkhmdcjb

Click on the “add to chrome”

Click Add extension

Then it should work to copy and paste between Tm1 app web and excel.

More information:
https://www.ibm.com/support/pages/plugins-mozilla-firefox-and-google-chrome-web-browsers-are-available-use-copy-and-paste-tm1-web

https://www.howtogeek.com/120743/how-to-install-extensions-from-outside-the-chrome-web-store

Product:
Planning Analytics 2.0.9
Microsoft Windows 2016 server

Problem:
After upgrade of Planning Analytics you get a error when you start Performance Modeler.
CCLMsg: system text=’Argument value is null’

Solution:
On your computer, uninstall Performance Modelere from Control Panel\Programs\Programs and Features.

Then install it again manual, from folder D:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\rcp_installs\PerformanceModeler64.msi

To make the installation be for all users, run it with this cmd command as administrator
msiexec /i “d:\install\pm\PerformanceModeler64.msi” /L*V “d:\install\mypm.log” TARGETDIR=”d:\Program Files\pm” ALLUSERS=1

More Information:
https://www.ibm.com/support/pages/error-opening-elist-item-webclient-cclmsg-system-textargument-value-null

Product:
Planning Analytics 2.0.7
Cognos Analytics 11.0.x
Microsoft Windows 2012 server

Problem:
During change of CA11 server, you can not login to TM1 Architect or TM1WEB.
You get error: SystemServerClientNotFound
The new windows IIS for the Cognos BI gateway server is using HTTPS.

Solution:
Inside tm1s.cfg file ensure the values for IntegratedSecurityMode=5 point to correct part of Cognos Analytics.

ServerCAMURI=http://caservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=https://caservername.domain.com:443/ibmcognos/bi/v1/disp

If the Cognos BI dispatcher also uses SSL, then set it up like this
https://www.ibm.com/support/pages/how-configure-planning-analytics-connect-ssl-secured-cognos-dispatcher

More Information:
https://www.ibm.com/support/pages/configure-tm1-cam-authentication-using-cognos-analytics-110-sso

Product:
Planning Analytics 2.0.8
Microsoft Windows 2016 Server

Problem:
How install the ILMT BIG FIX client to Planning Analytics servers?
IBM demand that virtual PA installations have the ILMT client installed and that the customer provide an ILMT report of the CPU usage for virtual installations.

https://lodestarsolutions.com/why-have-i-never-heard-about-the-ibm-ilmt-tool-for-cognos-bi-or-tm1/
http://www.aramartech.co.uk/for-ibm-cognos/ilmt-(1)
https://exploringtm1.com/tm1-ilmt/

How install the BIG FIX client:
You should have installed the ILMT and BIG FIX server in your organization on a separate server.
During the installation of the Big Fix server a license is created for your organization.
Above is a must for you to be able to install the client.

Download client file from here https://support.bigfix.com/bes/release/

The simplest way is that you get a setup.exe and actionsite.afxm file from the server copied to your Planning Analytics (TM1) server – place all files in same folder (c:\install). If you do not have the afxm file you get a error like this:

Run the installation of the client program BigFix-BES-Client-9.5.14.73.exe


(The files to copy for the client, can be found on the BigFix server in folder C:\Program Files (x86)\BigFix Enterprise\BES Installers\Client)

Click OK to the language selection.

Click Next.

Click next to the selection of installation folder.


Click install.


Click finish.

The client should talk to the server and show up direct, inside the Big Fix server console.

Then the IT department need to activate the scans for IBM software.
https://help.hcltechsw.com/bigfix/9.5/inventory/Inventory/planinconf/t_scheduling_soft_scans.html

There is the possibility that IT department need to download other scan software, as part of the Big Fix server configuration to allow the Big Fix client to perform the software scan. This is done with the Big Fix system.

Download software from here (old version):

Install the installation generator first from here;
http://software.bigfix.com/download/bes/95/BigFix-BES-9.5.2.56.exe

The server exe is found here;
http://software.bigfix.com/download/bes/95/BigFix-BES-Server-9.5.2.56.exe


After the installation generator is setup, you get instructions on how to install the clients.

More information:

https://support.hcltechsw.com/csm?id=bigfix_support
https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Installation/c_licensing_tasks.html
https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Installation/c_installing_the_client_manually.html
https://www.ibm.com/support/knowledgecenter/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/planinconf/t_changing_freq_sch_scan.html
https://www.ibm.com/support/knowledgecenter/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/overview/c_overview_main.html
https://www.ibm.com/support/knowledgecenter/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/planinconf/c_default_scan_configuration.html
https://forum.bigfix.com/t/bigfix-server-install-fails-missing-masthead/17434/4


The big fix program use port 52311 to talk to the server.

On the Big Fix server, launch console, create a lot of default values.

You can download a old client direct from here https://support.bigfix.com/bes/release/9.2/patch8/

https://uit.stanford.edu/service/bigfix/pc
https://www.ibm.com/support/knowledgecenter/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/planinconf/t_installing_bigfix_win.html#task_rnp_xzm_tx
https://forum.bigfix.com/t/endpoint-manager-need-to-create-new-masthead-file/13327/5
https://help.hcltechsw.com/bigfix/9.2/platform/Platform/Config/c_editing_the_masthead.html

Please check the current license demands from IBM on the Cognos and TM1 products, as they may change.

Product:
Planning Analytics Workspace
Microsoft Windows 2016 server

Problem:
PAW take long time to start when anti-virus software is running.
https://success.docker.com/article/endpoint-security-for-windows-containers

Suggested solution:
Depending on your anti virus program, the settings are different.

Please try this:
exclude this folders and sub-folders from scanning
c:\programdata\docker
c:\Program Files\ibm\cognos\tm1_64
c:\Program Files\ibm\cognos\analytics\temp\
c:\ProgramData\Microsoft\Windows\HNS
d:\ibm\paw
d:\docker
d:\tm1applications folder ( can be d:\tm1server\app1\data )

Folders name depend on the installation made of docker and PAW on your server.

For McAfee you can setup the exclude like this:
On-Access Default Processes Policies
**\Docker\*
**\ProgramData\Microsoft\Windows\HNS\*
**\Install\ipa_workspace_local_win*\*

Exclude also all “active scanning” and instead run a scan on the disk once a week, when you have stopped the PAW and Docker. Turn off Windows Defender Real-Time Protection.

Exclude scan of the processes used by docker and cognos, like java.exe.

 

Upgrade your anti virus software to latest version and see if that helps.

More information:
https://docs.docker.com/engine/security/antivirus/
https://ashleypoole.co.uk/2017/common-issue-pulling-windows-docker-images/
https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/anti-virus-optimization-for-windows-containers
Redundant scanning problem

There will likely be many containers depending on the same package layers. The same data stream of a given package file will provide the data for placeholders on multiple container system volumes. As a result, there is potential for redundant AV scans of the same data in every container. This has an unnecessary negative impact on the performance of containers. This is a signification cost given that containers are expected to start quickly and may be short-lived.

https://www.windowscentral.com/how-exclude-files-and-folders-windows-defender-antivirus-scans
https://github.com/moby/moby/issues/38582

https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/anti-virus-optimization-for-windows-containers

https://success.docker.com/article/endpoint-security-for-windows-containers

https://support.symantec.com/us/en/article.tech183201.html

https://support.symantec.com/us/en/article.tech246815.html

https://kc.mcafee.com/corporate/index?page=content&id=KB90041

https://www.ibm.com/support/pages/which-cognos-files-need-be-excluded-virus-scan

Product:
Planning Analytics 2.0.8
Microsoft Windows server 2016

Problem:
Open a tm1web view in the new PA version give error, it worked in the old TM1 server.

Error message:
Limits exceeded
The action has been terminated because it exceeds the configured maximum memory limit.

Solution:

Open tm1web_config.xml file in Notepad++. It is in folder C:\Program Files\IBM\cognos\tm1_64\webapps\tm1web\WEB-INF\configuration\

Having WorkbookMaxCellCount blank or setting it to less than 0 indicates that an unlimited cell count for workbooks is allowed.
Before IBM Planning Analytics version 2.0.7, the default value is -1, which indicates an unlimited number of cells are allowed in a workbook.
After IBM Planning Analytics version 2.0.7, the default value is 500000.
Setting this parameter to 0 indicates that workbooks cannot have any cells.
You must set it to above 0.

You must do a restart of the application server for the change to take affect.

If WorkbookMaxCellCount parameter is in tm1web_config.xml and it is not the default, when the user opens a workbook, the server validates its cell count against WorkbookMaxCellCount. If the cell count of the workbook exceeds WorkbookMaxCellCount, an error message is logged and the workbook is not opened.

Can also be other values that affect how tm1 show cells.

More information:
https://www.ibm.com/support/pages/tm1-error-maximum-memory-action-exceeded-view-may-be-too-large
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_tm1web_cfg_params_v10r2.html

Product:
Cognos TM1 10.2.2
Microsoft Windows 2008 server

Problem:
Can not connect to TM1 server from client TM1 Architect.
Error:  TM1 Perspectives cannot connect to TM1 Admin server

Solution:
Check that you have access to the TM1 admin server, by run telnet from the DOS prompt your client computer;

TELNET  servername  5498

if you get a black screen, and no error message, then you have a open connection.

Then check that you have the same version on you client as on the TM1 server.

You can check the file tm1api.dll in folder C:\Program Files\ibm\cognos\tm1_64\bin

Above the 10.2.2 TM1 client in RTM version.

Above the TM1 10.2.2 fix pack 7 version.  Version number 10.2.20700

https://www.ibm.com/support/pages/how-determine-exact-version-tm1-installed

If you do not have correct version, uninstall the TM1 client from your computer.

Install the correct program and update, and try again.

Run tm1_64b_10.2.2_win_ml.tar.gz and then up_tm1client_win64_10.2.5270.109_ml.tar.gz to install the needed software.

More Information:

https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_tm1_inst_defaultvaluesfortm1installation.html

https://www.ibm.com/support/pages/ibm-cognos-tm1-ssl-expiration-manual-fix-approach-landing-page

https://www.ibm.com/support/pages/node/553505

https://www.ibm.com/support/pages/e4-cannot-connect-admin-server-host-and-port-caused-expired-ssl-certificates

Product:
Planning Analytics 2.0.8
Planning Analytics Workspace 46
Microsoft Windows 2016 Server

Problem:
When going to Planning Analytics Workspace Administration dialog some of the TM1 instance are grey, in the area for memory and cpu usage.

Error:

On PA Agent version 2.0.47.1220, you can find this kind of error in the file c:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\logs\messages.log
00000048 SystemErr R ERROR:status.py:Error while getting windows registry details: ERROR: The system was unable to find the specified registry key or value
00000048 SystemErr R ERROR:status.py:error getting the registry details: local variable ‘return_object’ referenced before assignment
00000048 com.ibm.pa.kate.agent.scheduler.ScheduledTask E Error occurred while updating the server info json file
Traceback (most recent call last):
File “kateagent/scripts\status.py”, line 1053, in <module>
logger.exception(
NameError: name ‘data_directory’ is not defined
0000005d com.ibm.pa.kate.agent.service.PAKateAgentService E Exception
java.lang.NullPointerException

 

Solution:
A space have come into the TM1 application name in the TM1S.CFG file, and when registered with Microsoft Service, got a extra space in the name.
The PA Agent can not parse the space in the name, and therefor will not display all values.

Stop the TM1 instance.
Edit the tm1s.cfg file to correct value.
ServerName= proven_techniques
should be changed to
ServerName=proven_techniques
Delete the TM1 instance in Cognos Configuration.
Check that the instance is gone – if not, you may need to delete it from a DOS command line.

Enter
sc delete ” proven_techniques”
in the elevated cmd prompt.
Now the windows service should be gone.
Go into Cognos Configuration again,
Add the new TM1 instance and enter a correct name “proven_techniques”
and point out the folder for the configuration file.
Start the service from inside Cognos Configuration.

Surf to PAW and check that the administration page is correct.