We see this occasionally on our cluster servers also. I have updated the password via the B/A Client GUI as well as the command line. If one does not work I try the other one and is usually works. I know that does not make any sense but such is the case. Occasionally I have had to uninstall the scheduler and reinstall it.
Regards, James -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Monday, August 01, 2005 10:22 AM To: [email protected] Subject: [ADSM-L] Strange issue with a Windows server I Can't find anything with google, so I thought I'd hit the brain trust here before calling it in to IBM. We have a Windows 2000 cluster that's been working just fine for over three years -- and then the TSM service quit responding to my server (AIX, TSM 5.1.6.3). To my knowledge, there has been no change on either the Windos cluster or the TSM server -- but here's the problem report form the W2K admin: "Looking at the server this morning, it removes the password for ADSM from the registry when the service is started. I can perform an "update" which places it back in the registry, but it gets removed again once the service is started." And, from the dsmerror.log: 08/01/2005 07:32:37 Trying port number 56582 08/01/2005 07:32:37 Obtained new port number on which to listen. 08/01/2005 07:32:37 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 . 08/01/2005 07:32:37 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 . 08/01/2005 07:32:37 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 . 08/01/2005 07:32:37 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 . 08/01/2005 07:32:37 sessOpen: Error 137 from signon authentication. 08/01/2005 07:32:37 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 . 08/01/2005 07:32:38 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 . 08/01/2005 07:32:38 sessOpen: Error 137 from signon authentication. 08/01/2005 07:32:38 ANS1029E Communications have been dropped. Suggestions? Or do I give IBM a call? TIA Tom Kauffman NIBCO Inc
