FIX: STI Application Stops Responding When You Try to Use UnLockDevice() to Unlock the Device

Article translations Article translations
Article ID: 323571 - View products that this article applies to.
This article was previously published under Q323571
Expand all | Collapse all

SYMPTOMS

In certain instances, a Still Image Architecture (STI) application that successfully locked a device may stop responding (hang) indefinitely when you use the UnLockDevice method to try to unlock the device.

CAUSE

This problem occurs because the Windows Image Acquisition (WIA) service is deadlocked at this time and cannot process any more WIA or STI requests.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time    Version        Size    File Name
   -----------------------------------------------------
   11-Jun-2002  10:29   5.2.2.8        3,584   Spmsg.dll
   19-Jun-2002  15:48   5.1.2600.48   61,952   Sti.dll
   11-Jun-2002  15:50   5.1.2600.48  314,368   Wiaservc.dll
				

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

MORE INFORMATION

This problem occurs because of a bad assumption about which thread ID the lock belongs to. The WIA service uses the thread ID of the remote procedure call (RPC) instead of the thread ID of the client. Because RPC uses a thread pool, incoming requests may be processed on different threads, which causes the thread ID mismatch.

Properties

Article ID: 323571 - Last Review: September 27, 2005 - Revision: 1.2
APPLIES TO
  • Microsoft Windows XP Professional
Keywords: 
kbbug kbfix kbshell kbqfe kbwinxpsp1fix kbhotfixserver KB323571

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com