Planning Analytics Workspace version 36
Microsoft Windows 2016 server

After some time use, the user can not access the paw. They can not login.
This happen after the server have rebooted during a Microsoft Windows Patching.
To find out if your PAW installation is damage, check this steps:
When you run a docker ps command, you see services listed as restarting.
When you run a ./paw.ps1 stop command, you see services that does not stop, even after 20 minutes.

Error message:
503 The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Follow this guide lines to troubleshoot:

If nothing helps do this:
– increase to 8 cpu cores on your Microsoft Windows 2016 box
– turn off your anti virus software (McAfee and Symantec)
– turn off Windows Defender Real-Time Protection
– uninstall latest windows patch applied before last reboot of Windows server
– run paw.ps1 command as is, to repair containers (if they exist with strange names)
– remove paw and install it again
– restore your paw database backup with the ./restore.ps1 script

If you do not have a backup of paw database content, you need to do this steps;
– set docker service to manual
– stop cognos and planning service
– reboot the windows server
– after windows have started fine, manually start the docker service
– in powershell, enter docker ps, to monitor that the containers have started
– enter the command ./paw.ps1 stop
– when all containers is stopped, run the ./backup.ps1 command to get the backup zip files created.

Remove paw
– copy the configuration files from folder d:\ibm\paw\config to a different temp folder
– copy the backup files from folder d:\ibm\paw\backup to a different temp folder
– run ./paw.ps1 stop to stop all containers
– run ./paw.ps1 down –rmi all -v
– run docker ps -a to list all containers
– run docker rm $(docker ps -a -q) to remove all containers
– run docker images to list all images still there
– run docker rmi <image-id> to remove any Hello-World containers
– run docker network ls to show the docker networks
– rename the d:\ibm\paw\log folder to log-old
– create a new empty d:\ibm\paw\log folder
– copy the config/paw.ps1 file to a temp folder
– remove the d:\ibm\paw\config\paw.ps1 file

In case you need to remove docker, follow the steps last on this page

To install docker on Windows 2016, follow this steps

Run below command to test that docker works, before installing PAW.

docker container run hello-world:nanoserver-sac2016

Reinstall paw

– start the IBM Cognos Planning Analytics Services
– run ./Start.ps1 answer Yes to both questions.
– Inside the Administration web page, enter all the values (check in your old paw.ps1 file for values)
– click on validate
– click on update
– you may get a error, open the newly created d:\ibm\paw\config\paw.ps1 file in notepad++
– add manually the configuration values for $env:PAGatewayHTTPPort=”9580″ and $env:ProxyTimeoutSeconds=”600″ to the config/paw.ps1 file. Check from you backup config/paw.ps1 file what values you used last, when it was working.
– Inside the Administration web page, click on restart
– wait for paw containers to start
– surf to your paw page, does it work, but the folders are missing?
– run the ./restore.ps1 d:\temp\backup\yyyy-mm-dd  command to restore from your backup
– surf to your paw page, hopefully all is there.

If you still have issues, please contact IBM Cognos support for better instructions.

There can be new versions of other software that have issues with Docker containers;
If the system goes down after a few minutes, try to stop the VMware Tools service to see if that helps.

More information:

To prevent this from happening, you must:
Always run the ./paw.ps1 stop script before you restart docker service or reboot the server.
Every week run the ./backup.ps1 script, to make a zip backup of the content inside PAW.
Exclude the docker folders from your anti virus software.
Turn off Real Time Protection.
Set the Docker service to Automatically (Delayed Start)
Ensure there is at least 100 GB free space on the hard disk for docker files.
Add ./shutdown.ps1 script to windows shutdown policy.

More info about Anti-virus software:

“We find out with premier support that normally when container starts NET_LUID index for an NDIS loopback interface is allocated from registry key HKLM\SYSTEM\ControlSet001\Services\NDIS\IfTypes\24\IfUsedNetLuidIndices and when container stops it will be released.

But if you restart computer where is running containers then those values will not be released and if you have multiple automatically starting containers and scheduled restarts then eventually that registry key value will run out of free indexes and you are not anymore able to start containers”

