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/Nodes - 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