This appendix applies to Agent for Microsoft IIS 5.0. If a problem is discussed in this appendix, it either applies only to this agent or it applies to two or more agents with one of them being this agent. This appendix explains how you can resolve problems that you might encounter while deploying or using this web agent. Be sure to also check the Sun Java System Access Manager Policy Agent 2.2 Release Notes, to see if the problem that you encounter is a known limitation of this web agent. If workarounds are available for such problems, they will be provided in the release notes.
This section includes problems you might encounter. The explanation of the symptom is followed by possible causes and solutions.
Symptom: Cannot install the web agent after a previous installation has been removed.
You might have an existing installation of the web agent.
You might have a previously-installed web agent and did not use the web agent’s uninstallation program to uninstall the agent.
The installation program’s productregistry file might be corrupted.
Possible Solution: To resolve the issue, manually remove the web agent as explained in the following task description.
Stop all of the web sites.
Stop all of the application pools.
Remove Agent for Microsoft IIS 5.0.
Remove entries from product registry
Remove the PolicyAgent-base directory from the server.
where PolicyAgent-base represents the directory in which the web agent was originally installed.
Remove the following entries from the PATH variable:
Restart the server.
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.
Open Command Prompt Window.
Change directories to PolicyAgent-base.
Execute the following command:
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 AMAgent.properties configuration file to true as shown:
com.sun.am.policy.agents.config.override_port = true