Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Message selectors are only supported for API messages. |
Action | Ensure that the application does not use message selectors for non-API messages. |
Explanation | An attempt was made to convert the message from one message type to another message type. This conversion is not supported. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | JMS_IBM_MQMD_ properties must be set using specific variable types. |
Action | Correct the application code to use the required variable type to set this JMS_IBM_MQMD property. |
Explanation | The string is not a valid hexadecimal correlation ID. It must be of the form ID: followed by an even number of hexadecimal characters only. |
Action | Correct the string for which the conversion is failing. |
Explanation | An attempt to convert from a string to a byte array failed due to the string either containing non-hexadecimal characters, or an odd number of characters. |
Action | Check the content of the string for which the conversion is failing. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The WSDL importer was unable to import the file. |
Action | Ensure that you are importing valid WSDL files, and that you are using a supported version of the WSDL standard. |
Explanation | The WSDL importer was unable to locate a type definition. |
Action | Ensure that you have included an XML Schema definition of the type in the WSDL types section. |
Explanation | The WSDL importer was unable to locate an element definition. |
Action | Ensure that you have included an XML Schema definition of the element in the WSDL types section. |
Explanation | The run-time environment blocked access to the given URI. This is caused by an attempt to load an XML Schema that has not been deployed to the SDO repository. |
Action | Ensure that you have deployed appropriate WSDL and XML Schema files to the SDO repository. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The file included a nested resource, and errors were found while loading the nested resource. |
Action | See accompanying error messages for further information. |
Explanation | An exception was created while looking up the Ecore model. |
Action | See accompanying error messages for further information. |
Explanation | The WSDL importer was unable to locate a definition referenced within the WSDL. |
Action | Ensure that your WSDL definitions are complete, and that you have included all referenced WSDL files. |
Explanation | The XML Schema importer was unable to import the file. |
Action | Ensure that you are importing valid XML Schema files, and that you are using a supported version of the XML Schema standard. |
Explanation | The XML Schema importer was unable to load the file. |
Action | Ensure that you are importing valid XML Schema files, and that you are using a supported version of the XML Schema standard. |
Explanation | An error was reported while importing an XML Schema. |
Action | Refer to the error message for more information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occured parsing a Web Services message. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured writing a Web Services message. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure the message format follows the correct syntax for a SOAP message. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | The data object representing a header entry did not contain the correct number of child data objects. |
Action | Ensure that each header entry contains exactly one child. |
Explanation | The XML parser has reported an error while processing a SOAP message. |
Action | Ensure the message is well-formed XML. |
Explanation | The SOAP Parser expected a SOAP Envelope element, but encountered the above element. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser expected a SOAP Header or Body element, but encountered the above element. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser found a SOAP mustUnderstand attribute with an incorrect value. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser found a non-root SOAP body element, but the element is not SOAP encoded. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser found an element with an incorrect SOAP root attribute. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser encountered data within an element that had an xsi:nil="true" attribute. |
Action | Ensure the data in the message is compatible with the XML Schema specification. |
Explanation | The SOAP Parser encountered an element within an element that had an xsi:nil="true" attribute. |
Action | Ensure the data in the message is compatible with the XML Schema specification. |
Explanation | The SOAP Parser encountered an attribute within an element that had an xsi:nil="true" attribute. |
Action | Ensure the data in the message is compatible with the XML Schema specification. |
Explanation | The SOAP parser was unable to convert the value into an instance of the type. |
Action | Ensure the data in the message is compatible with the types modeled in the WSDL. |
Explanation | The XML element contained some text, but the WSDL model does not allow this element to contain data. |
Action | Ensure the data in the message is compatible with the types modeled in the WSDL. |
Explanation | The XML element contained an xsi:type attribute, but the value of the attribute could not be processed. |
Action | Ensure the data in the message is compatible with the XML Schema specification. |
Explanation | The message body in the SOAP message did not match any of the definitions in the WSDL. This may be because the SOAP message is incorrect or the format string may have identified the wrong WSDL. |
Action | Ensure the data in the message is compatible with the WSDL. |
Explanation | Each non-root SOAP body element should have an id attribute with a unique value. |
Action | Ensure that your message follows the SOAP encoding rules. |
Explanation | Each non-root SOAP body element should be referenced by some other part of the message. |
Action | Ensure that your message follows the SOAP encoding rules. |
Explanation | A SOAP encoded element uses an href attribute but an element with a matching id attribute cannot be found. |
Action | Ensure that your message follows the SOAP encoding rules. |
Explanation | The XML element contained a processing instruction, but SOAP does not allow elements to contain processing instructions. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The XML element contained a simple value, but the value does not fit into the data graph. |
Action | Ensure that the data in the message is compatible with the types modeled in the WSDL. |
Explanation | The XML element contained an attribute, but the attribute does not fit into the data graph. |
Action | Ensure the data in the message is compatible with the types modeled in the WSDL. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See accompanying error messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | Ensure the message format follows the correct syntax for the JMF Data Access Service. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that you have imported WSDL or XML Schema definitions for the message. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the WSDL or XML Schema definitions for the message are correct. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied Objects feature appropriate accessor methods. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied Objects feature appropriate accessor methods. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied Objects feature appropriate accessor methods. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied Objects feature appropriate accessor methods. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied Objects are appropriate. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that WSDL or XML Schema definitions are available for the message. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied Objects feature appropriate accessor methods. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the bean Object can be instantiated using Class.newInstance(). |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that WSDL or XML Schema definitions are available for the message. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that WSDL or XML Schema definitions are available for the message. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the data in the message is suitable for MIME body part creation. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the data in the message is suitable for Detail Element creation. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | See accompanying error messages for further information. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that the supplied attribute value is of an appropriate type. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that an appropriate mapping has been provided. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure that an appropriate mapping has been provided. |
Explanation | An error occured processing a Web Services request, response or fault. |
Action | Ensure the message format follows the correct syntax for the Bean Data Access Service. |
Explanation | The SOAP Parser was unable to locate the message metadata for the given message. |
Action | Ensure that you have imported WSDL definitions for the message. |
Explanation | The SOAP Parser was processing a message part whose content is delegated to a MIME attachment, but the part also contained a nested element. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser was processing a message part whose content is delegated to a MIME attachment, but the part also contained an unexpected attribute. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser encountered an exception while processing a MIME attachment referenced by the message part. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser could not find the MIME attachment referenced by the message part. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser encountered an IOException while processing a MIME attachment with the given content id and type. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The message format provided does not match an expected message format. |
Action | Ensure a correct message format is provided. |
Explanation | A parameter value was supplied that is not permitted for the defined method. |
Action | Ensure valid parameters are passed to the method in question. |
Explanation | It was not possible to deserialize the message element due to the linked IOException |
Action | Investigate and resolve the problem described in the linked IOException |
Explanation | It was not possible to copy a message element due to the linked Exception. |
Action | Investigate and resolve the problem described in the linked Exception |
Explanation | A parameter value was supplied that is not permitted for the defined method. |
Action | Ensure valid parameters are passed to the method in question. |
Explanation | It was not possible to serialize or deserialize the message element due to the linked IOException |
Action | Investigate and resolve the problem described in the linked IOException |
Explanation | The MimeElementList is a specialized list implementation that supports only MimeElement list entries. |
Action | Create a MimeElement object containing the parameter before trying to add it to the list. |
Explanation | The implementation does not support the type of the supplied message. |
Action | Do not supply messages of the specified type to this utility. |
Explanation | The implementation only supports messages that contain exactly one ContentType header field. |
Action | Do not supply messages containing zero, or more than one content-type fields to this utility. |
Explanation | It was not possible to copy a message element list due to the linked Exception. |
Action | Investigate and resolve the problem described in the linked Exception |
Explanation | Each part of a WSDL message must be associated with a XML Schema type or element. |
Action | Ensure that the definition of each message part includes either the 'type' or 'element' attribute. |
Explanation | The access of a JMS Map Message through SDO is not supported. |
Action | Rewrite the application to use supported function. |
Explanation | The serialization of the payload DataGraph failed. |
Action | Examine the linked exception to determine the problem. |
Explanation | The parsing of the byte array to create the DataGraph failed. |
Action | Examine the linked exception to determine the problem. |
Explanation | The Transcoding between the current SDO message DataGraph format and the new DataGraph format is not supported. |
Action | Rewrite the application to use supported function. |
Explanation | A non-null byte array is required to build a DataGraph of this format. |
Action | Examine the linked exception to determine the problem. |
Explanation | The WSDL identified by the format string could not be located. This may be because the location in the format is incorrect or because the WSDL has not been deployed. |
Action | Ensure that the WSDL location in the format string is correct. |
Explanation | The format string did not match the definitions in the WSDL. This may be because the service name or namespace in the format is incorrect or the wrong WSDL has been deployed. |
Action | Ensure that the service name and namespace in the format string match definitions in the WSDL. |
Explanation | The format string did not match the definitions in the WSDL. This may be because the port name in the format is incorrect or the wrong WSDL has been deployed. |
Action | Ensure that the port name in the format string matches the definition in the WSDL. |
Explanation | The format string did not match the definitions in the WSDL. This may be because the WSDL is incomplete or the wrong WSDL has been deployed. |
Action | Ensure that the port is associated with a binding in the WSDL. |
Explanation | The map name list and map value lists must be the same length. Together they represent the name and value pairs of the map message. |
Action | Ensure both lists have the same length. |
Explanation | The format string does not match any of the format strings recognized for a JMS message. |
Action | Ensure the message format is correct for a message type supported for JMS messages. |
Explanation | The program is attempting to serialize a JMS message and has failed to do so. |
Action | Examine the linked exception to determine the problem. |
Explanation | The program is attempting to verify the suitability of a supplied DataObject for forming the payload of a JMS message. |
Action | Modify the program to supply a DataObject of an appropriate type. |
Explanation | An unexpected error occurred while configuring an XML parser. |
Action | Examine the linked exception to determine the problem. |
Explanation | The payload of the JMS stream message is not valid XML. |
Action | Examine the linked exception to determine the problem. |
Explanation | An input/output error occurred in SAX processing while trying to parse the body of a JMS stream message |
Action | Examine the linked exception to determine the problem. |
Explanation | An input/output error occurred while attempting to write a JMS stream message payload. |
Action | Examine the linked exception to determine the problem. |
Explanation | The type of the element in question is not permitted in a JMS stream message. |
Action | Modify the program to ensure that objects of this type are not inserted into the stream message. |
Explanation | An unexpected error has occurred while writing the payload of a JMS stream message to bytes. |
Action | Examine the linked exception to determine the problem. |
Explanation | The type of the DataObject supplied as the payload of a JMS message must be compatible with the format of that message. |
Action | Modify the program to ensure that the supplied DataObject and format are compatible. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | If the message does not give sufficient information, check the accompanying messages for further help. |
Action | See the accompanying error messages for further information. |