August 2, 2023 at 8:50 am
Hi Folks.
We have two SQL Server 2019 Enterprise in an High Availability Group (always on). The OS is Windows server 2019. For the witness of the failover cluster we use a file share. The cluster itself runs perfect. But we have some troubles with the file VerifyShareWriteAccess.txt. The cluster service opens the file (read, write) but for some unknown reasons the files were not closed. So, at the of the day there are hundred of open VerifyShareWriteAccess.txt files.
Has anybody an idea about this?
Greetings Alphanew
August 3, 2023 at 9:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
August 3, 2023 at 3:19 pm
Is this causing an issue? Have you traced back who owns the file open requests?
There is some logging stuff as well, if you haven't seen this: https://learn.microsoft.com/en-us/windows-server/failover-clustering/troubleshooting-using-wer-reports
August 7, 2023 at 5:06 am
Hi Steve.
Thanks for helping.
I will have a look at your https://learn.microsoft.com/en-us/windows-server/failover-clustering/troubleshooting-using-wer-reports
>Have you traced back who owns the file open requests?
The owner of the file must be cluster service itself
The issue is,if I do not close this files with powershell script (close-SmbOpenFile -Force) there will be an infinite number of open files at the end of the day.
Greetings
Alphanew
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply