search cancel

SPS does not start and sends an HTTP error 503


Article ID: 50817


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On



When starting the httpd.exe file and try to access the home page of the server, it gives a HTTP 503 error.
No logs are created for the proxy-engine and no errors are logged in httpd logs (error logs are in DEBUG level).


HTTP error 503 means that the service is unavailable. According to RFC 2616, "the server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response."

When checking the installation log, it appears that the service could not be started after the installation had completed, failing on the error message:
"only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address"

Another Web Server or service is currently listening on port 80. You should reconfigure the SPS to use another port, or stop the another server if not in use.


Component: SMSPS