#1 Global Leader in Data Resilience

SQL VSS writer fails for SQL localdb on Azure AD Connect Sync server.

KB ID: 2911
Product: Veeam Backup & Replication
Version: Any
Published: 2019-03-13
Last Modified: 2020-08-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

Backup or replication jobs with Application Aware Image-Processing enabled may fail on the server hosting Azure AD Connect Sync with an error indicating the SQL writer has failed. After the job has failed, running “Vssadmin list writers” from an administrative command prompt on the Azure AD Connect Sync server shows the sql writer in failed state. In Hyper-V, the error in the statistics window in VBR may be “guest processing skipped” or may indicate that the checkpoint has failed. In Vmware, the error is usually “Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]

Cause

Updates to Azure AD Connect Sync will sometimes leave the server in a state where VSS snapshots will cause the SQL Server writer to fail.

Solution

After installing service pack 4 for sql localdb 2012 and rebooting the server (https://www.microsoft.com/en-us/download/confirmation.aspx?id=56040), the jobs will generally be able to run successfully. In some instances, the error may return after future updates to the Azure AD Connect Sync Client, in which case another reboot will resolve the issue. Microsoft has been made aware of the issue and future updates to Azure AD Connect Sync may either not cause this problem or should prompt the user for reboot. If a future update to the Azure AD Connect Sync client does not prompt for a reboot, you can either reboot proactively after updating to prevent this issue from happening or test the job and reboot if it fails following the update.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.