The URL that RLC is using to communicate with the SBM Application Engine is not valid. This is typically set by Configurator from the settings on the Component Server and IIS Server views. Here are a couple tips to try:
A SOAP call to the SBM Event Manager to trigger an orchestration may get an error of "The endpoint reference (EPR) for the Operation not found is /eventmanager/services/ALFEventManagerDocLit and the WSA Action = null. If this EPR was previously reachable, please contact the server administrator." This could be caused by missing headers such as SOAPAction that are required for the call that were added in newer versions of SBM. The call should work once all required headers are added.
Unable to create new environments from the Application Repository (Mashup Manager) Errors deploying to some environments give error: ERROR -- Failed to obtain security token: Web Services http://servername:80/gsoap/gsoap_ssl.dll?sbminternalservices72 returned an error: " soap _wsse_verify_X509"