- Veeam Support Knowledge Base
- Health Service (Monitoring Host) Handle Count has exceeded the threshold
Health Service (Monitoring Host) Handle Count has exceeded the threshold
| KB ID: | 1783 |
| Product: | Veeam Management Pack | 6.0 | 6.5 | 7.0 | 8.0 | 9.0 |
| Published: | 2013-06-26 |
| Last Modified: | 2025-06-18 |
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
Oops! Something went wrong.
Please, try again later.
Cause
The monitors raising the mentioned alerts ensure that the "Process\Handle Count" counter for the "MonitoringHost.exe" and "HealthService.exe" processes does not exceed a specific threshold over a series of consecutive samples. If the conditions are met, this monitor will change to a critical state, which will then roll up to the "Health Service State" monitor.
In the Veeam MP case, the values that trigger the monitor may result from Collector server overload. If too many VMware hosts and VMs are monitored, then the Health Service may be overwhelmed when processing the data.
How to View Number of Handles
The current number of handle counts can be checked using Windows Task Manager on the collector server:
- Open Windows Task Manager and switch to the Details tab.
- Right-click on any of the column headings and click Select columns.
- From the list of available columns, select Handles, and click OK.
Solution
Please check configuration of SCOM Agent co-located with Veeam collector, see KB1026.
Make sure you don't have either of the following alerts, reference KB1765:
Veeam Collector: Health Service dropped data
or
Veeam Collector: Health Service workflows failed
If no additional alerts indicating performance issues with SCOM Agent occur, you can try increasing thresholds for 2 monitors based on current number of handles:
- For MonitoringHosts.exe adjust "Veeam Collector: Health Service (Monitoring Host) Handle Count threshold"
- For HealthService.exe adjust "Veeam Collector: Health Service Handle Count threshold"
Otherwise you may consider moving VMware monitoring jobs to other Veeam Collectors or co-locating Veeam Collector with a SCOM Management Server.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.