I ran/run into this on some clients. What I found is that if you don't specify the NODENAME in the DSM.OPT file and let it default to the computername of the client...you'll see this problem..IF....the value returned for the computer name is in LOWER CASE characters.
Part of my install is to do a "SET | MORE" and check the value of COMPUTERNAME. if it is in lower case chars, then I code the nodename in both the DSM.OPT file and on the DSMCUTIL command(s) that install the scheduler and client interface services. I've never opened up a PMR with Tivoli on this. The number of servers are few and far between and usually I don't have access to be able to do trouble shooting for them. I've seen this on both the 3.7 and 4.1 client levels. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of <James> <healy> Sent: Friday, November 30, 2001 4:27 PM To: [EMAIL PROTECTED] Subject: WIN2k server losing the password Has anyone seen a situation with a win2k server running v 3.7.3 where you define the TSM scheduler service and it works fine for running a scheduled backup. Then you go and run a restor thru the GUI. The next time the scheduler runs it seems like the password is lost form the registry. The client dsmsched.log has the following errors: 1/28/2001 22:24:13 Node Name: SCH1ACSFS02 11/28/2001 22:24:13 Please enter your user id <SCH1ACSFS02>: ANS1029E Communications have been dropped. 11/28/2001 22:24:13 Scheduler has been stopped. Any Ideas?
