NonStop SOAP 4.1 User's Manual

Recovery
Ensure that the invalid phase is removed from the NonStop SOAP 4 message flow. Edit the
axi2.xml file to verify the correct phase order of the NonStop SOAP 4 deployment.
Configuration file cannot be found.
Cause
NonStop SOAP 4 did not locate the axis2.xml configuration file.
Effect
The request is not served.
Recovery
Ensure that the valid axis2.xml file is present in the <NonStop SOAP 4 Deployment
Directory> directory and restart the NonStop SOAP 4 server.
Data element of the OM node is NULL.
Cause
The AXIOM node does not contain any data element.
Effect
The request is not served.
Recovery
Ensure that all the modules and services deployed in NonStop SOAP 4 have their shared libraries
and configuration files with the right permissions.
Invalid handler state.
Cause
The handler description and deployment details are not correct.
Effect
The request is not served.
Recovery
Ensure that the reported handler includes the deployment information mentioned in the
corresponding module.xml configuration file. Also, ensure that the handler is not set to be
deployed in a non-existent phase.
Invalid module reference encountered.
Cause
A non-existent module is referenced by the NonStop SOAP 4 server.
Effect
The request is not served.
Recovery
Ensure that the reported module exists in the NonStop SOAP 4 deployment. In case the module
does not exist, either deploy the module or remove the reference to the module from the
services.xml and axis2.xml file.
Module not found.
Cause
The referenced module does not exist or has not been engaged.
Effect
The request is not served.
Recovery
Check the module reference in the axis2.xml or services.xml file to ensure that the reported
module is deployed and engaged to the NonStop SOAP 4 server.
NonStop SOAP 4 Error Messages 287