ADSM-L

Re: Error writing registry password

2004-11-16 14:38:19
Subject: Re: Error writing registry password
From: Bill Boyer <bill.boyer AT VERIZON DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 16 Nov 2004 14:38:20 -0500
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes

then under that is the NODENAME. Under the nodename is the TSM server name.
That has the encrypted password in it.

Searching Microsoft, there is no hit for the RegCreatePathEx() API function.
and the Win32 return code 2 is "The system cannot find the file specified.
". Any errors in the event log for that server?

Searching IBM only gives APAR IC30896 that has to do with more that 50 TSM
services being installed using DSMCUTIL.

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Thomas Denier
Sent: Tuesday, November 16, 2004 1:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Error writing registry password


We have a Windows NT client running 5.1.7.0 client code that cannot
perform scheduled backups. As far as I can tell, the underlying problem
is that all attempts to write the encrypted password to the registry have
failed. Attempts to create or update the scheduler service generate
messages about errors storing the password. When the service is started
it stops almost immediately, reporting error 1067. A manually triggered
backup prompts for a password and writes the following to the client error
log:

WritePswdToRegistry(): RegCreatePathEx(): Win32 RC=2

along with a number of similar messages about problems reading the password.
The system administrator for the client has tried all of the following:

Removing and reinstalling the service
Verifying permissions on files and registry keys
Using different administrator IDs
Using different TSM passwords
Removing the client software, removing all registry keys that appeared to
 be related to TSM, and reinstalling the software

None of these have resolved the problem. Does anyone know of a fix for this
problem? Failing that, does anyone know what registry key the password is
stored in? Knowing that would enable us to undertake a more focused search
for problems with registry permissions.

<Prev in Thread] Current Thread [Next in Thread>