WebSphere Process Server messages     Operating Systems: All supported
CWTKE0001E: An error occurred when setting up the scheduler.
Explanation: An unexpected exception occurred during the set up of the scheduling for escalations.
User Action: No action is required.

 

CWTKE0002E: An error occurred when setting up the mail environment.
Explanation: An unexpected exception occurred during the set up of the mail environment or when mail was sent.
User Action: No action is required.

 

CWTKE0004E: An error occurred when loading a plug-in
Explanation: A general error occurred during the loading of a plug-in.
User Action: No action is required.

 

CWTKE0006I: The result of the Service Component Architecture (SCA) service for the invocation task (originating task) is null or empty.
Explanation: A null or empty result was obtained for the SCA service associated to the invocation task (originating task).
User Action: Ensure that the invocation task and its associated SCA service are deployed correctly.

 

CWTKE0007I: The result of the Service Component Architecture (SCA) service for the invocation task (originating task) contains an invalid output message type.
Explanation: The result of the SCA service for the invocation task (originating task) contains an invalid output message type.
User Action: Ensure that the invocation task (originating task) and its associated SCA service are deployed correctly.

 

CWTKE0008I: The result of the Service Component Architecture (SCA) service for the invocation task (originating task) contains an invalid fault message queue name.
Explanation: The result of the SCA service for the invocation task (originating task) contains an invalid fault message queue name.
User Action: Ensure that the invocation task (originating task) and its associated SCA service are deployed correctly.

 

CWTKE0009I: The result of the Service Component Architecture (SCA) service for the invocation task (originating task) contains an invalid fault message type.
Explanation: The result of the SCA service for the invocation task (originating task) contains an invalid fault message type.
User Action: Ensure that the invocation task (originating task) and its associated SCA service are deployed correctly.

 

CWTKE0010I: A run-time exception was received for the Service Component Architecture (SCA) service and the invocation task (originating task).
Explanation: A run-time exception was received for the SCA service and the invocation task (originating task).
User Action: Ensure that the invocation task (originating task) and its associated SCA service are deployed correctly.

 

CWTKE0011E: Task exception ''{0}'' has occurred. Information parameters: {1}.
Explanation: This is a general purpose exception that is used when the product is in service and a new exception is needed.
User Action: See the exception message for details.

 

CWTKE0012I: The Human Task Manager (HTM) mail function will be disabled.
Explanation: The HTM mail session JNDI name or a mail custom property was not found. The HTM mail function will be disabled.
User Action: If you do not want the HTM mail function to be disabled, verify the HTM mail configuration.

 

CWTKE0013I: The Human Task Manager (HTM) scheduler will be disabled.
Explanation: The WebSphere scheduler or the HTM scheduler plug-in could not be loaded. The HTM scheduler will be disabled.
User Action: If you do not want the HTM scheduler to be disabled, verify the HTM scheduler configuration.

 

CWTKE0014I: Everybody is potential owner of task {0}.
Explanation: The people (staff) resolution default is that everybody becomes a potential task owner.
User Action: If this is not intended, verify the people assignment criteria (staff verb).

 

CWTKE0015W: Administrator(s) will be the potential owner(s) of the task {0}.
Explanation: The people (staff) resolution returned an empty potential owner list. Administrator(s) will be the potential owners of that task.
User Action: Verify the people assignment criteria (staff verb).

 

CWTKE0016W: The people (staff) assignment refresh daemon cannot be started.
Explanation: The scheduler entry for the people (staff) assignment refresh daemon cannot be created.
User Action: Check the log for any exceptions.

 

CWTKE0017W: The people (staff) assignment refresh daemon cannot be updated.
Explanation: The people (staff) assignment refresh daemon cannot be updated.
User Action: Check the log for any exceptions.

 

CWTKE0018W: The people (staff) assignment refresh daemon cannot be stopped.
Explanation: The people (staff) assignment refresh daemon cannot be stopped.
User Action: Check the log for any exceptions.

 

CWTKE0019I: The people (staff) assignment refresh daemon has been stopped.
Explanation: The people (staff) assignment refresh daemon has successfully been stopped.
User Action: No action is required.

 

CWTKE0020E: An error occurred when composing the e-mail.
Explanation: The e-mail body, subject, or both could not be loaded. The e-mail was not sent.
User Action: Check the escalation's e-mail configuration of the TEL file or TaskModel.

 

CWTKE0021W: Cannot refresh expired people assignment (staff query result).
Explanation: An exception occurred while refreshing the expired people assignments (staff query results).
User Action: Check the log for any exceptions.

 

CWTKE0022E: An error occurred when sending the e-mail. Reason: {0} - Receivers: {1}
Explanation: The e-mail could not be send to the specified receivers.
User Action: Check the e-mail configuration and the status of the outgoing mail server.

 

