TAPI Is Not Terminal Services Aware (308405)
The information in this article applies to:
- Microsoft Windows Server 2003, 64-Bit Datacenter Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows XP 64-Bit Edition Version 2003
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
- Microsoft Server Appliance Kit (SAK), version 2.0
This article was previously published under Q308405 SYMPTOMS Programs that control telephone systems through a serial
interface (COM port) may not work when using Terminal Services.
Even
though you can redirect a COM port to the client in the user session, a
Telephony Application Programming Interface (TAPI) Telephone Service Provider
(TSP) cannot access the COM port. CAUSE This problem occurs because TAPI and the TSPs run as
services in Windows 2000 and TSPs cannot access COM ports that are mapped in a
user session. Therefore, the services run in a different logon session than the
user programs.
Redirected COM ports are mapped in the per-session
object name space. For more information about this behavior, view the section about
"Kernel Object Name Spaces" in the "Platform SDK: Terminal Services" Microsoft
Developer Network (MSDN) chapter. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.MORE INFORMATIONBecause of the infrastructure in the TAPI architecture, a TSP cannot be Terminal Services aware. There is no existing way to implement a TSP that is Terminal Services aware.
| Modification Type: | Major | Last Reviewed: | 11/22/2004 |
|---|
| Keywords: | kbenv kbprb KB308405 |
|---|
|