Trying to Move Group - SQL Instance Won't Start

#1

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#2

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#3

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#4

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#5

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#6

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#7

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#8

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#9

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks

#10

Are you running theses instances with domain account that does not have the
appropriate privileges on the other nodes?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

<edsmith (AT) pascocountyfl (DOT) net> wrote

Server Environment:
N + 1 (Four Nodes), IBM X-Series, 32-bit, 4 processors, 16 GB RAM
SQL 2000, SP4 with hotfixes, AWE and PAE configured

The SQL cluster was originally built with 2 nodes (node-B is the
passive failover node). Months later we added nodes C & D. Nodes A,
C and D each have two SQL instances assigned and all failover to node
B. Everything worked great for months.
Now we have plans to evict node-D from the cluster for other usage. So
I decreased max server memory on all instances, changed "Possible
Owners" and did a "Move Group" to move SQL instance 3 to node-A. This
worked fine.
However, when I tried to move instances 5 & 6 from node-D to node-C,
the SQL Server resouce fail to start. (Instance 4 is currently on node-
C all by itself).
I then deselected the "Affect the Group" option for all resources for
SQL instance 6. Now the "Move Group" actually moved the resources to
node-C, but the SQL Server resource still fails to start. I can move
it back to node-D just fine.

Here's the error from the Cluster.log:

ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread:
RegOpenKeyExW failed (status 2)
ERR SQL Server <SQL Server (INS06)>: [sqsrvres] OnlineThread: Error 2
bringing resource online.
INFO [RM] RmpSetResourceStatus, Posting state 4 notification for
resource <SQL Server (INS06)>

We've been trying to troubleshoot for weeks now... we can move SQL
instances 5 & 6 to node-B just fine.
Please help--Thanks