Product:
Planning Analytics Workspace 2.1.19
Microsoft Windows 2022 server
Issue:
PAA agent is not connecting to PAW.
The file serversinfo.json in folder D:\Program Files\IBM\tm1_64\paa_agent\paaAgentCache should contain the names of your Tm1 instances. If it is empty, the python script have maybe not been able to read the windows services information.
Error in messages file in folder D:\Program Files\IBM\tm1_64\paa_agent\wlp\usr\servers\kate-agent\logs
[5/5/26, 15:57:40:994 CEST] 00000046 ice.notification.PaKateServerUnresponsiveNotificationService E Error occurred while getting latest servers info from json file
java.lang.NullPointerException: Cannot read field “modules” because the return value of “org.python.core.Py.getSystemState()” is null
at org.python.core.PyModule.module___init__(PyModule.java:64)
at org.python.core.PyModule.<init>(PyModule.java:47)
at org.python.util.PythonInterpreter.<init>(PythonInterpreter.java:104)
Solution:
Restore to the bootstrap.properties file that was installed with the upgrade.
Do not use a backed up file of bootstrap.properties – only add the SMTP parameters you need manually to the new bootstrap.properties.
SMTP_EMAIL_START_TLS_ENABLE=FALSE
SMTP_EMAIL_PASSWORD=
SMTP_EMAIL_PORT=25
SMTP_EMAIL_AUTH=FALSE
SMTP_EMAIL_USERNAME=
PAA_EMAIL_ADDRESS=yourname@domain.com
SMTP_EMAIL_HOST=smtp.yourcompany.domain.com
SEND_GRID_API_KEY=””
Start the PAA agent from the bat file: D:\Program Files\IBM\tm1_64\paa_agent\bin\PAAAgentStart.bat
If above does not work also check this:
- Re-register/Re-register the Agent Service: If upgrading to PAW 2.0.41 or higher, the agent must be updated.
-
- Stop the service.
- Run
<install_dir>\paa\bin\PAAAgentDelete.bat. - Run
<install_dir>\paa_agent\bin\PAAAgentSetJavaHome.bat. - Run
<install_dir>\paa_agent\bin\PAAAgentRegister.bat.
-
- Fix Java Path Issue: If the agent fails to start, run
PAAAgentSetJavaHome.batin<install_dir>\paa_agent\binto ensure the correct Java home is set.
- Ensure the PAA Agent is updated to match the version of PA Workspace in use. If not, then download the newer PAA Agent .zip file from PA Workspace administration UI.
- Review \paa_agent\wlp\usr\servers\kate-agent\bootstrap.properties for PAA Agent configuration errors
- In \paa_agent\wlp\usr\servers\kate-agent\bootstrap.properties verify SERVERS_DIR points to the parent folder of the TM1 data directories, not directly to one specific data directory.
- Review \paa_agent\wlp\usr\servers\kate-agent\server.xml for WLP-related errors
- Review \paa_agent\wlp\usr\servers\kate-agent\logs\ for errors
- Review \pa_workspace_install\logs\monitor\ for errors
*The monitor service is what the PA Workspace Administration page uses to communicate with the PAA Agent - Review \pa_workspace_install\config\paw.env (or paw.ps1) file
- Ensure that the IBM Planning Analytics Administration Agent service is running
- Ensure that the IBM Planning Analytics Administration Agent service account is configured with english locale
- Verify that the PAA Agent URL is accessible in a web browser where PAA Agent is installed (ignore the SSL certificate warning)
URL: https://localhost:9012
If available, PAA Agent just responds “NOT FOUND The application or context root for this request has not been found”
*PAA Agent runs on Port 9012 and uses SSL by default - Verify that PAA Agent is accessible from inside the docker virtual network of PA Workspace. Open Powershell and run these commands:
docker exec -it monitor Powershell cd curl* cd bin .\curl -v telnet://paa_agent_servername ipaddress:9012Replace “paa_agent_servername” by the exact server name specified in \config\paw.ps1 for “TM1Location” parameter (since PA Workspace finds PAA Agent server from TM1 Admin Server location)
- In the web browser, verify that the SSL Certificate is valid
See: https://www.ibm.com/support/pages/node/6562425 - Verify that the PAA Agent URL is also accessible through the Planning Analytics Workspace host by using browser or curl command
URL: https://paa_agent_servername:9012 - Verify that PAA Agent is listening on port 9012: from Windows start menu, run “resmon.exe”, select “Listening Ports”, and verify “javaw.exe” is listening on port 9012
- In Planning Analytics Administration Tool page, verify the IP addresses returned for the Admin Host and TM1 Server
URL: http://workspace_servername:8888 - Does your PAA Agent bootstrap.properties file contain a AGENT_API_KEY setting?
- Does Workspace paw.env / paw.ps1 file have AdminAgentAPIKey set?
See: https://www.ibm.com/support/pages/whats-coming-next-ibm-planning-analytics-workspace-2060
- Does Workspace paw.env / paw.ps1 file have AdminAgentAPIKey set?
- Does your PAA Agent use custom SSL?
- Were the certificates imported into Workspace?
See: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=ctas-configure-tls-between-planning-analytics-workspace-local-other-servers
- Were the certificates imported into Workspace?
- Does your TM1 Admin Server and TM1 Server use custom SSL?
- Were the certificates imported into the PAA Agent keystore?
- Stop the IBM Planning Analytics Administration Agent service
- Update the \paa_agent\wlp\usr\servers\kate-agent\bootstrap.properties file to include
- com.ibm.ws.logging.trace.specification=”*\=audit\:com.ibm.pa.kate.agent.*\=all”
- com.ibm.ws.logging.console.log.level=ERROR
- Start the IBM Planning Analytics Administration Agent service
- Replicate the problem as required
- Review the files in \paa_agent\wlp\usr\servers\kate-agent\logs\
More information:
https://www.ibm.com/support/pages/planning-analytics-administration-agent-not-reachable
https://www.ibm.com/support/pages/how-troubleshoot-planning-analytics-administration-agent
https://www.ibm.com/support/pages/how-obtain-planning-analytics-tm1-server-certificate
https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=only-configure-agent-windows
https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=cloud-configuring-premises-agent
If you find this error in the message.log for PAA agent instead;
Then you have more than one DATA folder, and the model_upload folder is created in wrong data folder. PAW PA Agent does not support more than one DATA folder listed in TM1S.CFG file.




