ScardGetStatusChange() API May Cause Deadlock in Smart Card Resource Manager (235899)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q235899 SYMPTOMS
The Smart Card Resource Manager may stop responding (hang) in the following
situation:
There are two processes (A and B) each with a single thread gaining access
to the same card (in the same reader) simultaneously. Each of the processes
runs the following sequence in a finite loop:
SCardEstablishContext
SCardConnect
SCardGetStatusChange(SCARD_STATE_UNWARE,.....)
SCardBeginTransaction
SCARDTransmit (many times)
.....
SCardEndTransaction
SCardDisconnect
SCardReleaseContext
The two processes run exactly the same code. After running the code for
several minutes (from 2 to 15 minutes), the two processes hang and no
other program may be able to gain access to the same reader. However,
another reader connected to the system can be accessed through the
Resource manager.
Even if you are forced to quit the two programs, the reader is still
inaccessible. To "unblock" the reader, the computer must either be
restarted or you must quit the Resource Manager program through a
utility like Pview.exe. You can also use Task Manager and then restart
Resource Manager. If you quit then restart Resource Manager, the two
other programs are immediately unblocked. RESOLUTIONWindows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual software update. For information on obtaining the
latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft
Product Support Services. For a complete list of Microsoft Product Support
Services phone numbers and information on support costs, please go to the
following address on the World Wide Web:
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB235899 |
---|
|