Troubleshooting Issues

This section describes issues that you may encounter while administrating the Portal Server Secure Remote Access component. It also includes the solution or workaround to resolve the issue.

Problem: Gateway does not display a confirmation message after you enter the start up command.

Solution: Although no confirmation messages is displayed, Gateway may be running. To verify if gateway is running, use netstat — an | grep <port number> and verify if the port is listening.

Problem: Gateway does not work when Netletproxy and Rewriterproxy are enabled in the Gateway profile in the psconsole.

Solution: Verify if Netletproxy and Rewriterproxy are running.

Problem: Cacao sends a timestamp check failed exception.

Solution: Ensure that the date and time is the same on both the nodes, when Gateway is installed on a remote node.

Problem: Gateway login problem due to cookies.

Solution: This issue occurs when the com.iplanet.encode property is not the same as the AMConfig.properties file on all the nodes; Access Manager, Portal Server, and Gateway nodes. Ensure that the password encryption key properties are the same too on both the nodes.

Problem: Netlet and Proxylet do not work.

Solution: This issue can occur if the enableSRAforPortal.xml file is not loaded. Ensure the file is in the installation directory: /opt/SUNWportal/export/request. To initialize this file, execute the amadmin command.

Problem: Unable to start or stop Gateway.

Solution: Try restarting cacao. To restart cacao, enter the /usr/lib/cacao/bin/cacaoadmin start or stop command.

Problem: Failed to initialize OLE.

This issue occurs if an application failed to initialize OLE.

Solution: Try running the applet again with appropriate administrative privileges.

Problem: Error installing DLL file.

This issue occurs when the registration of the OCX control fails.

Solution: Verify if the java.io.tmp directory exists and is writable. You can retrieve the value of java.io.tmp from the Java console.

Problem: Registering OCX ctrl.

This issue can occur if the DLL file is not written the to java.io.tmpdir location on the user's hard drive.

Solution: Try running the applet again with appropriate administrative privileges.

Problem: Unable to read proxy setting information.

This error occurs when the system fails to read the proxy settings of the browser.

Solution: Close all instances of the browser and try again.

Problem: Failed to configure browser proxy settings.

This error occurs when the browser proxy settings fails to get modified.

Solution: Close all instances of the browser and try modifying the proxy setting again. If you are using Mozilla, allocate sufficient cache memory.

Problem: Error trying to restore browser proxy settings.

This error occurs when trying to restore the original browser proxy settings.

Solution: The proxy settings must be restored manually by the user.

Problem: Unable to write to the disk.

This error occurs when the application fails to write to the specified location.

Solution: Ensure that the location has appropriate write permissions.

Problem: Problem displaying User Interface. Unknown error.

The user interface is not displayed due to this error.

Solution: Verify if the JVM installation is successfully installed and running else reinstall the JVM.

Problem: Session Timeout. Please login again.

Solution: Logon to the desktop again to resolve this error.

Problem: Bad Request.

This error occurs when Gateway does not accept a particular request.

Solution: It could be a network issue, try again later.

Problem: Access to this resource denied.

This error occurs when Gateway does not have appropriate privileges to fulfill the request.

Problem: Not found error.

This error occurs when the requested page cannot be located.

Solution: Verify if the URL is correct and try accessing the page again.

Problem: Gateway Service Unavailable.

This error occurs when Proxylet is unable to establish contact with Gateway.

Solution: Try again later.

Problem: Netlet is unable to bind to port.

Solution: Ensure that the values for the client bind IP address in NetletProvider is correct and start Netlet again.