https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTA4IiwiaGFzaCI6IjUyOWNkYjlhLTljMTctNDU0Yy1iNDVhLWZjMTk1MTMxYTIwYSJ9
1-800-691-1991 | 9am - 8pm ET
EN

The dependency service or group failed to start

Challenge


Cause

This error is usually caused by one or more Windows VSS services being disabled. To fix it, you will need to go to Start > Run, and enter "services.msc" (without quotes). Here, you will see a list of services, their description, and whether or not they are running. Make sure RPC service is up and running.
You may also check the user who starts the service (the user specified in Veeam job for VSS connection).

Solution

Check that services are enabled and providers are operating properly.
To resolve this issue, check that the COM+ Event System service is started and that the Volume Shadow Copy service (VSS service) and Microsoft Software Shadow Copy Provider service are both enabled. You should also make sure that third-party installed VSS providers are operating properly. If a VSS provider is not operating properly, you should try reinstalling it. If that does not work, you should contact the provider vendor.
KB ID:
1108
Product:
Veeam Backup & Replication
Version:
5.x
Published:
2011-07-26
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later