Cannot Register Management Service.
The Specified Service Has Been Marked for Deletion.

KB ID: 1929
Product: Veeam Backup & Replication | 11
Published: 2014-09-24
Last Modified: 2022-06-16
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

A Backup or Replication job using Application-Aware Processing fails with an error similar to:
Failed to prepare VM for processing: Unable to perform installation
Unable to register and start service. Attempt 10 of 10
Cannot register management service. Service name: [VeeamVssSupport].
Cannot create service. Machine: [hostname.domain.tld]. Service name: [VeeamVssSupport]. Service binary path: [C:\Windows\VeeamVssSupport\VeeamGuestHelper.exe]. Service account: [].
Cannot create service.
Win32 error:The specified service has been marked for deletion.
Code: 1072 (System.Exception)

Cause

The VeeamVssSupport service cannot be installed because the VeeamVSSSupport service is still present from a previous job run and is marked for deletion by the OS. The service becomes marked for deletion by the OS when the OS fails to process the service delete request that the previous job run sent.

By default, Non-Persistent Runtime Components are used by Veeam Backup & Replication when performing Application-Aware Processing. A connection is made to the Guest OS during each backup job run, and the VeeamVSSSupport service is installed. When the VM is done being processed, Veeam Backup & Replication sends a request for the VeeamVSSSupport service to be deleted.

Solution

Reboot the VM's guest OS to allow Windows to remove the VeeamVSSSupport service that is marked for deletion.

More information

If this issue frequently recurs for a specific VM, consider switching from Non-Persistent Runtime Components to Persistent Runtime Components. When using Persistent Runtime Components, the VeeamVSSSupport service is not removed after each job run and is left present within the Guest OS, ready for the next job run.

To enable the use of Persistent Runtime Components:

  1. Ensure the VeeamVSSSupport service is not stuck marked for deletion. If it is, reboot the VM.
  2. Enable Use persistent guest agent within the job for that specific VM.
  3. Manually install the Veeam Installer Service on the VM
    The VeeamInstallerSvc.msi is located on the Veeam Backup Server in:
    C:\Program Files\Veeam\Backup and Replication\Backup\Packages
     

With "Use persistent guest agent" enabled in the job and the Veeam Installer Service installed, during the next run of the job, the VeeamVSSSupport service will be created and will not be removed after the job completes.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.