+

Search Tips   |   Advanced Search

Troubleshooting the WAS hosting Cognos

If we encounter problems while deploying or configuring the IBM WebSphere Application Server hosting the IBM Cognos server, use this information to help resolve the problem.

Table 1 lists problems you might encounter with WebSphere Application Server and suggests solutions.

hosting Cognos Business Intelligence
Problem Solution

We need to stop (or restart) WebSphere Application Server.

Whenever stop (or restart) WebSphere Application Server, wait at least 1 full minute before starting it again, to ensure that all Cognos processes hosted on that server have fully stopped:

  • IBM AIX or Linux: cgsServer.sh and CAM_LPSvrprocesses

  • Windows: cgsLauncher.exe and CAM_LPSvrprocesses

The task to federate the Cognos node to the dmgr failed with a SOAP Connecter exception because the specified host and port could not be reached:

    Cannot create a SOAP connector to connect to host servername at port xxx.

This problem indicates the server hosting the dmgr was not available during the federation task. Resolve this issue with the following steps:

  1. Verify the dmgr is running.

  2. Verify used the correct port for the dmgr's SOAP Connecter in the addNode command. We can check the SOAP Connector port setting in the following file:/opt/IBM/Websphere/AppServer/profiles/Dmgr01/logs/AboutThisProfile.txt

  3. Verify that both servers either are registered in the DNS or are specified in each other's /etc/hosts file. On Linux, verify the specified host name is currently in effect on the dmgr.

  4. Federate the Cognos node.

The following exception appears in the WebSphere server log, called SystemOut.log: com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[CMServlet]: java.security.AccessControlException: Access denied (java.lang.RuntimePermission createClassLoader)

This message indicates a security issue where user verification has failed. We can resolve this problem by disabling Java 2 security on the dmgr with the following steps:

  1. Log into the WAS console as the WebSphere administrator.

  2. Click...

      Security | Global Security

  3. Look under "Java 2 security" and clear the selection for...

      Use Java 2 security to restrict application access to local resources

  4. Click Apply, and then click OK.

  5. Save the change to the master configuration by clicking Save in the "Messages" box.

The following exception appears in the WebSphere server log, called SystemOut.log: Cannot parse URL java.net.MalformedURLException: no protocol

Check the cogroot.link value to see if it matches the Cognos BI Server installation path. If the installed path is different (for example, you moved the files or renamed the directory), we can update the Cognos BI application file to reference the correct path. For instructions, see Manually changing the install directory name affects installations running under an application server in the Cognos information center.

The following exception appears in the WebSphere server log, called SystemOut.log: java.lang.UnsatisfiedLinkError: JCAM_Crypto_JNI (Not found in java.library.path)

Check the JVM environment variables to verify they correctly specify the locations of the JVM environment, and the library path. If the variables are incorrect, we can set them. For instructions, see Set environment variables in the Cognos information center.

The following exception appears in the WebSphere server log, called SystemOut.log: A WebGroup/Virtual Host to handle p2pd/servlet/gc has not been defined.

Check the virtual host settings on the Deployment Manager and verify the Cognos server port is included. For more information and a workaround, see the following technote: SRVE0255E: A WebGroup/Virtual Host to handle /p2pd/servlet/dispatch has not been defined.

On Linux, the Cognos WAS server stops quickly after starting.

Detail: Check SystemOut.log /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/cognos_server/SystemOut.log errors and stops.

    WSVR0103E: An error occurred destroying com.ibm.ws.webservices.admin.component.WebServicesAdminComponentImpl@5fd85fd8java.lang.IllegalStateException: The service has been unregistered

Add this variable to JVM environment variable

  1. Login to the WAS administrative console of the Cognos server.

  2. 2 Click Servers > Server Types > WebSphere application servers.

  3. 3 Click the cognos_server link.

  4. 4 Click JAVA and then Process Management- > Process definition > Environment Entries.

  5. 5 Click New to add the following entry:

      LD_PRELOAD = /usr/lib64/libfreebl3.so


Parent topic:
Troubleshooting Cognos Business Intelligence components