August 12, 2009 at 2:15 pm
I am receiving this error message when I try to install SQL Server 2005 Std on a clustered server.
The drive specified cannot be used for program location. Program files must be installed on a valid disk available on all cluster nodes. The valid values are:
There are no drives listed. It is blank. I can't get around this error.
Does anyone know what I need to do to fix this?
August 12, 2009 at 2:29 pm
Do all your nodes have the same local drive settings?
For example, you have local drives C and D on one node, and they should be present on all the other nodes too.
August 12, 2009 at 2:36 pm
Hi Patricia,
AFAIK the program files must be installed on the local drive i.e usually C or D drives.
Thank You,
Best Regards,
SQLBuddy
August 12, 2009 at 2:48 pm
Yes they are. The D: drive is the clustered drive.
August 12, 2009 at 2:54 pm
for the disk you want to install SQL on, be sure you can move the disk resource to all the nodes in your cluster using cluster administrator.
August 12, 2009 at 2:58 pm
Right now all I am trying to do is install on the C drive and it still doesn't work. I usually point the data files to the D: drive and that is where the database will reside.
August 12, 2009 at 3:04 pm
you have to install SQL to a disk that on SAN storage that can be moved or "failed over" to any of the nodes. that way, if there is a hardware failure on nodeA, it moves those disks to the other node.
August 12, 2009 at 3:04 pm
I remember seeing this...
Do you have any offline storage resources in your cluster groups? I had this exact problem when I had an offline disk that I had no intention to use. Bringing the storage resource online solved it for me.
August 12, 2009 at 3:14 pm
I will have to look at that. Right now the Windows SA's are looking at the server. I had this problem before and I don't remember what I did to resolve it. What is weird is there are no drive letters listed. They are blank. I am not sure what log to look at. Most of the logs have way to much information that you have to have a Dr's degree to understand them.
August 12, 2009 at 3:19 pm
Patricia Johnson (8/12/2009)
I will have to look at that. Right now the Windows SA's are looking at the server. I had this problem before and I don't remember what I did to resolve it. What is weird is there are no drive letters listed.
That's what makes me point to an offline disk resource somewhere in the cluster. I had that problem before, and that's what literally caused it.
August 12, 2009 at 3:42 pm
I looked and the resources are online.
August 12, 2009 at 3:44 pm
Can someone to confirm whether you have to install "EVERYTHING" on the D: drive? I thought with clustering, it installs on the second server for you behind the scenes. You just point the resource "which is the database" on the D: drive. That is what fails over back and forth between the 2 servers.
August 12, 2009 at 4:04 pm
Hi Patricia,
Usually the binaries are installed on the local drives of each node, but the datafiles (.mdf and .ldf) have to be placed on the SAN. If the datafiles are installed on the local drives like D, during the failover the failed over instance cannot function on the new node.
Thank You,
Best Regards,
SQLBuddy
August 12, 2009 at 4:12 pm
Thank you that is what I thought and that is what I am doing. I still can't get this to install. I searched the internet and there is some info that I may not have the rights as an administrator. But the Windows SA's have confirmed that I do. So I don't understand.
August 13, 2009 at 7:48 am
Patricia Johnson (8/12/2009)
I looked and the resources are online.
I just want to confirm that all the resources are online?
In my case when I went to do the install, the resources I intended to use were online, but there was a different cluster resource group with several offline storage resources. Until I brought them online as well, I could not install, and was given the same error message.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply