You don't say how you are installing the service - are you using
dsmsvci?

I know that it is OK to have the ADSM nodename different than the ADSM
machine name, because ours are different.

But, when you install the service, the default is to create the registry
entries using the machine name.
You have to specify a different nodename for the service if you are
using a different name in dsm.opt.

Your best bet may be to stop the service, uninstall it, and go through
the install again.

        ----------
        From:   Moir,Elizabeth[SMTP:Elizabeth.Moir AT ln.ssw.abbott DOT com]
        Sent:   Tuesday, November 11, 1997 9:16 AM
        To:     ADSM-L AT vm.marist DOT edu
        Subject:        ADSM and the NT Service

        Hello ADSMers who are also NT gurus - and others as well.

        I'm having a problem installing the ADSM Scheduler as an NT
service on two of
        my NT clients using ADSM V2.  Everything seems to go along fine
until it gets
        to the point of validating the node password.  At that point
everything just
        hangs, we get a "Quincy" error message that can't be removed
with the delete
        button and no service is installed.

        I have installed the service on my own machine without any
problems and I'm
        lost as to what the next step would be.  One thing I've noticed
that might
        make a difference - my machine's name is the same as my ADSM
nodename; their
        machine names are different.

        Does anybody have any suggestions.  Thanks in advance.