Fix AD Connect auto-update mechanism so it doesn't cause VSS SQL failures
Issue has been going on for at least a year. When AD Connect auto-updates, it messes something up with its 'SQL Server 2012 Express LocalDB' instance such that VSS backups of the server fail until addressed.
'Fix' is to run a repair installation of the LocalDB instance, after which the VSS operations succeed without requiring a server reboot.
Seems the same problem again now, as 'Anonymous' mentioned. I have 220.127.116.11 and have exactly this error.
The mentioned fix (repairing the "Microsoft SQL Server 2012 Express Local DB", with reboot, within Programs and Features) does still work for me on Win. server 2016. For how long, I don't know.
I think the same issue happened again after updating to 18.104.22.168
A fix for this issue was introduced in version 1.3.20:
Les Begnaud commented
For those using Veeam: we recently resolved our constant headaches with this by stopping the ADSync service before freeze, then starting after thaw (script section of app-aware backup section of job). We have an RMM that would let us know if the service is stopped for too long, but general disclaimers apply about using at your own risk.
Seems like it's not localdb that's the issue, so much as it is the ADSync service not releasing locks in a timely manner for SQLWriter. Stopping the service seems to have fixed it on about 25 different ADDCs
Stijn Wauters commented
Same problem here
Azure AD connect version 1.1.647.0 on windows server 2012 R2.
Backup with Veeam gives daily problems now with VSS SqlServerWriter.
Scott Thomson commented
Still not fixed, but updating thread to include link to MS Partner Support forum where issue is being looked at:
I will second Scott Thomson's request. I am a server administrator for multiple companies, and many of the clients who have Azure AD Connect are having issues backing up the server on which Azure AD Connect is installed. Repairing the "LocalDB" server requires a reboot for most of my clients' servers and it only "fixes" the issue temporarily.
Microsoft, please fix whatever is breaking the SqlServerWriter VSS writer. As Mr. Tompson said, the issue appears to be due to the auto-update feature of Azure AD Connect.
Feel free to reference my thread on this Microsoft TechNet forum for additional details regarding the specific issues with Windows Server Backup, the SqlServerWriter VSS writer, and Azure AD Connect on one of my clients' server: