The SiteMinder Agent module cannot establish an agent connection to the Policy Server.

Check the SiteMinder Default Agent log for any message indicating connection problems.

Make sure the SiteMinder Agent module's Agent configuration file points to the correct SmHost.conf file. Also, make sure the Agent module connects to the Policy Server.

Test the connection by using the Policy Server’s SiteMinder Test tool.

SiteMinder Agent classes are not available.

Check the SystemOut.log and SystemErr.log files.

Make sure the SiteMinder Agent .jar files exist in the WebSphere library directory WS_HOME\lib\ext.

For more information, see SiteMinder Agent Files.

The smagent.properties file is not installed on WebSphere or is not in the correct location on WebSphere.

Check the SystemOut.log and SystemErr.log files.

Make sure you have copied the smagent.properties file to the correct location on WebSphere.

For more information, see Copying the smagent.properties File to WebSphere

Incorrect path specified to the Agent configuration file.

Check the SystemOut.log and SystemErr.log files.

Make sure the correct path is specified to the failing module's Agent configuration file in the smagent.properties file.

SiteMinder host registration is configured incorrectly.

Check the SystemOut.log file, SystemErr.log file and the SiteMinder Default Agent log.

Verify the host configuration object and the trusted host in the SmHost.conf file also exist in the Policy Server.

Agent Configuration Object or the Default Agent Name are configured incorrectly.

Check the SiteMinder Agent log.

Make sure the AgentConfigObject parameter listed in the Agent configuration file file exists and is set correctly, and that the DefaultAgentName of the Agent Configuration Object in the Administrative UI is correct.