I'm having some problems with the TSM Scheduler service on some of my windows 2000/NT4 servers. The clients are a mix of 5.x and 4.2x.
Sometimes the service will not start at boot, and writes an event (ID 7022) stating "The TSM Scheduler service hung on starting."
Other times, we will get the following event (ID 7031):
"The TSM Scheduler service terminated unexpecetedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action."
Occasionally, when we try to start said service, it will not start and will pop up an error (ID 1067) "The process terminated unexpectedly." At this point, I can try two or three more times to start it and it will eventually start.
Any ideas? I'm getting complaints from my customers about these errors showing up in their event logs.
Thanks.
Sometimes the service will not start at boot, and writes an event (ID 7022) stating "The TSM Scheduler service hung on starting."
Other times, we will get the following event (ID 7031):
"The TSM Scheduler service terminated unexpecetedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action."
Occasionally, when we try to start said service, it will not start and will pop up an error (ID 1067) "The process terminated unexpectedly." At this point, I can try two or three more times to start it and it will eventually start.
Any ideas? I'm getting complaints from my customers about these errors showing up in their event logs.
Thanks.
