I finally did get it installed by doing the following:

1) Install the 2nd scheduler service as described in the 3.1.0.7 readme file
2) Using ControlPanel/Services, stop the service you just installed
3) From the ADSM/BACLIENT dir, start an ADSM command line session with DSMC
-optfile=Q:\ADSM\DSM.OPT (where Q: is the drive in the cluster group that
holds the dsm.opt for that group)
holds the dsm.opt for that group)
4) When you get the dsmc> prompt, issue Q SESS so that you get prompted for
the cluster group node password.  After you reply, you can quit this
session.  The cluster group node will now have an entry in the Registry with
its password stored.
5) Restart the 2nd scheduler service.

I then was able to finish the rest of the installation procedure.

I did notice that the dsmerror.log has a problem in that any new entry to
the log file will delete any previous entries, then put a string of garbage
characters before the current entry.  It used to just append to the current
log file.  There was another posting to this list recently complaining about
a similar problem.

James Louie
Nabisco

> -----Original Message-----
> From: Gerard Luechinger [mailto:gluech AT osys DOT ch]
> Sent: Friday, June 11, 1999 3:23 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Error installing 2nd scheduler service
>
>
> Louie
> today I have met EXACTLY the same situation trying to install
> the 2nd sched
> service in a MS cluster environment.
> I'll do further investigations on monday. Sorry, until now I
> have no good
> tip for you.
> Maybe anyone else can help?
>
> Gerard Luechinger
> Osys AG
> IBM Business Partner, Switzerland
>
>
> > -----Ursprungliche Nachricht-----
> > Von: Louie, James [mailto:LouieJ AT NABISCO DOT COM]
> > Gesendet am: Donnerstag, 10. Juni 1999 22:47
> > Betreff: Error installing 2nd scheduler service
> >
> > I'm trying the new NT client ver 3.1.0.7 on our MS cluster
> > server and have
> > run into a problem with DSMCUTIL and adding a second
> > scheduler service.  The
> > procedure calls for installing the client node and scheduler
> > as you normally
> > would for an ordinary NT client node.  This works fine.  I
> > then need to
> > install a 2nd scheduler service running under a different
> > nodename and using
> > a dsm.opt file stored on a drive other than C:.  Here's the
> > command line I'm
> > using (modelled after the one in the readme):
> >
> > dsmcutil install /name:"ADSM Scheduler - Group 3"
> > /clientdir:c:\adsm\baclient /optfile:f:\adsm\dsm.opt
> > /node:ns_cluster_grp3
> > /password:mypasswd /validate:no /autostart:yes /startnow:yes
> >
> > The command completes and the service shows up as started in Control
> > Panel/Services, but the ADSM errorlog has the following:
> >
> > 06/10/1999 15:30:01 Obtained new port number on which to listen.
> > 06/10/1999 15:30:01 cuGetAuthResult: Authorization failed.
> > Result code: 2
> > 06/10/1999 15:30:01 sessOpen: Error 137 from signon authentication.
> > 06/10/1999 15:30:01 ReadPswdFromRegistry(): RegOpenPathEx():
> > Win32 RC=2 .
> > 06/10/1999 15:30:01 sessOpen: Error 137 from signon authentication.
> >
> > and the schedule log has:
> >
> > 06/10/1999 15:30:01 Querying server for next scheduled event.
> > 06/10/1999 15:30:01 Node Name: NS_CLUSTER_GRP3
> > 06/10/1999 15:30:01 Scheduler has been stopped.
> >
> > In the registry
> > LocalMachine/Software/IBM/ADSM/CurrentVersion/BackupClient/Nod
> > es - I see an
> > entry for the client node, but not one for NS_CLUSTER_GRP3,
> the second
> > schedule/node that I'm trying to add.
> >
> > Has anyone seen this before?
> >
> > TIA - James Louie
> > Nabisco
> > 973.682.7150
> > louiej AT nabisco DOT com
> >
>