Which Readme file explains the manual registry entries. I have compared
registrys with a working server and a non-working server and I don't see
any difference. But then again I am VERY NEW to the workings of NT
Registry.
At 06:47 AM 11/25/96 -0600, you wrote:
>I had the exact same problem as Kelly Root. Only one of our NT servers
>would actually update the registry from the install script. I had to
>manually edit the registry with regedit32 according to the instructions
>in the readme file. I don't know why only one NT server was able to
>do it - am not really familiar enough with NT to say what the
>differences were between our five servers. I don't think the one that
>worked was the domain controller, and I had the problem both on NT 4.0
>and NT 3.5.1 in different domains. Manually editing is not too bad
>unless you have a lot of adsm clients to install.
> Ron Clendenny <rdclendenny AT vax2.rainis DOT net>
> Callaway Nuclear Power Plant
> Fulton, Missouri
>Mike Collins wrote:
>>
>> Kelly,
>>
>> Are you running with administrative authority when this happens?
>>
>> Mike Collins
>> ADSM Development
>>
>> Kelly Root writes:
>> > 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.
>> > >>
>> > >
>> > >
>
>
|