Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- From: hmscott <hmscott@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 18 Dec 2006 06:46:00 -0800
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 SP1nodes."
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
from
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
the instance that "owns" the resources. I read through the installationwith
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
this particular error.upgrade.
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
Verify the server is able to start and that you provided a valid sapassword
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
- Follow-Ups:
- Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- From: Anthony Thomas
- Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- From: hmscott
- Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- References:
- Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- From: hmscott
- Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- From: Anthony Thomas
- Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- Prev by Date: Re: Move from active/passive cluster to active/active
- Next by Date: Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- Previous by thread: Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- Next by thread: Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
- Index(es):
Relevant Pages
|
