This is, by far, the most frequent error encountered. It indicates that the SiteMinder Policy Server could either not be contacted (rare) or that the Policy Server refused the connection (very common). This is caused by either the agent not being defined on the Policy Server or a mismatch on the shared secret.
The best way to troubleshoot this error is to examine the SiteMinder console log (usually of the Authentication service), looking for entries denying a connection by an agent. The messages there are often cryptic, so check carefully the definition of the agent, especially the name of the agent (it is case-sensitive) and its shared secret.
This error should be considered equivalent to error -17, described below. Different versions of the SiteMinder Agent API return different errors, so you might see either error.
The application requested a function that is not currently implemented in SmPortal. This generally means that the service either requires a later version of SmPortal or that there is a significant problem with the application. Contact your application (or API) developer for resolution.
This error indicates that a fault was detected during processing. This generally indicates a programming error.
Indicates that the application program is not authorized to call into the Portal. This indicates a programming error in the application or API. Contact your application (or API) developer for resolution.
This error indicates that the Agent entry specified for the service could not be located in SmPortal.cfg. Check to make sure that the agent configured for this service is defined in the file.
SmPortal was unable to determine the shared secret for the specified agent. Check to ensure that a secret is defined for this service's agent.
This error indicates that there are no servers defined for this agent in the SmPortal.cfg file.
This error indicates that the SiteMinder Agent API could not be initialized. Typically, this error is returned if:
The Agent API intentionally does not distinguish between these errors. To do so would make cracking security significantly easier. To determine which of these cases is the actual cause, examine the Authentication Server's console log (on the Policy Server).
This error indicates that one of the servers defined for the agent was not defined elsewhere in the SmPortal.cfg file. Make sure that all of the servers defined for the Agent are defined with, minimally, an IP address (and that the IP address is not blank).
This is an internal application error indicating that the application passed an invalid handle to the SmPortal API. This indicates a programming error in the application or API. Contact your application (or API) developer for resolution.
The dynamic library (SmPortal.dll on Windows NT, libSmPortal.so on Solaris) could not be located. Update your PATH (Windows) or LD_LIBRARY_PATH (Solaris) environment variable in the context of the running user so that the dynamic library can be found. This error may also occur if the library can be located, but cannot be loaded because of another dependency.
The SmPortal configuration file (usually SmPortal.cfg) could not be located or opened. This usually means that the file either doesn't exist, is in the wrong place, or there is a missing or improperly set environment variable.
|
Copyright © 2014 CA.
All rights reserved.
|
|