You know, I have been running into this issue in the past week, but I am finding correcting the bad paths of the problematic database is not enough. Not even restarting the SQL VSS Writer service and the volume shadow copy service is enough. I have to take the disruption of rebooting the SQL server for the SQL VSS Writer to be happy again. Anyone know of a less drastic way to remedy this after you have corrected the paths in the database?
Statistics: Posted by HJAdams123 — Aug 05, 2025 1:40 am
