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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzIxIiwiaGFzaCI6IjFiYjI5Y2ZjLTcxMzktNGUyZS05ZjRkLTExYTRiYTk0MDM2MiJ9
1-800-691-1991 | 9am - 8pm ET
EN

All Veeam services stop at the same time everyday

Challenge

Veeam services stop at the same time every night.

Cause

Microsoft SCCM has a Health Agent Task scheduled to run over night. The task does not support WMI 3.0. WMI 3.0 is incorporated in Veeam Backup & Replication as a dependency. When the Health Agent clears the WMI repository, it kills Veeam services in the process. You might see other WMI errors in the event logs, or a message about an SMS Agent starting shortly before.

Solution

Please see the following Microsoft KB article http://support.microsoft.com/kb/2796086 for instructions on how to prevent the issue. Alternatively, open the task scheduler, expand Task Scheduler Library > Microsoft > Configuration Manager and disable the task.

More information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support
KB ID:
1721
Product:
Veeam Backup & Replication
Version:
All
Published:
2013-01-14
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