DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2795543 - Last Review: January 30, 2013 - Revision: 2.0

Symptoms

An application that calls the SignalObjectAndWait and PulseEvent APIs may experience a deadlock in Windows 7 or in Windows Server 2008 R2. If the threads that are signalled by SignalObjectAndWait call PulseEvent to signal the waiting object of the SignalObjectAndWait call, the caller thread of SignalObjectAndWait cannot receive the signal state of the waiting object.

Cause

The Signal and Wait operations are not guaranteed to be performed as atomic operations when an application calls the SignalObjectAndWait function.

Resolution

To resolve this problem, configure the application to call the SetEvent API instead of the PulseEvent API. This method should work in most cases.

Applies to
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows 7 Service Pack 1
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Standard without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Service Pack 1
Keywords: 
KB2795543
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support