Sun Java System Access Manager Policy Agent 2.2 Guide for Apache HTTP Server 2.0.54

Windows Systems: Troubleshooting Symptoms in Agent for Apache HTTP Server

This section includes various problems you might encounter on Windows systems. The explanation of the problem is followed by possible solutions.

Windows Systems: Troubleshooting Symptom 1

Symptom: Cannot install the web agent after a previous installation has been removed.

Possible Causes:

Possible Solution: To resolve the issue, manually remove the web agent as explained in the following task description.

ProcedureTo Manually Remove Agent for Apache HTTP Server

  1. Stop all of the web sites.

  2. Stop the web server instance.

  3. Remove Agent for Apache HTTP Server.

    1. In the Start menu, select Control Panel->Add/Remove programs

    2. Select Sun Java System Access Manager Policy Agent PolicyAgent-base.

    3. Click Remove

  4. Remove the PolicyAgent-base directory from the server.

    where PolicyAgent-base represents the directory in which the web agent was originally installed.

  5. Remove the following entries from the PATH variable:

    • PolicyAgent-base\bin

    • PolicyAgent-base\es6\bin

  6. Restart the server.

Windows Systems: Troubleshooting Symptom 2

Symptom: Unable to uninstall the agent from a Windows system using the Add/Remove Program option in the Control Panel.

Possible Causes: Java’s class path might not be set correctly on the machine.

Possible Solution: Perform the following task.

ProcedureTo Uninstall a Web Agent on a Windows System When the GUI Uninstallation Fails

  1. Open Command Prompt Window.

  2. Change directories to PolicyAgent-base

  3. Execute the following command:

    java uninstall_Sun_Java_tm_System_Access_Manager_Policy_Agent

Windows Systems: Troubleshooting Symptom 3

Symptom:When a user attempts to access a resource using Internet Explorer as the browser, access is denied.

Possible Cause: Internet Explorer overrides the port number of the web agent with the Access Manager port number. In such cases, the agent log file lists the URL that is being evaluated. The port number for that URL is incorrect.

Possible Solution: You can ensure this problem does not occur by setting the following property in the web agent configuration file to true as shown: = true