Trying to Move Group - SQL Instance Won't Start

#41

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

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

On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

Quote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed

#42

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#43

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#44

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#45

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#46

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#47

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#48

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#49

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.

#50

On Mar 28, 9:45*am, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

It sounds like when you added the nodes, you manually added the new nodes to
the "allowed nodes" list for that instance and did not run the installer to
put the binaries down on the new nodes. *This is what I would expect to see
after adding nodes without doing the install properly.

Did you follow the instructions in "Maintaining a Failover Cluster" in BOL
on recovering from a cluster node failure?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552 (AT) e67g2000hsa (DOT) googlegroups.com...
On Mar 27, 3:48 pm, "Tom Moreau" <t... (AT) dont (DOT) spam.me.cips.ca> wrote:

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 Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau

edsm... (AT) pascocountyfl (DOT) net> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88 (AT) 8g2000hsu (DOT) googlegroups.com...
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

The same domain account is used for all SQL services and for all
instances across all nodes.

Ed- Hide quoted text -

- Show quoted text -

Thanks Geoff, I'll be discussing with the server team.