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

Event pre-filtering causes high vCenter Database load


The vCenter Database utilizes most of the available CPU, impacting vCenter Server performance. Stopping nworks Collectors brings the CPU usage back to normal. The nworks vmspi log shows the following errors: 

VCEVT+** [VC250] retrieveEvents: createFilter failed, System.Net.WebException: The operation has timed out


nworks can use a vCenter-side event filter to reduce the traffic back to the Collector. The filtering, however, turns out to impact vCenter Database performance.


In nworks 5.6 and later, creation of the event filter is disabled by default. However, if the issue described above occurs, you will need to turn off the setting manually:
  1. In nworks Web UI, go to the Enterprise Manager tab, select the Collector in the hierarchy on the left and click Advanced settings

  2. Find the EnableVcVerboseFilter setting and set it to False

  3. You will be prompted to restart the Collector. To do that, select the Collector and click the Restart button.

Applied changes will not influence monitoring accuracy.

More information

If you have any questions or problems, please contact Veeam Support at
Veeam Management Pack for Microsoft System Center
Last Modified:
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.

ty icon

Thank you!

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


error icon

Oops! Something went wrong.

Please go back try again later.