1-800-691-1991 | 9am - 8pm ET
EN

Troubleshooting Error Code ‘32768’, Failed to create VM recovery snapshot

KB ID: 2687
Product: Veeam Backup & Replication
Version: 9.5
Published: 2018-07-13
Last Modified: 2020-08-13
Languages: FR

Challenge

Backups fail with the error Warning 'VM' could not initiate a checkpoint operation: %%2147754996 (0x800423F4). (Virtual machine ID 869a2794-6a7e-4104-8395-8f6a2313d7fa)'). Error code: '32768'.

Cause

If your version of Veeam Backup & Replication is 9.5 update 2 (9.5.0.1038) or prior, there was a known issue that could be addressed by a fix applicable only to that version. However, that known issue has been addressed in update 3 and newer (9.5.0.1536) so if your installation of Veeam Backup & Replication is not fully updated, it is strongly recommended that you consider doing so, or contact Support if you are unable to update and need the fix.

There is a distinct known cause for this error message when there are underlying issues with the SQL VSS writer on the guest VM. You should be able to see error messages in the guest VM’s Event Logs stating, “A critical component required by the SQL writer is not registered” or the VSS writer rejecting the event.

Running the “vssadmin list writers” command might also show the SqlServerWriter in a “Non-retryable error” state.

 

Solution

If you see these errors in the guest, this issue can generally be corrected by repairing the SQL instance on the guest VM as detailed below:
User-added image
User-added image
KB ID: 2687
Product: Veeam Backup & Replication
Version: 9.5
Published: 2018-07-13
Last Modified: 2020-08-13
Languages: FR

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.