Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The file included a nested resource, and errors were found while loading the nested resource. |
Action | See previous messages for further information. |
Explanation | An exception was thrown while looking up the Ecore model. |
Action | See previous messages for further information. |
Explanation | Errors were found while loading the resource. |
Action | See previous 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 | The BLOB Data Access Service was unable to parse the message. |
Action | See previous messages for further information. |
Explanation | The BLOB Data Access Service was unable to calculate the message length. |
Action | See previous messages for further information. |
Explanation | The BLOB Data Access Service was unable to write the message. |
Action | See previous messages for further information. |
Explanation | The message is based on a message model that the BLOB Data Access Service is unable to handle. The message may have been processed with the wrong Data Access Service. |
Action | If your message should be processed with another Data Access Service ensure that the message format is set correctly. |
Explanation | The SOAP Data Access Service was unable to parse the message. |
Action | See previous messages for further information. |
Explanation | The SOAP Data Access Service was unable to calculate the message length. |
Action | See previous messages for further information. |
Explanation | The SOAP Data Access Service was unable to write the message. |
Action | See previous messages for further information. |
Explanation | The format string does not match the syntax required by the SOAP Data Access Service. |
Action | Ensure the message format follows the correct syntax for the SOAP Data Access Service. |
Explanation | The start offset and data length are incompatible with the buffer length passed to the SOAP Data Access Service. |
Action | Ensure the region described by the start offset and data length fits within the buffer. |
Explanation | The SOAP Data Access Service was unable to create a new DataGraph. |
Action | See previous 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 Body contained an unexpected element. |
Action | Ensure the data in the message is compatible with the types modelled in the WSDL. |
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 modelled 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 modelled 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 a 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 simple value, but the value does not fit into the data graph. |
Action | Ensure the data in the message is compatible with the types modelled 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 modelled in the WSDL. |
Explanation | The JMF Data Access Service was unable to parse the message. |
Action | See previous messages for further information. |
Explanation | The JMF Data Access Service was unable to calculate the message length. |
Action | See previous messages for further information. |
Explanation | The JMF Data Access Service was unable to write the message. |
Action | See previous messages for further information. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The format string does not match the syntax required by the JMF Data Access Service. |
Action | Ensure the message format follows the correct syntax for the JMF Data Access Service. |
Explanation | The Bean Data Access Service was unable to parse the message. |
Action | See previous messages for further information. |
Explanation | The Bean Data Access Service was unable to create a DataGraph representing the message. |
Action | Ensure that you have imported WSDL or XML Schema definitions for the message. |
Explanation | The Bean Data Access Service was unable to create a DataGraph representing the message. |
Action | Ensure that the WSDL or XML Schema definitions for the message are correct. |
Explanation | The Bean Data Access Service was unable to create a message from the DataGraph. |
Action | Ensure that the supplied Java Objects feature appropriate accessor methods. |
Explanation | The Bean Data Access Service was unable to write the message. |
Action | See previous messages for further information. |
Explanation | The Bean Data Access Service was unable to create a message from the DataGraph. |
Action | Ensure that the supplied Java Objects feature appropriate accessor methods. |
Explanation | The Bean Data Access Service was unable to create a message from the DataGraph. |
Action | Ensure that the supplied Java Objects feature appropriate accessor methods. |
Explanation | The Bean Data Access Service was unable to create a message from the DataGraph. |
Action | Ensure that the supplied Java Objects feature appropriate accessor methods. |
Explanation | The Bean Data Access Service was unable to create a DataObject representing the MIME attachment. |
Action | Ensure that the supplied Java Objects are appropriate. |
Explanation | The Bean Data Access Service was unable to create a DataGraph representing the message. |
Action | Ensure that WSDL or XML Schema definitions are available for the message. |
Explanation | The Bean Data Access Service was unable to create a DataGraph representing the message. |
Action | Ensure that the supplied Java Objects feature appropriate accessor methods. |
Explanation | The Bean Data Access Service was unable to create a message from the DataGraph. |
Action | Ensure that the bean Object can be instantiated via Class.newInstance(). |
Explanation | The Bean Data Access Service was unable to create a DataGraph representing the message. |
Action | Ensure that WSDL or XML Schema definitions are available for the message. |
Explanation | The Bean Data Access Service was unable to create a DataGraph representing the message. |
Action | Ensure that WSDL or XML Schema definitions are available for the message. |
Explanation | The Bean Data Access Service was unable to create a MIME attachment from the DataGraph. |
Action | Ensure that the data in the message is suitable for MIME body part creation. |
Explanation | The Bean Data Access Service was unable to create a Detail Element from the DataGraph. |
Action | Ensure that the data in the message is suitable for Detail Element creation. |
Explanation | The Bean Data Access Service was unable to create a DataObject representing the Detail Element. |
Action | Ensure that the supplied Java Objects are appropriate. |
Explanation | The Bean Data Access Service was unable to create a new DataGraph. |
Action | See previous messages for further information. |
Explanation | The Bean Data Access Service delegated this operation to the JMF Data Access Service which was unable to parse the message. |
Action | See previous messages for further information. |
Explanation | The Bean Data Access Service delegated this operation to the JMF Data Access Service which was unable to write the message. |
Action | See previous messages for further information. |
Explanation | The Bean Data Access Service delegated this operation to the JMF Data Access Service which was unable to calculate the message length. |
Action | See previous messages for further information. |
Explanation | The Bean Data Access Service was unable to map the supplied attribute value to the supplied type. |
Action | Ensure that the supplied attribute value is of an appropriate type. |
Explanation | The Bean Data Access Service was unable to map the supplied type to a Java Class. |
Action | Ensure that an appropriate mapping has been provided. |
Explanation | The Bean Data Access Service was unable to map the supplied type to a Java Class. |
Action | Ensure that an appropriate mapping has been provided. |
Explanation | The format string does not match the syntax required by the Bean Data Access Service. |
Action | Ensure the message format follows the correct syntax for the Bean Data Access Service. |
Explanation | The SOAP Parser expected a SOAP Fault element, but encountered the above element. |
Action | Ensure the data in the message is compatible with the SOAP specification. |
Explanation | The SOAP Parser was unable to locate the message meta-data 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 specialised 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 supported 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 | The XML transcription of the clients datagraph is too big for the supplied buffer. |
Action | Ensure that the buffer is sufficient to accommodate the XML output, starting at the supplied offset. |
Explanation | The SAX XMLSerializer has received incorrect input. |
Action | Examine the linked exception to determine the problem. |
Explanation | The format string does not match the syntax required by the XML Data Access Service. |
Action | Ensure the message format follows the correct syntax for the XML Data Access Service. |
Explanation | No schema information could be found for the document element in the current context. |
Action | Modify the document to match the schema or the schema to match the document. |
Explanation | An exception was thrown while looking up the Ecore model. |
Action | See previous messages for further information. |
Explanation | The standard runtime Ecore model information for processing XML messsages can not be found. |
Action | This model data is part of the installation. Please refer to IBM service. |
Explanation | The document is attempting to give a value to a reference which is modeled as a non containment reference. |
Action | Modify the model to remove the non containment attribute or do not include optional non containment references in instance documents. |
Explanation | An unexpected error occured when passing the input source to the XML parser. |
Action | See the previous message for more information. |
Explanation | An exception was thrown while looking up the Ecore model. |
Action | See previous messages for further information. |
Explanation | An unexpected error associated with the input/output infrastructure has occured. |
Action | See previous messages for further information. |
Explanation | The XML document is being parsed on demand and an XML well formedness error occured. |
Action | See previous messages for more information. |
Explanation | An unexpected input/output error occured during lazy parsing of the XML document. |
Action | See previous messages for more information. |
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 XML Schema definition. |
Explanation | No schema information could be found for the document element in the current context. |
Action | Modify the document to match the schema or the schema to match the document. |
Explanation | No model information could be found to permit creation of a datagraph using the named root element and namespace. |
Action | Check the namespace, location and local name in the instance document. |
Explanation | The format string does not match the syntax required by the TrAX Data Access Service. |
Action | Ensure the message format follows the correct syntax for the TrAX Data Access Service. |
Explanation | The program is attempting to generate a TrAX Source instance from a serialized document and had encountered an unexpected parser configuration error. |
Action | See previous messages for more information. |
Explanation | The XML parser has detected an XML well formedness error in attempting to build the XSLT input. |
Action | See previous messages for more information. |
Explanation | An unexpected input/output error occured while building an input to the XSLT transform from a serialized XML document. |
Action | See previous messages for more information. |
Explanation | The message buffer appears to have been corrupted. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The accessor is not defined for this message part. |
Action | See previous messages for more information. |
Explanation | The message subtype is not in the expected range. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The broker command must be one of a defined set. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An MQ broker control message factory instance cannot be created because the installation is incomplete or corrupted. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The message buffer appears to have been corrupted. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The MQ format message cannot be sent to the target MQ system or application. |
Action | Increase the maximum message size accommodated in the channel definition. |
Explanation | The message buffer appears to have been corrupted. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
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 | 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 | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |