System Messages: GWWS Catalog 1000-1099
|
|
|
|
1001 |
HTTP Error: HTTP header parsing failure. | |
|
|
Description |
Client sent an invalid HTTP header in SOAP request. GWWS cannot parse it. |
|
Action |
Examine the request and find out what is incorrect in 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 |
| |
|
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. | |
|
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. | |
|
1010 |
SOAP Error: Failed to output SOAP Body. | |
|
|
Description |
GWWS failed to compose SOAP body in response. |
|
1011 |
SOAP Error: Failed to output SOAP Header. | |
|
|
Description |
GWWS failed to compose SOAP header in response. |
|
1013 |
HTTP Error: Failed 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: Failed 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 |
Oracle 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 (error message). | |
|
|
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. |
|
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. | |
|
1026 |
DataMapping Error: Attachment not found. | |
|
|
Description |
Input request utilizes MIME to send SwA (SOAP with Attachment) or MTOM message, there is no attachment for data. |
|
Action |
Check the client code to make sure it sends out the correct message. | |
|
1027 |
DataMapping Error: Failed to decode attachment. | |
|
|
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 maxlen_val. | |
|
|
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: Failed to allocate Tuxedo buffer. | |
|
|
Description |
GWWS failed to allocate TUXEDO buffer while converting SOAP input. |
|
Action |
Check memory usage. | |
|
1032 |
Internal Error: Queue Error. | |
|
|
Description |
GWWS failed to insert input for TUXEDO to internal queue. |
|
1033 |
Internal Error: Failed 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: Failed 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 'element_name' content exceeds max length maxlen_val. | |
|
|
Description |
Certain TUXEDO elements returned by service exceed 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: min_occurrence). | |
|
|
Description |
The certain element in the input SOAP message is fewer than definition in the Metadata Service Repository. |
|
Action |
Check the input SOAP message and review the number of element occurrences. | |
|
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 field 'field name' to TUXEDO buffer. TUXEDO returns 'error string'. | |
|
|
Description |
The TUXEDO process cannot enter the contents of the field into the TUXEDO buffer. The error string indicates the reason. |
|
Action |
Check the error string for cause. If the error persists, contact Oracle Customer Support. | |
|
1039 |
DataMapping Error: Missing element. tag_name tag 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: Failed 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 for cause. If the error persists, contact Oracle Customer Support. | |
|
1041 |
Internal Error: Failed 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, contact Oracle Customer Support. | |
|
1043 |
Internal Error: Failed 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, contact Oracle Customer Support. | |
|
1044 |
Internal Error: Failed 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 for cause. If the error persists, contact Oracle Customer Support. | |
|
1045 |
Internal Error: Failed 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 for cause. If the error persists, contact Oracle Customer Support. | |
|
1046 |
Internal Error: Failed 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 for cause. If the error persists, contact Oracle 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. | |
|
1049 |
DataMapping Error: Invalid data for tag 'tag name'. | |
|
|
Description |
The TUXEDO process handle the embedded CARRAY with Base64 or Hex encoding style. This error indicates that the encoded data cannot be recognized. |
|
Action |
Check the encoded data for the embedded CARRAY field. If the error persists, contact Oracle Customer Support. | |
|
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 tag type in the input SOAP message and the Metadata Service Repository definition. | |
|
1053 |
Internal Error: Failed to get input type from configuration. | |
|
|
Description |
The TUXEDO process cannot find the input typed buffer type. |
|
Action |
Check the Metadata Service Repository and GWWS configuration. If the error persists, contact Oracle Customer Support. | |
|
1054 |
Internal Error: Failed to get output type from configuration. | |
|
|
Description |
The TUXEDO process cannot find the output typed buffer type. |
|
Action |
Check the Metadata Service Repository and GWWS configuration. If the error persists, contact Oracle Customer Support. | |
|
1055 |
DataMapping Error: Tag 'tag name' occurrence does not meet service requirement (max: max_occurrence). | |
|
|
Description |
An element in the input SOAP message occurs more than defined in the Metadata Service Repository. |
|
Action |
Check the input SOAP message and review the number of element occurrences. | |
|
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. | |
|
1059 |
Internal Error: Tuxedo application service returns TPFAIL. | |
|
|
Description |
The TUXEDO service returns TPFAIL with the typed buffer; GWWS sends a SOAP FAULT message to the client. |
|
Action |
Check the server supplying the Tuxedo service and analyze why the server returns TPFAIL. | |
|
1060 |
Internal Error: Tuxedo application service does not return buffer with TPFAIL. | |
|
|
Description |
The TUXEDO service returns TPFAIL without the typed buffer; GWWS sends the SOAP FAULT message to the client. |
|
Action |
Check the server supplying the Tuxedo service and analyze why the server returns TPFAIL. | |
|
1061 |
Internal Error: Failed to find relevant operating function. | |
|
|
Description |
There is not the suitable rule to convert the data between the SOAP message and the typed buffer of TUXEDO. |
|
Action |
If using the data mapping plug-in, check the plug-in configuration and library files. Otherwise, check the data type expressed by the XML schema as well as the typed buffer. | |
|
1062 |
Internal Error: Failed to manipulate the XML document. | |
|
|
Description |
GWWS cannot generate the XML document from the DOM. |
|
Action |
Check the input SOAP message to determine which element does not follow the SOAP rule. | |
|
1063 |
Internal Error: Failed to manipulate the data in the operating function. | |
|
|
Description |
GWWS cannot obtain or use the data from the data mapping plug-in. |
|
Action |
Check the data mapping plug-in and ensure it can return the right data. | |
|
1064 |
Internal Error: error message. | |
|
|
Description |
General internal error. |
|
Action |
Check the SOAP Fault message. | |
|
1065 |
DataMapping Error: error message. | |
|
|
Description |
General data mapping error. |
|
Action |
Check the SOAP Fault message. | |
|
1066 |
Service Error: Getting service definition returns FAIL. | |
|
|
Description |
GWWS cannot obtain the service definition. |
|
Action |
Check the SALT configuration. | |
|
1067 |
Internal Error: Service buffer conversion returns FAIL with detail, but detail is not as expected. | |
|
|
Description |
The TUXEDO service returns the TPFAIL with the typed buffer, but SALT cannot convert the data into the SOAP Fault. |
|
Action |
Check the data returned by the TUXEDO service and TUXEDO Service METADATA repository definition. | |
|
1068 |
DataMapping Error: There is the redundant data in the received buffer. | |
|
|
Description |
There is the data that is not needed. |
|
Action |
Check the SOAP message or the typed buffer. | |
|
1069 |
DataMapping Error: The namespace of the element 'name' is error. | |
|
|
Description |
The element's namespace is wrong. |
|
Action |
Check the input SOAP message to determine which element does not follow the SOAP rule. | |
|
1070 |
Internal Error: Unsupported XML character encoding (encoding name). UTF-8 is expected. | |
|
|
Description |
Multiple encoding support is disabled for SOAP message encoding other than UTF-8. |
|
Action |
Enable multiple encoding support in the configuration. Or change the web service client to send UTF-8 request. | |
|
1071 |
Internal Error: Unsupported HTTP character encoding (encoding name). UTF-8 is expected. | |
|
|
Description |
Multiple encoding support is off while HTTP head declares charset other than UTF-8. |
|
Action |
Enable multiple encoding support in the configuration. Or change the web service client to send UTF-8 request. | |
 |
 |
 |