A couple of other things that I have seen related to this: 1. Something could be causing the scheduler service to crash when it tries to start. You will see dsmcrash.dmp/dsmcrash.log files in your baclient dir if this is the case. 2. Check the dsmerror.log file. There could be something wrong with the node password saved in the registry and this would be indicated in the dsmerror.log. You might have to go through the setup wizard and update the client services again if this is the case. 3. Someone has configured the scheduler service to run under a specific user other than system, and that user's password has been changed, or the user was deleted. Try to start the scheduler service manually and you will get the "service could not start due to a logon failure" message.
______________________________ John Monahan Senior Consultant Enterprise Solutions Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com Timothy Hughes <[EMAIL PROTECTED] IT.STATE.NJ.US> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> ANS1977E Dsmcad schedule invocation was unsuccessful 12/01/2005 09:48 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hello, Has anyone ever had trouble staring TSM services on a windows client and received the following message in the dsmwebcl.log and Dsmerror.log shows the following. ANS1977E Dsmcad schedule invocation was unsuccessful - will try again in 10 minutes. The next backup start time/date schedule never shows up I have tried several times and no luck. TSM 5.3.2.1 AIX 5.3 RS/6000 TSM Windows clients version 5.3 Platform windows 2000 I have read a couple of Threads on this but not much there. Thanks for any help!