I believe he's on NT and the password is in the registry, not in a file as some OS's. I'm not even sure if you remove the TSM service(s) if that will remove the registry keys. But removing and then re-installing the service(s) will at least correct the password in the registry.
I have seen a problem if you were not specifying a NODENAME in the DSM.OPT file and the value assigned to the %COMPUTERNAME% env variable was lower-case. How it gets assigned as lower-case, I'll never know, but the encrytpion algorithm TSM uses to store the password in the registry looks like it didn't UPPER(NODENAME) first in some cases. So the scheduler would work until you ran the line command which would ask you to re-entry the password. Then the scheduler wouldn't work anymore. Also affected the CAD service. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of Ricardo Ribeiro Sent: Wednesday, November 13, 2002 2:27 PM To: [EMAIL PROTECTED] Subject: Re: Error initializing TSM Api The only thing I can think of, is to remove the password file and try the dsmc command again to create a new password file... "Gill, Geoffrey L." To: [EMAIL PROTECTED] <GEOFFREY.L.GILL cc: @SAIC.COM> Subject: Re: Error initializing TSM Api Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] T.EDU> 11/13/2002 11:57 AM Please respond to "ADSM: Dist Stor Manager" > From the command line type dcsm > then type q sch Should have mentioned I did this too. Didn't ask for anything, just returned the schedule. Stop and start the service still shows the same error. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