CWTKE0023W: The e-mail could not be sent because no e-mail receiver could be found.
Explanation: There are no e-mail receivers specified for the escalation.
User Action: Check the escalation people (staff) assignment, or the people (staff) resolution configuration.

 

CWTKE0024W: The e-mail could not be sent to following addresses: {0}
Explanation: The e-mail addresses are not valid so the e-mail could not be sent to the recipients.
User Action: Make sure that the e-mail addresses are valid.

 

CWTKE0025I: The people assignment refresh daemon (staff query refresh daemon) will run next at {0}
Explanation: This shows the date when the people assignment refresh daemon (staff query refresh daemon) will next run.
User Action: useraction=No action is required.

 

CWTKE0026W: The cleanup mail daemon cannot be started.
Explanation: The cleanup mail daemon scheduler entry cannot be created.
User Action: Check the log for any exceptions.

 

CWTKE0027W: The cleanup mail daemon cannot be updated.
Explanation: The cleanup mail daemon cannot be updated.
User Action: Check the log for any exceptions.

 

CWTKE0028W: The cleanup mail daemon cannot be stopped.
Explanation: The cleanup mail daemon cannot be stopped.
User Action: Check the log for any exceptions.

 

CWTKE0029I: The cleanup mail daemon has been stopped.
Explanation: The cleanup mail Daemon has successfully been stopped.
User Action: No action is required.

 

CWTKE0030I: The Cleanup Mail Daemon will next run at {0}
Explanation: This shows the date when the Cleanup Mail Daemon will next run.
User Action: useraction=No action is required.

 

CWTKE0031E: An error occurred during people (staff) resolution.
Explanation: An error occurred during people (staff) resolution.
User Action: Check the people (staff) resolution configuration.

 

CWTKE0032E: The StaffQueryResultPostProcessorPlugin implementation could not be loaded.
Explanation: The implementing class of the people assignment (staff query result) post-processor plug-in could not be found.
User Action: Check the corresponding custom property and your classpath.

 

CWTKE0033W: The database contains group work items. If you disable the group work item feature, they will not work anymore.
Explanation: Authorization using group work items requires that the group work item feature is enabled. If you disable the feature, some users might lose their authorization for certain actions.
User Action: Do not disable the group work item feature while it is still used.

 

CWTKE0034W: The context variable {0} points to an instance of a DataObject. It should point to a leaf of a DataObject instance.
Explanation: The context variable points to an instance of a DataObject. It should point to a leaf of a DataObject instance that has a proper toString() implementation.
User Action: Check the name (definition) of the context variable.

 

CWTKE0035I: The action {0} has been vetoed.
Explanation: The action was rejected by the custom API Event handler.
User Action: useraction=No action is required.

 

CWTKE0036I: The people assignment refresh daemon (staff query refresh daemon) has triggered {0} refresh operations.
Explanation: This message indicates how many people assignments (staff query results) have been re-calculated.
User Action: No action is required.

 

CWTKE0037E: The "Duration Until Deletion" ({0}) for task {1} is not valid.
Explanation: The specified duration until task is to be deleted is not valid. The value "DURATION_INFINITE" is assumed.
User Action: Check the "Duration Until Deletion" value.

 

CWTKE0038E: The duration ''{0}'' is not valid for the scheduler.
Explanation: The duration, or date is not valid for the calendar currently used by the scheduler.
User Action: Check the duration value.

 

CWTKE0039E: The XPath expression ''{0}'' cannot be resolved. ''{1}'' is specified to be the part name. Perhaps you meant ''{2}''.
Explanation: The XPATH expression passed could not be resolved.
User Action: Check the syntax of your XPath variable. It must be: htm:input.[partname]\\XPath or htm:input.partname[\\XPath] or htm:output.[partname]\\XPath or htm:output.partname[\\XPath] .

 

CWTKE0040W: The task priority definition ''{0}'' could not be resolved: {1}. The default priority is assigned.
Explanation: The task "priority definition" contains a non-numeric value, a value less then zero or a variable that cannot be resolved.
User Action: Check the content of the "priority definition" field.

 

CWTKE0041E: The plug-in class ''{0}'' does not implement the interface ''{1}''.
Explanation: The plug-in implementation does not implement the required interface.
User Action: Specify a plug-in class that implements the required interface.

 

CWTKE0042E: EngineGetTypeError message when working on a task associated with application ''{0}''.
Explanation: Some required types or elements are not on the application's classpath.
User Action: Check which application name you specified when creating the task. Check for a deployed enterprise application with that name. Check whether this application contains the complex types or elements that were not found.

 

CWTKE0043W: Administrator(s) will be the escalation receiver(s) of the escalation {0}.
Explanation: The people (staff) resolution returned an empty escalation receiver list. Administrator(s) will receive that escalation.
User Action: Verify the people assignment criteria (staff verb).

 

