I have had this problem before. I changed the node password on the server
like you did. Then on the node from the command prompt ran
dsmcutil updatepw /node:<nodename> /password:<password>.

Hope this helps - t


 -----Original Message-----
From:   Bill Smoldt [mailto:smoldt AT STORSOL DOT COM]
Sent:   Monday, January 26, 2004 10:53 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        Re: Password cannot be authentcated

 Yiannakis,

What version of client and under what account are you starting the scheduler
service?

Try

dsmcutil showpw /node:<nodename>

You should be able to figure out the problem using that command and the
others from dsmcutil help.

Bill Smoldt
STORServer, Inc.

-----Original Message-----
From: Yiannakis Vakis [mailto:yiannakis.vakis AT ITD.BANKOFCYPRUS DOT COM]
Sent: Monday, January 26, 2004 8:25 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Password cannot be authentcated

Hi,
Somehow the TSM scheduler I have configured on a client cannot authenticate
the password set for the node.
I have stopped the scheduler, changed the password from TSM server for the
node, removed the scheduler using the client setup wizard, reinstalled it
and still get the same error.
The event viewer prompts me to look in dsierror.log:

Error Initializing TSM Api, unable to verify Registry Password, see
dsierror.log.

dsierror.log gives me the following error:
01/26/2004 17:13:38 sessOpen: Error 137 from signon authentication.

When I start-up the client BA gui I login without problems.

Any ideas ?

Yiannakis