Problems Using TAPI 2.1

ID: Q179187

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Server, Enterprise Edition version 4.0
Microsoft Windows NT Server version 4.0, Terminal Server Edition

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.

RESOLUTION

To 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, please see the following article in the Microsoft Knowledge Base:

Q152734 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.

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/tapi21-fix/

STATUS

Microsoft has confirmed this to be 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.

Additional query words: 4.00

Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4 NTSrvWkst
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug