Environment is SQL Server 2017. The problem occurs on different installations.
I describe one of the cases that im investigating:
On a Windows Server are 5 SQL Server Instances installed. All 5 SQL Server instances are configured to use SQL Server Filestreams. The Startup of all 5 Services for the SQL Server Instances are configured on "Automatic"
Usually, when the Windows Server is restarted, for example after Servicepack Installation, all 5 SQL Server Instances start without any problem. SQL Server Log Message: "FILESTREAM: connected to kernel driver RsFx0502. This is an informational message. No user action is required." Everything is alright.
But in some cases, after a restart ob the Windows Server, 2 of the SQL Server Instances can initialize the FileStreams. But the other 3 SQL Server Instances fail to initialize the Filestream Features:
Error Message:
FILESTREAM: failed to connect to kernel driver RsFx0502.
<{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070015 (-2147024875)
I can manually restart the 3 SQL Server Instances, and the FileStream Features get initialized.
Just my guess, is there a timing Problem with the Filestream Feature an the SQL Server Instance Start?
Is it possible to configure a dependency on the Service Start of the SQL Server Instance to wait for the Filestream Services?
My other thought was to configure all SQL Server Instance Services to manual and start the SQL Server Services with the Windows Scheduler using a PowerShell script to delay/time the start of the 5 SQL Server instances and their related Services.
Any advice, suggestion or fix for the problem?
Best regards
Paolo