System Messages: GWWS Catalog 400-499
|
401 |
ERROR: Cannot advertise outbound service service-name | |
|
Description |
GWWS can not advertize the outbound service. |
Action |
Increase MAXSERVICES parameter configured in UBBCONFIG. | |
402 |
ERROR: Conversation is not supported | |
|
Description |
GWWS does not support conversational communication model. |
Action |
Check if the client program is using conversational ATMI primitives (for example, tpconnect, tpsend) to communicate with GWWS. | |
403 |
ERROR: Internal system error at (file.line). Set tperrno in message. | |
|
Description |
GWWS encountered a serious internal system error when processing the outbound web service request. |
Action |
Contact Oracle Customer Support. | |
404 |
WARNING: Unable to invoke audit postop on completion of service. | |
|
Description |
The audit postop for a outbound service invocation failed. |
Action |
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by Oracle Systems, Inc., contact Oracle Customer Support. | |
406 |
ERROR: Invalid message buffer. | |
|
Description |
GWWS detect a badly formatted internal buffer. |
Action |
Contact Oracle Customer Support. | |
407 |
ERROR: Failed to send back reply: errorstr | |
|
Description |
GWWS failed to send outbound web service response to the client. Usually occurs because the client exits before the response is received. |
Action |
Check if the client process exits prematurely. | |
409 |
WARNING: Unable to audit policy enforcement event. | |
|
Description |
An attempt to audit an encryption or signature policy failure while dispatching a service failed. |
Action |
Contact Oracle Customer Support. | |
410 |
ERROR: Received invalid service request, service name service-name. | |
|
Description |
The outbound service request is invalid and GWWS can not handle it. |
Action |
Contact Oracle Customer Support. | |
411 |
ERROR: Service service-name has policy SIGNATURE_REQUIRED=signature-policy and ENCRYPTION_REQUIRED=encryption-policy but the input buffer was neither signed nor sealed. | |
|
Description |
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has a signature policy ( signature-policy ) and an encryption policy ( encryption-policy ). |
Action |
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, then the *MACHINE level and finally the *RESOURCE level. If any of those policies is 'Y', then the policy for service-name is 'Y'. | |
412 |
ERROR: Service service-name requires encryption but the input buffer is not encrypted. | |
|
Description |
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has an encryption policy of 'Y'. |
Action |
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, then the *MACHINE level and finally the *RESOURCE level. If any of those policies is 'Y', then the policy for service-name is 'Y'. | |
413 |
ERROR: Invalid public key context. | |
|
Description |
While attempting to dispatch a service with an encryption or signature policy, an invalid buffer was detected. |
Action |
Contact Oracle Customer Support. | |
414 |
ERROR: Service service-name requires encryption but the input buffer is not encrypted. | |
|
Description |
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has an encryption policy of 'Y'. |
Action |
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, then the *MACHINE level and finally the *RESOURCE level. If any of those policies is 'Y', then the policy for service-name is 'Y'. | |
415 |
ERROR: Service service-name requires a signature but the input buffer is not signed. | |
|
Description |
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has a signature policy of 'Y'. |
Action |
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, then the *MACHINE level and finally the *RESOURCE level. If any of those policies is 'Y', then the policy for service-name is 'Y'. | |
417 |
WARNING: Unable to invoke authorize operations at (file.line). | |
|
Description |
Authorization operation failed. |
Action |
Contact Oracle Customer Support. | |
418 |
WARNING: Unable to invoke audit preop on service invocation. | |
|
Description |
A call to the audit_preop() plugin security function on a service operation failed. This call was being attempted prior to the operation execution. No audit of the attempt was able to be performed/recorded. |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
419 |
WARNING: Unable to invoke audit postop on security failure. | |
|
Description |
The audit postop for a outbound service invocation failed. |
Action |
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by Oracle Systems, Inc., then contact Oracle Customer Support. | |
420 |
ERROR: Service service-name is not defined in outbound web service definition file, can't be advertised. | |
|
Description |
This message is issued when users try to adversize a service dynamically from tmadmin or via TMIB operation, but the service is not defined in the outbound web service definition file. |
Action |
Check if input the correct service name. | |
421 |
ERROR: Function name func-name is invalid, service service-name can't be advertised. | |
|
Description |
This message is issued when users try to adversize a service dynamically from tmadmin or via TMIB operation, but the function name func-name is invalid. The only valid function name is "GWWS" |
Action |
Use fixed function name "GWWS" or omit it to advertize outbound service. | |
423 |
ERROR: Invalid message buffer. | |
|
Description |
GWWS detected a badly formatted internal buffer. |
Action |
Contact Oracle Customer Support. | |
424 |
ERROR: Received invalid service request, service name service-name. | |
|
Description |
The outbound service request is invalid and GWWS cannot handle it. |
Action |
Contact Oracle Customer Support. | |
425 |
ERROR: Failed to duplicate message buffer. | |
|
Description |
GWWS failed to allocate memory to make a copy of the internal buffer. |
Action |
Check memory usage in your system when this error occurs. | |
426 |
ERROR: Invalid message buffer. | |
|
Description |
GWWS detected a badly formatted internal buffer. |
Action |
Contact Oracle Customer Support. | |
427 |
ERROR: Failed to allocate SCO entry. | |
|
Description |
SCO is acronym of SOAP Control Object, which is the processing unit GWWS allocates to handle inbound or outbound web service. The maximum number of outstanding SCO entries are 4096. GWWS will report this error message if it can not allocate new SCO for the limit is reached. |
Action |
Add more GWWS instances to balance the work load. | |
428 |
ERROR: Failed to allocate message context. | |
|
Description |
GWWS allocate a internal message context for each outstanding outbound service call. The maximum number of the message context is 1000. GWWS will report this error message if it can not allocate more message context for the limit is reached. |
Action |
Add more GWWS instances to balance the work load. | |
429 |
ERROR: Failed to append SCO to queue. | |
|
Description |
SCO is acronym of SOAP Control Object, which is the processing unit GWWS allocates to handle inbound or outbound web service. The newly created SCO is appended to an internal queue to be processed by working threads. This error message is issued if this process failure. |
Action |
Contact Oracle Customer Support. |