 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / February 2006Error installing SQL 2005 on a cluster
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? 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?  SignatureMike 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. >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. [quoted text clipped - 13 lines] > > Anyone run into this or know what can cause it? 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. > 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 [quoted text clipped - 17 lines] > > > > Anyone run into this or know what can cause it? 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 >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 [quoted text clipped - 25 lines] >> > >> > Anyone run into this or know what can cause it? 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! > You need the S now to install the SQL data, C for the bits. > [quoted text clipped - 37 lines] > >> > > >> > Anyone run into this or know what can cause it? I hope this resolves your issue. http://www.sql-server-performance.com/rn_sql_server_clustering_2000_to_2005_4.asp Thanks, Haris. > 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 [quoted text clipped - 45 lines] >> >> > >> >> > Anyone run into this or know what can cause it? 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. > 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 [quoted text clipped - 45 lines] > > >> > > > >> > Anyone run into this or know what can cause it? 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 > 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 [quoted text clipped - 52 lines] > > > >> > > > > >> > Anyone run into this or know what can cause it? That one is documented in a KB article somewhere. I can't remember where it is at though. SignatureMike 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. > Thanks for the help, but I've found an undocumented "feature" with SQL > 2005 [quoted text clipped - 84 lines] >> > > >> > >> > > >> > Anyone run into this or know what can cause it? 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. SignatureGeoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP > That one is documented in a KB article somewhere. I can't remember where > it is at though. [quoted text clipped - 94 lines] >>> > > >> > >>> > > >> > Anyone run into this or know what can cause it? Thank you for the feedback, I added the comments made here to the bug. On Mike's point earlier, there was a KB article with basically the same error that occurred when the user account used to run setup.exe wasn't an admin on all nodes. The issue was fixed and the KB article was removed. Ray This posting is provided "AS IS" with no warranties, and confers no rights. ------------- > 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 [quoted text clipped - 102 lines] > >>> > > >> > > >>> > > >> > Anyone run into this or know what can cause it? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.