NT4 Services fail to start automatically on reboot.

[bgan]

Hi all, just wondering if you've seen this one before...



We've got a NT 4 Server with Service Pack 6 installed and TSM Client Version 4 Release 2, Level 2. The TSM Scheduler service is set to start automatically.



Often after the machine has been restarted we take a look at the Services console and find that the TSM Scheduler service has failed to start.

A manual start of the service works ok from time to time but sometimes returns the following error:



"Could not start the TSM Scheduler service on \\{machine name}.

Error 1067: The process terminated unexpectedly"

In which case it will refuse to put the TSM Scheduler service in a "started" state.



The only work-around that we've been able to figure out if this happens is to establish a session with the TSM server via the "Backup Client Command Line".

Once we perform some arbitrary task (like a "query inclexcl") in the command line, an attempt to start the TSM Client service in the Servies console will usually be successfull.



This has been perplexing us for some time now and has been the cause for missed backups in the past. Any help or suggestions would be much appreciated.



Kind regards,

Bernard.

 

[ja954]

We had the same issue. Do you happen to install the TSM CAD service as well? If so set that to "MANUAL". This cleared up our issue.

 

[iyer_sab]

You may want to check if the Scheduler service is setup to use a "Domain Account" for authentication. Using a Local System Account for the service may resolve this problem.



Thanks.

AJ [email protected]

 

[bgan]

Thanks for the responses guys but unfortunately we don't use TSM CAD, and our services are already authenticating using a Domain account.

I've heard it mentioned that this problem can sometimes occur if there are older versions of the client that haven't been cleanly uninstalled and thus leaves old registry entries. Anyone have any suggestions on a nice method for a full registry clean and client install?