CWWBE0000E: Cannot create process from model ''{0}''.
Explanation: A process instance could not be created, for example, because the referenced process model is not deployed.
User Action: Determine why the process model does not exist.

 

CWWBE0001E: Uncaught exception in activity ''{0}''.
Explanation: An exception occurred during the navigation of the specified activity but the exception was not caught by the fault terminal of the activity.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0002E: Uncaught exception in process ''{0}''.
Explanation: An exception occurred during the navigation of the specified process but the exception was not caught by the fault terminal of the process.
User Action: Check the nested exception for the detail error message.

 

CWWBE0003E: An error occurred during the invocation of the activity implementation ''{0}''.
Explanation: An unexpected exception occurred during the invocation of an activity implementation.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0004E: The specified maximum number of retries for activity ''{0}'' is exceeded.
Explanation: The exit condition of the activity failed. The activity cannot be retried because the specified maximum number of retries is exceeded.
User Action: Determine why the exit condition failed. You might want to increase the maximum number of retries in your process model.

 

CWWBE0005E: An error occurred during the creation of a plug-in.
Explanation: An unexpected exception occurred during the creation of a plug-in.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0006E: An error occurred during data mapping.
Explanation: An unexpected exception occurred during data mapping.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0007E: An error occurred during the evaluation of the transition condition from source terminal ''{0}'' to target terminal ''{1}''.
Explanation: An unexpected exception occurred during the evaluation of a transition condition.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0008E: An error occurred during the evaluation of a loop condition.
Explanation: An unexpected exception occurred during the evaluation of a loop condition.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0009E: An error occurred during the evaluation of an exit condition.
Explanation: An unexpected exception occurred during the evaluation of an exit condition.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0010E: An error occurred during mapping of loop data.
Explanation: An unexpected exception occurred during data mapping from the output message to the input message of a loop.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0011E: An error occurred during the default loop mapping of a while-do loop.
Explanation: An unexpected exception occurred during the default data mapping from the input message to the output message of a while-do loop.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0012E: A wrong message instance was passed for message type ''{0}''.
Explanation: A message is passed that is not an instance of the type expected as process input message or as activity output message.
User Action: Pass a message of the defined message type.

 

CWWBE0013E: An error occurred during the event handling of ''{0}'' in the observer plug-in type ''{1}''.
Explanation: A state observer plug-in could not handle a certain event because an error occurred during the event handling.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0014E: Process model ''{0}'' is not configured to run synchronously.
Explanation: A process is invoked with "call" but the canRunSynchronous flag for the process is set to "false" or the longRunning flag to "true".
User Action: Use "sendMessage" or "initiate" to invoke the process.

 

CWWBE0015E: Process model ''{0}''is not configured to run interruptibly.
Explanation: A process is invoked with "initiate" but the canRunInterrupted or longRunning flag for the process is set to "false".
User Action: Use "sendMessage" or "call" to invoke the process.

 

CWWBE0016E: The specified maximum number of loop iterations is exceeded for activity ''{0}''.
Explanation: The loop exit condition of the activity failed but the activity cannot be repeated because the specified maximum number of iterations is exceeded.
User Action: Increase the number of iterations in your process model, or make sure that the loop exit condition is fulfilled before the maximum number of loopiterations is exceeded.

 

CWWBE0017E: No outgoing control link from fault terminal ''{0}'' of activity ''{1}''specified.
Explanation: A fault occurred but the associated fault terminal is unconnected.
User Action: Connect the fault terminal.

 

CWWBE0018E: Unknown Event for database audit: {0}.
Explanation: An unknown event name was found in the database audit extensibility element in the FDML.
User Action: Remove the incorrect event name in the FDML.

 

CWWBE0019E: Fault terminal ''{0}'' on process ''{1}'' has been navigated.
Explanation: A process is ended by navigating to a fault.
User Action: Determine the reason why the fault occurred.

 

CWWBE0020E: Process model ''{0}'' cannot run in an atomic sphere.
Explanation: A subprocess is invoked as part of a compensation sphere but the canRunSynchronous flag of the subprocess is set to "false".
User Action: The parent process model must allow the subprocess to run interrupted or the subprocess must be modified to run synchronously.

 

CWWBE0021E: The state of the object does not allow the requested action.
Explanation: The object is not in a state that allows the requested action.
User Action: Check the object state and the allowed actions.

 

CWWBE0022E: Object has wrong kind.
Explanation: Your request is not allowed for this kind of object.
User Action: Check the documentation for valid requests for this kind of object.

 

CWWBE0023E: Message object of fault terminal is null.
Explanation: The message object in a fault terminal is null.
User Action: Determine the reason why the message object is null.

 

CWWBE0024E: Fault terminal ''{0}'' does not exist for activity ''{1}''.
Explanation: An unknown fault terminal name is provided for the specified activity.
User Action: Check the fault terminals for this activity in the process model and pass a valid fault terminal name.

 

CWWBE0025E: An error occurred during the initialization of variable ''{0}''.
Explanation: An unexpected exception occurred during the initialization of a variable.
User Action: Investigate why the variable is not initialized.

 

CWWBE0026E: An error occurred during the creation of a work item.
Explanation: An unexpected exception occurred during work item creation.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0027E: No authorization for the requested action.
Explanation: You are not authorized to perform the requested action.
User Action: Check your authorization for the specified action.

 

CWWBE0028E: The API observer plug-in ''{0}'' does not allow to perform the ''{1}'' API function for entity ''{2}''.
Explanation: An API observer plug-in does not perform a certain API request.
User Action: This exception is not used.

 

CWWBE0029E: Process ''{0}'' cannot be deleted because it is a subprocess of process ''{1}''.
Explanation: Only top-level process instances can be deleted. When a top-level process instance is deleted, its sub processes are automatically deleted.
User Action: Delete the top-level process if appropriate.

 

CWWBE0030E: An error occurred during the initialization of the work item manager.
Explanation: An unexpected exception occurred during the initialization of the work item manager.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0031E: An error occurred in a data plug-in.
Explanation: An unexpected exception occurred during the execution of the isInstanceOf() or copy() method of the data plug-in.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0032E: Activity ''{0}'' cannot be completed because the user input is incomplete.
Explanation: To complete an activity, the required user input must be provided.
User Action: Provide the required user input and try again.

 

CWWBE0033E: Variable ''{0}'' does not exist.
Explanation: A variable with the specified name does not exist.
User Action: Check the name of the variable.

 

CWWBE0034E: An error occurred in the authorization plug-in.
Explanation: An exception occurred during the authorization check.
User Action: Check nested exceptions to find out the reason why the plug-in failed.

 

CWWBE0035E: An administrator cannot be determined for process ''{0}''.
Explanation: A process administrator was not determined because the corresponding staff query failed with an error or did not return a user.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0036E: The exit condition of activity ''{0}'' failed.
Explanation: The activity was not completed because the exit condition of the activity failed.
User Action: Complete the activity with an output message that meets the exit condition.

 

CWWBE0037E: Event unknown.
Explanation: A receive event with the specified event name is not waiting in the specified process instance.
User Action: Send only event requests if a receive event waits for the event.

 

CWWBE0038E: Duplicate awaited event ''{0}'' for process instance with process instance ID (PIID) ''{1}''.
Explanation: A receive event tried to register an awaited event that is already registered for this process instance.
User Action: Check the process model and remove the receive events that are waiting for the same events in parallel.

 

CWWBE0039E: Process instance name ''{0}'' is not unique.
Explanation: The process instance name already exists. The requested action requires a unique process instance name.
User Action: Use a unique process instance name.

 

CWWBE0040E: Subprocess ''{0}'' has no event that matches ''{1}''.
Explanation: An event definition is missing in the subprocess to be started.
User Action: Modify the subprocess model so that the subprocess defines an event for each event of the subprocess activity to be started. Redeploy the subprocess.

 

CWWBE0041E: Cannot run implementation ''{0}''.
Explanation: The specified implementation was not started, for example, because it was not deployed.
User Action: Check why the implementation is not found.

 

CWWBE0042E: Cannot update a read-only custom attribute.
Explanation: An attempt was made to update a custom attribute that was declared as read-only.
User Action: Avoid setting custom attributes that are marked as read-only.

 

