WebSphere Process Server messages     Operating Systems: All supported
CWWBA0001E: Unknown query table name: ''{0}''.
Explanation: The query string contains a reference to an unknown table or view.
User Action: Check the spelling of the table or view name in the query.

 

CWWBA0002E: Unknown query column name: ''{0}''.
Explanation: The query string contains a reference to an unknown column.
User Action: Check the spelling of the column name in the query.

 

CWWBA0003E: Unknown query operator in where-clause: ''{0}''.
Explanation: The query string for a where-clause contains an operator that is not supported.
User Action: Check the spelling of the operator.

 

CWWBA0004E: Incorrect timestamp in a query where-clause: ''{0}''.
Explanation: The timestamp in the query's where-clause has an incorrect format.
User Action: Check that the format of the timestamp is: TS('yy-mm-ddThh:mm:ss').

 

CWWBA0006E: The format of the ID ''{0}'' is not valid.
Explanation: The object ID passed either has an incorrect format or is null.
User Action: Check the object ID and try again.

 

CWWBA0007E: The type of the ID ''{0}'' is wrong.
Explanation: The passed object ID has an incorrect type.
User Action: Check the object ID and try again.

 

CWWBA0008E: Process template ''{0}'' is not found.
Explanation: The specified process template is not found.
User Action: Check the name or the object ID of the process template.

 

CWWBA0009E: Implementation ''{0}'' is not found.
Explanation: The specified implementation is not found.
User Action: Check the name or the object ID of the implementation.

 

CWWBA0010E: Unexpected exception during execution.
Explanation: During the execution an unexpected exception occurred.
User Action: Check the reported exception.

 

CWWBA0011E: Incorrect operand in a query where-clause: ''{0}''.
Explanation: The query string for a where-clause contains an incorrect operand.
User Action: Check if the operand is spelt correctly. If the operand is a literal, check that the operand type matches the type of the corresponding column.

 

CWWBA0012E: A parameter was referenced in the query text but no value was defined for it: ''{0}''.
Explanation: The query string contains a parameter that needs to be defined when the query is executed.
User Action: Check that the parameter value for the referenced parameter is defined and is spelt correctly.

 

CWWBA0013E: A template ''{0}'' that is still referenced cannot be deleted.
Explanation: The specified template is not deleted because it is referenced (early bound) by other templates.
User Action: First delete the templates that reference the template and then delete the specified template.

 

CWWBA0014E: The provided object name ''{0}'' is not valid.
Explanation: An object name provided by the user does not follow the naming rules, for example, it is too long.
User Action: Specify a valid name.

 

CWWBA0015E: The object ''{0}'' does not exist; it might have been deleted in the meantime.
Explanation: An attempt was made to perform an action on an object that does not exist.
User Action: Check if an object name or ID provided by you is spelt correctly. Check whether the object still exists, for example, by issuing a query. Note that the object may have been deleted. For example, you tried to perform an action on a process that reached its end and that is deleted automatically.

 

CWWBA0016E: Namespace ''{0}'' cannot be deleted.
Explanation: The namespace is not deleted because it contains active process templates or process instances.
User Action: Stop all process templates and delete all process instances in the namespace.

 

CWWBA0017E: Parameter ''{0}'' exceeds the allowed maximum length ''{1}''. Current length is ''{2}''.
Explanation: You specified a parameter that exceeds its allowed maximum length.
User Action: Reduce the length of your parameter.

 

CWWBA0018E: Parameter ''{0}'' specifies an invalid value.
Explanation: The specified parameter has an invalid value. For example, 'compensation' cannot be specified when terminating a process instance that is derived from a 5.0 schema.
User Action: Correct the parameter value.

 

CWWBA0019E: Service is not unique.
Explanation: The service to be called is not unique. For example, you issued call() to execute a microflow that starts with a pick activity and multiple onMessage definitions. Or, you called initiate() and there is more than one starting activity.
User Action: Use sendMessage() and specify the service to be called.

 

CWWBA0020E: Activity name ''{0}'' is not unique.
Explanation: There is more than one activity in the process that has the specified name. The requested action requires a unique name.
User Action: Either use a unique activity name or the activity instance ID.

 

CWWBA0021E: Method ''{0}'' is not applicable.
Explanation: The method that is not supported by the specified object. For example, transferWorkItem() or getFaultNames() can only be called on an object that is part of a BPEL process.
User Action: Call the method on a suitable object or use a method that is supported by the object.

 

CWWBA0022E: The specified ID and correlation sets do not match.
Explanation: You specified a process instance ID or name and a message to be sent to the process instance. The process instance identified by the correlation set for the message is different to the process instance identified by the ID or name.
User Action: Either send the message to the correct object or correct the message.

 

CWWBA0023E: Cannot access a message object.
Explanation: The message contained in ClientObjectWrapper or in ProcessResponseWrapper could not be accessed.
User Action: Check the exception or the trace for the cause of the error. Perhaps the message class was not found.

 

CWWBA0024E: Creation of process instance returns ''{0}''.
Explanation: A problem occurred when creating an instance.
User Action: Check that you exported the SQL DDL for a macroflow and created the appropriate table and try again.

 

CWWBA0025E: Missing message parts.
Explanation: The message does not contain all the parts that are expected by the correlation set.
User Action: Specify the missing parts and try again.

 

CWWBA0026E: Process instance already exists.
Explanation: A process instance with the specified correlation set already exists.
User Action: Specify different correlation set values in your message and try again.

 

CWWBA0027E: Process ''{0}'' is not a macroflow.
Explanation: The requested action requires that the process is a macroflow. For example, the name of a derived process instance can only be set for a macroflow.
User Action: Prevent the cause of the error and try again.

 

CWWBA0100E: Could not create WSIFPort_Process. def=''{0}'' service=''{1}'' port=''{2}''
Explanation: A WSIF process port instance could not be created.
User Action: Make sure that the WSDL that describes the process service is correct.

 

CWWBA0101E: Method executeInputOnlyOperation() is not supported.
Explanation: The method executeInputOnlyOperation() is not supported.
User Action: Specify an output and fault message for the process service in the WSDL.

 

CWWBA0102E: Could not invoke ''{0}'' : typeSystem is not set
Explanation: The typeSystem attribute of the input extension element of the process operation in the process binding is missing.
User Action: Include the typeSystem attribute in the WSDL definition.

 

CWWBA0103E: Could not invoke ''{0}'' : typeName is not set
Explanation: The typeName attribute of the input extension element of the process operation in the process binding is missing.
User Action: Include the typeName attribute in the WSDL definition.

 

CWWBA0104E: Could not invoke ''{0}'' : Unsupported type system: ''{1}''
Explanation: The attribute typeSystem of the input extension element of the process operation in the process binding contains an unknown value.
User Action: Include a correct value for the type system attribute in the WSDL definition.

 

CWWBA0105E: A successful invocation of a synchronous process did not return an output message.
Explanation: A successful invocation of a synchronous process did not return an output message.
User Action: Correct the process so that it returns an output message.

 

CWWBA0106E: Could not invoke ''{0}'' : A system exception occurred.
Explanation: A system exception occurred during the invocation of a process.
User Action: Correct the process so that it does not cause system exceptions.

 

CWWBA0107E: Invocation of ''{0}'' failed. ProcessFaultException contains no message.
Explanation: A process ended with a fault but the fault message is empty.
User Action: Make sure that the fault raised by the process actually returns a fault message.

 

CWWBA0108E: Invocation of ''{0}'' failed. ProcessFaultException contains an unknown message type ''{1}''
Explanation: A process returned a fault message with an unknown message type.
User Action: Make sure that the WSDL describing the process defines message types for the fault messages raised by the process.

 

CWWBA0109E: Could not invoke ''{0}''
Explanation: A process template could not be invoked due to an unexpected error condition. See the exception text for more information.
User Action: Check the exception stack for more information.

 

