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

Issue:
Inside TM1 architect you get a error when you run a TI process that uses the Package connector. Error happens when you start to import data to TM1 with the process.

Error Message:
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR3117) Unable to retrieve security objects. Please verify credentials.
– CCL-BIT-0005 A socket reported a communication error.
– CAM_Connect=0xffffffff -2113929065CAM-CRP-0321 The GSKit function ‘gsk_environment_init’ failed with the error code ‘9’

Solution:
Ensure that on the Planning Analytics server, where the TM1 applications are, that you have the GSK*.dll files that come with the TM1 package connector version. If they have been replace to solve other issues, you need to copy them back.

A clean new install of TM1 Package Connector on the PA 2.0.5 server can also help.

More information:

http://www-01.ibm.com/support/docview.wss?uid=swg21988056

Product:
Planning Analytics 2.0.5
PAX and PAW
Cognos Analytics 11.0.12
Microsoft Windows 2016 server

Problem:
When starting Excel and selecting Planning Analytics for Excel (TM1) you get a error after the login dialog.

Error message:
Cognos.Office.Tm1.Connections.Tm1WebException: The remote server returned an error: (503) Server Unavailable. —> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Cognos.Office.Tm1.Connections.Tm1Request.GetResponse()
— End of inner exception stack trace —
at Cognos.Office.Tm1.Connections.Tm1Connection.HandleWebException(Tm1WebException x, Uri path)
at Cognos.Office.Tm1.Connections.Tm1Connection.GetResponse(Tm1Request request)
at Cognos.Office.Tm1.Connections.Tm1Connection.SendRequest(Tm1Request webRequest, AcceptReturnEnum returns)
at Cognos.Office.Tm1.Connections.Tm1Connection.SendRequest(String method, String path, String postData, AcceptReturnEnum returns, Int32 timeout)
at Cognos.Office.Tm1.Connections.Tm1Connection.Get(String path, AcceptReturnEnum file, Int32 timeout)
at Cognos.Office.Tm1.Rest.Tm1RestCapabilities..ctor(Tm1Connection connection, String server, Int32 timeout)
at Cognos.Office.Tm1.Rest.Tm1RestConnection.RefreshCapabilities(String server, String path)
at Cognos.Office.Tm1.Rest.Tm1RestServer.UpdateCapabilities(String serverName)
at Cognos.Office.Tm1.Rest.Tm1RestDataSource.UpdateCapabilities(String serverName)
at Cognos.Office.Tm1.Tm1DataSource.On_LogOn(String server)
at Cognos.Office.Tm1.Tm1DataSource.Logon(LogonType logonType, DataSourcePropertiesCollection properties)
at Cognos.Office.Framework.Communications.DataSourceManager.LogOn(String dsType, String connectionString, String serverName, IDataSource& source)

Solution:
Check the values in PAW Admintool, special for the TM1 Application Server gateway URI. If that is wrong, like use HTTP instead of HTTPS when you have switch TM1WEB to use SSL, you will get above error inside PAX. To surf to PAW will still work fine.

