by ·Comments Off on Error occurred while updating the server info json file java.lang.NullPointerException: Cannot invoke “java.lang.String.length()” because “s” is null

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:56:20:933 CEST] 00000046 com.ibm.pa.kate.agent.scheduler.ScheduledTask                E Error occurred while updating the server info json file
java.lang.NullPointerException: Cannot invoke “java.lang.String.length()” because “s” is null
at org.python.core.PyString.charsFitWidth(PyString.java:122)
at org.python.core.Py.fileSystemEncode(Py.java:786)
at org.python.core.PySystemState.initArgv(PySystemState.java:1324)

[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.
      1. Stop the service.
      2. Run <install_dir>\paa\bin\PAAAgentDelete.bat.
      3. Run <install_dir>\paa_agent\bin\PAAAgentSetJavaHome.bat.
      4. Run <install_dir>\paa_agent\bin\PAAAgentRegister.bat.

  • Fix Java Path Issue: If the agent fails to start, run PAAAgentSetJavaHome.bat in <install_dir>\paa_agent\bin to ensure the correct Java home is set.

 

Generic:
  • 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
Connectivity-Related Errors:
  • 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:9012

    Replace “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 your PAA Agent use custom SSL?
  • Does your TM1 Admin Server and TM1 Server use custom SSL?
    • Were the certificates imported into the PAA Agent keystore?
Other problems encountered with the PAA Agent might require extra debugging to be enabled for review.

 

Enable PAA Agent Debug Logging:
  • 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;

[5/5/26, 17:04:14:303 CEST] 000003d9 bm.pa.kate.agent.service.fileManager.LocalFileManagerService E Failed to CREATE the ‘model_upload’ folder, err:
java.nio.file.NoSuchFileException: d:\tm1 data\faptest\Data\;.\Data_SysSettings\model_upload
at java.base/sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at java.base/sun.nio.fs.WindowsFileSystemProvider.createDirectory(Unknown Source)

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.

by ·Comments Off on Blank page when run standard report

Product:

Cognos Analytics version 12.1.2.15
Cognos Controller version  11.1.1003
Microsoft Windows 2022 server

Issue:

After upgrade to later version of Cognos Analytics, that is used for CAM login and Controller standard reports, the reports inside Cognos Controller does not work.

Solution:

The newer version of CA 12.0.4 and later have a different setup of MIME parameters. This is setup in IIS by the new CA_IIS_Config.bat script.

You can add it manually to IIS.

Go to IIS Manager and select the web site “ibmcognos”

Click on the MIME types icon

Add this

.mjs : application/javascript

Click OK

And restart the IIS server.

Restart Cognos Controller and run a standard report again.

 

If the PDF report works in Chrome, but not in a Edge browser, then you may need to add this:

Revert the report viewer to a more compatible display style, by making a change to the system’s Advanced Settings: 

  1. Log in to IBM Cognos Administration
  2. Go to the Configuration tab > Dispatchers and Services. 
  3. Select your dispatcher and locate the ReportService (and BatchReportService).
  4. Click Set properties > Settings tab.
  5. In the Environment category, go to Advanced settings and click Edit.
  6. Add the following parameters:
    • Parameter: VIEWER_PDFJS | Value: FALSE
    • Parameter: RSVP.PDF.USE_ADOBE_DRILL | Value: TRUE 
  7. Click OK and restart the Cognos services to apply the new parameters globally.

More Information:

https://www.ibm.com/support/pages/all-cognos-pdf-reports-render-blank

https://www.ibm.com/support/pages/opening-pdf-output-cognos-analytics-shows-blank-page 

https://www.ibm.com/docs/en/controller/11.1.2?topic=options-import-controller-standard-reports-package

https://www.ibm.com/support/pages/how-configure-ibm-cognos-controller-use-cognos-controller-embedded-report-library-ibm-cognos-controller-reports-standard-report-engine-ccrreports