Planning Analytics 2.0.5
Planning Analytics Workspace version 35
Linux Red Hat

After setup of HTTPS to PAW you can not surf to the paw webpage.
If you check the pa-gateway log files in folder /ibm/paw/log/pa-gateway/ you see a error like this
AH01903: Failed to configure CA certificate chain!
in the pa-proxy-error.log file.

Go to the /ibm/paw/config folder and check the file rights
ls -l
drwx—— dockeruser dockeruser 8774 Sep 26 11:03 pa-workspace.pem
if above will give that only the user dockeruser can read the certificate file, and therefor can not Apache read the file and include it in the upstart.
You need to ensure that the group docker can read the files.
To change owner and group of the file enter:
chown dockeruser:docker pa-workspace.pem
To change read rights to the file enter:
chmod 755 pa-workspace.pem

Stop PAW with command in /ibm/paw/scripts folder;
./ stop
Start paw with command

Now it should work. (you need to change path and users to match your environment.)

In PUTTY you can write this BASH commands to check the PAW environment.
To check what docker containers that is running enter:
docker ps
if the first one say pa-gateway is restarting, this mean that the Apache server is not up and the pa-gateway can not load.
To go into the pa-gateway container enter:
docker exec -i -t pa-gateway /bin/bash
To read the Apache log enter:
more /var/log/apache2/error.log
Enter exit to return to Linux:
To move to config folder enter:
cd /ibm/paw/config
To check content of paw.env file enter:
more paw.env
To edit paw.env file enter:
nano -w paw.env
Check that below rows are inside the paw.env file, this activate the https:
export EnableSSL=true
To save the changes in NANO enter:
To exit NANO text editor enter:


Sometimes a container is damage, then you can try to recreate it as below:

Stop the PAW containers with command:
./ stop
To erase pa-gateway container enter:
docker rm pa-gateway
To start paw and recreate containers missing enter:

How setup HTTPS with PAW:

Planning Analytics 2.0.5 TM1 Perspective version
Microsoft Windows 2016 terminal server
TM1 package connector version 10.2.6100.8-0

When you start TM1 Perspective you get a error, if TM1 Package Connector is installed on the same computer. If you remove TM1 Package connector – then TM1 perspective works fine.

Error message:
Microsoft Excel
Missing Library c:\program files\ibm\cognos\tm1_perspective\bin\gsk8ssl.dll
C:\program files\ibm\cognos\tm1_perspective\bin\gsk8km.dll

Suggested solution:
After install of TM1 Perspective, copy the gsk8*.dll files from the c:\program files\ibm\cognos\tm1_perspective\bin folder to the package connector folder c:\program files(x86)\ibm\cognos\c10\bin folder. Overwrite the existing files.

Test to start TM1 perspective again.

If you use a older TM1 Package Connector version, then above error is also gone.

Planning Analytics 2.0.5
Planning Analytics for Office
Microsoft Windows 2016 server

When you connect to PAW server from PAX inside Excel you get a error.

Error message:
System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetResponse()
at Cognos.Office.Reporting.Common.ImageBalloon.ShowAnimation()

Possible solution:
That a proxy server is setup inside IE – Internet options that is preventing the communication to happen.

Go to Control panel on your laptop
Click on Internet Options
Click Connections tab
Click LAN settings button
Unmark Proxy server
Click OK and test again.

More information:

Setup of SSL at TM1WEB

Cognos Enterprise Planning 10.2.1 PLANSVR=10.2.1000.1-0
Microsoft Windows 2016 Server

How move analyst folders from PROD to DEV server?

Locate where the files are on the server, normally in the same file share as the filesys.ini file.
Inside Analyst you find the path to filesys.ini from menu Tools – Options, read Active Filesys.ini file value.
Inside Analyst you find the path to your data from menu File – Administration – Maintain Libraries and Users, note down the path that is listed in this dialog.
Take a backup of the files in the BIN folder, that is mostly these files

From PROD copy the above files to DEV servers file share.
Rename folder containing any old planning analyst data files under folder \programs\ on the DEV server.
Copy all your planning data folders and files from PROD servers \\servername\planning$\programs\adaytum\… to your DEV server.
The path can be different in your setup.

