Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > ipMonitor > Unexpected disconnection from remote device

Unexpected disconnection from remote device

Created by Chris Foley, last modified by MindTouch on Jun 23, 2016

Views: 111 Votes: 0 Revisions: 7


This article describes an issue where WMI-based monitors intermittently fail with the following error:


Unexpected disconnection from remote device.


  • All ipMonitor versions 
  • All Windows versions 


This is due to issues with the wmiprvse.exe process on the target system running out of resources and halting.


There are several workaround options for this issue:

  1. Download and install any/all available HotFixes for wmiprvse.exe from Microsoft.
  2. Configure the Monitors to use SNMP instead:
    1. Open the Settings page for the Monitor.
    2. Set the Communication Type to SNMP.
    3. Enter the required SNMP Community string.
    4. Click Select, which forces a rediscovery of the resources using SNMP.
    5. Select the resource the Monitor was monitoring and then click Apply.
  3. Configure the Monitors with Accumulated failures per Alert to two or higher. Configure a Warn timing setting to 30 seconds or lower. As a result, when a failure is detected, the Monitor runs a test again before triggering alerts.
    1. Open the Settings page for the Monitor.
    2. Open the Timing section and set the Warn (failures but not alerting) field to 30.
    3. Open the Notification Control section and set the Accumulated failures per Alert to two or higher.
    4. Click OK.
Last modified
19:38, 22 Jun 2016