CWWBE0043E: Process model ''{0}'' stopped.
Explanation: A process instance was not created because the referenced process model was stopped.
User Action: Start the process model and try again.

 

CWWBE0044E: A compensation sphere is required but not open.
Explanation: The 'requiresCompensationSphere' attribute of the subprocess is set to true but the top-level process does not support compensation. That is, the'requiresCompensationSphere' attribute of the top-level process is set to false.
User Action: Change your process or subprocess model.

 

CWWBE0045E: The compensation sphere for process ''{0}'' could not be completed.
Explanation: An error occurred during completion of a compensation sphere. The compensation sphere is not complete.If the 'requiresCompensationSphere' attribute is set to true, a process runs in acompensation sphere. The compensation sphere is completed when the process ends.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0046E: It is unknown whether the compensation sphere for process ''{0}'' completed or not.
Explanation: If the 'requiresCompensationSphere' attribute is set to true, a process runs in a compensation sphere.The compensation sphere is completed when the process ends. An error occurred during the completion of thiscompensation sphere. It is not known whether the compensation sphere is complete.
User Action: Check the nested exception for the detailed error message and check the state of the compensation sphere.

 

CWWBE0047E: The compensation sphere for process ''{0}'' could not be opened.
Explanation: A process runs in a compensation sphere when the 'requiresCompensationSphere' attribute is set to true. The compensation sphere could not be opened becauseof an unexpected error.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0048E: Process ''{0}'' has been compensated.
Explanation: A process runs in a compensation sphere if the 'requiresCompensationSphere' attribute is set to true. The compensation sphere for this process was rejected,that is, the process was compensated although the process did not end with a failure.
User Action: Create and execute a new process instance with the same input parameters to retry the action.

 

CWWBE0049E: The WebSphere scheduler service cannot be found.
Explanation: The session bean implementing the WebSphere Scheduler service cannot be found. It is needed if an activity is specified with a maximum duration.
User Action: Contact your WebSphere System Administrator.

 

CWWBE0050E: ''{0}'' is a wrong duration format.
Explanation: The duration is the number of seconds that must not be exceeded by the duration of the activity.
User Action: Specify a correct duration.

 

CWWBE0051E: Calendar ''{0}'' cannot be found.
Explanation: The session bean implementing the user-defined calendar cannot be found.
User Action: Contact your WebSphere System Administrator.

 

CWWBE0052E: An error occurred in the scheduler.
Explanation: An exception occurred during scheduling the maximum duration of an activity.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0053E: The mandatory parameter ''{0}'' may not be null in ''{1}''.
Explanation: An attempt was made to call an API function with a mandatory parameter value 'null'.
User Action: Specify a parameter value that is not null.

 

CWWBE0054I: An invalid message was received from the internal queue.
Explanation: The internal queue that is used for navigation of interruptible processes contains a message with invalid content. Because the internal queue must not be used by external programs, the message was ignored.
User Action: Ensure that no other program is using the internal message queue.

 

CWWBE0055E: A ReplyContext instance was received that cannot be unwrapped.
Explanation: The engine cannot unwrap a ReplyContext object that is passed in a callWithReplyContext request.
User Action: Make sure that the class file for the ReplyContext object is installed as part of the client enterprise application.

 

CWWBE0056E: Compensation is not supported for synchronous processes.
Explanation: If the 'requiresCompensationSphere' attribute of a process is set to 'true', it cannot be executed as a synchronous process.
User Action: Either execute your process as an interruptible process, or modify your process model.

 

CWWBE0057I: Activity ''{0}'' of processes ''{1}'' has been stopped because of an unhandled failure.
Explanation: If a failure occurs that cannot be handled by an activity fault terminal, (for example, a run-time exception in a transition condition) the corresponding activityis set to state stopped to allow you to manually repair the process.
User Action: Contact the process administrator to force retry or force complete the activity. Check the nested exception for details about the unhandled failure.

 

CWWBE0058I: Description of activity or process instance cannot be resolved: ''{0}''.
Explanation: This message occurs if the description of an activity or process contains replacement variables (for example, %input.name%) and the description cannot be resolved.
User Action: Correct the description string on the template object.

 