CWTKE0044I: Originator becomes administrator of task {0}. Usually this happens, because no people assignment criteria is defined for the administrators of the task, or because its usage returns an empty set of users.
Explanation: Because no administrator could not be found, the task's originator will also be the task's administrator. This can occur, when either the task's people assignment criteria (staff verb) for administrator returns an empty set of users, or when this people assignment criteria is not defined.
User Action: If this is not what you want, check the people assignment criteria (staff verb): Maybe the people assignment criteria need to be changed, or you need to define a people assignment for the administrators of the task.

 

CWTKE0045I: Everybody is potential starter of task {0}. Usually this happens, because no people assignment criteria is defined for the potential starters of the task, or because its usage returns an empty set of users.
Explanation: Because no potential starter could not be found, everybody will be a potential starter of the task. This can occur, when either the task's people assignment criteria (staff verb) for potential starters returns an empty set of users, or when this people assignment criteria is not defined.
User Action: If this is not what you want, check the people assignment criteria (staff verb): Maybe the people assignment criteria need to be changed, or you need to define a people assignment for the potential starters of the task.

 

CWTKE0046I: Originator becomes potential starter of task {0}. Usually this happens, because no people assignment criteria is defined for the potential starters of the task, or because its usage returns an empty set of users.
Explanation: Because no potential starter could not be found, the task's originator will also be a potential starter of the task. This can occur, when either the task's people assignment criteria (staff verb) for potential starters returns an empty set of users, or when this people assignment criteria is not defined.
User Action: If this is not what you want, check the people assignment criteria (staff verb): Maybe the people assignment criteria need to be changed, or you need to define a people assignment for the potential starters of the task.

 

CWTKE0047I: Everybody is potential instance creator for task {0}. Usually this happens, because no people assignment criteria is defined for the potential instance creators of the task, or because its usage returns an empty set of users.
Explanation: Because no potential instance creator could not be found, everybody will be a potential instance creator of the task. This can occur, when either the task's people assignment criteria (staff verb) for potential instance creator returns an empty set of users, or when this people assignment criteria is not defined.
User Action: If this is not what you want, check the people assignment criteria (staff verb): Maybe the people assignment criteria need to be changed, or you need to define a people assignment for the potential instance creator of the task.

 

CWTKE0048I: Process starter becomes process administrator for process {0}. Usually this happens, no admin administration task has been defined for the process, or because no people assignment criteria is defined for the administration task of the process, or because its usage returns an empty set of users.
Explanation: Because no process administrator has been configured, the process starter will also be the process administrator.
User Action: If this is not what you want, check the people assignment criteria (staff verb).

 

CWTKE0049I: People substitution was enabled successfully. Ensure that the Virtual Member Manager (VMM) repository that hosts the user substitution attributes is available.
Explanation: The people substitution is enabled.
User Action: No action is required.

 

CWTKE0050W: The following users have no e-mail address configured: {0}
Explanation: There seems to be some users with no e-mail address configured. The e-mail address is required for processing.
User Action: Check the user e-mail configuration in the people directory (staff repository).

 

CWTKE0051W: Could not retrieve the user registry from the JNDI. Possible cause: Application security is not enabled for the WebSphere Application Server. Application security must be enabled for business processes with human tasks.
Explanation: WebSphere Application Server security must be enabled for business processes with human tasks.
User Action: Enable WebSphere Application Server application security.

 

CWTKE0052W: Cannot send escalation e-mails to one or more administrators because the administrator work item is not of type user.
Explanation: The administrator work item is either a group work item or an everybody work item. E-mails can only be sent to dedicated users.
User Action: Make sure that the escalation receiver people assignment criteria (staff verb) can resolve e-mail addresses.

 

CWTKE0053I: A custom scheduler plug-in has been loaded for the Human Task Manager.
Explanation: The custom scheduler plug-in will be used by the Human Task Manager to schedule task and escalation events. Note: This is not a public interface, but just for JUnit. You should implement a WebSphere custom calendar instead.
User Action: No action is required.

 

CWTKE0054I: The group work item feature is enabled.
Explanation: A group ID query can be deployed.
User Action: No action is required.

 

CWTKE0055I: The group work item feature is not enabled.
Explanation: A group ID query cannot be deployed.
User Action: No action is required.

 

CWTKE0056I: People substitution is not enabled.
Explanation: People substitution cannot be used.
User Action: No action is required.

 

CWTKE0057I: Outputting people (staff) resolution diagnosis messages is enabled.
Explanation: When the Human Task Manager default people (staff) assignment is performed, it will be logged.
User Action: No action is required.

 

CWTKE0058I: The Virtual Member Manager (VMM) entity type ''{0}'' has been augmented by the property ''{1}'' of type ''{2}''.
Explanation: The VMM entity type has been augmented by a required attribute.
User Action: No action is required.

 

CWTKE0059E: The Virtual Member Manager (VMM) entity could not be found, received VMM message is ''{0}''.
Explanation: The VMM entity could not be found.
User Action: Check the VMM invocation parameters and the people directory content.

 

CWTKE0060E: Attribute ''{0}'' contains an invalid value: ''{2}''. Valid values are: {1}.
Explanation: An invalid attribute value was found.
User Action: Check the people (staff) query elements in the human task model and the people assignment criteria (staff verb) mapping XSLT stylesheets for errors.

 

CWTKE0061E: The Virtual Member Manager (VMM) search expression ''{0}'' could not be applied, the message received from VMM is ''{1}''.
Explanation: The VMM search expression could not be applied to perform a VMM search operation.
User Action: Correct the search expression.

 

CWTKE0062W: Virtual Member Manager (VMM) entity ''{0}'' has no attribute with the name ''{1}'' and type ''{2}''.
Explanation: A VMM entity does not contain the requested attribute.
User Action: Check that the entity has the requested attribute of the requested type.

 

CWTKE0063W: The Virtual Member Manager (VMM) invocation returned no result entities.
Explanation: The VMM invocation returned no result entities.
User Action: The result may be correct, otherwise check the VMM invocation parameters and the people directory content.

 

CWTKE0064E: The Virtual Member Manager entity ''{0}'' does not have an attribute with the name ''{1}'' of type ''{2}''.
Explanation: The Virtual Member Manager entity does not contain the specified attribute.
User Action: Make sure that the entity has an attribute of the specified name and type.

 

CWTKE0065E: The property ''{0}'' of type ''{1}'' is not defined for Virtual Member Manager (VMM) entity type ''{2}''.
Explanation: The property is not defined for the VMM entity type.
User Action: Check the VMM entity type definition and add the property.

 

CWTKE0066E: The property ''{0}'' of type ''{1}'' could not be added to Virtual Member Manager (VMM) entity type ''{2}''.
Explanation: A property could not be added to a VMM entity type.
User Action: Check the VMM configuration for correctness.

 

CWTKE0067E: The properties ''{0}'' could not be modified for the Virtual Member Manager (VMM) entity ''{1}''.
Explanation: Some properties could not be modified for a VMM entity. Possible reasons are: (a) the properties are not configured for the VMM Property Extension Repository, nor supported by a user repository that is used by VMM. (b) the properties are configured for the VMM Property Extension Repository, but the repository is not accessible. (c) the properties are configured for a user repository that is used by VMM, but the repository is not accessible.
User Action: Check the possible reasons and correct them.

 

CWTKE0068E: Virtual Member Manager (VMM) access error: {0}
Explanation: An error occurred while accessing VMM.
User Action: Check the explanation.

 

CWTKE0069W: Virtual Member Manager (Federated repositories) is not configured for Websphere security.
Explanation: Virtual Member Manager (VMM) is not configured for Websphere security.
User Action: Configure VMM (Federated repositories) for Websphere security.

 

CWTKE0070W: The Websphere security setting for using domain qualified user names must be disabled for the Human Task Manager (HTM) to work properly.
Explanation: The Websphere security setting for using user names with a domain qualifier must be disabled for HTM to work properly. Queries for task and work item lists are not guaranteed to yield correct results.
User Action: Disable the Websphere security setting for using domain qualified user names.

 

CWTKE0071E: While evaluating a Human Task Manager (HTM) variable, the following problem occurred: {0}
Explanation: The variable expression passed could not be resolved.
User Action: Check the syntax of your variable expression. It must be: htm:input.[partname]\\XPath or htm:input.partname[\\XPath] or htm:output.[partname]\\XPath or htm:output.partname[\\XPath] .

 

CWTKE0072E: The parent process context cannot be accessed.
Explanation: The parent process context cannot be read.
User Action: See the nested exceptions for more information.

 

CWTKE0073I: The people assignment refresh daemon (staff query refresh daemon) has completed {0} of {1} refresh operations.
Explanation: This message indicates how many people assignments (staff query results) have been recalculated.
User Action: No action is required.

 

CWTKE0074E: Another instance of RefreshStaffQueryMessage is still refreshing staff queries.
Explanation: This message indicates that another thread is already refreshing staff query results.
User Action: Stop the other thread by clicking the Stop Running Refresh Staff Queries button in the administrative console.

 

CWTKE0075E: The "Duration Until Resumes" ({0}) for the {1} task is not valid.
Explanation: The specified duration until the suspended task resumes is not valid. The value "DURATION_INFINITE" is assumed.
User Action: Check the "Duration Until Resumes" value.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009