Kelly,
The new ADSM 32-bit client is very particular to the specifics of
the NT Service Name you have registered to run. If you are doing a
new install, make sure that 'ADSM Central Scheduler Service' is the
ADSM Client Service Name when you run the DSMCSVCI.EXE utility to
register ADSM as a true NT service. If you are doing an upgrade,
check first in ControlPanel/Services to see what is the exact name
that is registered. Run the DSMCSVCI.EXE to remove the existing
service, be sure to supply the exact name of the ADSM Scheduler
that is registered. When the removal is successful, run Install to
install the new service. This part is crucial to a successful
install, make sure the ADSM Client Service Name is 'ADSM Central
Scheduler Service', nothing else.
As to the TCP/IP problem, I could go on. However, make sure that the
DSM.OPT file is correct, pointing to the right host, etc., and is sitting in the
BACLIENT directory. The same DSM.OPT file should sit in the SACLIENT directory
too if you are running the Adminstrative client from this node. Be sure the
executable you are running is the new one. On upgrades, one could get confused
because the install does not delete the old executables and their icons. My
solutions for your TCP/IP problem assume that you have successfully registered
that particular node to your ADSM server.
Hope this helps,
==Viet==
______________________________ Reply Separator _________________________________
Subject: Re: Windows NT scheduler client running as a Service
Author: Kelly Root <kroot1 AT TUELECTRIC DOT COM> at INTERNET
Date: 11/22/96 1:59 PM
I have installed ADSM WIN-32 bit on numerous NT 4.0 workstations & servers.
Sometimes the
scheduler installs correctly and I don't have any problems and other times
I get the following errors:
getKeyHandle<>: RegOpenKeyEx: WIN RC2
RegOpenPathEX<>:KeyOpen failed
Error opening registry path 'SYSTEM\CurrentControlSet\Services\ADSM Central
Scheduler Service'
When I look in the Event Viewer I get:
Service Control Manager
The ADSM Central Scheduler Service failed to start.
The service did not respond to the start or control request in a timely
fashion.
Also when I try to run a backup manually I get a TCP/IP error. I have had
our 'TCP/IP Expert' look at the setup and he said it looks good.
Any ideas as to what I'm doing wrong?
At 07:35 AM 11/18/96 -0500, you wrote:
>Chris,
> Subsequent maintenance to the ADSM 32-bit Windows client allows it to
>run as an NT service. In fact, in the latest PTF level (2.1.05),
>there's even an icon set up to install it as a service for you. We're
>running it this way on about 20 NT servers with no problems.
>
>>----------
>>From: Chris Halstead[SMTP:halstead AT WORLDNET.ATT DOT NET]
>>Sent: Sunday, November 17, 1996 9:06 AM
>>To: Multiple recipients of list ADSM-L
>>Subject: Windows NT scheduler client running as a Service
>>
>>Hello all,
>>I'm relatively new to ADSM and was wondering if anyone out there could tell
>>me if they have run the NT client as an NT Service. We are currently running
>>ADSM on MVS to back up Netware servers, and we would like to include our NT
>>servers. The problem is starting the client automatically. We have installed
>>the client on an NT box, and it works great, except for the fact that you
>>have to manually start it. The ADSM installation guide suggests starting the
>>client at a preset time every day using NT's built-in AT scheduler, but if
>>you don't stop the client you end up with multiple instances running at once.
>> The ADSM manual states that the client cannot run as a service, but I'm not
>>sure if they mean that it will not work if set up as a service, or if they
>>mean that it isn't capable of it right out of the box. There are utilities
>>to set up an executable as a service under NT, but before I tried it I
>>thought I'd see if any one else has done it with the ADSM client.
>>
>>Thanks in advance...
>>
>>Chris Halstead, MCSE
>>Network Engineer
>>John H. Harland Co.
>>
>
>
|