Copy also the Locks.log and Logins.log files from the PROD to the DEV server in folder \\servername\planning$\bin\Locks.

On the DEV server open the filesys.ini file in NOTEPAD.
Edit the path to TAB and log files to match the new server.
change Libs=\\prodservername\planning$\bin\LIBS.TAB to Libs=\\devservername\planning$\bin\LIBS.TAB
change Locks=\\prodservername\planning$\bin\wct\..\Locks\Locks.log to Libs=\\devservername\planning$\bin\wct\..\Locks\Locks.log
change UGR=\\prodservername\planning$\bin\UGR.TAB to Libs=\\devservername\planning$\bin\UGR.TAB
Repeat for the top five lines to update.
Save your updated FILESYS.INI file on the DEV server.

Start Analyst against the DEV server and go into File – Administration – Maintain Libraries and Users dialog. Right click and select Change Library Path…
In dialog Replace Path Component enter below values:
Find String: \\prodservername\planning$
Replace with String: \\devservername\planning$
Click on Replace.

This will update the path to the data files in the LIBS.TAB file.
Click OK and exit Analyst.

Ask a different user to test Analyst in your DEV(test) environment to see that it worked.

User, Groups and Roles are stored in the UGR.TAB file.

In the Locks folder on the servers file share, you can see a USR00000.LOG file for each Planning Analyst user who have logged in.

More Information:

So, in order for users to see the expected set of libraries in Analyst, the Planning Store defined in Cognos Configuration needs to contain the correct filesys.ini path (this Planning Store entry can be viewed or updated via CAC, at: Tools>Update FileSys.Ini options); And the filesys.ini defined in Planning Store/CAC needs to point to the correct LIBS.TAB file, which in turn needs to contain the correct library location information.

Changes to library paths, and the adding or removal of a library from Analyst, are made in the ‘File’>’Maintain Libraries and Users’ dialog in Analyst, which writes these changes to the LIBS.TAB file at the location indicated in filesys.ini. Use of the ‘File’>’Maintain Libraries and Users’ dialog is the only supported way to modify LIBS.TAB.

Cognos Planning 10.2.1 PLANADMIN_version=PLANADMIN-AW32-ML-RTM-10.2.1000.1-0
Microsoft Windows 2016
Microsoft SQL 2016 server

Can not start Cognos Planning client programs on new computer where the new Client software is installed for Cognos Planning.

Download cognos planning from here:

Error message:

A fatal error has occured in the startup section of the application.

The application will be terminated.

Please report the following information:
Section: Message Init
Could not create or read file:  c:\program files (x86)\ibm\cognos\c10\bin\Language\English\MESSAGES.AMC



The user that start the planning programs first time, they need to have write access to the folder where the program is installed. Because the program will create a file called MESSAGES.AMC.

On the client computer go to the folder c:\program files (x86)\ibm\cognos\c10 and right click.
Select Properties.
Select Security tab.
Select Users in list and click Edit.
Select Users and click in Modify at the Allow column.
Click OK.
Click OK.

This should give all users on that computer write access to the folder C10, try to start your Cognos Configuration or Cognos 10 Planning Analyst program again.

More info:


Cognos Planning 10.2

Windows 2012 server


How install the new Cognos planning on windows server?

Some help:

Use of this information should help you get it right, ensure this things are done before you test the installation.

To integrate with Cognos BI try this  tips from ”How can I install IBM Cognos Planning in the same environment as 64-bit IBM Cognos Business Intelligence”

Error when start Planning Analyst and other tools ”cannot find files”
Ensure to do this:

renamed adminbifs.amf to adminbif.AMF
renamed adminodbc.AMF to adminodb.AMF

Windows supports long file names up to 255 characters in length. Windows also generates an MS-DOS compatible short file name in 8.3 format to allow MS-DOS based or 16-bit windows based programs to access these files. When the 8.3 setting is enabled only short file names are generated. Therefore the long file name of adminbifs.AMF is shortened to adminbif.AMF and adminodbc.AMF is shortened to adminodb.AMF and this causes the error on startup as the file cannot be located as it does not exist under that name and Analyst is a 32-bit program and works off the long file name only.
Error when starting Planning Analyst of type ”cannot connect libraries”
Ensure to do this:

