Product:
Planning Analytics 2.0.6
Microsoft Windows 2016 server
Planning Analytics Administration Agent version 1.0.36.736

Problem:
When starting the PAA Agent in windows after change from local system to a windows service account, you get a error. The service account works on the other IBM Cognos TM1 services, only the IBM Planning Analytics Administration Agent that does not start.

Error msg in Windows event log can be:
The IBM Planning Analytics Administration Agent service terminated with the following service-specific error:
Incorrect function.

Solution:
Check that the Windows Service account is local administrator on the Planning Analytics server.
The PA Agent needs more local rights to read the files in folder D:\Program Files\ibm\cognos\tm1_64\paa_agent, than the other IBM Cognos TM1 service does.

You can find the message.log file here D:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\logs, that can contain more error messages.

The python code that can give some of the message is in folder; d:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent\kateagent\scripts\status.py

More information:

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

Instructions to configure and start PAA Agent:

1. Open Windows “Services” desktop application
2. Stop “IBM Planning Analytics Administration Agent” service, if running
3. Navigate to <PA install directory>\paa_agent\wlp\usr\servers\kate-agent
4. Open the bootstrap.properties file in a text editor
5. Set the full path of directory containing TM1 databases data directories to SERVERS_DIR. Multiple paths must be separated by semicolon.
E.g. SERVERS_DIR=C:\tm1\samples\tm1\;C:\prod\servers\
6. Save and close the bootstrap.properties file
7. Start “IBM Planning Analytics Administration Agent” Windows service
8. PAA Agent is now ready to use

Product:
Cognos Analytics 11.1.3
Planning Analytics 2.0.6
Microsoft Windows 2016 server

Problem:
When run a CA11 report against a Tm1 Cube, you get this error;
XQE-MD-0007 Unable to establish a metadata connection to data source /content/package
DIM-ERR-1007 Det gick inte att efterfråga kubinformation för datakällan. Kontrollera anslutningssträngen och se till att servern är tillgänglig.

Solution:
The user who runs the CA11 report must have access to data in the TM1 cube.
Go in to TM1 Architect, and right click and select Rights – clients/groups dialog.
Check the user belongs to some of the security groups.
For a quick test, mark your user as ADMIN.
Click OK.
And log out from CA11 and in again, try the same report again.

If you get the below error when you run a Cognos Analytics 11 report;
QE-DEF-0157 The model or package /content/folder does not exist or you are not allowed to use if because of security settings.

Then it can be that the FM package is deleted.

Click on search icon on the left in Cognos 11, and search for the package name. If you find it, check that the user group the user belongs to have “run” rights, on the package.
More Information:
https://www.ibm.com/support/pages/dim-err-1007-failed-query-cube-information-data-source-when-using-planning-analytics-data-server-connection
https://www.ibm.com/support/pages/dim-err-1007-failed-query-cube-information-data-source-tm1

https://www.ibm.com/support/pages/package-permissions-errors-qe-def-0157

Product:
Planning Analytics 2.0.8 workspace
Microsoft Windows 2016 datacenter

Problem:
When surf to paw (on a windows 2016) server and you enter name and password for the TM1 native login method. The screen flickers, and nothing happens. You see the blank login screen again.
If you surf from a local computer it works fine, it is only when you surf over a VPN tunnel from a partners laptop, you can not login.
If you surf to the PAW (http://servername.domain.com/) from a server, there is no problem – it works fine.

Solution:
Check your antivirus program – so it is not stopping the connection because it is unsecured.

For example; Bitdefender internet Security can have a policy: Feature: Online Threat Prevention
“Privacy threat blocked
An attempt to send your password unencrypted was about to occur on servername. We blocked the connection to stop your private data from being exposed and tampered with.”

Click on Add to exceptions, and add the PAW server to you internet security programs exceptions list.
Other solution is to add HTTPS to you paw server.
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_paw_enable_ssl.html

Ensure also that you are not using the same sub-net as the paw docker network. Normally docker paw network is a 172.x.x.x network.
You update docker network in file C:\ProgramData\docker\config\daemon.json with the following contents:
{
“fixed-cidr”: “192.168.80.0/24”
}

You need to restart docker.

More information:
https://www.ibm.com/support/pages/troubleshooting-planning-analytics-workspace-related-docker-issues
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_paw_trbl_cant_access_over_vpn_ip_address.html

https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture

https://forums.docker.com/t/ip-address-for-container/27454/4

https://www.eiseverywhere.com/file_uploads/b16ad176a58e3a9a360d66f1a4009c4e_Plan_IBMPlanningAnalyticsLocal_SoufianeAzizi.pdf

http://www.pantarhei.at/wp-content/uploads/2018/06/PAW-Local-Distributed-Soufiane-Azizi.pdf

Product:
Planning Analytics 2.0.8
Planning Analytics Workspace 45
Microsoft Windows 2016 server

https://www.ibm.com/support/pages/ibm-planning-analytics-pa-workspace-and-pa-microsoft-excel-fix-list

Problem:
After a reboot of the server, the docker service does not start. If you login to server and click on start in the service manager it will start. Ensure that you wait 5 min before testing with “start”.

Suggested Solution:
Check the format of the c:\programdata\docker\config\daemon.json file.
If it contain illegal characters, the docker service will not start.

If you enter docker ps or docker version to see running containers you get this message:

If you check the C:\ProgramData\docker\panic.log you may see this:

Failed to fire hook: The interface is unknown lock: = it did not get the response it needed in time, but windows service will try again in a few minutes,  so wait an see if it starts.

If you check the windows event log, you may see this:

Open the file c:\programdata\docker\config\daemon.json in NOTEPAD++
ensure it looks correct, and do not have any errors.

Debug parameter will write more information in the Windows Event log for Docker. When you have issues with Docker, check the Windows Event log for any errors.

You can copy the text in the json file to this site, to validate https://jsonformatter.curiousconcept.com/

There can be other causes, for this problem, that the docker service does not start.

Ensure that one network cards is prioritize, and that your DNS is working from this server.

You need also at least 4 cpu and 32 GB ram on the PAW server.

More information:
https://blogs.msdn.microsoft.com/jikuma/2018/03/19/error-pipedocker_engine-access-is-denied-in-the-default-daemon-configuration-on-windows/
https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon#set-docker-security-group
https://www.reddit.com/r/docker/comments/82myaw/invalid_character_in_string_escape_code/
https://docs.docker.com/v17.09/engine/admin/#start-the-daemon-manually

https://success.docker.com/article/error-streaming-logs-invalid-character-after-object-key-value-pair

Product:
Planning Analytics 2.0.8
Planning Analytics Workspace 45
Microsoft Windows 2012 server

Problem:
When you surf to your PAW, and go to Administrator page, tab – Databases. It says the Agent is not available.

Solution:
Even do you are on the same server. You need to open the Windows Firewall inbound port 9012 to make the PAW have access to the PA Agent.

Go to Control Panel
Go to Administrative tools
Go to Windows Firewall
Click Inbound Rules
Click New Rule
Select Port
Enter 9012 (and the other TM1 ports) at Specific Local ports
Click next for Allow the connection
Click next to keep that the rule apply to all domains
Enter a name like “Cognos TM1”
Click Finish

Now it should work.

When you check a previous made firewall rule it can look like this;

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_administer_servers.html
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_tm1_inst_defaultvaluesfortm1installation.html