When a user start Excel and PAX, the first connection is to the PAW server.
Then the PAW server will check the TM1S.CFG for value ClientCAMURI=http://caservername.domain.com/ibmcognos/bi/v1/disp
this URL will be used by PAX to log you in. After you login, the PMHUB.HTML file need to list the URL to PAW to allow you to get back.
You need to check the pmhub.html file in folder c:\Program Files\ibm\cognos\analytics\webcontent and c:\Program Files\ibm\cognos\analytics\webcontent\bi.
Open it in notepad++ and check that the PAW servers name or DNS alias at var pmhubURLs = [“https://tm1web.domain.com:9443” , “https://centospaw.lab.local”];
When you are back at PAW server in the communication route – pax will use the PAW ADMINTOOLS value in TM1 Application Server gateway URI before it show you are connected. If that value does not point to the CA11 server you get above error.

PAX is not using the PAW ADMINTOOLS value for IBM Cognos BI Gateway URI, instead you have the value  export TM1LoginServerURL=”https://tm1serverhost:12345″ in the paw.env file. The TM1 application that use the HTTPPortNumber = 12345, that value in its tm1s.cfg file is used.

If the value in PMHUB.HTML is wrong you get a error like “Cannot redirect back to planning analytics because the host URL (http://centospaw.lab.local) has not been whitelisted.”

Do not enter the port number for paw server in the PMHUB.HTML file.

Product:
Planning Analytics 2.0.4 (TM1)
Microsoft Windows 2016 server

Problem:
TM1 Architect is connecting the TM1 applications on the wrong network card on the Microsoft Windows server.

Possible solution:
The default network card with the lowest metric value is selected from all network cards to be the default network card. Use Get-NetIPInterface to see metrics.

Start Powershell on the Windows server
Enter: Get-NetIPInterface
This will list the network interfaces on the server.
Check the value for ifIndex and InterfaceMetric (A low value indicates a higher priority.)
The card with lowest value for InterfaceMetric will be used by TM1.
Is this the correct one? or is it for a backup network?

ifIndex InterfaceAlias AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp ConnectionState PolicyStore
——- ————– ————- ———— ————— —- ————— ———–
18 Ethernet 2 IPv6 2800 20 Enabled Connected ActiveStore
1 Loopback Pseudo-Interface 1 IPv6 4294967295 50 Disabled Connected ActiveStore
18 Ethernet 2 IPv4 2800 20 Disabled Connected ActiveStore
12 Ethernet IPv4 1500 10 Enabled Connected ActiveStore
1 Loopback Pseudo-Interface 1 IPv4 4294967295 50 Disabled Connected ActiveStore

Change with Set-NetIPInterface, for example:
Set-NetIPInterface -InterfaceIndex -InterfaceMetric
Example
Set-NetIPInterface -InterfaceIndex 12 -InterfaceMetric 50
Set-NetIPInterface -InterfaceIndex 18 -InterfaceMetric 10
Above will make card 18 to be the new default.
Check the ip address of the card by enter IPCONFIG
Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a8cd:d4c4:120e:3ed1%18
Autoconfiguration IPv4 Address. . : 169.254.62.209
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 25.255.255.254

Start TM1 Architect
Expand an TM1 application
See in the right side the IP address that will be used.

More information:
https://docs.microsoft.com/en-us/windows-server/networking/technologies/network-subsystem/net-sub-interface-metric
https://social.technet.microsoft.com/Forums/windows/en-US/cb8dac7f-5f04-42b1-8065-a95c946f6ec2/change-network-adapter-priority-order?forum=ws2016

Product:
Cognos Planning Analytics Workspace version 30
Microsoft Windows 2016 Server

Problem:
In a Planning Analytics (TM1) environment where native security is used, you get a error when you try to add content to workspace from the PA databases on left side of screen.

Error Message:
unable to fetch data for content tree. Session can not be established for server: BUDGET 401 (Unauthorized) (“errorMessage”.””.”query”.”https://…..

Possible Solution:
Log out from Workspace
Go into TM1 Architect.
Set a password for all users, do not use blank (empty) as a password. That will not work for workspace. Also ensure that the ADMIN account have a password like apple.

After the user have a password set, exit TM1 Architect and surf to Planning Analytics Workspace again.

Product:
Planning Analytics 2.0.4 on Microsoft Windows 2012 server
Planning Analytics Workspace 30 on Linux server
Cognos Analytics 11.0.9 on Microsoft Windows 2012 server

Issue:
https://www.ibm.com/communities/analytics/cognos-analytics-blog/cognos-analytics-and-planning-analytics-integration-walkthrough-part-2/
Have setup PA with SSO to CA11 as above link, but when a user surf from Internet Explorer to PAW at address http://pawservername.domain.com/ –  the user end up logged into the CA11 portal (cognos connection) instead of the PAW page.

Solution:
Start PUTTY and login to the Linux server
Enter sudo -su to a root user.
Go to the ../paw folder.
Go to the /paw/config folder.
Enter more paw.env  to see the settings used in Planning Analytics Administration Tool listed on screen. They are saved to this file paw.env
Enter nano paw.env  to be able to edit the file.
Change the IBM Cognos BI Gateway URI and IBM Cognos BI Dispatcher URI fields, to both end with /bi/v1/disp

pawsso

(in later versions of PAW the IBM Cognos BI Dispatcher URI should be http://caservername.domain.com:9300/p2pd/servlet/dispatch)

Two lines in paw.env should look like this;
export IBMCognosGatewayURL=”http://caservername.domain.com:80/ibmcognos/bi/v1/disp”
export IBMCognosServlet=”http://caservername.domain.com:9300/bi/v1/disp”

Press CTRL+X to exit the NANO editor in linux.
Press Y to save the changes to paw.env file.

In the paw/scripts folder enter ./paw.sh down  to stop the PAW services.
In the paw/scripts folder enter ./paw.sh to load the PAW services again.
In the paw/scripts folder enter ./paw.sh start  to start the PAW services.
Wait 10 minutes.
Surf to http://pawservername.domain.com  to test if it works.

This change can also be done in the Planning Analytics Administration Tool, but then you first need to turn off SSO in IIS and change to security mode 1 in tm1s.cfg file.

More Information:
https://www.ibm.com/communities/analytics/cognos-analytics-blog/cognosanalytics-and-planninganalytics-integration-walkthrough-part-3/

https://community.ibm.com/community/user/businessanalytics/blogs/nadine-mnch/2018/03/07/cognosanalytics-and-planninganalytics-integration-walkthrough-part-3

https://www.ibm.com/support/pages/cognos-analytics-and-planning-analytics-integration

Product:
Planning Analytics Workspace 2.0.4
Microsoft Windows 2016 server

Issue:
When starting the PAW administration tool you get a error when updating settings.

Error Message:
Failed to fetch the status. Ensure the Administration tool is running.

If you from a power shell prompt test the installation by running the command ./paw.ps1 ( from folder d:\install\paw\scripts\) you get this error:

Error: for pa-gateway Cannot start service pa-gateway: failed to create endpoint pa-gateway on network NAT. HNS failed with error: The object already exist.
Encountered errors while bringing up the project.
Execution failed with exit code 1.

Troubleshoot:
Use the scripts/paw.ps1 script instead of Administration tool from power shell prompt.
Enter scripts/paw.ps1 to ensure all services are running and up-to-date.
Enter scripts/paw.ps1 ps to see status of all services.

Above may show that you have a pa-gateway already running.
Check that no other application is using port 80 and 443.
Start IE on the server and surf to http://localhost/ – what does that give?

Stop all PAW with scripts/paw.ps1 down
Then start it again with scripts/paw.ps1

Did it help?

Enter docker ps -a to see all running containers. Any duplicates?
Then to remove a container enter docker stop <container-id> ; then docker rm <container-id>.

Check the log files in folder D:\install\paw\log\pa-gateway\error.log
If you see this; AH00558: httpd.exe: Could not reliably determine the server’s fully qualified domain name, using fe80::5db7:f898:8a1:858c. Set the ‘ServerName’ directive globally to suppress this message. Then that is nothing to be concerned about.

To remove installation of PAW on Microsoft Windows 2016 do this steps in paw folder:
scripts/paw.ps1 stop
scripts/paw.ps1 rm -v
docker rm $(docker ps -a -q)
docker rmi $(docker images -q)
…after that you can install again with ./Start.ps1

You can recreate the docker network with below commands (try this first):
Stop the docker service: stop-service docker
Make sure the hns service is running: start-service hns
Now run this PowerShell command: get-containernetwork | remove-containernetwork
Start the docker service again: start-service docker

If it still doesn’t work, you can also try the same steps except with get-netnat | remove-netnat:

Stop the docker service: stop-service docker
Make sure the hns service is running: start-service hns
Now run this PowerShell command: get-netnat | remove-netnat
Start the docker service again: start-service docker

After that is done, go to the d:\install\paw\scripts folder in power shell.
Start the PAW with ./paw.ps1 start.

Check the file D:\install\paw\config\paw.ps1 contain the values you have set in the administration tool before. Should look similar to this;
# paw.ps1 file generated by the Administration Tool
$env:TM1Location=”https://labwin2012ca.lab.local:5898″
$env:TM1ApplicationsLocation=”http://labwin2012ca.lab.local:9510″
$env:PAAuthMode=”tm1basic”
$env:TM1LoginServerURL=”https://labwin2012ca.lab.local:8010″

Surf to servername to see if paw is working e.g.  http://labwin2012ca.lab.local/

To get more detail debug info on screen,
stop the docker service.
Run the Docker daemon in debug mode:
C:\Program Files\Docker\dockerd -D

More Information:

https://github.com/MicrosoftDocs/Virtualization-Documentation/issues/529#issuecomment-310236487

https://docs.docker.com/v17.09/engine/userguide/networking/

https://docs.docker.com/config/daemon/

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

 

Product:
Cognos Analytics 11.0.10
Microsoft Windows 2016 Server

Issue:
When you try to install the ExternalDiskCache_amd64_en-US.msi you get a error.

Error Message:
IIS version 7.0 or greater is required to install Microsoft External Cache Version 1 for IIS 7

Workaround:
You can resolve this problem by modifying registry.

Open run dialog and enter regedit, to open the Registry Editor.
Find MajorVersion in the path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters.
Open the value MajorVersion and select Decimal radiobutton.
Change Its value from 10 to 9.
Click OK.

After finishing the steps above, you can install External Disk Cache and Microsoft Web Farm Framework successfully.

You can also try download a new version from here
https://blogs.iis.net/iisoobs

More Information
https://docs.microsoft.com/en-us/iis/extensions/installing-application-request-routing-arr/install-application-request-routing-version-2
http://www-01.ibm.com/support/docview.wss?uid=swg22000097

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.