We have had this problem on several installs, I posted the problem to
the list,
but at that time no one else had seen the problem. Basically, hit it
with a hammer
enough times an it will work. Our fixes ranged from running the update
command to
a full uninstall of ADSM, Reboot and reinstall on our most stubborn
client.
On most of our problem clients, it took several tries.
Kelly Root wrote:
>
> I have loaded client code ADSM V3.1.1 on an Win NT 4.0 server. The software
> works great. I can manually start a backup. But when I use the DSMCUTIL to
> install scheduled services I receive the following:
>
> C:\WIN32APP\IBM\ADSM3\baclient>dsmcutil install /name:'ADSM Scheduler'
> /pass:ads
> m /node:isi004 /val:yes /autostart:yes
>
> ADSM Windows NT Scheduler Service Configuration Utility
> Command Line Interface Version 1.00.d
> Last Updated 9-11-1997
>
> Command: Install and Configure ADSM Scheduler Service
> Machine: ISI004 (Local Machine)
>
> Installing ADSM Client Service:
>
>        Machine          : ISI004
>        Service Name     : ADSM Scheduler
>        Client Directory : C:\WIN32APP\IBM\ADSM3\baclient
>        Automatic Start  : Yes
>
> The service was successfully installed.
>
> Creating Registry Keys ...
>
> Updated registry value 'ImagePath' .
> Updated registry value 'EventMessageFile' .
> Updated registry value 'TypesSupported' .
> Updated registry value 'OptionsFile' .
> Updated registry value 'EventLogging' .
> Updated registry value 'ClientNodeName' .
> Updated registry value 'ADSMClientKey' .
>
> Generating registry password ...
> Authenticating password with ADSM for node ISI004 ....
>
> Unable to locate/open NLS message repository .
>
> Password Authentication failed.
>
> The Registry password wasn't updated.
>
> I get the same error when I use the DSMCUTIL UPDATE. Does anyone understand
>  what the NLS message
> repository is?