![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The statusCode and statusMsg fields are used in private messages that are sent in response to a request. See Responder Inbound Request — BusinessConnect to Private Process and Responder Outbound Response — Private Process to BusinessConnect for examples of this.
Table 49 statusCode and statusMsg Fields When the value in the statusCode field is set to under 200 or above 299, the SOAPFault element is sent to the trading partner and the body is ignored even if it contains data. To send the content of the body, the value in the statusCode field must range between 200 and 299. Access Denied: reason Transport transport is not supported by SOAP. Cannot send operation type request to multiple trading partners Received SOAP Fault. Fault String: fault_string This is detected by the initiator process. Make sure there is an agreement between the message and the schema registered in the
Operation > Request Action tab of the Operations Editor. Or do not select Validate Message check box in the Operation > Request Action tab of the Operations Editor. This is detected by the initiator process. Make sure there is an agreement between the message and the schema registered in the
Operation > Response Action tab of the Operations Editor. Or do not select Validate Message check box in the Operation > Response Action tab of the Operations Editor. Attachment processing error, msg: message (request from private process) Attachment processing error, msg: message (response from private process) Posting error: reason Check the Operations Editor settings. No matching transaction found for ID ID. The request might have timed out. Access Denied: reason Verify that your default host accepts anonymous messages by selecting the Allow Anonymous SOAP Messages check box for the default host. This is detected by the responder process. Make sure there is an agreement between the message and the schema registered in the
Operation > Request Action tab of the Operations Editor. Or do not select Validate Message check box in the Operation > Request Action tab of the Operations Editor. Check the Operations Editor settings. This is detected by the responder process. Make sure there is an agreement between the message and the schema registered in the
Operation > Response Action tab of the Operations Editor. Or do not select Validate Message check box in the Operation > Response Action tab of the Operations Editor. No matching transaction found for ID ID. The request might have timed out.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |