Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)

It is quite alright, but when conditions are such, it is difficult to
determine the particular problem you are having.

The sub-thread you responded to response has the KB for the Multi-Path IO
issue.

However, as far a clustering SQL Server, my prior post lists the steps.

My concern is determining how many instances (appears to be 3) of SQL
Server, and how many cluster resource groups for this instances. Each must
have at least 1 dedicated shared volume, at least among the nodes that will
be supporting the failovers.

In addition, you will need 1 volume for the Quorum (which from your
statements, you already have configured).

And another volume for the dedicated MS DTC resource group, again which
appears you already have configured.

How many of these SQL Server instances have already been clustered, or are
attempting to install all three simultaneously?


Anthony Thomas


--

"hmscott" <hmscott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A8BA407-C103-4838-AFF2-35FACAA179F4@xxxxxxxxxxxxxxxx
Anthony,

I'm sorry, I searched through the forum and did not find your previous
post.
I looked at all of my posts and the oldest one I could find was from
10/27
(which is maybe why I reposted on Saturday).

You mention that the shared drives are not properly configured. I won't
dispute the point, but could you please elaborate?

I recognize that something is wrong in the MSCS configuration because when
I
went to add another node in the cluster, the cluster configuration utility
gave me a warning that the fourth node in the cluster was unable to detect
the Quorum disk. I was able to "get around" that error message by using
the
advanced configuration which bypasses some of the checks. Once the node
was
added to the cluster, I was able to use the "Move Group" to pass the
"Cluster
Group" (containing the Quorum drive) around to all four nodes in the
cluster
with no trouble. Likewise, I was able to pass the MSDTC group around to
all
nodes in the cluster.

I assumed that the error was because the local (on board) SCSI drives are
different among thr four nodes. On two nodes, there is only one virtual
disk
while on the other two nodes there are two virtual disks.

I again apologize if I did not pick up on your response to my first post.
I
realize it's very bad etiquette, but I am stretched fairly thin at this
point. I would be very grateful for any added assistance you can provide.

Regards,

hmscott
hugh.scott3.at.verizon.net

"Anthony Thomas" wrote:

I think you had an additional post, which I responded to, but you had
some
things here that concern me as well.

First, you are installing SS2K on a Win2K3 SP1 machine. SP3 will be
required. Moreover, SP1 security enhancements disable TCP until after
you
apply SP3.

Specifically, items 5 and 6 below are unnecessary because item 2 already
deployed the RTM binaries.

The sequence is:

1. Add new node to cluster.
2. Install RTM SS2K and designate the node membership.
3. Create Named Pipe aliases on each member node for the Named Instance
you
are managing.
4. Install SS2K SP3 from the active node.
5. Install SS2K SP4 from the active node.
6. Install at least SP4 HF2040, but would be highly recommended that you
apply SP4 HF2187.

Nevertheless, from your other post, it appears that you still have not
gotten your shared volumes configured correctly first. This is a
prerequisite.

Sincerely,


Anthony Thomas


--

"hmscott" <hmscott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9D800B12-9E4A-4A59-9E61-96CD6BDC1A7A@xxxxxxxxxxxxxxxx
O/S: Windows 2003 Enterprise SP1
SQL Server 2000 EE (32 bit)

I had a three-node A/A/P cluster.

This weekend, I added a fourth node and a third active instance
(A/A/A/P).
The installation process went smoothly:

1. Add new node to cluster
2. Install SQL 2000 (RTM) (new named instance)
3. Install SQL 2000 (SP4)
4. Install SQL 2000 (hf 2040)
5. Install SQL 2000 binaries on newly added node for Instance 1
6. Install SQL 2000 binaries on newly added node for Instance 2

The problem came when I tried to apply SP4 on the new node for
Instances 1
and 2. I keep getting the following error:

"All cluster disks available to this virtual server are owned by other
nodes."

It comes right after I type in the name of the Virtual Server to be
maintained. I am outside the maintenance window now, so I can't run
SP4
from
the instance that "owns" the resources. I read through the
installation
guide a couple of times, and I've searched a fair amount on the
boards. I
see where other people have come across a different error (See
http://support.microsoft.com/?kbid=905286), but I've never seen anyone
with
this particular error.

I have another three-node cluster in the test environment and when I
added
the thrid node for that cluster in, things went just fine.

I'd be grateful for any thoughts and/or suggestions.

Here is the tail end of the sqlsp.log file:

13:07:47 Previous Install Version: 8.00.194
13:07:47 ReleaseSetupTopology
13:07:47 End Action DialogShowSdMaintain
13:07:47 begin ShowDialogsUpdateMask
13:07:47 nFullMask = 0xb034603, nCurrent = 0x400, nDirection = 1
13:07:47 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
13:07:47 Dialog 0x400 returned: 1
13:07:47 End Action ShowDialogsHlpr
13:07:47 ShowDialogsGetDialog returned: nCurrent=0x2000,index=13
13:07:47 Begin Action ShowDialogsHlpr: 0x2000
13:07:47 Begin Action: DialogShowSdUpgrade
13:07:47 ShowDlgUpgrade returned : 1
13:07:47 Checking databases on instance 'MSSQLSERVER'
13:07:47 Begin Action: Check for VS Node
13:07:50 All cluster disks available to this virtual server are owned
by
other node(s).
13:07:51 Setup was unable to verify the state of the server for an
upgrade.
Verify the server is able to start and that you provided a valid sa
password
and restart setup.
13:07:51 End Action DialogShowSdUpgrade
13:07:51 End: ShowDialogs()
13:07:51 Action CleanUpInstall:
13:07:51 Installation Failed.


Regards,

hmscott





.

Relevant Pages

  • Re: Clustering Question
    ... You could make a test environnement through Virtual Machine to get a picture on Cluster. ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)
  • Re: Cant get SQL 2000 installed on new node in Cluster
    ... You can apply a service pack to a new node without taking the Virtual SQL ... server offline. ... When the install is asking for a virtual server name, ... one for the MSCS cluster or the one for the SQL cluster? ...
    (microsoft.public.sqlserver.clustering)
  • Re: Exchange 2007 CCR on Windows 2008 x64 RTM
    ... install guide, but I always did it too quickly after the failure. ... I'm an MCITP on Server 2008 & Exchange ... I'm told that this is caused by the way the cluster service creates the ... respond to the start or control request in a timely fashion occured ...
    (microsoft.public.exchange.setup)
  • Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... SQL Server 2000 EE ... I had a three-node A/A/P cluster. ... Install SQL 2000 binaries on newly added node for Instance 1 ... "All cluster disks available to this virtual server are owned by other nodes." ...
    (microsoft.public.sqlserver.clustering)
  • Re: Clustering Question
    ... You could make a test environnement through Virtual Machine to get a picture on Cluster. ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)