Re: Error installing SQL 2005 on a cluster

I found and reported this during the CTP process. I got a very good
explanation that boils down to "Unavoidable side effect of installing on a
clustered host". Here is the fun part: The installer fails on a clustered
system, even if you are trying to do a stand-alone install. And it fails if
ANY clustered resources are offline.

And yes, it drove me nuts figuring out this one.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP


"Michael Hotek" <mike@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uW5s1AwNGHA.2176@xxxxxxxxxxxxxxxxxxxxxxx
That one is documented in a KB article somewhere. I can't remember where
it is at though.

--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.


"CShane" <CShane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F22BFD0D-8834-4781-AFFD-28C4454F9F6A@xxxxxxxxxxxxxxxx
Thanks for the help, but I've found an undocumented "feature" with SQL
2005
clustering. Setup will fail if you have any offline physical disk
resources.
I had created an "Unused Drives" resource group to keep my unused
physical
disk resources from becoming corrupted but hadn't brought them online.
My
solution was to bring all physical disk resources online while running
SQL
2005 setup. Keep in mind, it wasn't the SQL disk that was offline. It
was a
physical disk resource that I planned to use later for something like
Exchange or file sharing. I hope this saves someone else a bottle or two
of
Asprin!

Thanks again!
Shane

"Ray Schueler[MSFT]" wrote:

Setup scans all the cluster nodes to make sure there is at least 1
common
drive between all of them. On a 32bit cluster it's usually C or D. If
all
your nodes have a C: drive in common then you should be fine. Look in
the
SQLSetup_machinename_WI.log file for more information.

Thanks.


"CShane" wrote:

I'm not quite sure I understand your suggestion. The C:\Program
Files\
folder is where I'm trying to install the software. If I can ever get
past
feature selection, I will select the S: drive for data. However, the
S:
drive resource is online and functioning correctly inside cluster
administrator. I can also write to it from the resource owner.

Thanks for any help!


"Rodney R. Fournier [MVP]" wrote:

You need the S now to install the SQL data, C for the bits.

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


"CShane" <CShane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:69BC9FF1-38C1-490A-BC6B-704D22B1A607@xxxxxxxxxxxxxxxx
C drives are local for both nodes. The S drive will eventually be
the SQL
drive, although I am not able to get to that point in the
installation to
specify the resource group yet, although it is online and
functioning. Q
is
the quorum and it's working fine.


"Michael Hotek" wrote:

Which drive letters do you have on each node? Which ones are
local disks
and which are in the shared array? Which disks are configured in
the
cluster group you are specifying for the failover cluster
instance?

--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents
my sole
views on the subject. It does not represent the views of any
other
person
or entity either by inference or direct reference.


"CShane" <CShane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9314C7CC-067B-4732-9274-DC6BA28AC092@xxxxxxxxxxxxxxxx
I am installing SQL 2005 on a two node 2003 SP1 cluster and get
an error
after selecting components and I have narrowed it down to
Shared Tools.
The
error is:

"The drive specified cannot be used for program location.
Program
files
must be installed on a valid local disk available on all
cluster nodes.
The
valid values are"

The help icon gives a LinkID of 20467, but I can't find any
info on
that.

I'm installing to C:\Program Files\Microsoft SQL Server, which
the Data
Files feature seems happy to install to. If only Shared Tools
wasn't a
required component!

Anyone run into this or know what can cause it?










.

Relevant Pages

  • Phisical disk resource
    ... I'm setting up a 2 node cluster under 2003 ent. ... is working but I am not able to bring the shared disk ... INFO FmpPropagateResourceState: resource a94c4968- ... INFO Physical Disk: ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)
  • Re: Unable to start the cluster service when creating a new 2 node
    ... existing cluster and could no form a new cluster. ... node 1 as possible host for resource 6add91be-f8ae-4fb7-b78d-2488c502ad0a. ... FmpAddPossibleNodeToList for restype Physical Disk ... [DiskArb] ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... yeta lot of times it depends on each customer's enviornment and the complexity of the SAN migration. ... 305793 How to Replace a Disk That Is on a Windows 2000 or a Windows 2003 Server ... Windows NT/2000/2003 Cluster Technologies ... >> 4) Create a new Disk Resource for the new disk and have that in the SQL ...
    (microsoft.public.windows.server.clustering)
  • Re: Error installing SQL 2005 on a cluster
    ... I had created an "Unused Drives" resource group to keep my unused physical ... disk resources from becoming corrupted but hadn't brought them online. ... On a 32bit cluster it's usually C or D. If all ...
    (microsoft.public.sqlserver.clustering)
Loading