This section includes various problems you might encounter with this agent on Windows systems. The symptom of the problem 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 IBM Lotus Domino 6.5.4.
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.
Symptom: Unable to uninstall the agent from a Windows system using the Add/Remove Program option in the Control Panel.
Possible Cause: Java’s class path might not be set correctly on the machine.
Possible Solution: Perform the following task.
Open Command Prompt Window.
Change directories to PolicyAgent-base
Execute the following command:
Symptom: IBM Lotus Domino 6.5.4 server starts with the following error message:
Unable to load filter
Possible Cause: The DSAPI filter is configured incorrectly. Generally, if any path issue or associated library issue occurs while the DSAPI filter is being added, this error is generated.
Possible Solution: Ensure that the DSAPI filter has been configured with the correct information. For example, verify that the following path has been specified:
Symptom: The DSAPI filter is not functioning properly on a server instance.
When the DSAPI filter was configured, the database selected was not correct.
The partitioned database was not updated.
Ensure that the correct database was selected during configuration.
Replicate the database from the IBM Lotus Domino 6.5.4 administration server.
Symptom: The agent goes into an infinite loop.
Possible Cause: The value for the following property in the web agent AMAgent.properites configuration file is a resource to which users are assigned:
The users assigned to this resource, do not have allow in the policy definition.
Possible Solution: For the get method, specify allow in the policy definition.
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
Symptom: After the agent is installed, the web server fails to start.
Possible Cause: Libraries that agents depend on for Windows systems are missing. Ensuring that the libraries msvcp70.dll and msvcr70.dll are available is a pre-installation step in this guide. If the libraries were not properly added, the web server might not start.
Possible Solution: Obtain the appropriate libraries as described in Preparing to Install Agent for IBM Lotus Domino 6.5.4 on Windows Systems.