1. Launch MSCONFIG by from the Run menu.

2. Click on the Tools tab. Scroll down till you find “Disable UAC” . Click on that line.
3. Press the Launch button.
4. A CMD window will open. When the command is done, you can close the window.
5. Close MSCONFIG. You need to reboot the computer for changes to apply.


Alternate Solution:
1. Give the everyone group full control to the folder where the libraries are located.

Alternate Solution: If User Account Control resolution above does not resolve issue:
1. Right-click the Analyst shortcut
2. Select Properties > Compatibility tab
3. Check the box: Run this Program as Administrator
4. Now open Analyst as the user who is receiving the error.

To have access to the folders on the SQL server you need to do this:
Install the SQL Server Client tools (if this has not already been done).

NB For SQL Server 2005 you need to have the full SQL Client installed (comes with SQL Express) as the Native Client does not install all of the required .dll files.
For SQL Server 2008 full client tools required.

Once the SQL Server Client tools are installed, ensure that the Contributor user account used to connect to SQL Server has EXEC permissions to the following Extended Stored Procedures in the Masters Database:

Contributor Datastore server connection check Trusted Connection instead of login with an account

Depending on the setup you should use Trusted or SQL account login. Try the other if you have issues like “Subscript out of range”

There are more things to configure — search if you get issues.


Cognos Planning 10.1.1

Cognos Insight

Windows 2008 R2 server

Windows 7 client



How install Cognos Contributor client or Cognos Insight with a Powershell script ?


Script to save in notepad as a file named installrcp.ps1:

#MSI Configuration


$computername = Get-Content ‘\\\cognos102\response\plan\plan_contributor_client\computerTest.txt’

$sourcefile = “\\\cognos102\response\plan\plan_contributor_client\*”

$para0= ” /i”

$para1= ” ALLUSER=1″

$para2= ‘ TARGETDIR=”c:\program files (x86)\ibm” ‘

$para3= ” NOUPDATE=Yes”

$para4= ” /qn /passive”


#This section will copy the software to computer in list


foreach ($computer in $computername)


$destinationFolder = “\\$computer\C$\download\cognos”

#This section will copy the $sourcefile to the $destinationfolder. If the Folder does not exist it will create it.

if (!(Test-Path -path $destinationFolder))


New-Item $destinationFolder -Type Directory


Copy-Item -Path $sourcefile -Destination $destinationFolder



#This section will install the software


$currentLocation = “c:\download\cognos\”

$msi = @(‘contributor.msi’, ‘cognosrcp.msi’)

foreach ($msifile in $msi)



## write-host is for debug to show result of variabled in powershell-ise

## write-host “$env:systemroot\system32\msiexec.exe” -ArgumentList $para0, $msifile , $para1, $para2, $para3 , $para4 -Wait -WorkingDirectory $CurrentLocation


## call the msiexec.exe with paratmeters and starts


Start-Process -FilePath “$env:systemroot\system32\msiexec.exe” -ArgumentList $para0, $msifile , $para1, $para2, $para3 , $para4 -Wait -WorkingDirectory $CurrentLocation





Text files save as PS1 will be run and executed by the Power Shell engine in Windows OS.


To prepare above, you need to create a file share, \\\cognos102\response\plan\plan_contributor_client

where you place the msi files to install and a text file;





The text file computertest.txt should contain the names of the workstations where you want to install the software.


The PS1 file should be on the share, and started from the client computer where you want to install.


In the script the variables are set in the beginning:

$computername = Get-Content ‘\\\cognos102\response\plan\plan_contributor_client\computerTest.txt’

$sourcefile = “\\\cognos102\response\plan\plan_contributor_client\*”

You need to change servername.domain to the path to your file share for this installation.




The * at the end of the source file path means it will copy all files in this folder locally.


$para0= ” /i”

$para1= ” ALLUSER=1″

$para2= ‘ TARGETDIR=”c:\program files (x86)\ibm” ‘

$para3= ” NOUPDATE=Yes”

$para4= ” /qn /passive”

The parameters are for the installation of the MSI;

/i is to tell it to install

ALLUSER=1 is to make the program available to all users on the PC not only the one installing it. This mean it will write values to other paths in registry can CURRENT_USER.

TARGETDIR= is the path to where the software will be install, program files is better than in the windows user profile folder ( c:\user\%username%\AppData\Roaming\IBM\Cognos Insight)

NOUPDATE=Yes will prevent the client software from downloading and update itself when there is a new version of the client on the Cognos Server.

$para4= ” /qn /passive”

Will not show any prompts or error dialogs during the installation, only a progress bar.


foreach ($computer in $computername)

This is a loop function – for each item in the variable list, the steps in the parentheses below are done. Foreach take all items in the list, it does not do any conditional testing.


$destinationFolder = “\\$computer\C$\download\cognos”

This give the variable $destinationFolder the value in ” ” – in this case the contain of variable $computer and the path.

if (!(Test-Path -path $destinationFolder))


New-Item $destinationFolder -Type Directory

Above will check if path exist, if not it will create the folders.


Copy-Item -Path $sourcefile -Destination $destinationFolder

This will copy all files from $sourcefile folder to the $destinationfolder catalog.


$currentLocation = “c:\download\cognos\”

This will set variable where the MSI files to install are.


$msi = @(‘contributor.msi’, ‘cognosrcp.msi’)

Here you list the msi files to install, you can add more like cognosinsight.msi or performancemodeler.msi ( this files are found in folder \ibm\cognos\tm1_64\webapps\pmpsvc\rcp_installs\ on the TM1 server)


foreach ($msifile in $msi)

Will process the code block below for each file in the list.


Start-Process -FilePath “$env:systemroot\system32\msiexec.exe” -ArgumentList $para0, $msifile , $para1, $para2, $para3 , $para4 -Wait -WorkingDirectory $CurrentLocation

Start-process will call the EXE file and start it with the parameters added ( $para1) and so one. The -workingdirectory is where they will be run, so the $currentlocation should be the folder where the MSI files are stored on the local workstation.

Parameters are separated with comma, and can be any number that the exe file supports.

In our case the second parameter is the name of the MSI file to install, so all parameters after the $smifile parameter, are parameters that is for the MSI file.


Hopefully can you improve this script to make it work for your organization.

A other way to run the install in power shell could be with this command

Invoke-Command -ComputerName $computer -ScriptBlock { & cmd /c “msiexec.exe /i c:\download\cognos\cognosrcp.msi” /qn ADVANCED_OPTIONS=1 CHANNEL=100}

A way of populate the variable with current location would be this command

$CurrentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;

A other way to run the install without parameters more than msi file name is command

Start-Process -FilePath “$env:systemroot\system32\msiexec.exe” -ArgumentList “/i `”$msifile`” /qn /passive” -Wait -WorkingDirectory $CurrentLocation


To debug the variables, you can show them in power shell editor by remove remark for this line

## write-host is for debug to show result of variable in powershell-ise

write-host “$env:systemroot\system32\msiexec.exe” -ArgumentList $para0, $msifile , $para1, $para2, $para3 , $para4 -Wait -WorkingDirectory $CurrentLocation

write-host is command to display text and variables on screen.

power shell can be case sensitive in the commands, you need to pay attention to the small caps.


More Information

Cognos Planning 10.1.1
Windows 2008 R2 server
Oracle database

You can not create new Cognos Planning Applications from Cognos Administration Consolde (CAC) and get an error about the password.

