Bill,

If you go back into the tdp gui and hit the restore tab it should prompt you
for a password.  It is due to the password being stored in the registry with
reversible encryption (something like that :)).  When you have
re-authenticated restart the service in services.

 -----Original Message-----
From:   Mayo, Bill [mailto:bemayo AT CO.PITT.NC DOT US]
Sent:   23 April 2004 23:05
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Prompted for Password every time/Scheduler exited with a
result code of 12.

I am fairly confident at this point that the problem is that the
password is not being properly updated in the registry, but I am at a
loss as to how to correct it.  The reboot did not help.  I will admit to
not completely understanding what registry it is trying to update.  I
was looking at the local registry when I mentioned observing it for
changes, but I am now thinking that it is really using the cluster
registry.

At any rate, I have used the query command to update the password, but
it just won't stick.  I feel like I must be doing something wrong, but I
don't know what.

> _____________________________________________
> From:         Mayo, Bill
> Sent: Friday, April 23, 2004 11:12 AM
> To:   'ADSM-L AT VM.MARIST DOT EDU'
> Subject:      Prompted for Password every time/Scheduler exited with a
> result code of 12.
>
> I had a working, clustered TDP Exchange scheduler.  Due to an issue, I
> had to reset the password on the node.  Since doing that, I have been
> unable to get the service to run again.  The service will start
> briefly and then stop.  The Event Log shows first a warning ID 4098
> (Error initializing TSM api, unable to verify Registry Password), and
> ends with an error ID of 4099 (Scheduler exited with a result code of
> 12).  I believe a symptom of the same problem is exhibited when I run
> the client manually.  When I do this, I am prompted for the password
> every time.
>
> I have used the UPDATEPW command to reset the password in the
> registry.  I have even deleted the registry key beforehand so that I
> can see that it is actually being created/updated (it appears to be
> working as expected).  Doing a QUERY seems to work ok as well.
>
> I have also deleted the service and recreated it.  I have been careful
> to make sure the nodename, clusternode, and clustername parameters are
> updated correctly.
>
> Am I missing something obvious here?  Any assistance gratefully
> accepted.  Thanks!
>
> ~~~~~~~~~~
> Bill Mayo
> Network Administrator
> Pitt County MIS
>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________