Consider the following scenario:
You install Windows Server 2012 R2 update 3000850 or 2975719 on a server that is running an instance of Microsoft SQL Server 2014 or 2016.
You create or use a FILESTREAM-enabled database.
The FILESTREAM-enabled database files are stored on a dynamic disk.
In this scenario, you may receive error messages that resemble the following:
Error: 17207, Severity: 16, State: 1.
STREAMFCB::Startup: Operating system error 0xc0000225(failed to retrieve text for this error. Reason: 317) occurred while creating or opening file <file path>. Diagnose and correct the operating system error, and retry the operation.
Error: 17204, Severity: 16, State: 1.
FCB::Startup () failed: Could not open file <file path> for file number 65537. OS error: 0xc0000225(failed to retrieve text for this error. Reason: 317).
Error: 5120, Severity: 16, State: 106.
Unable to open the physical file <file path>. Operating system error -1073741275: "0xc0000225(failed to retrieve text for this error. Reason: 317)".
Error: 5105, Severity: 16, State: 14.
A file activation error occurred. The physical file name <file path> may be incorrect. Diagnose and correct additional errors, and retry the operation.
This problem was first fixed in the following cumulative update for SQL Server:
Cumulative Update 6 for SQL Server 2014 Service Pack 1
Cumulative Update 1 for SQL Server 2016
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Latest cumulative update for SQL Server 2014
Latest cumulative update for SQL Server 2016
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.