CWWBE0059I: A replacement variable in an activity or process description cannot be resolved, because it does not match the required syntax <variable-name>.<part>[<expression>]: ''{0}''
Explanation: A replacement variable cannot be resolved.
User Action: Check that the variables in the description string on the template object have the required syntax.

 

CWWBE0060E: The scope instance ''{0}'' is force terminated.
Explanation: There was a fault in an enclosing scope. This is a BPEL standard fault.
User Action: None.

 

CWWBE0061E: A fault ''{0}'' was raised by activity ''{1}''.
Explanation: An invoke or throw activity is signaling a modelled fault.
User Action: None.

 

CWWBE0062E: The partner link ''{0}'' cannot be resolved.
Explanation: The endpoint reference of the partner link cannot be resolved.
User Action: Check the partner resolution definition.

 

CWWBE0063E: The partner link ''{0}'' is not valid.
Explanation: The endpoint reference of the partner link does not match the abstract definition.
User Action: None.

 

CWWBE0064E: The join condition of activity ''{0}'' evaluated to false.
Explanation: Thrown when the join condition of an activity evaluates to false and the suppressJoinFailure attribute equals false. This is a BPELstandard fault.
User Action: None.

 

CWWBE0065E: Activity ''{0}'' and activity ''{1}'' cannot be enabled simultaneously.
Explanation: Thrown when more than one receive or pick activity are enabled simultaneously for the same port type and operation. This is a BPELstandard fault.
User Action: Correct your process model.

 

CWWBE0066E: A two-way Request for port type ''{0}'' and operation ''{1}'' was received, but there is currently a conflicting request for the same port type andoperation being processed.
Explanation: A two-way (or request - response type) request arrived for a port type and operation, but there is currently an open requestfor the same port type and operation being processed. This means, that the reply activityfor a request with the same port type and operation has not yet been executed.This is a BPEL standard fault.
User Action: Make sure that the client waits until the preceding request for the same port type and operation is finished beforerequesting a new one. If this is not feasible, then check your model, whether it ispossible to use different port types or operations for different receive or pick activities.

 

CWWBE0067E: The maximum duration of ''{0}'' is exceeded.
Explanation: The activity's maximum duration was exceeded.
User Action: None.

 

CWWBE0068E: During process execution, activity ''{0}'' tried to access an uninitialized part in variable ''{1}''.
Explanation: An attempt was made to access an uninitialized part of a variable. This is a BPEL standard fault.
User Action: Correct the process model.

 

CWWBE0069E: An error occurred during the selection of object ''{0}''.
Explanation: A selection operation performed either in a function such as bpws:getVariableData, or in an assignment, encountered an error.For example, the object might not exist. This is a BPEL standard fault.
User Action: Correct the process model.

 

CWWBE0070E: After the invocation of ''{0}'' the rollback-only flag was set.
Explanation: The navigation cannot proceed because an application has set the rollback flag.
User Action: None.

 

CWWBE0071E: A two-way request for port type ''{0}'' and operation ''{1}'' was accepted by activity ''{2}''. The process ended beforea corresponding reply activity was executed.
Explanation: No reply activity was executed for a two-way request that has been accepted by a receive or pick activity.
User Action: Correct your process model.

 

CWWBE0072E: A request for port type ''{0}'' and operation ''{1}'' was accepted without a waiting receive or pick activity.The process ended before a receive or pick activity wasactivated that could accept the request.
Explanation: A process ended before a request that was accepted by the process could be delivered to a receiveor pick activity.
User Action: Check the actions of the clients of the process.

 

CWWBE0073E: Reply activity ''{0}'' was executed for port type ''{1}'' and operation ''{2}'' and returned a fault with name ''{3}''.
Explanation: The reply activity returned an application modelled fault.
User Action: None.

 

CWWBE0074E: Correlation violation in activity ''{0}'' for correlation set ''{1}''
Explanation: The contents of the messages that were processed in an invoke, receive, or reply activity did not match the specified correlation information.
User Action: Correct the process model.

 

