Re: TDP for SQL on Clustered Servers

Bill,

This could be a few things...

Usually this means that the password was never
primed in the registry to begin with. To do this,
go to the TDP for SQL directory and enter a command
that will store the CLUSTER_NODE password into the
registry.  For example:

    sqldsmc /adsmquerydb /adsmpwd:your-password

The other possibility is that the wrong option
file is being used for the scheduler.
Use the DSMCUTIL QUERY command to make sure it
is using the correct one.

If this doesn't help, please reread the appendix C
of the latest User's Guide (1.1.2) VERY closely.
Cluster setup is picky and if you do any of the steps
out of order or forget to do any of them,
it can expose itself in strange ways.

Hope this helps,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com


William R Zehnder <wzehnder AT JCPENNEY DOT COM>@VM.MARIST.EDU> on 04/06/2000
04:39:13 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  TDP for SQL on Clustered Servers



I just installed TDP for SQL Server on 2 clustered machines.  Everything
went pretty well, except I can't get my newly defined scheduler service
to retain its password.  When I entered the following under Registry
Replication -

SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\NODES\CLUSTER_NODE

it appears to work.  But when I bring the scheduler service online
through cluster administrator, it generates the follow errors on the
server -

04/06/00   14:04:29  ANR0444W Protocol error on session 4848 for node
                      CLUSTER_NODE (WinNT) - out-of-sequence verb (type
                      SignOff) received.
04/06/00   14:04:29  ANR0484W Session 4848 for node CLUSTER_NODE (WinNT)

                      terminated - protocol violation detected.

When I go into the registry and drill down to BackupClient\NODES, I
would expect to see CLUSTER_NODE listed there along with the actual
machine name.  Its not appearing there though.  The machine name is
there, but CLUSTER_NODE is not.

The client level is 3.7.1.03, TDP level is 1.1.2, server level is
3.1.2.50.

Has anyone seen anything similar to this?

--
Cordially,
Cordially,

Bill Zehnder
972-431-8733  Fax 972-531-8733