- 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: None.
- 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: None.
- CWTKE0004E: An error occurred when loading a plug-in
- Explanation: A general error occurred during the loading of a plug-in.
- User Action: None.
- CWTKE0006I: The result of the SCA service for the originating task is null or empty.
- Explanation: A null or empty result was obtained for the SCA service for the originating task.
- User Action: Ensure that the originating task and its SCA service are deployed correctly.
- CWTKE0007I: The result of the SCA service for the originating task contains an invalid output message type.
- Explanation: The result of the SCA service for the originating task contains an invalid output message type.
- User Action: Ensure that the originating task and its SCA service are deployed correctly.
- CWTKE0008I: The result of the SCA service for the originating task contains an invalid fault message queue name.
- Explanation: The result of the SCA service for the originating task contains an invalid fault message queue name.
- User Action: Ensure that the originating task and its SCA service are deployed correctly.
- CWTKE0009I: The result of the SCA service for the originating task contains an invalid fault message type.
- Explanation: The result of the SCA service for the originating task contains an invalid fault message type.
- User Action: Ensure that the originating task and its SCA service are deployed correctly.
- CWTKE0010I: A run-time exception was received for the SCA service for the originating task.
- Explanation: A run-time exception was received for the SCA service for the originating task.
- User Action: Ensure that the originating task and its 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: HTM mail function will be disabled.
- Explanation: The HTM mail session JNDI name or a mail custom property wasn't found.The HTM mail function will be disabled.
- User Action: If not desired, verify the HTM mail configuration.
- CWTKE0013I: HTM scheduler will be disabled.
- Explanation: The WebSphere scheduler or the HTM scheduler plug-in couldn't be loaded. The HTM scheduler will be disabled.
- User Action: If not desired, verify the HTM scheduler configuration.
- CWTKE0014I: Everybody is potential owner of task {0}.
- Explanation: The staff resolution is configured such that everybody is supposed to be a potential task owner.
- User Action: If not desired, verify the staff verb definition.
- CWTKE0015W: Administrator(s) will be the potential owner(s) of the task {0}.
- Explanation: The staff resolution returns an empty potential owner list. Administrator(s) will be the potenial owner of that task.
- User Action: Verify the staff verb definition.
- CWTKE0016W: Refresh staff query daemon cannot be started.
- Explanation: The scheduler entry for the refresh staff query daemon cannot be created.
- User Action: Check possible exceptions.
- CWTKE0017W: Refresh staff query daemon cannot be updated.
- Explanation: Refresh staff query daemon cannot be updated.
- User Action: Check possible exceptions.
- CWTKE0018W: Refresh staff query daemon cannot be stopped.
- Explanation: Refresh staff query daemon cannot be stopped.
- User Action: Check possible exceptions.
- CWTKE0019I: Refresh staff query daemon has been stopped.
- Explanation: Refresh staff query Daemon has successfully been stopped.
- User Action: None.
- CWTKE0020E: An error occurred when composing the email.
- Explanation: The eMail body and/or subject could not be loaded. The eMail wasn't sent.
- User Action: Please check the escalation's email configuration of the TEL file or TaskModel.
- CWTKE0021W: Cannot refresh expired staff queries.
- Explanation: An exception occured during the refresh of expired staff queries.
- User Action: Check possible exceptions.
- CWTKE0022E: An error occurred when sending the email. Reason: {0} - Receivers: {1}
- Explanation: The eMail could not be send to the specified receivers.
- User Action: Please check the email configuration and the status of outgoing mail server.
- CWTKE0023W: The email could not be sent since no email receiver could be found.
- Explanation: There are no email receivers specified for that task or escalation.
- User Action: Please check the task, escalation or staff configuration.
- CWTKE0024W: The email could not be sent to following addresses: {0}
- Explanation: The email addresses are not valid so the email could not be sent to these receivers.
- User Action: Please check if the email addresses are valid.
- CWTKE0025I: The Staff Query Refresh Daemon will run at next at {0}
- Explanation: This shows the date when the Staff Query Refresh Daemon will run the next time.
- User Action: useraction=None.
- CWTKE0026W: Cleanup mail daemon cannot be started.
- Explanation: The cleanup mail daemon scheduler entry cannot be created.
- User Action: Check possible exceptions.
- CWTKE0027W: Cleanup mail daemon cannot be updated.
- Explanation: Cleanup mail daemon cannot be updated.
- User Action: Check possible exceptions.
- CWTKE0028W: Cleanup mail daemon cannot be stopped.
- Explanation: Cleanup mail daemon cannot be stopped.
- User Action: Check possible exceptions.
- CWTKE0029I: Cleanup mail daemon has been stopped.
- Explanation: Cleanup mail Daemon has successfully been stopped.
- User Action: None.
- CWTKE0030I: The Cleanup Mail Daemon will run at next at {0}
- Explanation: This shows the date when the Cleanup Mail Daemon will run the next time.
- User Action: useraction=None.
- CWTKE0031E: An error when calling the staff resolution.
- Explanation: An error when calling the staff resolution.
- User Action: Please check the staff configuration.
- CWTKE0032E: StaffQueryResult Post Processing Plugin could not be loaded.
- Explanation: The implementing class of the StaffQueryResult Post Processing Plugin 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: Don't disable the group work item feature as long as it is in use.
- 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=None.
- CWTKE0036I: The Staff Query Refresh Daemon has triggered {0} refresh operations.
- Explanation: This message indicates how many staff queries have been re-calculated.
- User Action: None.
- 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 passed duration/date is not valid for the calendar currently used by the scheduler.
- User Action: Check the duration value.
- CWTKE0039E: The XPath expression ''{0}'' could not be resolved. ''{1}'' is specified to be the part name. Maybe you meant ''{2}''.
- Explanation: The passed XPATH expression could not be resolved.
- User Action: Check the syntax of your XPath variable. Must be: htm:input.[partname]\\XPath or htm:output.[partname]\\XPath