Error Code | Description |
5502 | Unable to create the node document_name under package package_name. Ensure that you have sufficient permission. |
Explanation: Error. Occurs when the adapter fails to create folders for document generation. | |
Action: Make sure that you have webMethods administrator privileges and sufficient credentials. For information about setting user privileges, see the webMethods Integration Server Administrator’s Guide. | |
5555 | Exception interfacing the Service Backbone. |
Explanation: Error. Generic error that occurs during the handling of the SOPERA Service Backbone library. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5556 | Failed to release message handler for service IS_service_name. |
Explanation: Error. Occurs when the adapter fails to release the message handler for the specified Integration Server service. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5557 | Failed to create service skeleton for service IS_service_name. |
Explanation: Error. Occurs when the adapter fails to create the specified Integration Server service as a SOPERA service. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5558 | Unable to retrieve XML string from SOPERA incoming message. |
Explanation: Error. Occurs when receiving an XML message from the SOPERA infrastructure. | |
Action: Verify the input message to the adapter service or notification. | |
5559 | Unable to invoke IS service to satisfy SOPERA request. It might be that the service does not adhere to the predefined signature (one input parameter incomingMessage and one output parameter outgoing message). |
Explanation: Error. Occurs when the adapter fails to invoke an Integration Server service in response to a request from the SOPERA infrastructure. | |
Action: Check the Integration Server error logs for the Integration Server service invoked and verify the implementation of the Integration Server service. | |
5561 | Unable to produce outgoing message for SOPERA. |
Explanation: Error. Occurs when the adapter fails to create a response message from the Integration Server service invoked by the SOPERA infrastructure. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5562 | Unable to send service response via SOPERA. |
Explanation: Explanation: Error. Occurs when the adapter fails to send an Integration Server service response message to SOPERA. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5563 | SBB error while invoking SOPERA service SOPERA_service_name operation operation_name with request message request_message_sent. |
Explanation: Error. Generic error that occurs when invoking an adapter service. | |
Action: Verify the values of the input parameters for the service. Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5564 | Error identifying how many attachments the response message contains. |
Explanation: Error. Occurs when attempting to get the attachment count in the response message in a RequestResponse Call or the pub.wmsopera.service:getNonBlockingServiceResponse service. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5567 | No message handler delivered. |
Explanation: Error. No responseMessageHandler passed to the pub.wmsopera.service:getNonBlockingServiceResponse service. | |
Action: Ensure that the message handler object is passed as input to the pub.wmsopera.service:getNonBlockingServiceResponse service. | |
5568 | Error generating IS document document_name in package package_name. Errors: error_text |
Explanation: Explanation: Error. Occurs when the adapter fails to generate a document from a SOPERA service. The value of error_text is null when no document is generated. | |
Action: Ensure that the correct folder name is appended to both the Input document type and the Output document type. | |
5569 | Invalid value of document type. Either folder name or document type name is missing in document_type_value |
Explanation: Error. Occurs when either the folder name or document type name is missing from the value of the timeout parameter. | |
Action: Ensure that the document type value has folder name and document name separated by ':'. | |
5570 | Unable to read and transform SOPERA request message into readable format for the Integration Server service. |
Explanation: Error. Occurs when the adapter fails to read or transform a SOPERA request message into an Integration Server service. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5571 | Unable to instantiate Admin Facade at Admin_Facade_location. |
Explanation: Error. Occurs when there is an error during the AdminFacade creation when enabling an adapter connection or starting Integration Server. | |
Action: Verify the connection parameters in the SOPERA Adapter sopera.config file, located in the Integration Server_directory \packages\ WmSoperaAdapter \config directory. For information about the SOPERA Adapter configuration file, see
Completing the Installation. | |
5572 | Unable to instantiate ServiceBackbone. |
Explanation: Error. Occurs when there is an error during the ServiceBackbone creation when enabling an adapter connection or starting Integration Server. | |
Action: Verify the connection parameters in the SOPERA Adapter sopera.config file, located in the Integration Server_directory \packages\ WmSoperaAdapter \config directory. For information about the SOPERA Adapter configuration file, see
Completing the Installation. | |
5601 | Unable to create/register the one-way service IS_service_name in the SOPERA registry. |
Explanation: Error. Occurs when there is an issue during the creation or registration of an Integration Server service as a one-way service in the SOPERA service registry. | |
Action: Check the AdminFacade error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5602 | Unable to create/register the request-response service IS_service_name in the SOPERA registry. |
Explanation: Error. Occurs when there is an issue during the creation or registration of an Integration Server service as a request-response service in the SOPERA service registry. | |
Action: Check the AdminFacade error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5603 | Transport not enabled or port not configured. |
Explanation: Error. Occurs when the transport port property is not configured properly in the SOPERA Adapter configuration file. | |
Action: Configure the transport port property as required. For information about the SOPERA Adapter configuration file, see
Completing the Installation. | |
5604 | Unable to create/register provider for service: IS_service_name |
Explanation: Error. Occurs for any error occur during the registration of a new SOPERA service provider for the specified Integration Server service. | |
Action: Check the AdminFacade error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5605 | Required parameters not provided for the notification. |
Explanation: Error. Validation error for a notification in which required message parameters are missing. | |
Action: Check all required parameters in the notification and set them as required. For information about configuring adapter notifications, see
Configuring Listener Notifications. | |
5606 | Invalid SOPERA service name service_name found. The service name should be of the format {<namespace_uri>}<service_name>. |
Explanation: Error. Occurs when an incorrect SOPERA service name is specified while configuring the notification to invoke an Integration Server service via SOPERA. | |
Action: Check if the service name is specified in the following format and correct it if it is not: {<namespace_uri}<service_name> Example: {http://myservice.com/example} TestService | |
5607 | Error while generating IS service/document service/document_name. Error error_text |
Explanation: Error. Occurs while generating an empty Integration Server service or document. | |
Action: Ensure that the IS service name or IS document name is a valid Integration Server name and no other Integration Server service or document of the same name exists. | |
5608 | IS document does not exist document_name. Enter an existing one. |
Explanation: Error. Occurs when you attempt to create a SOPERA notification provider with a non-existing IS document. | |
Action: Ensure that the IS document exists onIntegration Server. | |
5573 | Error while retrieving the SOPERA service service_name from the registry. |
Explanation: Error. Occurs when attempting to retrieve the specified adapter service name instance from the registry name. | |
Action: Ensure that the service name is correct and the service is registered. See the AdminFacade logs for the exact reason for the error. | |
5574 | Error while processing input parameters while invoking SOPERA service service_name |
Explanation: Error. Occurs when the adapter is unable to convert the input message into XML or the request message is missing. | |
Action: Recreate the input document type for the specified service. | |
5575 | Fault message received - error encountered in service provider while invoking SOPERA service. |
Explanation: Error. The exception occurs during the invocation of the SOPERA provider service. | |
Action: Check the error logs at the SOPERA provider end. | |
5576 | SBB Error encountered when receiving non-blocking response from provider. |
Explanation: Error. Occurs when the adapter is unable to get non-blocking response from the pub.wmsopera.service:getNonBlockingServiceResponse service. | |
Action: Check the SOPERA infrastructure error in the logs to see the cause of the exception and take appropriate action. If the problem persists, contact Software AG Global Support. | |
5577 | Invalid value of timeout parameter. |
Explanation: Error. Occurs when the value of the timeout parameter is not numeric. | |
Action: Verify the value of the timeout parameter passed in the pub.wmsopera.service:getNonBlockingServiceResponse service. | |
5578 | Callback timeout. Increase timeout value. |
Explanation: Error. Occurs when attempting to get a response for a Nonblocking request. | |
Action: Increase the timeout value in the input parameter and retry. Also, ensure that the provider has not thrown any error. | |
5579 | Configure local endpoint for service service_name and operation operation_name and then restart all adapter connections. |
Explanation: Error. Local endpoint not found for the specified SOPERA callback operation in the SOPERA infrastructure. | |
Action: Configure the local endpoint for the SOPERA callback service and the service operation. Restart all adapter connections. | |
5580 | Authentication error invoking operation operation_name on service service_name with subject user_credentials |
Explanation: Error. A SOPERA outgoing call failed because of invalid user credentials. | |
Action: Ensure that the user who invoked the adapter service on Integration Server has access to the specified SOPERA service on the SOPERA Infrastructure. |