Scheduled Tasks on the Notification Server show a status of "Could not start"
Last Updated January 18, 2007
The status of most Scheduled Tasks on the Notification Server Is "Could not start." All but three or four of the scheduled tasks were configured to use the same domain admin account. The "Last Run Time" for all tasks was nearly two weeks earlier when this condition was found, and the domain admin account being used did not experience a password change.
In this case, the Task Scheduler status of "Could not start" was caused by the Task Scheduler losing the password of the configured "Run as" user. The Event Viewer logs and the a.logs did not contain any information pointing to authentication or credential problems.
Reentering and then applying the same domain administrator password allows the scheduled tasks to be executed, both manually and by the configured schedule.
NOTE:: As a shortcut, Re-enter the Username and password to the NS.Weekly schedule. When you run the NS.Weekly schedule, it will re-create the rest of the Scheduled tasks with the correct access credentials.
Applies To Notification Server 6.0 SP3
Symantec Management Platform 7.x
Imported Document ID: TECH26028
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe