I opened up an ETR with IBM on this. In our environment (OS390 Server 3.1.2.20) 
it
was suggested we create archive copy pools, which we did and it seems to have
worked. At least it worked on the Novell side and seemed to work w/NT with the 
ADSM
client. However, I tried installing TSM client 3.7.1.7 last nite on an NT Server
(SP6) and got the same dr. watson errors. Went w/3.1.0.6 with no probs.

Anyone know what, if any, are the functional differences between the latest 
ADSM and
TSM versions? Readmes are virtually identical.

Andreas Boesler/bebit/LNN/DE wrote:

> Hello ADSMers,
>
> I migraded the nt-client from 3.1.0.3 to 3.1.0.8 after stopping the
> ADSM-services.
> If i remove and re-install the ADSM scheduler i get dr.watson.
> The ADSM-server is at the same system.
>
> Any ideas ?
>
> Thanks,
> Andreas.
>
> Protocol:
>
> ...
>
> The service was successfully removed.
>
> C:\ADSM\baclient>dsmcutil install /name:"ADSM Scheduler" /password:...
>
> ADSM Windows NT Client Service Configuration Utility
> Command Line Interface Version 2.00.b
> Last Updated Nov 12 1999
>
> Command: Install ADSM Client Service
> Machine: XYZ (Local Machine)
>
> Installing ADSM Client Service:
>
>        Machine          : XYZ
>        Service Name     : ADSM Scheduler
>        Client Directory : C:\ADSM\baclient
>        Automatic Start  : No
>        Logon Account    : LocalSystem
>
> 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 XYZ ....
>
> Connecting to ADSM Server via client options file 'C:\ADSM\baclient\dsm.opt' 
> ...
>
> --> dr.watson <--
>
> There are no error-messages in log-files.
>
> After starting the services "ADSM Scheduler" i get the following log-files:
>
> svcerror.log: dscsvc.c(967): GetRegistryEntries():
>               Unable to open registry entry for ADSM node'XYZ'
>
> dsmerror.log: ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 .
>               sessOpen: Error 137 from signon authentication.
>               ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2 .
>               sessOpen: Error 137 from signon authentication.
>               ANS1029E Communications have been dropped.
>
> dsmsched.log: Querying server for next scheduled event.
>               Node Name: PWAGS04
>               ANS1029E Communications have been dropped.
>               Scheduler has been stopped.

--
Jim Kirkman
Jim Kirkman
AIS UNC-Chapel Hill
966-5884