Product:
Planning Analytics 2.0.4
Planning Analytics Workspace 30
Microsoft Windows 2016 Server

Issue:
You have installed docker, but before you install PAW, you realize that you do not have the needed 50 GB of free space on C drive. How do I tell docker to create the images on the D drive?

Solution:
Create a folder d:\docker\images
Stop the docker service
Open Notepad and enter this
{
“data-root”: “d:\\docker\\images”
}
save the file as c:\programdata\docker\config\daemon.json

docker1 docker2
Start the docker service

Any previous created images in C:\ProgramData\docker\containers\ are not moved.

How Install Docker on Windows 2016 – Get Docker EE for Windows Server
Docker EE for Windows Server 2016 is simple to install.
1. Installation

Open a PowerShell command prompt, and type the following commands:

Install-Module DockerProvider -Force
Install-Package Docker -ProviderName DockerProvider -Force

2. Test your Docker EE Installation
Test your Docker EE installation by running the hello-world container:

PS> docker container run hello-world:nanoserver

Unable to find image ‘hello-world:nanoserver’ locally
nanoserver: Pulling from library/hello-world
bce2fbc256ea: Pull complete
3ac17e2e6106: Pull complete
8cac44e17f16: Pull complete
5e160e4d8db3: Pull complete
Digest: sha256:25eac12ba40f7591969085ab3fb9772e8a4307553c14ea72d0e6f98b2c8ced9d
Status: Downloaded newer image for hello-world:nanoserver

Hello from Docker!
This message shows that your installation appears to be working correctly.

Download a working docker-compose-Windows-x86_64.exe file;

Invoke-WebRequest "https://github.com/docker/compose/releases/download/1.21.0/docker-compose-Windows-x86_64.exe" -UseBasicParsing -OutFile $Env:ProgramFiles\docker\docker-compose.exe

Rename it to docker-compose.exe and copy it to the c:\program files\docker folder.

Then after a reboot of the Windows 2016 server, turn off your Anti-Virus software and start your PAW installation from a administrative powershell prompt with the command ./Start.ps1

More about docker:
https://blog.devmatter.com/docker-on-windows-server-2016-the-journey-begins/
https://sysinfo.io/ubuntu-16-04-move-docker-root/

https://docs.docker.com/compose/install/#install-compose

Installation videos on planning analytics workspace:

https://www.youtube.com/channel/UC3kn-tJsPigGlmaaO9EcisQ

Product:
Planning Analytics 2.0.4
Planning Analytics Workspace 2.0.4
Microsoft Windows 2016 Server

Issue:
When you run Start.bat under Windows 2016 to install PAW you get a error.

Error message:
ERROR: The system was unable to find the specified registry key or value.
Install Docker Toolbox for Windows and try again.

Possible Solution:
You have follow this instructions to install Docker for Windows 2016.
https://docs.docker.com/install/windows/docker-ee/#install-docker-ee
But you have downloaded the wrong PAW file that is for Windows 2012 and try to install that.
Here how setup Windows 2012 with docker
https://docs.docker.com/docker-for-windows/install/
If you have the correct PAW file for Windows 2016 you should start a powershell file called Start.ps1.
Download the correct file ipa_workspace_local_win_2.0.30.228.6.zip from below link
http://www-01.ibm.com/support/docview.wss?uid=swg27049597

and from a powershell prompt enter ./Start.ps1 to install PAW.

Product:
Planning Analytics 2.0.4
Planning Analytics Workspace 2.0.4
Microsoft Windows 2016 Server

Issue:
When you in powershell run ./Start.ps1 from paw_2.0.4_win16_ml folder you get a error.

Error message:
unable to invoke ‘docker-compose’. Ensure docker-compose is installed and is on the PATH

Possible solution:
Check that the file docker-compose.exe exist in folder c:\program files\docker
Enter PATH at a DOS prompt to check that c:\program files\docker is part of your path string.
In a DOS prompt enter DOCKER-COMPOSE VERSION, do you get a message that
‘docker-compose’ is not a recognized as an internal or external command, operable program or batch file?
Go to the docker folder with command cd \program files\docker and try the DOCKER-COMPOSE again.
Same error, try enter DOCKER-COMPOSE.EXE. Does that work?
If you get a list of possible docker commands, it works.
But the DOCKER-COMPOSE.EXE file can be corrupt.
Erase the DOCKER-COMPOSE.EXE file and copy a new file to the docker folder.
Rename the new DOCKER-COMPOSE-Windows-x86_64.exe file to DOCKER-COMPOSE.EXE and try again to enter only DOCKER-COMPOSE.
If that works, and you get a list of commands, then the file was corrupt.
Please try ./Start.ps1 again from your powershell session.

Product:
Planning Analytics 2.0.4
Planning Analytics Workspace 30
Microsoft Windows 2016 Server

Issue:
When you validate settings in PA Workspace Administration Tool page you get a error for TM1 Application Server Gateway URI:

Error Message:
Error: getaddrinfo ENOTFOUND servername servername:9510

Possible Solution:
Port 9510 is not open in the local Windows Firewall on the server.
Go to Control Panel
Go to Windows Firewall
Go to Advanced Settings
Click on Inbound Rules
Click on New Rule
Select Port and click Next
At Specific local ports enter 80,443,9510,5495,5498,8888, 12345,12354,53333,5011,12346,8010 and click Next. The last port numbers depend on what you have set in your tm1s.cfg file.
Click Next at Allow the connection
Click Next when the rule apply for all (Domain, Private, Public)
Enter a name like Cognos TM1 and click Finish
Check the validate again.

Product:
Planning Analytics 2.0.4
Planning Analytics Workspace 30
Microsoft Windows 2016 Server

Issue:
When you in PA Workspace Administration Tool click on validate you get a error for TM1 Admin Server URI.

Error Message:
Error: connect ECONNREFUSED 127.0.0.1 443

Possible Solution:
The text you have entered in the field for TM1 Admin Server URI is not correct.
You have installed PA and PAW on a Windows server you have named DonaldDuck.
In the field you have entered:
https:/donaldduck.domain.com:5898

Note that you have missed one / at the https:/ point where it should be https://

Enter https://donaldduck.domain.com:5898 and test again.

Product:
Planning Analytics 2.0.3
IBM Cognos TM1 Applications
Microsoft Windows 2016 server

Issue:
When publishing a updated TM1 application in Performance Modeler to the TM1 Applications web (contributor web portal), the application is deleted.

Error can be:
[DeployApplicationThread:9b649fa9-1cf1-46f7-9bae-5f2fde393121] ERROR () com.ibm.cognos.pmpsvc.PMPService – deployApplication Throwable
com.ibm.cognos.pmpsvc.PMPSVCException: An exception occurred on the server. Please contact your system administrator. :com.ibm.cognos.pmpsvc.handler.PMPTM1Exception: TI_NODE_NOT_EXIST[CAMID(“CDS:u:uid=roger,ou=people,ou=eu”) | }tp_modify_application_attribute | }ElementAttributes_}tp_applications, BounceMode ] :EXCEPTION

Solution:
There is a chance that there are “left-overs” from a old application with similar name in the portal, therefor the application is deleted before a new is created. The first time you publish a TM1 application to a new PMPSVC (contributor) web server, you need to ensure there is not a old application there since a previous crash.

Before republishing a old TM1 10.2.2 application to a new PA 2.0.3 server do this;
— stop the TM1 instance windows service.
— erase the log folder for the tm1 instance.
— copy a new fresh data folder from the TM1 10.2.2 application.
— surf to http://paservername.domain.com:9510/pmpsvc and remove the old application with the same name from the list of applications. You do this from the TM1 applications configuration page. You must be ADMIN in the TM1 instance you try to remove.
Check in the file TM1InstallRoot\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml that the application is not listed any more.
— stop the IBM Cognos TM1 windows service (tm1web and pmpsvc service).
— surf to Cognos Analytics http://caservername.domain.com/ibmcognos and go to Team Content – IBM Cognos TM1 Applications – My Applications. Remove the link to your published application. PM can not publish a application if there already exist on with the same name.
— start the IBM Cognos TM1 Windows service (pmpsvc service).
— start the TM1 instance, that you had issues with.
— Surf to http://paservername.domain.com:9510/pmpsvc and add the TM1 instance to the portal, and make it a application you can work with from PM tool.
— Log into Performance Modeler as a ADMIN in your TM1 application. Open up and see the application you have built before, validate the application first. Then try to publish it again.

If you have a working TM1 instance, then above should solve the issue, because you start from a fresh working data folder. There should not be any corrupt files you need to delete. Surf to http://paservername.domain.com:9510/pmpsvc to see if it worked.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.doc/c_tm1_inst_contrib_strtlnk.html

If you Run the }tp_admin_delete_all process from Architect, then all applications can be erased, and you may have to recreate them.

Product:
Planning Analytics 2.0.3
IBM Cognos TM1 Applications
Microsoft Windows 2016 server

Issue:
When user inside Cognos TM1 Applications (contributor) are reporting there numbers. Then they click on X to close the window, they get a error message: 54: ObjectNameInvalid, when they press OK the application exits as it should.

Only when you use CAM authentication.

Suggested Solution:
You are using Internet Explorer in wrong emulation mode.

Press F12.
Select Emulation.
Change Document mode to Edge or 10, from 11.
Go into the node again and test.

To get to TM1 Applications you surf to http://paservername.domain.com:9510/pmpsvc

This error can also be found if the name of the TM1 application is to long, so the total length of the temp files BLB is more than 255 characters on the Windows server. During start of the Contributor session a blb file is created with the user name as filename in the datafiles folder, if this file is not created (due to its name is to long), when you exit your Planning Analytics Contributor application you get above error, because TM1 can not find the file and erase it.  All work, but you get a irritating error.

Solution is to have TM1 instances installed with short names like d:\tm1server\112\datafiles or similar.

You can also find in the tm1server.log error like this NAME INVALID error and that causes TM1.Blob FileCreateOpenDelete.

