SQL Server 2012 FileStream on Windows Server 2012 R2 Cluster not work RRS feed

  • Question

  • It have failed to install if I choose a FileStream as SQL server installation options on Windows Server 2012 R2 Cluster.
    An error occurred while setting the private property 'Security0x20Descriptor' value 'System.Byte []'.

    So I installed by choosing the only DB engine. After the installation of the DB engine to Cluster, I introduced SQL Server SP2.
    Then the introduction of the SP2, I was able to enable the FileStream option using the SQL Configuration Manager.

    So I can use DB engine for remote access (Web Server), but I can not use Filestream.
    Cluster resource of 'File Share' was failed.

    Is there a way which can avoid this situation and use FileStream?

    Thank you.

    Tuesday, July 28, 2015 12:12 PM


All replies

  • Hi Koba33,

    Based on your description, you are unable to use FILESTREAM on a failover cluster. Could you please post the full error message from Event Viewer?

    Also please check the following things.
    1. The name that you specify for Windows Share Name must be the same across all nodes in the cluster. In other words, make sure that Filestream had a folder and it was named the same on all the nodes.
    2. Check if there are any offline cluster resources in Cluster Administrator.
    3. Make sure that SQL Server Service account has access to the file share.

    There is a similar thread for your reference.

    For more details about setting up FILESTREAM on a failover cluster, please review the following article.

    Lydia Zhang

    Lydia Zhang
    TechNet Community Support

    Wednesday, July 29, 2015 6:03 AM
  • Hi Lydia Zhang,

    Thank you for your suggestion.
    And i am sorry for the late reply. 

    Because my environment is Japanese, I can't post full error message in English.
    (and i am not good at English...)

    I write below the summary of this error message.
    ・this error event id is 1069.(Cluster event)
    ・Cluster resource '%1' in Resource Group '%2' failed.
     %1: SQL Server FILESTREAM Share (Instance Name)
     %2: File Share

    I configured SQL Server 2012 with FileStream option in Failover Cluster 
    on Windows Server 2008R2 three years ago and this system has worked all the time. 

    At that time, I do not remember that I did special setting about the File Share Config 
    with the Failover Cluster Administrator.

    I guess that it is necessary to configure File Share explicitly 
    in Windows Server 2012 R2 Failover Cluster, like your check point 1st.

    But I do not understand File Share Settings for SQL Server Filestream option 
    in Failover Cluster Administrator snap-in on Windows Server 2012 R2.

    Please show me web site, article or books that explains this settings method(or hands-on).

    Thank you.

    • Edited by Koba33 Sunday, August 2, 2015 10:19 AM
    Friday, July 31, 2015 3:57 PM
  • Hi Koba33,

    You can refer to this blog to configure file share on Windows Server 2012 R2. After that, make sure File Share resource is online in cluster administrator and then check if FILESTREAM works properly.

    Lydia Zhang

    Lydia Zhang
    TechNet Community Support

    Tuesday, August 4, 2015 9:50 AM
  • Hi Lydia Zhang,

    Thank you for helping me.

    I read the page you taught.
    I noticed my mistake about File Share and Filestream on Failover Cluster.
    I didn't take care of File Share Service in Cluster at all.

    Because I uninstalled SQL Server from Cluster, the current situation is a state that Cluster has been set and MSDTC Service has been configured.
    And I removed Cluster Resource that was used to SQL Server.
    (I checked Get-ClusterResource command.)

    I will try to configure SQL Server 2012 in the following step.
    1: Install a SQL Server Failover Cluster that select DB engine only. (not select filestream option)
    2: Update SQL Server 2012 to SP2.
    3: Configure File Share Service in Failover Cluster as you taught.
    4: Enable Filestream option on SQL Server Configuration Manager. then Share Name of Filestream set same as the name for File Share Service.

    I'd like to begin these steps and check behavior.

    Thank you very much.

    Wednesday, August 5, 2015 8:15 PM