Oggetto: Re: dsmcutil dr.watson nt-client 3.1.0.8
2000-03-27 07:48:22
Hi!!!
You can try find with regedit " adsm scheduler " Could be a blank in this
string. If so you must put in to " ".
I hope you have understad.!!!
Good luck
Alessio
"Andreas Boesler/bebit/LNN/DE" <aboe AT BEBIT.BUB DOT DE> il 27/03/2000 14.39.17
Per favore, rispondere a "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Per: ADSM-L AT VM.MARIST DOT EDU
Cc: (ccr: Alessio Prodon/Centro di Gestione/G-Net/IT)
Oggetto: Re: dsmcutil dr.watson nt-client 3.1.0.8
I did not find the problem, but
dsmcutil install ..... /validate:no
and starting the ADSM Scheduler Service
works fine.
Andreas.
---------------------------------------------------------------------------
------
------
Hello ADSMers,
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.
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.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Oggetto: Re: dsmcutil dr.watson nt-client 3.1.0.8,
Alessio Prodon <=
|
|
|