Explanation | The destination defined for correlation support could not be found. |
Action | Ensure that the destination has been defined correctly. |
Explanation | The specified boolean property could not be found. |
Action | Ensure that the boolean property has been defined correctly. |
Explanation | The specified string property could not be found. |
Action | Ensure that the string property has been defined correctly. |
Explanation | An error occurred while sending information to the correlation destination. |
Action | Ensure that correlation destination has been defined and enabled correctly. |
Explanation | The workarea used by filters could not be accessed. |
Action | Ensure that the deployed filters access the workarea correctly. |
Explanation | The message received was not in a recognized form. |
Action | Enable tracing and inspect the form and content of the message received. |
Explanation | The message received was not recognized as one could that be converted by an installed data mediator. |
Action | Ensure that an appropriate data mediator for the message format has been installed. |
Explanation | Information about the request received could not be logged. |
Action | Ensure that the log file is writable and that there is sufficient storage space to record the logging information. |
Explanation | The list of filters provided in the property was not recognized. |
Action | Ensure that the list of filters is provided in a comma-separated (CSV) form, using the correct encoding. |
Explanation | The filter {0} could not be found within the system or could not be instantiated. |
Action | Ensure that the filter {0} has been correctly deployed and activated. |
Explanation | A filter could not query the routing information for the current message. |
Action | Enabling tracing for the Gateway runtime, to determine where the problem occurred. |
Explanation | A filter could not modify the routing information for the current message. |
Action | Enabling tracing for the Gateway runtime, to determine where the problem occurred. |
Explanation | A filter indicated that a response should be sent, but this could not be done. |
Action | Enabling tracing for the Gateway runtime, to determine where the problem occurred. |
Explanation | A filter threw an unrecoverable exception, which could not be handled by the Gateway. |
Action | Enable tracing for the Gateway runtime and the filter, to determine the cause of the exception. |
Explanation | Information about the response received could not be logged. |
Action | Ensure that the log file is writable and that there is sufficient storage space to record the logging information. |
Explanation | An error occurred while retrieving information from the correlation destination. |
Action | Ensure that correlation destination has been defined and enabled correctly. |
Explanation | An error occurred while performing a lookup. |
Action | Ensure that object has been defined correctly. |
Explanation | An error occurred while working with the specified namespace. |
Action | Use trace information to determine what task was being performed when the error occured, and check that the namespace is correct and makes sense at that point. |
Explanation | An error occurred while working with the specified service. |
Action | Use trace information to determine what task was being performed when the error occured, and check that the service is correct and makes sense at that point. |
Explanation | An error occurred while working with the specified portname. |
Action | Use trace information to determine what task was being performed when the error occured, and check that the portname is correct and makes sense at that point. |
Explanation | An error occurred while working with the specified property. |
Action | Use trace information to determine what task was being performed when the error occured, and check that the property and its value are correct and make sense at that point. |
Explanation | An error occurred while working with the specified property. |
Action | Check that the property value is correct and consistent with the required format. |
Explanation | An expected property within the message could not be located. |
Action | Determine the contents of the message and its properties, and confirm that the expected property is present and in the correct form. |
Explanation | The given location could not be set as the target service because this location has not been defined as a target service for this gateway service. |
Action | Ensure that the correct target service location is specified. |
Explanation | A target service can only be selected using a non-null value for the identity. |
Action | Modify the calling code to ensure that the target service identity value is never null. |
Explanation | A target service was requested by identity, but the identity information does not match any currently deployed target service. |
Action | Ensure that the identity information is correct, and that there is a target service deployed to the given gateway service with the right identity information. |
Explanation | The WSDL definition for the given location could not be returned because this location has not been defined as a target service for this gateway service. |
Action | Ensure that the correct target service location is specified. |
Explanation | The WSDL definition for this target service could not be retrieved. |
Action | Ensure that the gateway and target services are correctly defined. |
Explanation | The default target service location cannot be obtained for the gateway service as no suitable target services are defined for it. |
Action | Ensure that one or more target services are defined for the gateway service. |
Explanation | There are no outbound ports defined for the outbound service associated with the given target or proxy service. |
Action | Make sure that there is at least one outbound port defined for the outbound service associated with the given target or proxy service. |
Explanation | The given location could not be set as the target service because this location has not been defined as a target service for this gateway service. |
Action | Ensure that the correct target service location is specified. |
Explanation | The requested port does not exist for the target service. |
Action | Ensure that a valid port is requested and defined as an outbound port in the outbound service associated with the given target or proxy service. |
Explanation | The filter {0} threw a non-fatal exception. |
Action | Enable tracing for filter {0} to determine the cause of the exception if this was unexpected. |
Explanation | No filter made a change to the message. |
Action | No action required. It is possible that one or more of the filters are not required. |
Explanation | A request message has been received. |
Action | No action required. |
Explanation | A response message has been received. |
Action | No action required. |