none
standalone sql server on wfc cluster cannot have files on shared disk locations

    Question

  • Hi,

    Im trying to install a new Sql Server which will be added to an availability groups. Its meant to be standalone ( ie not part of FCI).

    I have enabled cluster services and added the server to the existing cluster but when I try and install I get this validation error on the install screen.

    The directory d:\xxxxxxxxx\xxxxx  is not a valid path.  Standalone sql server on wfc cluster cannot have files on shared disk locations

    Any ideas where i have gone wrong here?

    Server is windows server R2. Sql Server version 2012
    • Edited by Blakmk Wednesday, May 30, 2012 11:06 AM
    Wednesday, May 30, 2012 11:06 AM

Answers

  • Quickest way is to kick the machine out of the cluster, install a stand-alone SQL instance, then re-add it to the cluster.  Since the machine doesn't participate in an FCI, the cluster membership can come after the installation.  And you do need the matching drive paths for Availability Groups to work so the different letters as listed above will cause problems later on.


    Geoff N. Hiten Principal Consultant Microsoft SQL Server MVP

    • Proposed as answer by Peja Tao Thursday, May 31, 2012 6:34 AM
    • Marked as answer by Peja Tao Wednesday, June 06, 2012 1:40 AM
    Wednesday, May 30, 2012 7:10 PM
    Moderator

All replies

  • http://msdn.microsoft.com/en-us/library/ff877884.aspx

    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

    Wednesday, May 30, 2012 11:39 AM
  • Thanks uri, Im struggling to see how this helps.

    If look at this link I can see that a node can have its own separate storage but still be part of the wsfc

    http://msdn.microsoft.com/en-us/library/hh270278.aspx

    Wednesday, May 30, 2012 12:25 PM
  • This seems to be because the standalone instance was using the same drive letters as the FCI. Changing them to be different allows the install to go ahead
    Wednesday, May 30, 2012 12:52 PM
  • Quickest way is to kick the machine out of the cluster, install a stand-alone SQL instance, then re-add it to the cluster.  Since the machine doesn't participate in an FCI, the cluster membership can come after the installation.  And you do need the matching drive paths for Availability Groups to work so the different letters as listed above will cause problems later on.


    Geoff N. Hiten Principal Consultant Microsoft SQL Server MVP

    • Proposed as answer by Peja Tao Thursday, May 31, 2012 6:34 AM
    • Marked as answer by Peja Tao Wednesday, June 06, 2012 1:40 AM
    Wednesday, May 30, 2012 7:10 PM
    Moderator
  • I have installed evaluation version of mssqlserver 2012 now I have pid but dont know how to update it.?

    Thanks

    Thursday, May 09, 2013 2:00 PM
  • I had exactly this problem. Evicting the node from the cluster worked perfectly for me. I didnt even have to restart the installation.

    Thanks!

    Thursday, January 23, 2014 3:31 PM