Rick, In such a case, it will be necessary to initialize the password manually, using command line interface : you will be prompted to enter the new password at first attempt to connect to TSM server. (You may first have to set a new password on TSM server for this node, as the existing one has been machine-generated and there's no way to read it).
However this is only a temporary workaround, and you'll face the very same problem next time a new password will be generated. To my knowledge, the only way to keep the passwords syncronized in such an environment would be to use the TSM scheduler service ... HTH, just my 2 cents ! Arnaud ************************************************************************ ****** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ************************************************************************ ****** -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rick Harderwijk Sent: Monday, 27 August, 2007 09:46 To: ADSM-L@VM.MARIST.EDU Subject: ANS2050E message Hi, I just started at a new company and for the moment they are still running TSM. One of the clients on Windows 2000 Server SP4 (5.3.4.0) did not backup last night; the message I got in the errorlog was '08/27/2007 08:04:53 ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background.'. I checked the dsm.opt and confirmed that the option PASSWORDACCESS GENERATE is set. I suspect that the problem stems from the fact that the backup is started through a batchfile using the Windows Task Scheduler instead of through the TSM Scheduler service (which is not installed) for some reason not yet known to me. Am I correct in my observation and is there any workaround - as this problem will most likely come back as soon as the password expires again. Cheers, Rick Harderwijk
