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)
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.
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:
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.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case