Re: WIN2k server losing the password
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..IFthe 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 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 : ANS1029E Communications have been dropped. 11/28/2001 22:24:13 Scheduler has been stopped. Any Ideas?
Re: WIN2k server losing the password
We ran into something similar when a restore was done for NodeA on a different server Nodeb. The TSM client on Nodeb was at a higher level than that of Nodea. Tim Rushforth City of Winnipeg -Original Message- From: [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 3: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 : ANS1029E Communications have been dropped. 11/28/2001 22:24:13 Scheduler has been stopped. Any Ideas?
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 : ANS1029E Communications have been dropped. 11/28/2001 22:24:13 Scheduler has been stopped. Any Ideas?
Re: WIN2k server losing the password
James, here my ideas. *- Are you using the same tsm client machine to the restore operation? If no, the TSM Server can think that the Node client has change his IP Number and in the next client scheduler operation try to start trough the New IP Number... *- Have your tsm client machine 2 or more network card? The restore operation can be use the othe card, then the same situation... *- The option file is the same for the scheduler operation and the gui sess? If no, the TCP CLIENT ADDRESS Option can be different . Good Luck... --- Claudio Cofré Caro Ingeniero Especialista de Producto S&A Consultores - Chile Fono: +56 (2) 940-1546 Fax : +56 (2) 940-1501 Central : +56 (2) 940-1500 e-mail: [EMAIL PROTECTED] " " To: [EMAIL PROTECTED] Sent by: cc: "ADSM: Dist Subject: WIN2k server losing the password Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 30-11-01 17:27 Please respond to "ADSM: Dist Stor Manager" 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 : ANS1029E Communications have been dropped. 11/28/2001 22:24:13 Scheduler has been stopped. Any Ideas?
