Explanation | The Scheduler Service is started. |
Action | No user action is required. |
Explanation | The Scheduler Service has stopped and is no longer scheduling tasks. |
Action | No user action is required. |
Explanation | An unexpected error occurred. See the FFDC logs and the associated exception for details. |
Action | See the server log files for detailed exception data. |
Explanation | The data store used by this scheduler instance could not be reached. |
Action | See the server log files for detailed exception data. |
Explanation | A scheduler instance cannot be used on this server while the scheduler service is disabled. |
Action | See the documentation found under the Scheduler topic in the information center about enabling the Scheduler service. |
Explanation | The UserCalendar session bean specified by this task could not be contacted. |
Action | Verify that the session bean is available. |
Explanation | The Notification Sink session bean specified by this task could not be contacted. |
Action | Verify that the session bean is available. |
Explanation | When creating or scheduling objects, this attribute is required. |
Action | Provide the missing attribute and try again. |
Explanation | A WorkManager was specified on a Scheduler resource, however, the WorkManager with the specified JNDI name is not present. |
Action | Verify that the specified work manager exists in the global name space. If it does not exist, create it or alter the Scheduler resource to use the default WorkManager. |
Explanation | A data source was specified on a Scheduler resource, however the data source with the specified JNDI name is not present. |
Action | Verify that the specified data source exists in the global name space. If it does not exist create it or alter the Scheduler resource to use an alternate JNDI name. |
Explanation | The specified configuration information is not valid or missing. |
Action | Verify that the configuration attributes for the Scheduler resource are present and valid. Use the administrative console to verify the Scheduler resource. |
Explanation | An unexpected exception has occurred. |
Action | Check for other messages that contain exceptions further in the log. |
Explanation | The specified scheduler could not be initialized and is unable to poll for scheduled tasks. |
Action | Verify that the Scheduler resource is configured correctly and that the associated database is active. |
Explanation | A key was passed into the Messages class to resolve to a string, but a properties file for the locale could not be found and the appropriate message could not be retrieved. |
Action | Determine why the message catalog could not be found. |
Explanation | The Scheduler service has been disabled in the configuration, but will continue to run because because of service dependencies. |
Action | Re-enable the scheduler service in the configuration to avoid receiving this message in the future. |
Explanation | The Scheduler service experienced an error during initialization. The service is inaccessible on the given server. The root error should have been logged previously. |
Action | Try to resolve the previously logged errors. If unable to do so, contact IBM support. |
Explanation | The Scheduler service could not resolve the specified service, which is required for the Scheduler service. Look through the log to see if the specified service started successfully. |
Action | If you wish to use the Scheduler service, correct the problem with the specified service. If you are unable to correct the problem, contact IBM support. |
Explanation | The Scheduler Service is starting. |
Action | No user action is required. |
Explanation | The specified Scheduler instance is initializing. |
Action | No user action is required. |
Explanation | The specified Scheduler instance has initialized and is ready to accept requests. |
Action | No user action is required. |
Explanation | The specified Scheduler instance and daemon are stopping. |
Action | No user action is required. |
Explanation | The specified Scheduler instance and daemon have stopped. |
Action | No user action is required. |
Explanation | The Scheduler Service is initialized. |
Action | No user action is required. |
Explanation | The Scheduler Service has been initialized. |
Action | No user action is required. |
Explanation | The Scheduler Daemon has started for the specified Scheduler instance. |
Action | No user action is required. |
Explanation | The Scheduler Service has stopped for the specified Scheduler instance. |
Action | No user action is required. |
Explanation | The Scheduler Service is stopping. |
Action | No user action is required. |
Explanation | A scheduler resource requires a data source JNDI name, however the data source JNDI Name attribute in the configuration information for the specified scheduler resource is blank or null. |
Action | Use the administrative console to configure a data source JNDI name for the specified scheduler resource. |
Explanation | A scheduler resource requires a work manager JNDI name, however, the Work Manager JNDI name in the configuration information for the specified scheduler resource is missing. This can occur for the following reasons: The Work Manager attribute for the specified scheduler resource is blank or not configured, the configured Work Manager"s JNDI name attribute is blank or null, or the configured Work Manager cannot be found in the configuration information. |
Action | Use the administrative console to verify a Work Manager is configured for the specified scheduler resource. Also, verify the configured Work Manager"s configuration contains a valid JNDI name attribute. |
Explanation | A scheduler resource requires a JNDI name, however, the JNDI name in the configuration information for the specified scheduler resource is blank or null. |
Action | Use the administrative console to configure a JNDI name for the specified scheduler resource. |
Explanation | The configured poll interval value is not in the specified range, however, the scheduler resource is created with the specified poll interval. The poll interval value specifies the length of time in seconds the scheduler polls the database for tasks. |
Action | Use the administrative console to configure the poll interval value for the specified scheduler resource. |
Explanation | An exception occurred while retrieving the authentication alias for the data source configuration information. |
Action | Use the administrative console to verify the authentication alias for the data source is configured correctly. |
Explanation | The specified table cannot be found in the configured database for the specified scheduler resource. The possible causes are: An incorrect data source JNDI name has been configured, an incorrect table prefix has been configured, or the scheduler tables have not been created in the database. |
Action | Use the administrative console to verify the data source JNDI name and the table prefix configuration. To create the scheduler database tables, see the "Creating the database for scheduler" article in the information center. |
Explanation | The specified TaskInfo class type cannot be used because it is not of a registered type. |
Action | Modify the application to use a TaskInfo class that has a registered implementation and submit the create request again. |
Explanation | The NumberOfRepeats attribute must not be zero. |
Action | Set the NumberOfRepeats attribute to a value other than zero and submit the request again. |
Explanation | Creating a new task using a start-by time less than the start time for a non-repeating task is not a valid operation. |
Action | Modify the StartByTime, the StartTime, StartTimeInterval, or the NumberOfRepeats and submit the request again. |
Explanation | The specified InitialState value is not valid at this time. The valid values are SCHEDULED or SUSPENDED. |
Action | Set the InitialState value to either SCHEDULED or SUSPENDED and submit the request again. |
Explanation | The specified task has already run or has been cancelled and cannot be resumed. |
Action | No user action required. |
Explanation | Attempt was made to purge the task, however, the task is not in the correct state to be purged. The task must be in COMPLETE state or it must be CANCELLED. |
Action | Allow the task to run before purging or cancel the task first and then submit the purge request again. |
Explanation | The specified task has already run or has been canceled and cannot be suspended. |
Action | No user action is required. |
Explanation | The TaskInfo object could not be created because an error occurred. |
Action | See the user action for the message that contains the cause of the error. |
Explanation | An error occurred that prevented the NotificationSink object to be retreived from the task information. See the message that contains the cause of the error. |
Action | See the user action for the message that contains the cause of the error. |
Explanation | The task with specified task ID cannot be inserted into the database because the task already exists in the database. This can occur when another Scheduler inserts the same task into the database table. |
Action | No user action is required. |
Explanation | The task with the specified task ID cannot be updated in the database because it was already updated. |
Action | No user action required. |
Explanation | The task with the specified task ID cannot be updated in the database because the task record is locked by another process. This can occur when another Scheduler is updating the same task record. |
Action | No user action is required. |
Explanation | The task with the specified task ID cannot be removed from the database because it does not exist. |
Action | No user action is required. |
Explanation | The task with the specified task ID cannot be removed from the database because the task record is locked by another process. This can occur when another Scheduler is updating or removing the same task record. |
Action | No user action is required. |
Explanation | The task with the specified task ID and owner token is not in the database. |
Action | Specify another task ID and try the request again. |
Explanation | The Scheduler is attempting to run the specified task, however, the version of the task record is not supported by this scheduler. This can occur when a task is created on a later version of the Application Server and then run on an earlier version of the Application Server. |
Action | Make sure the version of the Application Server product is at the same or later version than the version of the Application Server that created the task. |
Explanation | The Scheduled task failed to run due to an unexpected error and was rolled-back. See the service log for the detailed exception stack trace. |
Action | See the message that contains the cause of the error. The task will continue to run until the problem is resolved or the task is cancelled. |
Explanation | The scheduler tried to commit the transaction, but an error occurred. The transaction is rolled back. See the message that contains the cause of the error. |
Action | See the message that contains the cause of the error. |
Explanation | The scheduler tried to roll back the transaction, but an error occurred. See the message that contains the cause of the error. |
Action | See the message that contains the cause of the error. |
Explanation | An error occurred attempting to calculate the next fire time using the default User Calendar. |
Action | See the message that contains the cause of the error. |
Explanation | An error occurred while calculating the next fire time or the start by interval. The previous message contains the cause of the error. |
Action | See the previous message for the cause of the error. |
Explanation | The scheduler attempted to run the task, but an error occurred preventing the task from running. |
Action | See the previous messages for the cause of the error. |
Explanation | Another scheduler ran or updated the task prior to this scheduler updating or running the task. The task was run or updated by another scheduler. This can occur when the two or more schedulers compete for the same tasks. |
Action | See the information center for information on reducing task collisions. |
Explanation | The Task Store object for this scheduler is null. |
Action | See previously listed error messages to determine the cause. |
Explanation | The JNDI name of the scheduler resource is the same as the scheduler resource data source JNDI name attribute. |
Action | Use the administrative console to modify either the data source JNDI name or the JNDI name of the scheduler resource. |
Explanation | The JNDI name of the specifed scheduler resource is the same as the work manager JNDI name attribute. |
Action | Use the administrative console to modify either the work manager JNDI name in the Work Manager resource or modify the JNDI name of the scheduler resource. |
Explanation | The scheduler implementation class for the specified scheduler resource is missing. An implementation class is required. |
Action | Specify a valid scheduler implementation class. |
Explanation | An error occurred which prevented the specified scheduler from acquiring a read lock for the AsynchScope. |
Action | See the message that contains the cause of the error. |
Explanation | An unexpected error occurred while the specified scheduler resource was cancelling the specified task. |
Action | See the message that contains the cause of the error. The server log files may contain additional failure details. |
Explanation | An unexpected error occurred while the specified scheduler resource was firing the specified notification event for the specified task. |
Action | See the message that contains the cause of the error. The server log files may contain additional failure details. |
Explanation | The Scheduler Service has initialized and is starting each configured Scheduler instance. |
Action | No user action required. |
Explanation | The Scheduler Service has initialized and has started each configured Scheduler instance. |
Action | No user action required. |
Explanation | The Scheduler attempted to re-run a task that previously failed due to an error. |
Action | See previous messages and the included exception for further information. Once the error is resolved, the Scheduler will attempt to re-run the failed task. |
Explanation | The Scheduler attempted to create an instance of the defined task hander EJB home, but failed to do so because of an unexcepted error. |
Action | See previous messages and the included exception for further information. Once the error is resolved, the Scheduler will attempt to re-run the failed task. |
Explanation | The Scheduler attempted to create an instance of the defined task hander EJB home, but failed to do so because of an unexcepted error. |
Action | See the message that contains the cause of the error. The server log files may contain additional failure details. |
Explanation | The Scheduler attempted to find the server, node or cell name from the URI. The URI does not contain the expected key field names server or node or cell. |
Action | Correct the URI and try your request again. |
Explanation | The Scheduler attempted to find the configuration described in the message but could not locate it. |
Action | Correct the URI and try your request again. |
Explanation | The Scheduler attempted to find the lease manager tables and they are missing. The lease manager tables must reside in the specified data source and have names that begin with the configured table prefix and end with "LMGR" and "LMPR". |
Action | See the information center for information on creating scheduler tables. |
Explanation | The Scheduler was unable to find the data source for the specified JNDI name in the message. |
Action | Verify that the specified data source exists in the configuration and it exists at the same or higher scope than the scheduler configuration. If it does not exist, create it or alter the Scheduler resource to use an existing datasource. See the information center for more information about creating data sources and modifying scheduler configurations. |
Explanation | The specified table already exists in the database. |
Action | No user action required. |
Explanation | The Scheduler tables were created in the database. |
Action | No user action required. |
Explanation | The specified index was created in the database. |
Action | No user action required. |
Explanation | The specified table cannot be dropped because it does not exist in the database. |
Action | No user action required. |
Explanation | The Scheduler tables were dropped from the database. |
Action | No user action required. |
Explanation | The specified beginning index value is larger than the specified end index value. |
Action | Modify the index values so the beginning index is smaller than the end index and submit the request again. |
Explanation | The specified beginning index value is less than 0. |
Action | Modify the beginning index value so it is equal or greater than 0 and submit the request again. |
Explanation | The specified end index value is less than 0. |
Action | Modify the end index value so it is equal or greater than 0 and submit the request again. |
Explanation | The specified end index value is less than the specified beginning index value. |
Action | Modify the index values so the beginning index is smaller than the end index and submit the request again. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The current user is not in a role that has authority to run the specified method. All Scheduler API and Mbean methods are protected by role-based security. In general, to modify scheduler tasks or scheduler runtime attributes the user must be in a operator or higher role. To view tasks or scheduler runtime attributes the user must be in a monitor or higher role. |
Action | Either login with a user id which is in the appropriate role or add this user to the appropriate role. Adding users to roles is performed using the administrative console. Please see the information center for more information. |
Explanation | The supplier of the specified task type has indicated that the specified task operation is not allowed. |
Action | Change your application so it does not call the specified operation. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An unexpected error occurred. See the FFDC logs and the associated exception for details. |
Action | See the server log files for detailed exception data. |
Explanation | The Scheduler tables were verified in the database. |
Action | No user action required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The Scheduler is attempting to run a task, but the application or module that the task was created with is not available. |
Action | Start or install the application, module or component. |
Explanation | The Scheduler is attempting to load tasks from the database, but was unable to complete due to an unexpected exception. Some tasks will fail to run until the problem is resolved. |
Action | Review the error and resolve the problem. The daemon will continue to attempt to poll the database. |
Explanation | The Scheduler is attempting to read an object from an input stream, but the object"s version number was unexpected. |
Action | This error is typically caused by a mismatch in product versions or an unexpected product error. Verify that the version of the Scheduler that logged this error is compatible with the version of the Scheduler that created the task. |
Explanation | The Scheduler is attempting to read an object from an input stream, but a field is incorrect or out of order. |
Action | This error is typically caused by a mismatch in product versions or an unexpected product error. Verify that the version of the Scheduler that logged this error is compatible with the version of the Scheduler that created the task. |
Explanation | The Scheduler is attempting to read an object from an input stream, but the object"s type number was unexpected. |
Action | This error is typically caused by a mismatch in product versions or an unexpected product error. Verify that the version of the Scheduler that logged this error is compatible with the version of the Scheduler that created the task. |
Explanation | The Scheduler is attempting to read a HomeHandle object from an input stream, but the Home is unavailable. |
Action | This error is typically caused when the application, module or EJB is not available. Review the full error to determine the cause of the problem. |
Explanation | The specified field or argument must not be null. |
Action | Change the method or object call to set the appropriate argument or verify that the field value is properly set. |
Explanation | The DayOfWeek term for the CRON calendar interval string is not in the correct range. |
Action | Update the DayOfWeek term in the calendar interval string to use a number between 1 and 7. |
Explanation | The CRON calendar interval string requires 6 terms: second minute HourOfDay DayOfMonth Month DayOfWeek |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The CRON calendar interval string requires that either the DayOfMonth or DayOfWeek is specified, but not both. |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The CRON calendar interval string requires that either the DayOfMonth or DayOfWeek is specified, but not both. |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The CRON calendar interval string allows terms with repeat values. Each repeating term type has a lower limit of 1 and an upper limit based on the term position. |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The specified CRON calendar interval string has an incorrect term at the specified position. Positions are from 1 to 6. |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The CRON calendar interval string allows terms with range values. The specified range is not of the correct syntax. |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The specified CRON calendar interval string term is formatted incorrectly and has too many tokens. |
Action | Correct the CRON calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The Scheduler uses synchronization locks to maintain consistency. The thread waiting for the lock either timed-out or was interrupted. |
Action | Try running the operation again. If the application server is shutting down at the time of the error, then no action is necessary. |
Explanation | The specified value is not numeric. |
Action | Correct the method or object call to specify a number. |
Explanation | The SIMPLE calendar interval string supports the following terms: seconds, minutes, hours, days, weeks, months and years. An incorrect term was specified. |
Action | Correct the SIMPLE calendar interval string to use the correct terms. See the API documentation for class com.ibm.websphere.scheduler.UserCalendar for details. |
Explanation | The LeaseManager tables are missing or the database is inaccessible. |
Action | Create the missing LeaseManager tables using the instructions found under the Scheduler topic in the information center and verify that the Scheduler can communicate correctly with the database. The Scheduler will continue to function without the LeaseManager tables, but performance will be decreased when using redundant or clustered Schedulers. |
Explanation | A dependent attribute was not set or was null. |
Action | Set the attribute and retry the operation. |
Explanation | The specified field or attribute is not valid. |
Action | Correct the field or attribute value with a value in the proper format or range. |
Explanation | The specified object could not be initialized. |
Action | Review the error, solve the problem and retry the operation. |
Explanation | An unexpected exception occurred while processing the specified operation. |
Action | Review the error, solve the problem and retry the operation. |
Explanation | The instance API method was called before the scheduler service was initialized. |
Action | Check the startup time values specified for the component. |
Explanation | An application attempted to modify or change a task created by another application. |
Action | Check the task ID and verify that the correct application is being used to access that task, or use the WASScheduler JMX MBean to administer the task. |
Explanation | An unexpected error occurred. See the FFDC logs and the associated exception for details. |
Action | See the server log files for detailed exception data. |
Explanation | An unexpected error occurred while starting the specified MBean. |
Action | Review the error, solve the problem and retry the operation. |
Explanation | The scheduler tables cannot be created, dropped or verified because of the specified error. |
Action | Resolve the error and try the operation again or use the supplied SQL or DDL files to create or drop your tables. See the information center for details. |
Explanation | The scheduled task has been running for a long period of time. If this behavior is by design, then no further action is necessary. When the thread completes, a WSVR0606W message is logged. |
Action | If the task is running longer than expected, then the task and thread should be examined to determine if is running properly. If the task is hung, the thread should be interrupted or the application server ended and the task should be suspended or cancelled until the problem can be resolved. |
Explanation | The scheduled task has failed multiple times consecutively and will no longer run on this application server. |
Action | Review other related error messages to determine what the problem is. Once the problem is resolve, either suspend and resume the task using the scheduler API methods, or restart this scheduler daemon. |
Explanation | The scheduler uses a lease to allow clustered scheduler servers to avoid contention. Only one scheduler instance per server may hold the lease at one time. All tasks will run on the scheduler instance who holds the lease. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The scheduler uses a lease to allow clustered scheduler servers to avoid contention. Only one scheduler instance per server may hold the lease at one time. All tasks will run on the scheduler instance who holds the lease. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | A custom property was set for the specified scheduler, but the value is not valid. This property will be ignored. |
Action | Update the custom property value to be valid. |
Explanation | The lease manager tables are required to reduce the contention between redundant or clustered schedulers. If the tables are absent, there will be a large amount of collisions. |
Action | Use the supplied DDL files to create the lease manager tables or use the createTables operation on the WASSchedulerCfgHelper MBean or administrative console to add the new tables. See the information center for details. |
Explanation | There was an error when attempting to create the specified EJB instance. See the nested exception for details on the cause of the problem. |
Action | Verify that the EJB, Application, Host and Port are available. If no longer available, cancel or suspend the task. |
Explanation | There was an error when attempting to retrieve the EJBHome instance from a HomeHandle. See the nested exception for details on the cause of the problem. |
Action | Verify that the EJB and Application are available. If no longer available, cancel or suspend the task. |
Explanation | There was an error when attempting to invoke a method using the specified EJB. See the nested exception for details on the cause of the problem. |
Action | Review the details from the nested exception stack to determine the cause of the error. |
Explanation | This message displays information about an EJB"s remote destination, which includes the remote host, port and Java Platform, Enterprise Edition component that the EJB is a member of. |
Action | No user action is required. |
Explanation | A database operation threw an SQLException. |
Action | Review the cause or chained SQLException and documentation for the database or database driver throwing the exception to resolve the problem. |
Explanation | The lease for the specified resource does not exist. Operations on a lease are only available when the lease has been acquired. |
Action | Attempt to acquire a lease before running the operation. |
Explanation | The lease has not been acquired. Operations on a lease are only available when the lease has been acquired. |
Action | Attempt to acquire a lease before running the operation. |
Explanation | The operation could not complete because the database connection is stale. |
Action | Examine database logs and other messages to determine if there is a configuration problem and retry the operation. |
Explanation | A connection to the database could not be obtained before the connection manager timed-out. |
Action | Increase the number of connections or continue to retry the operation until a connection can be retrieved. |
Explanation | The lease has been cancelled. Operations on a lease are only available when the lease has been acquired. |
Action | Attempt to acquire a lease before running the operation. |
Explanation | The component has lost the lease because it has expired. Operations on a lease are only available when the lease has been acquired. |
Action | Attempt to acquire a lease before running the operation. If the lease is already acquired by another owner, then the lease can only be forcibly acquired. |
Explanation | The lease has been disabled. Operations on a lease are only available when the lease has been acquired. |
Action | The lease must be enabled prior before the lease can be acquired or renewed. |
Explanation | A message with a chained exception was generated, but there was no chained exception. |
Action | Review the message details and stack trace for the root exception. |