I started getting this on a W2k server, too, running a 5.1.5.0 client. The server had been successfully backing up since June and the scheduler was still working, just didn't work for backups. I could still run ACT=COMMAND scheduled through it. The GUI and command line would similarly fail when trying to do a backup. I ended up just upgrading to a 5.1.6.7 client version and it's working fine now. But then it was working fine before, too! :-)
The "owner" of the box said that a new application was installed right before the problems started. I thought that a common DLL or something was overlayed. We tried uninstalling the TSM services and re-instlaling them...reboots... nothing worked until I upgraded. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stephan Dinelle Sent: Friday, September 26, 2003 9:09 AM To: [EMAIL PROTECTED] Subject: TSM Scheduler service terminated unexpectedly I have the 5.1.5.0 client running locally on a W2K (SP3) server. The backup of this client is generally less than 1Gb per day, but the TSM scheduler service on that client regularly terminates unexpectedly with the following error in the W2K event log: ---------------------------------------------------------------------------- Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7031 Date: 09/26/2003 Time: 8:04:38 PM User: N/A Computer: FILESERVER Description: The TSM Scheduler service terminated unexpectedly. It has done this 22 time(s). The following corrective action will be taken in 0 milliseconds: No action. ANY IDEAS???
