Skip to content
English
Submit a support ticket
Back to www.opslogix.com
  • There are no suggestions because the search field is empty.

VMware MP Collector service crashes and objects are undiscovered

Why the collector service restarts at random and VMware objects disappear, and how to fix it.

Applies to: OpsLogix VMware Management Pack (all versions) · SCOM 2019, 2022, 2025
Last updated: October 2026 · Reading time: 3 minutes

Symptom

On a server in the VMware resource pool, the Opslogix VMware Collector Service (service name OpsLogix.VMware.Collector.Service) stops unexpectedly. While it's stopped:

  • The Service Running State monitor of the collector service turns unhealthy (Monitoring workspace, OpsLogix > VMware > VMware Collector > State VMware Collector Service).
  • VMware monitors and performance rules that run on that server get no data, and vCenter alarms aren't forwarded.
  • The monitor OpsLogix VMware check if the license is still valid can change to Warning, because it gets no answer from the collector. This doesn't mean your license is invalid.
  • The Windows Application event log on the server shows a crash of OpsLogix.VMware.Collector.Service.exe, usually event ID 1026 (source .NET Runtime) and event ID 1000 (source Application Error).

A stopped collector doesn't remove VMware objects from SCOM by itself. If objects disappear, the cause is usually a license problem. See "OpsLogix VMware license is not valid": update your license and No VMware instances are monitored in SCOM.

Cause

The most common cause is a lack of resources on the server: not enough memory or CPU for the VMware workload, often in a large environment or on a server that also runs other workloads. Very verbose logging can add to this.

Resolution

  1. Restart the service automatically. The installer doesn't set recovery actions for the service. Run this as administrator on each server in the VMware resource pool, so Windows restarts the collector after a crash: 
    sc failure OpsLogix.VMware.Collector.Service reset= 86400 actions= restart/60000/restart/60000/restart/60000
  2. Check the resources. On the servers in the VMware resource pool, check that the average CPU queue length stays below 2 and that there is free memory. Compare with Sizing for the VMware Management Pack, and add memory or CPU cores where needed.
  3. Spread the load. Add a server to the VMware resource pool, or split a large vCenter connection over several pool members with scale out. See Configure the VMware resource pool and Scale out a vCenter connection.
  4. Reduce logging. If debug logging is still on from an earlier support case, turn it off. See Enable debug logging for the VMware MP.
  5. If the service keeps crashing, collect the crash events and the output of Gather information for a support ticket, and contact OpsLogix support.

See the state of the service in SCOM

Each collector service is an object in SCOM, under OpsLogix > VMware > VMware Collector > State VMware Collector Service. In Health Explorer, the monitor Service Running State (under Availability) shows whether the Windows service is running. It raises an alert by default when the service stops.

Verify it worked

The service keeps running, no new crash events appear in the Application log, and the license monitor returns to Healthy at its next check (it runs once a day).

See also