Product:
Planning Analytics 2.0.3
Planning Analytics Workspace  (ipa_workspace_local_2.0.29.1080.2.zip)
Microsoft Windows 2016 server
Red Hat Linux server

Problem:
When inside PAW, and you try to expand a node of a TM1 instance, you get a error message.

Error:
Session can not be established for server proven_techniques 500 (internal server error) “code” “explorer” “refID” “message” .”Failed to get children for server cubes”. “cause”.”java.net.NoRouteToHostException: No route to host”.

paw39
Solution:
In one case this is because of DNS and routing problems in network. The PAW server and PA server have both two network cards, and can only communication on one of them.
You must in TM1S.CFG tell Tm1 instance what network card it should use.

Add the line
IPAddressV4=”10.200.30.40″
in TM1S.CFG and restart the TM1 instance.

Replace the ip number with the correct ip address of your Planning Analytics server.
Important that the IP address are inside ” double quotation mark.

Product:
Planning Analytics Workspace
Planning Analytics 2.0.3
Microsoft Windows 2016 Server

Problem:
When user surf to the PAW, they are not administrator and can not add other users.
Surf to http://pawservername.domain.com
Click on the user — and see there is not a option for Administration.
This is a new PAW setup with CAM authentications.

Solution:
The first users that you add in a TM1 instance as ADMIN will be admin in paw when you login to paw. Therefor you must add CAM users to a native TM1 instance first.

Open up a Tm1 application in Native mode. Like Proven_Techniques.
Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Add the lines;
IntegratedSecurityMode=2
ServerCAMURI=http://caservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=http://caservername.domain.com:80/ibmcognos/bi/v1/disp
Close TM1 architect.
Update the C:\Users\%username%\AppData\Roaming\Applix\tm1\tm1p.ini file with
AllowImportCAMClients = T
CognosGatewayURI = http://caservername.domain.com:80/ibmcognos/bi/v1/disp

Start PAW administration console and surf to http://pawservername.domain.com:8888
Setup like this (change to your servers name);
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Authentication Mode: TM1
TM1 Login Server URI: https://paservername.domain.com:5011
Click validate and update.

(This TM1 instance you point out with the HTTPport number is the instance that will define the first ADMIN in paw, even if you use security mode 5).

Start TM1 Architect and login to Proven_Techniques as Admin.
Go to Security – Client/Groups. From menu Clients select Add New Client.
Add your CAM user from your AD domain, that you want to be ADMIN in paw.
Mark the user to be ADMIN in TM1 Architect. Click OK.
Exit Tm1 Architect.

Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Change; IntegratedSecurityMode=5
Save the file and restart the TM1 instance.
Now TM1 instance is using CAM authentication.

Update PAW admin console by surf to http://pawservername.domain.com:8888
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Change to Authentication Mode: CAM
Set IBM Cognos BI Gateway URI: http://caservername.domain.com:80/ibmcognos
Set IBM Cognos BI Dispatcher URI: http://caservername.domain.com:9300/p2pd/servlet/dispatch
Set IBM Cognos BI Authentication Namespace ID: AD
Click Validate and update.
Click on status tab – wait until CPU usage is below 1%.

Surf to http://pawservername.domain.com
Login as the CAM user you have given ADMIN rights in Proven_Techniques.
This user should now have a ADMINISTRATOR option under its name.

The list will only show name for people who have already try to login.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_paw_administration_top_level.html

Product:
Cognos Tm1 10.2.2 Fix pack 7 (10.2.5270.108)
Microsoft Windows 2008 R2 server

Issue:
When click save in TM1 Cognos Configuration you get a error message that you can not save, but can save in plain text.
The Cognos TM1 Application Web is using the value Environment – group properties – Gateway uri as default values in http://localhost:9510/pmpsvc setup.
If localhost is used in Cognos Configuration, the BI services (if it exist) on the local server is used as key for the creation of the crypto files.

Error details:
[Cryptography]
[ ERROR ] CAM-CRP-1132 An error occurred while attempting to request a certificate from the Certificate Authority service. Unable to connect to the Certificate Authority service. Ensure that the Content Manager computer is configured and that the IBM Cognos services on it are currently running. The HTTP result code ‘500’ was returned from the server.

but first you may get
:java.lang.nullpointerexception
when you try to save Cognos Configuration.

Possible workaround:
In Cognos Configuration, select Local Configuration, click the and then click Add.

Type StandaloneCertificateAuthority in the Name box.
Type True in the Value box.
Click OK.

This will make the TM1 cognos configuration not use the BI values to create the crypto keys.

Check also that you have not installed a fix pack over a TM1 installation that uses custom key certs.
Check that you have access to the Cognos BI server by in IE surf to http://cognosbiservername:80/ibmcognos/cgi-bin/cognosisapi.dll
Check that the Cognos Controller FAP or Cognos TM1 admin services is stopped when you update Cognos Configuration.
Check that you do not have doublets of the Cognos TM1 admin services.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21655725&myns=swgimgmt&mynp=OCSS9RXT&mync=R
http://www-01.ibm.com/support/docview.wss?uid=swg21902547
https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.3.doc/t_config_tm1_cont.html