Hello, I've seen this when upgrading from one level to another, (in my case from 4.1.x to 4.2.x). I used DSMCUTIL to remove the service, then started the client, and from utilities, installed scheduler service again, importing same opt-file, and it worked fine. I don't know if this is the case for v. 5.1.x, but it's worth a try...maybe?
Rgds. Geirr G. Halvorsen -----Original Message----- From: Boireau, Eric (MED) [mailto:[EMAIL PROTECTED]] Sent: 9. august 2002 07:35 To: [EMAIL PROTECTED] Subject: Re: 5.1.1 Windows 2000 scheduler won't start I have the same kind of issue on my Laptop with Win2K Pro and TSM 5.1.0.1 Client. It sayd that the service hangs at startup. But the service is started and run well Regards, Eric -----Original Message----- From: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Sent: Friday, August 09, 2002 3:27 AM To: [EMAIL PROTECTED] Subject: Re: 5.1.1 Windows 2000 scheduler won't start Hi Eliza: We are experiencing this on SOME of our Windows 2000 Servers. On these servers the Schedule service fails SOMETIMES on reboot. On other 2000 servers we have never had a problem. I've opened a problem with Tivoli on this (PMR 40368). The only similarity for machines that are failing that I can see (so far!) is that they are all multi-processor. We are running 5.11 clients, server is windows 2000 4.2.0. (We've just started to roll out the 5.11 client - all looked good in testing!) Tim Rushforth City of Winnipeg -----Original Message----- From: Eliza Lau [mailto:[EMAIL PROTECTED]] Sent: August 8, 2002 11:39 AM To: [EMAIL PROTECTED] Subject: 5.1.1 Windows 2000 scheduler won't start We are experiencing problems with the TSM scheduler not starting on Windows 2000 servers. A user installed TSM client 5.1.1 on a Windows 2000 server with SP2 and all hotfoxes. After the scheduler is installed, the user got the following message: An error occurred while starting the service He then pressed OK and a message box said Scheduler successfully installed When he looked at the Scheduler service, it was installed but not started. He started it manually and things worked fine from then on. The error in the event log: event 7031 The TSM scheduler service terminated unexpectedly After the machine reboots, the schedule doesn't start even though it is set to automatic. In the event log: event 7022 The TSM scheduler service hung on starting After a manual start, the scheduler works again. He can reproduce it everytime. This only happens on our Windows 2000 server machines. We have other Windows 2000 Professional machines that have no problems. server: AIX 4.3.3, TSM 4.2.1.15 client: Windows 2000 server with SP2 and all hotfixes TSM client 5.1.1 Eliza Lau Virginia Tech Computing Center 1700 Pratt Drive Blacksburg, VA 24060 [EMAIL PROTECTED]
