Sun Java System Access Manager Policy Agent 2.2 Guide for Microsoft Internet Information Services 5.0

Troubleshooting Symptoms in Agent for Microsoft IIS 5.0

This section includes problems you might encounter. The explanation of the symptom is followed by possible causes and solutions.

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 Microsoft IIS 5.0

  1. Stop all of the web sites.

  2. Stop all of the application pools.

  3. Remove Agent for Microsoft IIS 5.0.

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

    2. Select Sun Java System Access Manager for IIS5.0

    3. Click Remove

  4. Remove entries from product registry

    1. Issue the following command from the command line:

    2. Traverse to the following:

    3. Click Software

    4. Click Sun Microsystems

    5. Remove the following entry:

      Access Manager IIS Agent

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

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

  6. Remove the following entries from the PATH variable:

    • PolicyAgent-base\bin

    • PolicyAgent-base\iis\bin

  7. Restart the server.

Troubleshooting Symptom 2

Problem: Unable to uninstall the agent from the Windows system using the following menu sequence: Start menu > Settings > Control Panel > Add/Remove Programs

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

Solution: Perform the steps in the following task description.

ProcedureTo Uninstall a Web Agent 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

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