NonStop SOAP 4.1 User's Manual

Effect
The request is not served.
Recovery
Correct the MEP used by the client for service invocation and try sending the request again.
MEP mismatch.
Cause
There is a mismatch between the MEP used by the client and the one allowed by the service.
Effect
The request is not served.
Recovery
Correct the MEP used by the client for service invocation and try sending the request again.
NonStop SOAP 4 Engine Errors
NonStop SOAP 4 logs the following error messages because of runtime inconsistencies or error
conditions in the NonStop SOAP 4 engine.
Invalid message context state.
Cause
The message context is either NULL or corrupt.
Effect
The request is not served.
Recovery
Check if the request message is well formed and try sending the request again.
Service accessed has invalid state.
Cause
The accessed service has no name for the server class mentioned in the services.xml file.
Effect
The request is not served.
Recovery
The service developer must mention a valid name for the server class.
Service not yet found.
Cause
The service accessed is not located by the NonStop SOAP 4 server.
Effect
The request is not served.
Recovery
Ensure that the service requested exists in the NonStop SOAP 4 deployment.
Invalid phase found in the phase validation.
Cause
NonStop SOAP 4 encountered an invalid phase during startup.
Effect
The request is not served.
286 NonStop SOAP 4 Error and Warning Messages