Re: Trying to Move Group - SQL Instance Won't Start

On Mar 31, 9:58 am, edsm...@xxxxxxxxxxxxxxxxx wrote:
On Mar 28, 9:45 am, "Geoff N. Hiten" <SQLCrafts...@xxxxxxxxx> wrote:





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...@xxxxxxxxxxxxxxxxx> wrote in message

news:9c148020-46b5-4251-8e5e-c021ba6bc552@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Mar 27, 3:48 pm, "Tom Moreau" <t...@xxxxxxxxxxxxxxxxxxxx> 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...@xxxxxxxxxxxxxxxxx> wrote in message

news:61340dcb-4f73-48bd-8a8f-581c1a0a3e88@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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.- Hide quoted text -

- Show quoted text -

When we added nodes C & D to the cluster, the "possible owners" (In
Cluster Administrator) for these nodes were set to only include
themselves (Node C or D) and the failover node (Node B in our case).
Consequently, the SQL binaries were only installed on these two nodes.
Now I want to move the two virtual SQL instances (INS05 and INS06)
from node D to node C but as Geoff pointed out, the binaries for the
node-D instances don't exist on node-C. (Node-C has instances INS04
and INS05 installed)
I see no way to legitimately installing instance INS05 and INS06 to
node-C without first uninstalling these virtual SQL instances from the
nodes their currently on (node-D and failover node-B).
Am I correct, or is their another solution?


.

Relevant Pages

  • Re: MSSQL2K and MSSQL side by side in clustered environment
    ... If the cluster has any resource or resource group offline, the SQL ... installer will crash. ...
    (microsoft.public.sqlserver.clustering)
  • Re: SP3a does not work on a cluster
    ... After you type the virtual server name in the text box of the SQL Server Service Pack 2 installation wizard, and then click Next, the setup program checks for the validity of the virtual server name by checking the ... resource type for SQL Server, depending on the Network Name resource. ... If the setup program does not find the SQL Server resource as the first resource that depends on the SQL Network ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL or Access DB
    ... But with SQL Express ... is it worth it any longer to mess with an MSDE installation? ... > correctly write an installer project that installed MSDE correctly and set ... It comes with SQL Server 2000 Standard. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help... disk wont come online after it is offlined
    ... Do you know any way to do dependency across resource groups? ... the resources in the primary group where SQL Service and other drives are? ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: MSSQL2K and MSSQL side by side in clustered environment
    ... You need to start out with a disk resource in its own resource group. ... Network Name and IP address resource for the clustered SQL instance are ... It appears that the installer sees a complete ... > (is this what you referring to as SQL Server Virtual?). ...
    (microsoft.public.sqlserver.clustering)