CWWBA0110E: Could not find the operation model for the process operation.
Explanation: Could not find the operation model for the process operation.
User Action: Verify the WSDL definition of the process operation. Make sure that the names of the operation, input and output in the binding section match with the corresponding port type names.

 

CWWBA0111E: The attribute name of a fault message in the binding of a process operation has not been set.
Explanation: The attribute name of a fault message in the binding of a process operation has not been set.
User Action: Include the name attribute for every fault message in the process binding in the WSDL definition.

 

CWWBA0112E: Could not find the format type for the part ''{0}''.
Explanation: The format type of a part has not been set in the WSDL definition.
User Action: Add a typeMap entry for the respective part in the typeMapping section of the process binding.

 

CWWBA0113E: The typeMapping section is missing in the process binding.
Explanation: The typeMapping section is missing in the process binding.
User Action: Add the typeMapping section to the process binding.

 

CWWBA0114E: On-demand installation of the process template ''{0}'' failed: Could not open binary process file at location ''{1}''.
Explanation: The on-demand installation of a process template failed because a binary process file could not be found.
User Action: Make sure that the binary process file is located where required.

 

CWWBA0115E: On-demand installation of the process template ''{0}'' failed.
Explanation: The on-demand installation of a process template failed. See exception text for more information.
User Action: Make sure that the FDML referenced by the WSDL description of the process can be found. Also check the exception stack for more information.

 

CWWBA0116E: No operation named ''{0}'' with input ''{1}'' and output ''{2}'' is available in port ''{3}''.
Explanation: An operation with a particular signature (operation name, input name, output name) could not be found in a port of the process binding.
User Action: Check the FDML implementation section, and the WSDL definition to which it refers for correctness and consistency.

 

CWWBA0117E: The operation could not be completed due to an error reported by the database system.
Explanation: The database system reported an exception. See the enclosed SQL exception for details.
User Action: Check the enclosed SQL exception and the arguments passed to the called function.

 

CWWBA0118E: Verb ''{0}'' specified in the JMS request is invalid.
Explanation: A JMS request contained an invalid value in the wf$verb property.
User Action: Resend the JMS request message with a valid wf$verb property.

 

CWWBA0119E: JMS request processing will terminate because the retry limit has been exceeded.
Explanation: A JMS request was retried until the retry limit was exceeded.
User Action: Check the system log for exceptions that caused the problem. Resend the message when the problem is fixed.

 

CWWBA0120E: An exception occurred when reading the payload of the JMS request.
Explanation: An exception occurred when reading the payload of a JMS request.
User Action: Check the enclosed exception for the cause of the problem.

 

CWWBA0121E: Processing a JMS request failed.
Explanation: An exception occurred when processing a JMS request.
User Action: Check the enclosed exception for the cause of the problem.

 

CWWBA0122E: The ''{0}'' JMS request is invalid. Neither wf$piid nor wf$processInstanceName is specified.
Explanation: A JMS request that either requires wf$piid or wf$processInstanceName to be set, specified neither of these properties.
User Action: Resend the message with either the wf$piid or the wf$processInstanceName property set.

 

CWWBA0123E: The sendEvent JMS request is invalid. The wf$eventName property is not specified.
Explanation: The sendEvent JMS request requires the wf$eventName property to be specified.
User Action: Resend the message with the wf$eventName property set.

 

CWWBA0124E: The process result cannot be sent.
Explanation: A process that was started via callWithReplyContext has ended normally. Sending the process result caused an exception.
User Action: Check the enclosed exception for the cause of the problem.

 

CWWBA0125E: The exception cannot be sent.
Explanation: A process that was started via callWithReplyContext ended with a System fault exception. Sending the exception caused an exception.
User Action: Check the enclosed exception for the cause of the problem.

 

CWWBA0126E: The PIID cannot be sent.
Explanation: A JMS message requested the initiation of a process. Sending the PIID of the initiated process to the JMSReplyTo caused an exception.
User Action: Check the enclosed exception for the cause of the problem.

 

CWWBA0127E: An empty JMS reply cannot be sent.
Explanation: A JMS request message is to be answered with an empty reply message. Sending the empty reply message to the JMSReplyTo caused an exception.
User Action: Check the enclosed exception for the cause of the problem.

 

CWWBA0128E: JMSReplyTo specified by a JMS request is not an instance of javax.jms.Queue.
Explanation: A JMS API request message specifies a JMSReplyTo that is not an instance of javax.jms.Queue.
User Action: Make sure that the JMSReplyTo setting is an instance of javax.jms.Queue.

 

CWWBA0129E: An error occurred during data handling.
Explanation: A general error occurred during data handling, for example during the copying of a message.
User Action: Check the cause of the error and try again.

 

CWWBA0130E: Could not process a JMS RequestMessage because it is not of type TextMessage.
Explanation: The MQWFInteropMDB received a JMS Message that is not of type TextMessage. MQWFInteropMDB supports only TextMessages and therefore ignores this message.
User Action: Make sure that only ActivityImplInvoke Messages from WebSphere MQ Workflow are sent to the queue on which MQWFInteropMDB is listening.

 

CWWBA0131E: Could not find a Process Model with name ''{0}''.
Explanation: The MQWFInteropMDB received a JMS Message requesting to invoke an operation. The request specifies that this operation is implemented by a process model which was not found in the database.
User Action: Make sure, that WebSphere MQ Workflow is set up so that it only requests services from processes that exist.

 

CWWBA0132E: Could not find Process Name in the incoming message.
Explanation: The MQWFInteropMDB received a JMS Message that did not contain the name of the process that is to be invoked.
User Action: Make sure that only ActivityImplInvoke Messages from WebSphere MQ Workflow are sent to the queue on which MQWFInteropMDB is listening.

 

CWWBA0133E: API error: ''{0}''. Error parameter(s): ''{1}''.
Explanation: This is a general purpose message to be used when the product is in service and a new message is needed.
User Action: Check the error description and any nested exceptions to solve the problem.

 

CWWBA0134E: Unable to retrieve the expected message part ''{0}'' from the incoming message
Explanation: When an incoming message was evaluated to extract property values for correlation, a message part could not be retrieved.
User Action: Make sure that the incoming message contains the parts that are referenced in the associated property aliases of the process model.

 

CWWBA0135E: Unable to evaluate the query expression ''{0}'' on message part ''{1}''
Explanation: When a message was evaluated to extract property values for correlation, an error occurred when the query expression was evaluated.
User Action: Check the nested exceptions and make sure that the content of the message allows the query to be performed successfully. The message can either be an incoming message or a message that is stored in a variable inside the process.

 

CWWBA0136E: Part ''{0}'' of the incoming message is not of type ''{1}''
Explanation: When an incoming message was evaluated to extract property values for correlation, a message part was found with a type that is not valid. If a query expression is not specified, then the part type must match the type definition in the property alias. If a query expression is specified, then the part must be of type commonj.sdo.DataObject.
User Action: Check nested exceptions and make sure that the type of the part in the incoming message is correct.

 

CWWBA0137E: Query ''{0}'' on part ''{1}'' of the incoming message was expected to yield an object of type ''{2}'', but the result was an object of type ''{3}''
Explanation: When an incoming message was evaluated in order to extract property values for correlation, the type of the extracted object does not match the type specified in the process model.
User Action: Check nested exceptions and make sure that the type of the part in the incoming message is correct.

 

CWWBA0138E: Correlation processing found instance ''{0}'' for correlation set ''{1}'' and instance ''{2}'' for correlation set ''{3}'' when evaluating the incoming message
Explanation: When an incoming message was evaluated to extract property values for correlation, more than one process instance was found. This can happen if multiple correlation sets are contained in the message, and they do not all identify the same process instance.
User Action: Make sure that all of the correlation sets in one message refer to the same process instance.

 

CWWBA0139E: Expected type ''{0}'' and found type ''{1}'' for message ''{2}''
Explanation: When a message was evaluated to extract property values for correlation, it had the wrong type.
User Action: Make sure that the message has the correct type.

 

CWWBA0140E: No process instance found for the process template ''{0}'' and createInstance is false for port type ''{1}'' and operation ''{2}''
Explanation: An incoming request did not find an associated process instance and no receive or pick activity for this port type and operation has the createInstance attribute set to yes.
User Action: Make sure that the incoming message for this port type and operation correlates with an existing process instance.

 

CWWBA0141E: The Human Task Manager component was not found.
Explanation: The communication with the Human Task Manager component failed.
User Action: Check your installation.

 

CWWBA0142E: An exception occurred while handling a human task that is associated with object ''{0}'' in process ''{1}''.
Explanation: The Human Task Manager has thrown a task exception.
User Action: Check any nested exceptions for more information.

 

CWWBA0143E: The stored query name ''{0}'' is not unique.
Explanation: You tried to create a stored query definition but the name you specified is not unique. It is already used for a stored query in the database.
User Action: Check whether the stored query in the database defines the query you wanted to create. If not, create your stored query with a different name.

 

CWWBA0144E: Parameter ''{0}'' is not valid.
Explanation: You specified a parameter that is not valid. For example, the type of the parameter might be incorrect.
User Action: Specify the parameter correctly.

 

CWWBA0145E: Parameter list ({2}) for StoredQuery ''{0}'' and where-clause ''{1}'' is not valid.
Explanation: The number of parameter values passed for replacement in the where-clause of the named stored query do not match the expected number of parameters.
User Action: Check the where-clause of the named stored query and pass the required number of parameter values.

 

CWWBA0146E: The WebSphere Application Server UserRegistry has reported an exception.
Explanation: Either the WebSphere Application Server UserRegistry is not available for requests, or it has reported an exception. For further reasons see the nested exception.
User Action: Enable WebSphere Application Server global security. When using a CustomRegistry, ensure that it implements the deprecated getUsersForGroup method. For further actions see the nested exception.

 

CWWBA0147E: The user ''{0}'' does not exist.
Explanation: You specified an unknown user.
User Action: Check the user name or ID.

 

CWWBA0148E: Work item does not exist.
Explanation: An attempt was made to perform an action on a work item that does not exist.
User Action: Check the owner of the work item or the assignment reason.

 

CWWBA0149E: The application does not allow the requested action.
Explanation: The application that provides the context for the process does not allow the requested action. For example, you tried to set a custom property but the application does not allow the action.
User Action: No action is required.

 

CWWBA0150E: Cannot generate a join condition between ''{0}'' and ''{1}''.
Explanation: The SQL query generator has no rule to define a join condition between the views.
User Action: Modify your query and try again.

 

CWWBA0151E: Invalid parameter in query: ''{0}''.
Explanation: The SQL query generator cannot process the query because of parameters that are not valid.
User Action: Modify your query parameters and try again.

 

CWWBA0152E: A group work item cannot be created or deleted.
Explanation: An attempt was made to perform a create or delete action on a group work item.
User Action: Check the work item.

 

CWWBA0153E: An error occurred during a query: {0}.
Explanation: The query cannot be processed because of an error.
User Action: Work on the error reported by the exception and try again.

 

CWWBA0154E: An error occurred while processing the query hint ''{0}''.
Explanation: The query cannot be processed because of an error in a query hint.
User Action: Modify the query hint and try again.

 

CWWBA0155E: The query hint ''{0}'' is not valid.
Explanation: The query hint is either not valid, or not supported.
User Action: Check the query hint for errors, modify the query, and retry.

 

CWWBA0156E: The query hint ''{0}'' is not valid. The value parameter of the query hint is missing, or not valid.
Explanation: The value parameter of the query hint is either missing, or not valid.
User Action: Check the value of the query hint for errors, modify the query, and retry.

 

CWWBA0157E: The scope of the query hint ''{0}'' is not valid.
Explanation: The scope of the query hint is not valid.
User Action: Check the query hint for errors, modify the query, and retry.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009