Hi Krystian, please contact technical support for a closer investigation. You can also check Windows Event Log for related messages and search this forum for the error code - there are a few threads with similar issues.
03774749
I checked the case and our team was responsive and gave you guidance how to fix it on the Microsoft SQL side. The above is a Microsoft generic issue.
The case was closed with no reponse from customer.
I suggest to open a new case and share the case number here so that we can monitor the case. We can as well escalate the case to match reaction times. A specialist can help with executing the request Microsoft tools.
Team has opened a new case for you. 03822240
They will have to request log upload again as the old ones were deleted by (time) policy.
Maybe there will be a need to open a Microsoft Case as well as the error is on the Microsoft Software side. Our team will assist you in this case with Microsoft (no fingerpointing).
Just a small workaround; I have created a start-script for some VMs which restarts the SQL VSS Service.
This seemed to be much easier then locating the real cause
Hi Max, thanks for sharing this. Please know that depending on what you restart with the script, you need to add a wait period to it.
When you restart the VSS writers or the VSS framework at all, it will take some time until all the VSS writers are registered again.
If you restart them and then execute the VSS framework it always finish successfull because the writers are not present potentially.
You can check your script and then execute the command
vssadmin list writers (you need to start a CMD in admin mode)
and compare it against the same command before you restart the services to compare the list.
