I haven't seen this in particular, but I've seen a lot of hosed up registry entries on NT boxes that have continuously been upgraded from v3.1 to v4.1.x and when it appears that noone ever did a full uninstall by deleting all the directories and registry keys...
----- Original Message ----- From: "brian welsh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 12:50 PM Subject: TSM Scheduler service failed to start after reboot > Hello, > > TSM Server 4.1.1 on AIX 4.3.3 > TSM Client 4.1.3 on Windows NT 4.0 SP6a (About 100 clients) > > Our NT-department have to schedule a reboot for some servers every day. > Mostly there is no problem, but now and then, during reboot the TSM > Scheduler service failed to start. The start-up of the service is automatic, > but it failed to start. We have a feeling that the TSM Scheduler service > starts too fast. Our workaround is to set the service on manual and schedule > 10 minutes after the reboot via a batchfile the start of the TSM Schedule > service. > > I was wondering if someone has experienced this before and what workarounds > are being used. > > Thanks, > > Brian. > > > > > _________________________________________________________________ > MSN Foto's is de eenvoudigste manier om je favoriete foto's te delen, te > bewerken en af te drukken. http://photos.msn.nl/Support/WorldWide.aspx
