A common error found in the WebAgent log when attempting to start up a SiteMinder WebAgent for the first time is "Unable to load SiteMinder host configuration object or host configuration". This error can be caused by one of several issues. Here are the things to check: The WebAgent needs to have certain environment variables set in order to start up properly. Verify that you are sourcing nete_wa_env.sh in the user's profile, apachectl, or envvars. This is by far the most common cause of the error. Ensure that the spelling of the Host Config Object, Agent Config Object used during the WebAgent configuration are correct (match what is configured on the Policy Server). You can check the ACO by looking at the AgentConfigObject parameter in the WebAgent.conf. The HCO can be verified by looking at the hostconfigobject parameter in SmHost.conf. Verify that the HostConfigFile parameter in WebAgent.conf contains the correct full path to SmHost.conf On the Policy Server, verify that the DefaultAgentName in the Agent Config Object (ACO) is set to the correct name of this agent (also configured on the Policy Server). Verify that the Host Config Object on the Policy Server lists the proper IP addresses or hostname of the Policy Server(s) If checking the above items does not resolve the issue, there are some more generic issues to look into: Verify that the WebAgent server is able to communicate to the Policy Server (from the WebAgent server, ping the IP address of the Policy Server, and telnet to the Policy Server ports listed in SmHost.conf) Check the Policy Server log of the bootstrap server (the one listed first in SmHost.conf) for errors when this WebAgent starts up Delete SmHost.conf on the WebAgent and the corresponding Trusted Host Object (for this WebAgent server) on the Policy Server, then re-register this host using the smreghost command.