Stephan,

Yes, this is a message that happens quite often with Windows clients. I have 
seen that this happens when the server is rebooted overnight and upon start-up 
TSM has problems starting the TSM Scheduler service again. Under the Scheduler 
properties and the 'RECOVERY' tab, set  'First Failure: to Restart the Service' 
and 'Second Failure: to Restart the Service' as well. Sometimes it will restart 
the service automatically if it dies. It's a hit-or-miss scenario.

Regards,

Demetrius Malbrough
Tivoli Certified Consultant

   -------Original Message-------
   > From: Stephan Dinelle <SDinelle AT CANADELLE DOT COM>
   > Subject: TSM Scheduler service terminated unexpectedly
   > Sent: 26 Sep 2003 13:09:08
   >
   >  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???
   -------Original Message-------