Post reply

Cluster Shared Volumes on SQL Server 2016 using FILESTREAM

  • June 22, 2017 at 3:01 am

    #322197

    Hi all,
    We are trialling using Cluster Shared Volumes on SQL Server 2016 using FILESTREAM. We have successfully created a FILESTREAM database and uploaded and viewed data when using a SQL Server 2016 instance not using Cluster Shared Volumes. However when we migrate this application / database to a instance using Cluster Shared Volumes although we can still view the previously uploaded attachments we are no longer able to upload attachments the following error message is displayed.System.Data.SqlClient.SqlException: The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may have been open at commit time or a disk I/O error may have occurred. '\v1\EthicalReview\dbo\uolt_attachment\fsContent\FC90EE3C-9DE9-44BA-92EE-4AC1C9AFA5B3\b440f4078e0f476390e8ed9008729bf1' was one of the one or more files involved. ErorrCode: 0xc0000128Strangely even with this error being displayed the attachment appears in the FILESTREAM folder but the required entry fails to be inserted into the required table. So although the file is in the FILESTREAM folder structure there is no reference in the table so cant be accessed.I'm assuming that FILESTREAM and Cluster Shared Volumes is a supported configuration ?Many thanks

  • June 22, 2017 at 4:27 am

    #1947701

    marco.roth - Thursday, June 22, 2017 3:01 AM

    I'm assuming that FILESTREAM and Cluster Shared Volumes is a supported configuration ?Many thanks

    Have you googled to check

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • June 22, 2017 at 5:31 am

    #1947714

    Yes, it should be supported. But how can i solve the issue?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply