NonStop SOAP User's Manual

Using NonStop SOAP with a TS/MP Application and
NonStop Processes
NonStop SOAP User’s Manual—520501-012
6-50
Fault Messages
-205 Unmarshal Error: optional nodes
are not present. Input request XML
does not conform to DTD.
The DDL uses redefines to specify
that one of set of nodes must be
present, but none of the nodes is
present in the request.
-206 Unmarshal Error: error in getting
value of node:
fieldname
Error getting value of node from
node tree. This is an internal error.
-207 Unmarshal Error: incorrect value in
node: fieldname
The value specified for a node is
invalid.
-208 Unmarshal Error: node:
fieldname must occur num
times. Input request XML does not
conform to DTD.
The specified field does not occur
the correct number of times, as
required by the DTD.
-209 Unmarshal Error: error decoding
the Base64 encoded node: < node
name
>.
The specified error was
encountered decoding the Base64
encoded node.
-210 Unmarshal Error: no session
element in header - Target service
requires session.
The specified error was
encountered in the header.
-215 Unmarshal Error: “service: < name >
not found in the Service Definition
Repository.
The specified error was
encountered unmarshalling the
request.
“No Service Map Entry for service:
< name > found in: < service map
file
> file.
-216 Unmarshal Error: the XML
message for the service:
< service name > should be
SOAP compliant.
The specified error was
encountered unmarshalling the
request.
-217 Unmarshal Error: the XML
message for the service:
< service name > should not be
SOAP compliant.
The specified error was
encountered unmarshalling the
request.
-218 An error occured during parsing.
Message: < message from
parser >.
The specified error was
encountered parsing the XML
document.
-219 Request is not valid. Unexpected
node: < node name > at the end.
The specified error was
encountered parsing the XML
document.
Table 6-1. Faults for Unmarshal Errors (page 2 of 2)
Detail Code Detail String Description