{1F3E2C63-11E3-4091-917B-537CFAF5D155} 7 2014-08-18 18:49:20.449 UTC +120 EAdminUI_10 10.1.4074.0 MTSEAdminDB MTSCreateAndPopulateApplication 140 Oracle Automation 440 Unable to execute statement. 28003 ORA-28003: password verification for the specified password failed~ORA-20009: Password must contain at least one digit, one character~~~~~The SQL was:~~CREATE USER go_expenses_contributor IDENTIFIED BY PASSWORD DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS QUOTA UNLIMITED ON USERS QUOTA UNLIMITED ON USERS~~~~The Connect String was:~~Provider=OraOLEDB.Oracle;Data Source=servername.COM;User ID=PLANADM;Password=*********;~~~~SQL execution error, ORA-28003: password verification for the specified password failed~ORA-20009: Password must contain at least one digit, one character~

The issue is that the Oracle Database DBA have applied a strong password policy.
Possible Solution:
Change the default password used by Cognos Planning during creation of the Planning application schema.
Go to the Cognos Planning Admin server. Open the file C:\Program Files (x86)\ibm\cognos\c10\bin\ epEAdminORA8Resources.xml in notepad.
To a new row with a new password that contain a combination of a-z and numbers (0-9)

Save the file. The new default password is now donaldduck747.
Log in to CAC again and test again.

Cognos Planning 10.1.1
Windows 2008 R2 server
Oracle database

You get an error message when you try to add an existing application to the Planning store from inside Cognos Planning Administrator Console.
And the Cognos 10 Planning service is shut down on the Planning Admin Server. You need to restart the Windows Cognos 10 Planning service to continue to work in CAC.
Error message:
An error occurred during the in-place upgrade of your Cognos Planning Application.
Please see the Cognos Planning error log for details on the error.
In the Planningerrorlog.csv file (on the Cognos planning server) you will find;
{B581E2FC-7A35-439C-87D4-FE9AD820842D} 2 2014-08-18 10:44:27.256 UTC +120 AppModelAdmin_10 10.1.4074.0 Admin ApplicationStateWriteDevelopmentDefinitionUsingConnection 240 Microsoft Cursor Engine -2147217864 Unable to update the recordset with SQL of: SELECT definition, definitiondt, appstateguid ~~FROM PSC_ADMIN.applicationstate ~~WHERE appstateguid='{520980BF-780D-46E3-9542-AA695B383343}’~~~~The BLOB with 30418 characters was being written to field ‘PSC_ADMIN.applicationstate.definition’.~~~~Row cannot be located for updating. Some values may have been changed since it was last read.
Other errors you can get as a follow up error are;
{04E4AF77-106D-4829-9129-6C9E4FE34EB7} 1 2014-08-19 08:45:17.655 UTC +120 epsTransport 10.1.4074.0 default OSStub.cpp invokeRemoteMethod 180 epsTransport::default::OSStub.cpp::invokeRemoteMethod::180 -2147467259 general exception in try block
{8BD66C73-3272-4073-A8F5-AA5953A4EB70} 5 2014-08-18 19:32:21.256 UTC +120 UpgradeEng_10 10.1.4074.0 Upgrader InPlaceApplicationUpgrade 110 DebugTools_10 -2147417848 Unable to collect error information from underlying component
{459D64CA-9D0D-46F7-846F-E89B5C9AA5C4} 2 2014-08-19 08:37:55.472 UTC +120 ModelHelper_10 10.1.4074.0 Helper UnPackModel 190 ACE2_10.Model -2147352567 Unable to set the EnvironmentID on the Model, this may be because the J Server is not registered.~~~~Unknown error
Possible solution:
The Oracle driver is not correct installed on the Cognos Planning server.
It can be missing components, like Oracle Data Access Components, in the Oracle client install.
Stop the Cognos Planning and Cognos BI services.
Uninstall the Oracle driver, and manually install a new Oracle driver.
Open Cognos Configuration, save and start the Cognos services again.
Test if you can link to existing application again.
In some cases you may need to erase the fields for the PAD connection inside the Cognos planning application database before you can attach the Application to the pad again.
Open Oracle SQL Developer, log in as a super user account for Cognos Planning, and expand you planning application schema ( for example GO_CAPEX_CONTRIBUTOR).
Open the tables and open the data for ADMINOPTION table.
Clear the optionvalue for PAD_NAME, PAD_GUID and PAD_NAMESPACE.
Commit and exit SQL developer.
Run the test again in Contributor Administration Console (CAC).