TAPI Enters an Infinite Loop State and Does Not Signal an Event That Is Expected by a Program (295385)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Professional SP1
This article was previously published under Q295385 SYMPTOMS
Under some conditions, programs that use third-party TAPI service providers may stop responding (hang).
CAUSE
This problem can occur if TAPI is incorrectly processing the LINEDEVSTATE_MSGWAITON and LINEDEVSTATE_MSGWAIT messages. When TAPI calls the lineSetLineDevStatus function instead of signaling the appropriate event interface, an unexpected call is made into the TSP, and the program that expects the event never receives it.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
---------------------------------------------------------
5/31/2001 07:22p 5.0.2195.3661 375,568 Tapi3.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
| Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbenv kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB295385 |
|---|
|