TAPISRV.EXE Thread Uses Excessive CPU Time

 Last reviewed: January 20, 1998
Article ID: Q154387
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 4.0
  • Microsoft Windows NT Server versions 4.0

SYMPTOMS

A thread in Tapisrv.exe begins using an excessive amount of processor time (as much as 95% to 100%) when you run a TAPI server application under a heavy load of phone calls.

CAUSE

This problem occurs when the thread that is using all the processor time has become stuck in an infinite loop due to a problem in the ring management code.

RESOLUTION

To resolve this problem, obtain the following fix or wait for the next Windows NT service pack.

This fix should have the following time stamp: 

   10/24/97  02:51p            220,944 Tapisrv.exe  (Alpha)
   10/24/97  02:19p            141,072 Tapisrv.exe  (Intel)
NOTE: This hotfix requires TAPI 2.1. Applying this hotfix with a previous version of TAPI may cause unpredictable behavior.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Additional query words: 4.00
Keywords : kbbug4.00 kbfix4.00 NTSrvWkst ntutil kbenv kbtool
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbpatch

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.