Problems Using TAPI 2.1 (179187)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Server, Enterprise Edition 4.0
This article was previously published under Q179187 SYMPTOMS
You may experience one or more of the following problems while using TAPI
2.1:
- The data an application provides for lineSetCallData is lost when Remote
TSP is used.
- TAPISRV becomes unresponsive and CPU utilization peaks at 100%.
- TAPISRV cannot be started when RAS or another Windows NT Service starts
TAPI.
- TAPISRV causes an Access Violation error message when calling Agent
functions such as lineAgentSpecific and lineGetAgentActivityList.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or 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
NOTE: This hotfix requires TAPI 2.1. Applying this hotfix with a previous
version of TAPI may cause unpredictable behavior.
For your convenience, the English version of this post-SP3 hotfix has been
posted to the following Internet location. However, Microsoft recommends
that you install Windows NT 4.0 Service Pack 4 to correct this problem.
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 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.MORE INFORMATION
Windows NT 4.0 Service Pack 3 includes TAPI 2.0.
| Modification Type: | Major | Last Reviewed: | 6/29/2004 |
|---|
| Keywords: | kbbug kbfix KB179187 |
|---|
|