WebSphere Process Server messages     Operating Systems: All supported
CWMBO0100E: The BODataObject service cannot retrieve the change summary. The failing business graph type is {0}.
Explanation: The change summary was not created during the creation of a new business graph of the specified type. Therefore, the business graph is not valid.
User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0101E: The BODataObject service cannot retrieve the event summary. The failed business graph type is {0}.
Explanation: The event summary was not created during the creation of a new business graph of the specified type. Therefore, the business graph is not valid.
User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0102E: The following required business object services were not found: {0}
Explanation: At least one of the following business object services was not found: BOFactory (the service for creating business objects), BOChangeSummary (the service for manipulating change summaries), and BODataObject (the service for manipulating data objects).
User Action: Refer to the Troubleshooting guide on the WebSphere Process Server Support Site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0103E: The business graph cannot be created. The failed business graph type is {0}.
Explanation: The BOFactory service, which creates business objects and business graphs, cannot create a business graph of the specified type. The business graph definition is either not valid or it cannot be found.
User Action: In the WebSphere Process Server log file, locate the BOFactory message for this failed business graph type. Follow the recommended action. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0104E: The data object of the namespace {0} and the name {1} cannot be created.
Explanation: The BOFactory service, which is responsible for creating business objects and business graphs, cannot create a data object of the specified namespace and name. The namespace, the name, or both are not valid.
User Action: In the WebSphere Process Server log file, locate the BOFactory message for the failed data object. Follow the recommended action. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0105E: The following XML input value is not valid: {0}.
Explanation: The source adapter passed in a null or empty message.
User Action: Verify that the adapter XML exists and is valid.

 

CWMBO0106E: The parsed XML message returned no root.
Explanation: The document parsed from the input XML string is not valid because the input string itself is not valid.
User Action: Verify that the adapter XML is valid.

 

CWMBO0107E: The XML message "{0}" cannot be parsed for the following reason: {1}
Explanation: An exception occurred while parsing the specified XML string to a document. The source adapter passed in the specified XML, which is not valid.
User Action: Correct the adapter XML according to the parsing error.

 

CWMBO0108E: The "verb" attribute cannot be found.
Explanation: The input element must have a "verb" attribute.
User Action: Make sure the input element is valid, and add a "verb" attribute.

 

CWMBO0109E: The business graph cannot be extracted from the input data object of the type {0}.
Explanation: The BODataObject service cannot retrieve the business graph from the specified input data object because the input data object is not a valid business graph.
User Action: Verify that the input data object is a business graph. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0110E: The input data object is empty.
Explanation: The data object that was sent to the adapter cannot be converted to XML because the object is empty.
User Action: Try to determine at which point the data object became empty. You can do this by using print statements in the Business Process Execution Language (BPEL) and maps or by enabling Service Component Architecture (SCA) tracing in the administrative console to view the WebSphere Process Server logs. Refer to the WebSphere Process Server documentation at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp for information on correcting the problem. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0111E: The type cannot be extracted from the input data object.
Explanation: The error occurred when the data object was sent to the adapter because the data object does not exist.
User Action: If the data object definition does not exist, create a definition for the missing data object. If the data object definition exist, add it to the class path if it is not there. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0112E: No top-level verb value was found. The business graph is not an after-image.
Explanation: The data object cannot be sent to the adapter because the top-level verb is empty.
User Action: If no top-level verb is included in the business graph, add it. If the verb definition exists and the verb has a value but is now empty, determine at which point the verb became empty. You can do this by using print statements in the Business Process Execution Language (BPEL) and maps or by enabling Service Component Architecture (SCA) tracing in the administrative console to view the WebSphere Process Server logs. Refer to the WebSphere Process Server documentation at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp for information on correcting the problem. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0113E: No top-level business object type {0} was found for the following business graph type: {1}
Explanation: Likely reasons for this problem are that the top-level business object does not exist or its definition is not in the class path or is not valid.
User Action: If the definition does not include a top-level business object, add it. If the definition is valid, add it to the class path if it is not there. If the problem persists, refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0114E: The XML factory was not initialized.
Explanation: The XML document for the adapter is created from the WebSphere Process Server data object. The error occurred while initializing the DocumentBuilderFactory service to make this conversion.
User Action: Refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 

CWMBO0115E: The XML cannot be serialized.
Explanation: The XML document for the adapter is created from the WebSphere Process Server data object, and an exception occurred while trying to serialize the final XML. So the final XML is not valid.
User Action: Refer to the Troubleshooting guide on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009