John

How Can I configure the Generic Service (Scheduler Resource) to avoid an
entire group failover if the service fails? I must configure the Exchange
Scheduler this week and the customer does not want to have more failovers.

Thanks in advance.

Henry Aranda

From: John Monahan <JMonahan AT COMPURES DOT COM>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Continuous cluster failovers configuring TDP Exchange
Scheduler
Date: Wed, 21 May 2003 22:21:29 -0500

This has happened to me a couple of times before.  Usually it was do to an
error in the dsmcutil batch files used to create the services, like a typo
in the cluster name especially.  I would uninstall the service on each
node, double check your syntax, options files, etc. and try going through
it again.  Restart the services on each node a couple of times to verify
they are working correctly before trying to add the service into the
cluster again.

You can also change the properties of that service so it doesn't cause an
entire group failover when it fails, at least until you get things working
correctly.

______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.compures.com




             Henrry Aranda
             <harango@HOTMAIL.
             COM>                                                       To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Continuous cluster failovers
                                       configuring TDP Exchange Scheduler

             05/21/2003 06:27
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Hi,
I have the following environment:
XSeries machine with Windows 2000 Server running TSM server v.4.2.1.15
attached to an IBM LTO 3583
Two Xseries machines with Windows 2000 Advanced Server running MSCS
Active/Active, Exchange 2000 Server, TSM B/A Client v.5.1.5.7 and TDP for
Exchange v.5.1.5.0

After I created the TDP for Exchange Scheduler resource in the Cluster
Administrator, I bring the resource online, but after a couple of minutes
the resource goes offline. After that the resource tries to go online five
times, It causes a cluster failover. The same situation occurs in the other
exchange virtual until the resource causes a fail back. The problem
continues repeatedly until I delete the resource.
I got the following error messages in the dsierror.log:
05/21/2003 03:22:14 sessOpen: Error 137 from signon authentication.
05/21/2003 03:22:14 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
05/21/2003 03:22:14 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
05/21/2003 03:22:34 sessOpen: Error 137 from signon authentication.
05/21/2003 03:22:34 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .
05/21/2003 03:22:34 ReadPswdFromRegistry(): getRegValue(): Win32 RC=2 .

When I check the registry I see the password for both virtual exc nodes.
I am following the installation procedure exactly. Please help me! this
cluster is really important, the customer needs to protect it.

Thanks / Regards.
Henry Aranda

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail