WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


CWSIF

CWSIF0001E: A JsMessageFactoryImpl instance cannot be created: exception {0}.
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/.
CWSIF0011E: A JsJmsMessageFactoryImpl instance cannot be created: exception {0}.
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/.
CWSIF0021E: A TrmMessageFactoryImpl instance cannot be created: exception {0}.
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/.
CWSIF0031E: A JsMessageHandleFactoryImpl instance cannot be created: exception {0}.
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/.
CWSIF0041E: A ControlMessageFactoryImpl instance cannot be created: exception {0}.
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/.
CWSIF0051E: A CompHandshakeImpl instance cannot be created: exception {0}.
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/.
CWSIF0061E: A {0} instance cannot be created: exception {1}.
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/.
CWSIF0101E: Message selectors are not supported for message {0}.
Explanation Message selectors are only supported for API messages.
Action Ensure that the application does not use message selectors for non-API messages.
CWSIF0102E: Message type {1} was expected but message type {0} was found.
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/.
CWSIF0103E: Message type {0} with format {1} can not be converted to a JMS message as adapter type {2} is not valid.
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/.
CWSIF0181E: The SDO DataGraph cannot be obtained from the message payload.
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/.
CWSIF0182E: The message contains an incorrect encapsulation class: {0}
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/.
CWSIF0191E: The hexadecimal string {0} is incorrectly formatted for a correlation ID.
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.
CWSIF0200E: The hexadecimal string {0} is incorrectly formatted.
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.
CWSIF0211E: The message format cannot be identified: exception {0}
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/.
CWSIF0212E: The message length cannot be calculated: exception {0}
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/.
CWSIF0213E: The message cannot be calculated: exception {0}
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/.
CWSIF0214E: The JMF message cannot be unsassembled: exception {0}
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/.
CWSIF0221E: JMF schema ID error: exception {0}
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/.
CWSIF0222E: The message cannot be parsed: exception {0}
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/.
CWSIF0232E: Unable to import WSDL file {0}: exception {1}
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.
CWSIF0233E: Unable to locate type: name {0}, namespace {1}.
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.
CWSIF0234E: Unable to locate element: name {0}, namespace {1}.
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.
CWSIF0235E: Blocking access to input stream for URI: {0}.
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.
CWSIF0236E: Blocking access to output stream for URI: {0}.
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/.
CWSIF0237E: An exception was raised while loading included resource. Resource URI: {0}, exception: {1}.
Explanation The file included a nested resource, and errors were found while loading the nested resource.
Action See previous messages for further information.
CWSIF0238E: An exception was raised while locating Ecore model. Target namespace {0}, location hint {1}, exception {2}.
Explanation An exception was thrown while looking up the Ecore model.
Action See previous messages for further information.
CWSIF0239E: A repository exception was raised while loading resource. Resource location: {0}, exception: {1}.
Explanation Errors were found while loading the resource.
Action See previous messages for further information.
CWSIF0240E: Unable to locate WSDL {0} with name {1}. The definition was referenced within file {2}.
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.
CWSIF0241E: Unable to import XML Schema file {0}: exception {1}
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.
CWSIF0242E: Error loading XML Schema: {0}
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.
CWSIF0243E: {0}
Explanation An error was reported while importing an XML Schema.
Action Refer to the error message for more information.
CWSIF0251E: Unable to parse message: exception {0}
Explanation The BLOB Data Access Service was unable to parse the message.
Action See previous messages for further information.
CWSIF0252E: Unable to calculate message length: exception {0}
Explanation The BLOB Data Access Service was unable to calculate the message length.
Action See previous messages for further information.
CWSIF0253E: Unable to write message: exception {0}
Explanation The BLOB Data Access Service was unable to write the message.
Action See previous messages for further information.
CWSIF0254E: Incorrect message model: type name {0}, namespace {1}.
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.
CWSIF0271E: Unable to parse message: exception {0}
Explanation The SOAP Data Access Service was unable to parse the message.
Action See previous messages for further information.
CWSIF0272E: Unable to calculate message length: exception {0}
Explanation The SOAP Data Access Service was unable to calculate the message length.
Action See previous messages for further information.
CWSIF0273E: Unable to write message: exception {0}
Explanation The SOAP Data Access Service was unable to write the message.
Action See previous messages for further information.
CWSIF0274E: Incorrect format string: {0}
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.
CWSIF0275E: Incorrect buffer offsets: Buffer length {0}, Start offset {1}, data length {2}.
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.
CWSIF0276E: Unable to create a new SDO DataGraph: exception {0}
Explanation The SOAP Data Access Service was unable to create a new DataGraph.
Action See previous messages for further information.
CWSIF0281E: Header entry contains wrong number of child data objects. Expected 1, found {0}.
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.
CWSIF0291E: Unable to parse the message. Error URI {0}, error code {1}, additional data {2}
Explanation The XML parser has reported an error while processing a SOAP message.
Action Ensure the message is well-formed XML.
CWSIF0292E: Unexpected element found. Element name {0}, element namespace {1}
Explanation The SOAP Body contained an unexpected element.
Action Ensure the data in the message is compatible with the types modelled in the WSDL.
CWSIF0293E: Unexpected element found. Element name {0}, element namespace {1}.
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.
CWSIF0294E: Unexpected element found. Element name {0}, element namespace {1}.
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.
CWSIF0295E: Unexpected mustUnderstand value found. Element name {0}, element namespace {1}, mustUnderstand value {2}.
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.
CWSIF0296E: Incorrect non-root SOAP body element found. Element name {0}, element namespace {1}.
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.
CWSIF0297E: Incorrect SOAP root attribute found. Element name {0}, element namespace {1}, SOAP root attribute value {2}.
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.
CWSIF0298E: Data found within nil element. Element name {0}, element namespace {1}, data {2}.
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.
CWSIF0299E: Element found within nil element. Element name {0}, element namespace {1}, nested element name {2}, nested element namespace {3}
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.
CWSIF0300E: Attribute found within nil element. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3}
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.
CWSIF0301E: Unable to parse a value within the message. Type name {0}, type namespace {1}, data {2}
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.
CWSIF0302E: Unexpected text found. Element name {0}, element namespace {1}, data {2}
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.
CWSIF0303E: Incorrect xsi:type attribute encountered while processing element name {0}, namespace {1}, xsi:type value {2}
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.
CWSIF0304E: The message body did not match any of the definitions in the WSDL
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.
CWSIF0305E: An id attribute cannot be found for a non-root SOAP body element. Element details: name {0}, namespace {1}.
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.
CWSIF0306E: An element with id attribute value {0} is not referenced.
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.
CWSIF0307E: An element which matches href attribute value {0} cannot be found.
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.
CWSIF0308E: Unexpected processing instruction found. Element name {0}, element namespace {1}, target {2}.
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.
CWSIF0309E: Unexpected element found. Element name {0}, element namespace {1}.
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.
CWSIF0310E: Unexpected attribute found. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3}.
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.
CWSIF0311E: Unable to parse message: exception {0}
Explanation The JMF Data Access Service was unable to parse the message.
Action See previous messages for further information.
CWSIF0312E: Unable to calculate message length: exception {0}
Explanation The JMF Data Access Service was unable to calculate the message length.
Action See previous messages for further information.
CWSIF0313E: Unable to write message: exception {0}
Explanation The JMF Data Access Service was unable to write the message.
Action See previous messages for further information.
CWSIF0314E: Message length {0} does not match the expected length {1}
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/.
CWSIF0315E: Incorrect format string: {0}
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.
CWSIF0321E: Unable to parse message: exception {0}.
Explanation The Bean Data Access Service was unable to parse the message.
Action See previous messages for further information.
CWSIF0322E: Failed to create DataObject: parent type name {2}, property name {0}, namespace {1}.
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.
CWSIF0323E: Unable to determine base type for restriction derived type: type name {0}, namespace {1}.
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.
CWSIF0324E: Failed to acquire and invoke a method while introspecting an Object representing an enumerated type: type name {0}, namespace {1}, method name {2}, target class name {3}.
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.
CWSIF0325E: Unable to write message: exception {0}.
Explanation The Bean Data Access Service was unable to write the message.
Action See previous messages for further information.
CWSIF0326E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
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.
CWSIF0327E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
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.
CWSIF0328E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
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.
CWSIF0329E: Failed to parse MIME attachment: content type {0}.
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.
CWSIF0330E: Failed to create DataObject for SOAP fault message: fault feature name {0}, namespace {1}, location {2}.
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.
CWSIF0331E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}.
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.
CWSIF0332E: Failed to create a new instance of a bean Object: parent type name {2}, property name {0}, namespace {1}, class name {3}.
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().
CWSIF0333E: Failed to locate model for creation of DataObject representing SOAP-encoded array message: namespace {0}, location {1}.
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.
CWSIF0334E: Failed to locate model for creation of DataObject representing SOAP-encoded array message: namespace {0}, location {1}.
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.
CWSIF0335E: Failed to write MIME attachment: content type {0}, content transfer encoding {1}, content id {2}.
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.
CWSIF0336E: Failed to write fault message: message name {0}, operation name {1}.
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.
CWSIF0337E: Failed to parse fault message: message name {0}, operation name {1}.
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.
CWSIF0338E: Unable to create a new SDO DataGraph: exception {0}
Explanation The Bean Data Access Service was unable to create a new DataGraph.
Action See previous messages for further information.
CWSIF0341E: Unable to parse message: exception {0}.
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.
CWSIF0342E: Unable to write message: exception {0}.
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.
CWSIF0343E: Unable to calculate message length: exception {0}.
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.
CWSIF0346E: Failed to process attribute value: type name {0}, namespace {1}, attribute value {2}.
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.
CWSIF0347E: Failed to map schema type to a Java Class: type name {0}, namespace {1}.
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.
CWSIF0348E: Failed to map schema type to a Java Class: type name {0}, namespace {1}.
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.
CWSIF0350E: Incorrect format string: {0}.
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.
CWSIF0351E: Unexpected element found. Element name {0}, element namespace {1}.
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.
CWSIF0353E: Failed to locate meta-data for message. Service namespace {0}, service name {1}, port name {2}, operation name {3}, message name {4}.
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.
CWSIF0354E: Unexpected element found within message part. Message part name {0}, Element name {1}, element namespace {2}.
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.
CWSIF0355E: Unexpected attribute found within message part. Message part name {0}, Attribute name {1}, attribute namespace {2}.
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.
CWSIF0356E: Unable to process MIME attachment. Message part name {0}, exception {1}.
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.
CWSIF0357E: Unable to locate MIME attachment. Message part name {0}, reference {1}.
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.
CWSIF0358E: Unable to process MIME attachment. Content ID {0}, Content type {1}, exception {2}.
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.
CWSIF0362E: The message format {0} is incorrect
Explanation The message format provided does not match an expected message format.
Action Ensure a correct message format is provided.
CWSIF0371E: The supplied value {0} is not valid for the parameter {1} of method {2}
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.
CWSIF0372E: An IOException occured while obtain the content of the message element.
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
CWSIF0373E: An Exception occured during the copying of a message element: {0}.
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
CWSIF0381E: The supplied value {0} is not valid for the parameter {1} of method {2}
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.
CWSIF0382E: An IOException occured while serializing or deserializing the message in method {0}
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
CWSIF0383E: The MimeElementList only supports MimeElement entries. The supplied parameter was of type {0}.
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.
CWSIF0384E: The supplied message is of type {0}, and is not the required type of multipart/related.
Explanation The implementation does not supported the type of the supplied message.
Action Do not supply messages of the specified type to this utility.
CWSIF0385E: {0} ContentType header entries were found in the message.
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.
CWSIF0386E: An Exception occured during the copying of a message element list: {0}.
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
CWSIF0391E: The XML Data Access Service write operation was supplied a buffer which is too small.
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.
CWSIF0392E: Serialization of the datagraph failed while processing the object at path {0} with the linked exception {1}.
Explanation The SAX XMLSerializer has received incorrect input.
Action Examine the linked exception to determine the problem.
CWSIF0393E: Incorrect XML Data Access Service format string: {0}, problem substring: {1}.
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.
CWSIF0394E: The XML document contains an element which is not allowed. The element has the path {0}.
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.
CWSIF0395E: Exception raised while locating Ecore model. Local name {0}, target namespace {1}, location hint {2}, exception {3}.
Explanation An exception was thrown while looking up the Ecore model.
Action See previous messages for further information.
CWSIF0397E: The model data for parsing generic XML is not available. Exception {0}.
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.
CWSIF0398E: Attempt to set a value at path {0}. Non containment references are not supported by the XML Data Access 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.
CWSIF0399E: An input/output error occured when setting the parser input source. The error is {0}.
Explanation An unexpected error occured when passing the input source to the XML parser.
Action See the previous message for more information.
CWSIF0400E: Exception raised while locating Ecore model for local name {0} at location {1}, target namespace {2}, exception {3}.
Explanation An exception was thrown while looking up the Ecore model.
Action See previous messages for further information.
CWSIF0402E: An input/output exception occured during XML serialization. The error is {0}.
Explanation An unexpected error associated with the input/output infrastructure has occured.
Action See previous messages for further information.
CWSIF0404E: A parsing error occured during lazy XML parsing. The error is {0}.
Explanation The XML document is being parsed on demand and an XML well formedness error occured.
Action See previous messages for more information.
CWSIF0405E: An input/output error occured during lazy XML parsing. The error is {0}.
Explanation An unexpected input/output error occured during lazy parsing of the XML document.
Action See previous messages for more information.
CWSIF0406E: Unexpected attribute found. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3}.
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.
CWSIF0407E: The XML document contains an attribute which is not allowed. The attribute is named {0} with namespace uri {1} and is associated with the element path {2}.
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.
CWSIF0408E: The Ecore class containing the metadata for the global element in namespace {0} at location {1} with local name {2} is not available.
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.
CWSIF0411E: Incorrect format string: {0}
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.
CWSIF0412E: A parser configuration error occured when attempting to generate a SAX Source from a serialized XML document. The error is {0}.
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.
CWSIF0413E: The TrAX Data Access Service had encountered a SAX processing exception when attempting to parse a serialized document in order to create the input for an XSLT transform. The error is {0}.
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.
CWSIF0414E: An input/output error occured in the TrAX Data Access Service. The error is {0}.
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.
CWSIF0421E: Incorrect part indicator {0}.
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/.
CWSIF0422E: Incorrect accessor {0}.
Explanation The accessor is not defined for this message part.
Action See previous messages for more information.
CWSIF0423E: Unexpected message subtype {0}.
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/.
CWSIF0424E: Unrecognized broker command {0}.
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/.
CWSIF0425E: MQ broker control message factory cannot be instantiated.
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/.
CWSIF0426E: Incorrect frame offset {0}.
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/.
CWSIF0427E: Message size {0} is greater than the limit {1} defined for the MQ channel.
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.
CWSIF0428E: Incorrect segment type {0}.
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/.
CWSIF0431E: The WSDL Part {0} in message {1} is not associated with a type or element.
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.
CWSIF0500E: A JMS Map Message can not be accessed as an SDO DataGraph.
Explanation The access of a JMS Map Message through SDO is not supported.
Action Rewrite the application to use supported function.
CWSIF0501E: An error occurred while attempting to access a message''s payload datagraph as a byte array. The linked exception is {0}.
Explanation The serialization of the payload datagraph failed.
Action Examine the linked exception to determine the problem.
CWSIF0502E: An error occurred while attempting to create a message''s payload datagraph from a byte array using format {0}. The linked exception is {1}.
Explanation The parsing of the byte array to create the datagraph failed.
Action Examine the linked exception to determine the problem.
CWSIF0503E: The Transcoding from format {0} to format {1} is not supported.
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.
CWSIF0600E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The WSDL could not be located.
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.
CWSIF0601E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The WSDL was located, but did not contain the named service.
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.
CWSIF0602E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The service was located, but did not contain the named port.
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.
CWSIF0603E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The port was located, but did not contain a reference to a binding.
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.
CWSIF0700E: The map message does not have an equal number of names and values
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.
CWSIF9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help.
Action See previous messages for further information.
Reference topic    

Terms of Use | Feedback

Last updated: May 3, 2010 12:35:57 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.sib.mfp.CWSIFMessages.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)