#1 Global Leader in Data Resilience

Update to Microsoft Entra Connect causes SQL VSS issues

KB ID: 2326
Product: Veeam Backup & Replication
Published: 2017-07-31
Last Modified: 2025-08-12
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.

Article Applicability
This article is specific to environments where the Azure AD Connect or Microsoft Entra Connect package is installed on the machine where Microsoft SQL Server is installed.

Challenge

You receive the following error during the guest processing:

Unable to release guest. Error: Unfreeze error (over VIX): [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. 
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{6323fe10-0205-47df-b015-4a5ff60c31e2}]. 
Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Solution

If an update to Azure AD Connect or Microsoft Entra Connect was recently installed, a repair of the SQL installation should fix the issue.
Note: Even if a recent update wasn't installed, it may be worthwhile to attempt the repair.

  1. Open the list of installed applications.
  2. Find and select the Microsoft SQL Server 20XX Express LocalDB entry.
  3. Click Modify.
Screenshot of Microsoft SQL Server LocalDB entry within installed applications list with the Modify button highlighted.
  1. Within the installer wizard, select the option for Repair.
    Note: In some scenarios, a reboot may be required.
Screenshot of the Microsoft SQL Server 2019 LocalDB installer showing the Repari and Remove options with the Repair option selected.
If repairing the SQL Express LocalDB does not help, further SQL Server Writer troubleshooting will be required. As a workaround, until the issue with the SQL Server Writer is resolved, you can configure the backup job to allow creating crash-consistent backups by setting it to "Try application processing, but ignore failures."

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

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

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.
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.