CWWBE0075E: Cannot access parent process context.
Explanation: The parent process context cannot be written or read.
User Action: Check for nested exceptions.

 

CWWBE0076E: An error occurred during the invocation of the undo action of activity ''{0}''.
Explanation: An unexpected exception occurred during the invocation of the undo action.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0077E: An error occurred during the evaluation of the join condition of activity ''{0}''.
Explanation: An unexpected exception occurred during the evaluation of a join condition.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0078E: An error occurred during the evaluation of the transition condition of link ''{0}''.
Explanation: An unexpected exception occurred during the evaluation of a transition condition.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0079E: An error occurred during the evaluation of a timeout expression for activity ''{0}''.
Explanation: An unexpected exception occurred during the evaluation of a timeout expression.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0080E: Reply activity ''{0}'' was navigated, but for port type ''{1}'' and operation ''{2}'' no request was pending.
Explanation: A reply activity was navigated for which no corresponding receive or pick activity had been performed.
User Action: Check that your process is modelled correctly.

 

CWWBE0081E: Cannot access JMS API context.
Explanation: The JMS API context cannot be written or read.
User Action: Check for nested exceptions.

 

CWWBE0082E: The namespace URI of fault ''{0}'' is not defined in the process.
Explanation: A qualified fault name has been passed via an API method but with a namespace URI that is not defined in the process.
User Action: Specify a correct namespace URI.

 

CWWBE0083E: The duration specified for activity ''{0}'' is invalid.
Explanation: A maximum duration has been specified for an activity but the format used is not valid for the calendar.
User Action: Specify a valid duration.

 

CWWBE0084E: EJB lookup for JNDI name ''{0}'' in application ''{1}'' failed. The EJB represents the process template ''{2}''.
Explanation: The EJB home object that represents the process template cannot be located.
User Action: Make sure that the JNDI name of the EJB representing the process template matches the given name.

 

CWWBE0085E: Incompatible types encountered during assignment to a variable or partner link ''{0}'' in activity ''{1}''.
Explanation: Incompatible types were encountered during the assignment to a variable or partner link in an assign or scriptactivity. This is a BPEL standard fault.
User Action: Correct the process model.

 

CWWBE0086E: The compensation sphere descriptor for process ''{0}'' is not valid for the given sub-process hierarchy.
Explanation: A non-autonomous child process must have a compensation sphere descriptor of 'CS_REQUIRED' or 'CS_SUPPORTS' and the descriptor must be compatible with thecompensation sphere descriptor of the top-level process. Autonomous child processes must notclaim to participate in an existing compensation sphere, that is, they must have a descriptor of'CS_NOT_SUPPORTED' or 'CS_REQUIRES_NEW'.
User Action: Make sure the compensation sphere descriptor is valid.

 

CWWBE0087E: Cannot continue navigating process ''{0}'' because the process starter ''{1}'' has been deleted.
Explanation: The user ID of the process starter must not be deleted from the User Registry as long as the process exists. This is because the userID of the process starter is used to establish the security context for the process.
User Action: Recreate the user ID of the process starter in the User Registry.

 

CWWBE0088E: An incompatible object was encountered during assignment to part ''{0}''.
Explanation: For an assignment to be valid, the types associated with the source and the target must be compatible.
User Action: Assign a compatible object.

 

CWWBE0089E: An error occurred during the evaluation of a condition associated with activity ''{0}''.
Explanation: An unexpected exception occurred during the evaluation of a while or case condition.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0090E: An attempt was made to start a process instance for template ''{0}'', but the first activity that was navigated in this process was not a receive or pick activity. Thereforethe process instance cannot be created.
Explanation: This problem can occur, for example, if an initial receive is contained in a while loop with a condition that evaluates to false in the first iteration.Initially all variables are empty. The first variable is set only after the first receiveactivity is executed. You must define loop conditions accordingly.
User Action: Correct your process model.

 

CWWBE0091E: A ReplyContext instance for process ''{0}'' cannot be deserialized.
Explanation: The engine cannot deserialize a ReplyContext object from the database that was passed with a previous request.
User Action: Make sure that the class file for the ReplyContext object is installed in the classpath of the enterprise application associated with the process.

 

CWWBE0092E: Transferring, deleting, or creating further work items is not supported when a work item for this object is assigned to 'Everybody'.
Explanation: Every authenticated user already has an assigned a work item for this object with this reason. Adding further users, transferring, or deleting a work item for a specific user is not supported.
User Action: If you want to use an explicit list of users, you must modify the process template.

 

CWWBE0093E: This is the last administrator work item and it cannot be deleted.
Explanation: If the last administrator work item were deleted, the owning object would become unusable.
User Action: Transfer the work item to another user, for example a Business Process Choreographer system administrator.

 

CWWBE0094E: This work item cannot be transferred or deleted because a process reader work item for the same user ID exists.
Explanation: Transferring or deleting an activity reader work item makes no sense if the same user ID still has a process reader work item assigned.
User Action: First transfer or delete the process reader work item, then you can transfer or delete the activity reader work item.

 

CWWBE0095E: The process instance ''{0}'' does not exist; it might have been deleted in the meantime.
Explanation: An attempt was made to perform an action on a process instance that does not exist.
User Action: Check whether the process instance still exists, for example, by refreshing your query.

 

CWWBE0096E: The activity instance ''{0}'' does not exist; it might have been deleted in the meantime.
Explanation: An attempt was made to perform an action on an activity instance that does not exist.
User Action: Check whether the activity instance still exists, for example, by refreshing your query.

 

CWWBE0097W: Business Process Choreographer entered quiesce mode and stopped normal processing
Explanation: When the Business Process Choreographer internal MDB receives a series of messages (default = 20) that cannot be processed successfully, it infers that there is an infrastructureproblem, for example, a database, a transaction log, or a JMS provider is damaged and then entersquiesce mode. In quiesce mode processing is slower because the MDB sleeps 2 seconds before itprocesses a message. As soon as a message can be processed successfully, quiesce mode is left,and the MDB continues with normal processing. Messages that fail in quiesce mode are put to theend of the Business Process Choreographer internal queue.
User Action: Check that the infrastructure that is needed by Business Process Choreographer is working correctly and fix any problems that are found. For example, if a database table is full, increasethe space for this table.

 

CWWBE0098I: Business Process Choreographer left quiesce mode and is continuing with normal processing.
Explanation: While Business Process Choreographer was in quiesce mode, a message was processed successfully. This caused Business Process Choreographer to leave quiesce mode and continue normalprocessing.
User Action: None.

 

CWWBE0099E: Cannot create a process instance using the session facade with the valid-from date {0} because this date is not active.
Explanation: Incoming requests on the specific session facades can only create or access template instances with the same valid-from date as contained in the JNDI name of the facade.To create an instance for the given valid-from date, use another facade.
User Action: Adapt the client application so that it uses the JNDI name that contains the correct valid-from date to access the session facade.

 

CWWBE0100E: Engine error: ''{0}''. Error parameter(s): {1}.
Explanation: General purpose message 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.

 

CWWBE0101E: Repeated compensation of scope ''{0}'' in process ''{1}'' .
Explanation: An attempt was made to call a compensation handler more than once.
User Action: Correct the process model.

 

CWWBE0102E: The work manager for the JNDI name ''{0}'' cannot be found.
Explanation: The recovery handler processing failed because the work manager cannot be found.
User Action: Make sure that a work manager with this JNDI name is configured and check for any nested exceptions.

 

CWWBE0103E: The user compensation scope for the JNDI name ''{0}'' cannot be found.
Explanation: The recovery handler processing failed because the user compensation scope cannot be found.
User Action: Make sure that a user compensation scope with this JNDI name is configured and check for any nested exceptions.

 

CWWBE0104E: A CScope could not be obtained from the transaction.
Explanation: The recovery handler processing failed because it could not get a CScope.
User Action: Check for nested exceptions.

 

CWWBE0105E: An unexpected error occurred during processing of the recovery handler facility.
Explanation: The recovery handler processing failed.
User Action: Check for nested exceptions.

 

CWWBE0106E: The process base class of process ''{0}'' cannot be loaded.
Explanation: The class that contains the Java snippets and Java conditions of a process is not in the current class path. This error indicates an inconsistency in your setup.
User Action: None.

 

CWWBE0107E: The compensation sphere is not valid.
Explanation: Compensation support failed due to an illegal compensation sphere nesting.
User Action: This error indicates that either the compensation sphere descriptor is invalid or the compensation sphere nesting is invalid. Invalid nesting can occur if your current process has the compensation sphere descriptor of "Supports" and you try to invoke a process with a compensation sphere descriptor of "Required". This scenario is not supported.

 

CWWBE0108E: An unexpected error occurred during processing of the compensation facility.
Explanation: Compensation processing failed.
User Action: Check for nested exceptions. Check the First Failure Data Capture tool.

 

CWWBE0109E: The specified object is not of type 'ServiceRefType'.
Explanation: BPEL specifies a 'service-ref' wrapper of type 'ServiceRefType' that wraps a partner link. When a partner link is assigned fromor to a variable, the source or target must be of type 'ServiceRefType'.
User Action: Correct the partner link assignment.

 

CWWBE0110E: An error occurred during the evaluation of a timeout expression for an event handler. Expression name ''{0}''.
Explanation: An unexpected exception occurred during the evaluation of a timeout expression.
User Action: Check the nested exception for the detailed error message.

 

CWWBE0111E: The duration specified in an onAlarm event handler for expression ''{0}'' is invalid.
Explanation: A maximum duration is specified for an onAlarm event handler but the format used is not valid for the calendar.
User Action: Specify a valid duration.

 

CWWBE0112E: The property ''{0}'' has been defined multiple times.
Explanation: Two or more properties have been defined with same name but different name spaces. For such properties, the XPath extension functions that access variableproperties are not supported.
User Action: Use different property names.

 

CWWBE0113E: A null message instance was passed for operation ''{0}''.
Explanation: A null message is passed for an operation. Since this operation has a CorrelationSet associated, it does not accept null messages.
User Action: Pass a message of the correct message type.

 

CWWBE0114E: The partner role of partner link ''{0}'' used in activity ''{1}'' is not initialized.
Explanation: An attempt was made to use the uninitialized partner role of a partner link. This is a BPEL standard fault.
User Action: Correct the process model.

 

CWWBE0115E: An unexpected error occurred during resolving a complex type or element with namespace ''{0}'' and local name ''{1}''.
Explanation: The data type of a BPEL variable cannot be obtained. Without knowing the data type, the BPEL process cannot be executed. The problem may be causedby an incomplete EAR file.
User Action: Check for nested exceptions and contact your WebSphere System Administrator.

 

CWWBE0116E: An unexpected error occurred during creation of a data object with namespace ''{0}'' and local name ''{1}''.
Explanation: An instance of a BPEL variable cannot be created. Without being able to create an instance for a BPEL variable, the BPEL process cannotbe executed. The problem may be caused by an incomplete EAR file.
User Action: Check for nested exceptions and contact your WebSphere System Administrator.

 

CWWBE0117E: An unexpected error occurred during copying a data object with namespace ''{0}'' and local name ''{1}''.
Explanation: An instance of a BPEL variable cannot be copied. Without being able to copy an instance of a BPEL variable, the BPEL process cannotbe executed. The problem may be caused by an incomplete EAR file.
User Action: Check for nested exceptions and contact your WebSphere System Administrator.

 

CWWBE0118E: The name of the activity passed as first parameter ''{0}''must match the name of the current activity ''{1}''.
Explanation: The usage of the API method is currently limitated to the current activity.
User Action: Set the first parameter to the name of the current activity and try again.

 

CWWBE0119E: The originating task for operation ''{0}'' does not match the expected task on activity ''{1}'' and process ''{2}''.
Explanation: An attempt was made to send a message to a process instance using an originating task, but the taskdefined on the receiving activity or event handler differs from the task used.
User Action: Correct your application logic.

 

CWWBE0120E: The service invoked by activity ''{0}'' threw an unchecked business fault ''{1}''.
Explanation: An unchecked business fault is a fault that is not declared in the interface of the corresponding service. An unchecked businessfault can only be caught by a catchAll BPEL fault handler.
User Action: Consider to declare the fault in the interface of your service and to catch the fault in a BPEL fault handler.

 

CWWBE0121E: Activity ''{0}'' and Event Handler starting with activity ''{1}'' cannot be enabled simultaneously.
Explanation: Thrown when more than one receive activity or equivalent are enabled simultaneously for the same port type and operation.This is a BPEL standard fault. In the currentsituation, a scope started that has an associated event handler, which implementsthe same port type and operation as an activity that is currently waiting for anincoming operation.
User Action: Correct your process model.

 

CWWBE0122E: Event Handler with start Activity ''{0}'' and activity ''{1}'' cannot be enabled simultaneously.
Explanation: Thrown when more than one receive activity or equivalent are enabled simultaneously for the same port type and operation.This is a BPEL standard fault. In thecurrent situation, a receive or pick activity becomes ready that implementsthe same port type and operation as a currently active event handler.
User Action: Correct your process model.

 

CWWBE0123E: Event Handler starting with Activity ''{0}'' and Event Handler starting with activity ''{1}'' cannot be enabled simultaneously.
Explanation: Thrown when more than one receive activity or equivalent are enabled simultaneously for the same port type and operation.This is a BPEL standard fault. In the currentsituation an event handler is being activated that implements the same port typeand operation as an event handler already active.
User Action: Correct your process model.

 

CWWBE0124E: The service invoked by activity ''{0}'' has been terminated.
Explanation: The invoked service responded with a termination exception rather than an ouput or fault message.
User Action: None.

 

CWWBE0125E: The activity instance state ''{0}'' of activity ''{1}'' defined in process template ''{2}'' does not allow to perform the requested action ''{3}''.
Explanation: The activity instance is not in a state that allows to perform the requested action.
User Action: Check the state of the activity instance.

 

CWWBE0126E: The process instance state ''{0}'' of process ''{1}'' does not allow to perform the requested action ''{2}''.
Explanation: The process instance is not in a state that allows to perform the requested action.
User Action: Check the state of the process instance.

 

CWWBE0127E: The task associated with the activity ''{0}'' defined in process template ''{1}'' does not allow to perform the requested task action.
Explanation: The task does not allow to perform the requested action.
User Action: See nested exception for more information.

 

CWWBE0128E: The task associated with process ''{0}'' does not allow to perform the requested task action.
Explanation: The task does not allow to perform the requested action.
User Action: See nested exception for more information.

 

CWWBE0129E: The task associated with an event handler on scope ''{0}'' defined in process template ''{1}'' does not allow to perform the requested task action.
Explanation: The task does not allow to perform the requested action.
User Action: See nested exception for more information.

 

CWWBE0130E: The requested action ''{0}'' is not allowed to be performed on process ''{1}''. The action is only allowed for processes build with version ''{2}'' or later.
Explanation: The action is not allowed to be performed on this process instance, because the action is a new feature and it is not supported for old process models.
User Action: Check the build version of the process template.

 

CWWBE0131E: The activity kind ''{0}'' of activity ''{1}'' defined in process template ''{2}'' does not allow to perform the requested action ''{3}''.
Explanation: The requested action is not allowed for the activity.
User Action: Check the activity kind.

 

CWWBE0132E: The requested action ''{0}'' is not allowed to be performed on process ''{1}''. This action is only allowed for top-level proceses.
Explanation: The requested action is not allowed for the process.
User Action: Check the autonomy attribute of the process.

 

CWWBE0133E: User ''{0}'' is not allowed to perform the requested action ''{1}'' on process ''{2}''.
Explanation: The requested action is not allowed for the process.
User Action: Check the staff settings of the process.

 

CWWBE0134E: User ''{0}'' is not allowed to perform the requested action ''{1}'' on activity ''{2}'' defined in process template ''{3}''.
Explanation: The requested action is not allowed for the activity.
User Action: Check the staff settings of the activity.

 

CWWBE0135E: User ''{0}'' is not allowed to perform the requested action ''{1}'' on the inbound service ''{2}'' in process ''{3}''.
Explanation: The requested action is not allowed for the inbound service.
User Action: Check the staff settings of the activity or event handler.