Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Overlapped I/O operation error in ipMonitor

Overlapped I/O operation error in ipMonitor

Updated October 1, 2018

Overview

When you run monitors in ipMonitor, the monitors fail with the following error message:

Overlapped I/O operation is in progress.

Environment

All ipMonitor versions

Cause

The Windows APIs used for monitoring over WMI is running threads that are trying to use a disk or socket handle that is already in use by another thread. This issue cannot be controlled by ipMonitor.

The Monitors that typically use WMI are resource-based monitors (such as CPU, Memory, Drive Space and Services) and Windows Event Log.

Workaround

 Use SNMP, instead of WMI whenever possible or move ipMonitor to a Windows or Windows Server 2008 system so its APIs can better handle overlapped I/Os that are in progress.

Last modified

Tags

Classifications

Public