GWWS Messages 1000-1099
|
|
|
1001
HTTP Error: HTTP header parsing failure.
Description
Client sent an invalid HTTP header in SOAP request. GWWS cannot parse it.
Action
Try to interceive the request and find out what is wrong with the HTTP header.
1002
HTTP Error: Request path not found.
Description
The path in the HTTP header does not match the server path server. This may be caused by using the wrong WSDL file to generate client code.
Action
Create the WSDL file from GWWS configuration file.
See Also
tmwsdlgen(1)
1003
SOAP Error: SOAP Envelope not found.
Description
GWWS failed to find SOAP Envelope tag in the request.
Action
Check the request. It may not be a SOAP request.
1004
Internal Error: Failed to get 'element' from configuration file.
Description
GWWS failed to retrieve element definition from the configuration file.
Action
Check the configuration file and Metadata Service Repository.
1005
Service Error: TUXEDO Service 'name' return NULL.
Description
When transferring request to real TUXEDO service, the service response is invalid.
Action
Check the Metadata Service Repository definition. It may be incorrect or different from the actual service.
1006
Service Error: Type 'type1' mismatch. 'type2' is expected for TUXEDO buffer.
Description
TUXEDO service returns a type1.buffer. Metadata Service Repository indicates it should be type2.
Action
Correct Metadata Service Repository definition.
1007
Internal Error: Memory allocation failure.
Description
GWWS failed to allocate memory while processing request.
Action
If it cannot be recovered, make sure that there is enough memory and reboot GWWS.
1008
Internal Error: Fail to get MBString encoding.
Description
TUXEDO service returns an MBString buffer and cannot determine encoding.
Action
Check the service to ensure it returns a valid MBString.
1009
SOAP Error: Output Tuxedo buffer 'type name' type XML conversion failure
Description
GWWS failed to convert TUXEDO buffer with type name into XML in response.
1010
SOAP Error: Fail to output SOAP Body.
Description
GWWS failed to compose SOAP body in response.
1011
SOAP Error: Fail to output SOAP Header.
Description
GWWS failed to compose SOAP header in response.
1012
HTTP Error: Fail to count output buffer length.
Description
Internal error.
1013
HTTP Error: Fail to serialize output buffer.
Description
GWWS failed to compose response.
1014
SOAP Error: Invalid SOAP message.
Description
Error happens when GWWS parsing the request SOAP message.
Action
Check the request. It may be malformed or not a SOAP request.
1015
Internal Error: Fail to create SOAP Header.
Description
GWWS failed to allocate internal structure to handle SOAP header.
Action
This error may be due to memory allocation failure. Check if there is enough memory.
1016
SOAP Error: Cannot handle MustUnderstood Header 'tag'
Description
BEA SALT does not support the ˇ°MustUnderstood" tag in the Soap Header.Check the client code to see if it is utilizing some unsupported protocol.
1017
SOAP Error: Invalid SOAP header.
Description
Error happens when GWWS parses the SOAP header.
1018
Security Error: Authentication Needed.
Description
Request does not contain HTTP Basic Authentication information, though TUXEDO is configured to using USER_AUTH or ACL.
Action
Use TUXEDO username/password as HTTP Basic Authentication username/password and resend the request. Make sure that there is the HTTPS connection if you don't want the username/password to be visible to others.
1019
Security Error: Authentication Failed.
Description
Request contains HTTP Basic Authentication information, but TUXEDO authentication rejects the username/password.
Action
Make sure the username is a valid TUXEDO user and that the password is correct.
1020
Internal Error: TUXEDO Error.
Description
Internal error happens when GWWS calls TUXEDO API.
1021
SOAP Error: SOAP Body not found.
Description
Error happens when GWWS parses the SOAP body.
1022
SOAP Error: Invalid SOAP Body.
Description
Error happens when GWWS parses the SOAP body.
1023
SOAP Error: SOAP Body is empty.
Description
Error happens when GWWS parses the SOAP body.
1024
Service Error: Service 'name' not found in configuration file.
Description
The local name of the SOAP body first-child element configured service is not found in configuration file.
Action
Check the WSDL file and configuration file to make sure which one is incorrect.
1025
DataMapping Error: Input buffer is not valid.
Description
Error happens when GWWS parses the input parameter that is the child-element of service name. The input parameter does not match our requirement.
Action
Check the request and WSDL file, compare it with the one generated from configuration file to see the difference.
1026
DataMapping Error: Attachment not found.
Description
Input request utilizes MIME to send SwA(SOAP with Attachment) message, there is no attachment for data.
Action
Check the client code to make sure it sends out the correct message.
1027
DataMapping Error: Decode attachment failure.
Description
When client sends Base64-encoded attachments in message, the attachment contains invalid base64 encoding characters.
Action
Check client code to make sure the encoding is correct. If not, change it to binary.
1028
DataMapping Error: Unsupported attachment encoding. Binary or Base64 is expected.
Description
When an Input request utilizes MIME to send an SwA(SOAP with Attachment) message, the attachment uses unsupported encoding.
Action
Change client code to use binary or base64 encoding for attachment.
1029
"DataMapping Error: Input 'tag name' content exceeds max length %d."
Description
Certain element(s) in the input SOAP message exceed the max length defined in Metadata Service Repository.
Action
Check the input SOAP message and definition in the Metadata Service Repository.
1030
"DataMapping Error: Input 'tag name' is empty."
Description
Certain input SOAP message element(s) are null, but are defined by Metadata Service Repository.
Action
Check the input SOAP message to determine which element is null, and can get the wsdl to know the request of the Metadata Service Repository.
1031
Internal Error: Fail to allocate Tuxedo buffer.
Description
GWWS failed to allocate TUXEDO buffer while converting SOAP input.
Action
Make sure that there is enough memory.
1032
Internal Error: Queue Error.
Description
GWWS failed to insert input for TUXEDO to internal queue.
1033
Internal Error: Fail to call Tuxedo Service 'name'. Tuxedo returns error message'.
Description
GWWS failed to call TUXEDO service. The error message is returned by TUXEDO.
1034
"DataMapping Error: Fail to parse tag tag name."
Description
The TUXEDO process cannot parse certain tag content.
Action
Check the input SOAP message to determine which element does not follow the SOAP rule.
1035
"DataMapping Error: Output '%s' content exceeds max length %d."
Description
Certain TUXEDO elements returned by service exceeds the max length defined in the Metadata Service Repository.
Action
Check the input SOAP message to obtain the element length. Check the Metadata Service Repository definition.
1036
"DataMapping Error: Tag 'tag name' occurrence does not meet service requirement (min: %d)."
Description
The certain element in the input SOAP message is fewer than definition in the Metadata Service Repository.
Action
Check the input SOAP message to get the number the certain element occurs.
1037
"DataMapping Error: Tag 'tag name' is unexpected."
Description
There is an extra tag that is not included in the Metadata Service Repository.
Action
Compare the input SOAP message and the Metadata Service Repository definition.
1038
"Internal Error: Failed to add tag 'tag name' to TUXEDO buffer. TUXEDO returns error string."
Description
The TUXEDO process cannot enter the contents of the tag into the TUXEDO buffer. The error string indicates the reason.
Action
Check the error string to see the reason. If the error persists, please contact BEA Customer Support.
1039
"DataMapping Error: Missing element, tag tag name is expected."
Description
The tag is missing in the input SOAP message.
Action
Check the input SOAP message and Metadata Service Repository definition.
1040
"Internal Error: Fail to build TUXEDO buffer index. TUXEDO returns error string."
Description
The TUXEDO process cannot build the TUXEDO buffer index, the error string indicates the reason.
Action
Check the error string to see the reason. If the error persists, please contact BEA Customer Support.
1041
"Internal Error: Fail to get TUXEDO buffer tag name field id. TUXEDO returns error string."
Description
The TUXEDO process cannot get the TUXEDO buffer field Id, the error string indicates the reason.
Action
Usually if the TUXEDO environment value is incorrect or missing, this error occurs. Check the environment variables, for example, VIEWFILES, FLDTBLDIR and so on. If the error persists, please contact BEA Customer Support.
1042
"Internal Error: Fail to access tag name in configuration file."
Description
The TUXEDO process cannot get input buffer definition.
Action
Check the Metadata Service Repository definition.
1043
"Internal Error: Fail to get TUXEDO buffer 'element name' field occurrence. TUXEDO returns error string."
Description
The TUXEDO process cannot find the TUXEDO buffer field number occurrence, the error string indicates the reason.
Action
Check the error string to see the reason indeed. If the error persists, please contact BEA Customer Support.
1044
"Internal Error: Fail to calculate TUXEDO buffer 'buffer name' size. TUXEDO returns error string."
Description
The TUXEDO process cannot get the TUXEDO buffer size relevant to current SOAP message. The error string indicates the reason.
Action
Check the error string to see the reason. If the error persists, please contact BEA Customer Support.
1045
"Internal Error: Fail to initialize TUXEDO buffer 'buffer name'. TUXEDO returns error string."
Description
The TUXEDO process cannot initialize the TUXEDO buffer relevant to current SOAP message. The error string indicates the reason.
Action
Check the error string to see the reason. If the error persists, please contact BEA Customer Support.
1046
"Internal Error: Fail to get relevant TUXEDO buffer 'buffer name' definition. TUXEDO returns error string."
Description
The TUXEDO process cannot get relevant TUXEDO buffer definition.
Action
Check the error string to see the reason. If the error persists, please contact BEA Customer Support.
1047
"Internal Error: Cannot find relevant field for tag 'tag name' in TUXEDO buffer."
Description
The relevant TUXEDO data structure element is missing in for the input SOAP tag.
Action
Check the Metadata Service Repository definition and the relevant TUXEDO environment value.
1048
"Internal Error: Fail to get TUXEDO buffer type."
Description
The TUXEDO process cannot find the buffer type returned by the TUXEDO service.
Action
Check the TUXEDO service return buffer, the buffer should be allocated by "tpalloc" and returned by "tpreturn". If the error persists, please contact the BEA Customer Support.
1049
"DataMapping Error: Invalid Base64 data for tag 'tag name'."
Description
The TUXEDO process handle the embedded CARRAY via Base64 encoding style. This error indicates that the encoded Base64 data cannot be recognized.
Action
Check the Base64 encoding data for the embedded CARRAY field. If the error persists, please contact BEA Customer Support.
1050
"DataMapping Error: Fail to parse ending tag 'tag name'."
Description
The TUXEDO process cannot handle the ending tag or cannot find the ending tag. The input SOAP message may have a format error or an invalid character.
Action
Check the input SOAP message and ensure the message is properly formatted.
1051
"DataMapping Error: Fail to serialize '%s'."
Description
The TUXEDO process cannot serialize XML typed buffer from TUXEDO service.
Action
Check the XML typed buffer returned by TUXEDO service and make sure it is properly formatted.
1052
"DataMapping Error: Type 'type name' mismatch. 'type name' is expected for 'tag name'."
Description
The TUXEDO process finds the tag type of is different from the Metadata Service Repository definition.
Action
Check the tags type in the input SOAP message and the Metadata Service Repository definition of the.
1053
"Internal Error: Fail to get input type from configuration."
Description
The TUXEDO process cannot find the input typed buffer type.
Action
Check the Metadata Service Repository and configure of GWWS. If the error persists, please contact BEA Customer Support.
1054
"Internal Error: Fail to get output type from configuration."
Description
The TUXEDO process cannot find the output typed buffer type.
Action
Check the Metadata Service Repository and configure of GWWS. If the error persists, please contact BEA Customer Support.
1055
"DataMapping Error: Tag 'tag name' occurrence does not meet service requirement (max: %d)."
Description
The certain element in the input SOAP message is more than definition in the Metadata Service Repository.
Action
Check the input SOAP message to get the number the certain element occurs.
1056
SOAP Error: Unknown SOAP request.
Description
The requested service name (local name of the first SOAP body child element) does not match any services.
Action
Check client code and WSDL file.
1057
"DataMapping Error: Tag 'tag name' is unexpected, 'tag name' is expected."
Description
The input SOAP message element does not follow the rule requested by WSDL file.
Action
Check the SOAP message and compare it to the WSDL file.
1058
"DataMapping Error: Fail to parse %s."
Description
The TUXEDO process cannot parse the tag content relevant to XML typed buffer.
Action
Check the input SOAP message to determine which element does not follow the SOAP rule.
 |
 |
 |