Passwords not being seeded on NT?

Over the past month (maybe longer, my memory is whacked) or so, we have had an
increasing frequency of the NT server's passwords going out of sync, with no
apparent reason.

I find this in the dsmerror.log

02/09/2001 09:25:26AM ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 .
02/09/2001 09:25:26AM sessOpen: Error 137 from signon authentication.
02/09/2001 09:25:26AM cuSignOnResp: Server rejected session; result code: 53
02/09/2001 09:25:26AM ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 .
02/09/2001 09:25:26AM ANS1835E PASSWORDACCESS is GENERATE, but password needed
for server 'TSM_HQ_1'.
Either the password is not stored locally, or it was changed at the server.
02/09/2001 09:25:26AM sessOpen: Error 137 from signon authentication.
02/09/2001 09:25:26AM Authentication failure


this is in the svcerror.log

2/09 03:14:47 dscsvc.c(983): GetRegistryEntries(): Unable to open registry entry
for node'SCDATA06'


and this from the dsmsched.log

02/08/2001 03:23:49AM --- SCHEDULEREC OBJECT END COMPAQ_SERVERS 02/08/2001
02:30:00AM
02/08/2001 03:23:49AM Scheduled event 'COMPAQ_SERVERS' completed successfully.
02/08/2001 03:23:49AM Sending results for scheduled event 'COMPAQ_SERVERS'.
02/08/2001 03:23:49AM Results sent to server for scheduled event
'COMPAQ_SERVERS'.

02/08/2001 03:23:49AM ANS1483I Schedule log pruning started.
02/08/2001 03:23:50AM Schedule Log Prune: 455 lines processed.  77 lines pruned.
02/08/2001 03:23:50AM ANS1484I Schedule log pruning finished successfully.
02/08/2001 03:23:50AM Querying server for next scheduled event.
02/08/2001 03:23:50AM Node Name: SCDATA06
02/08/2001 03:23:50AM Session established with server TSM_HQ_1: AIX-RS/6000
02/08/2001 03:23:50AM   Server Version 3, Release 7, Level 4.0
02/08/2001 03:23:50AM   Server date/time: 02/08/2001 03:39:49AM  Last access:
02/08/2001 02:31:19AM

02/08/2001 03:23:50AM --- SCHEDULEREC QUERY BEGIN
02/08/2001 03:23:50AM --- SCHEDULEREC QUERY END
02/08/2001 03:23:50AM Next operation scheduled:
02/08/2001 03:23:50AM
------------------------------------------------------------
02/08/2001 03:23:50AM Schedule Name:         COMPAQ_SERVERS
02/08/2001 03:23:50AM Schedule Name:         COMPAQ_SERVERS
02/08/2001 03:23:50AM Action:                Incremental
02/08/2001 03:23:50AM Objects:
02/08/2001 03:23:50AM Options:               -ERRORLOGR=5,D -SCHEDLOGR=5,D
02/08/2001 03:23:50AM Server Window Start:   02:30:00AM on 02/09/2001
02/08/2001 03:23:50AM
------------------------------------------------------------
02/08/2001 03:23:50AM Waiting to be contacted by the server.
02/08/2001 03:23:50AM Waiting to be contacted by the server.
02/09/2001 02:14:39AM TCP/IP accepted connection from server.
02/09/2001 02:14:40AM Querying server for next scheduled event.
02/09/2001 02:14:40AM Node Name: SCDATA06
02/09/2001 02:14:41AM Please enter your user id <SCDATA06>: ANS1029E
Communications have been dropped.
02/09/2001 02:14:41AM Scheduler has been stopped.


ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2-- does this mean that it is
looking for the password, going to the path and then giving the return code of
2-- the system cannot find the file specified, i.e., the encrypted password
isn't in the registry?

(Passwordaccess is generate in the dsm.opt files, and the password at the server
has not been manually changed prior to the client accessing the server).

Since it is showing that after accessing the server, it is asking for the userid
and password, is this the action that will "seed" the password?


Why doesn't dsmcutil updatepw work anymore?  It used to be that if you resync'd
the password with the dsmcutil, it worked.  Now it seems that it may or may not
work, for a few days or not.

Has anyone else experienced this, and how did you make it go away??

thanks!!
lisa