Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot reuse a virtual channel handle after you disconnect and then reconnect a Terminal Services session that is established on a Windows Server 2008-based terminal server


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You establish a Terminal Services session on a Windows Server 2008-based terminal server.
  • You create a virtual channel handle on the Terminal Services session by using the Citrix Virtual Channel SDK or by using the Terminal Services API.
  • You keep the virtual channel handle open after you disconnect the Terminal Services session. Later, you reconnect the Terminal Services session.
  • You call the WriteFile function by using the virtual channel handle.
In this scenario, the WriteFile function fails. Additionally, when you call the GetLastError function, it returns an instance of error 1 (ERROR_INVALID_FUNCTION).

This problem affects applications that use virtual channels in Terminal Services sessions.

↑ Back to the top


Cause

When the virtual channel transfers from the old session to the new session, Terminal Services does not verify that the virtual channel already exists in the new session.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2008, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Agp440.sys6.0.6001.2215456,37610-Apr-200805:05x86
Amdagp.sys6.0.6001.2215457,40010-Apr-200805:05x86
Isapnp.sys6.0.6001.2215449,72010-Apr-200805:05x86
Machine.infNot Applicable288,44410-Apr-200800:13Not Applicable
Msisadrv.sys6.0.6001.2215416,44010-Apr-200805:05x86
Mssmbios.sys6.0.6001.2215431,28810-Apr-200805:05x86
Nv_agp.sys6.0.6001.22154109,11210-Apr-200805:06x86
Pci.sys6.0.6001.22154151,09610-Apr-200805:06x86
Rdpdr.sys6.0.6001.22154248,83210-Apr-200803:07x86
Sisagp.sys6.0.6001.2215455,86410-Apr-200805:08x86
Streamci.dll6.0.6001.2215425,14410-Apr-200805:08x86
Swenum.sys6.0.6001.2215415,28810-Apr-200805:08Not Applicable
Termdd.sys6.0.6001.2215454,32810-Apr-200805:08x86
Uliagpkx.sys6.0.6001.2215460,98410-Apr-200805:08x86
Viaagp.sys6.0.6001.2215456,88810-Apr-200805:08x86
Volmgr.sys6.0.6001.2215452,79210-Apr-200805:08x86
Windows Server 2008, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Agp460.sys6.0.6001.22154136,70410-Apr-200802:43IA-64
Isapnp.sys6.0.6001.2215437,43210-Apr-200805:27IA-64
Machine.infNot Applicable270,75810-Apr-200800:10Not Applicable
Msisadrv.sys6.0.6001.2215425,14410-Apr-200805:27IA-64
Mssmbios.sys6.0.6001.2215457,40010-Apr-200805:27IA-64
Pci.sys6.0.6001.22154439,86410-Apr-200805:29IA-64
Rdpdr.sys6.0.6001.22154709,63210-Apr-200803:38IA-64
Streamci.dll6.0.6001.2215446,13610-Apr-200805:23IA-64
Swenum.sys6.0.6001.2215419,25610-Apr-200805:23Not Applicable
Termdd.sys6.0.6001.22154156,21610-Apr-200805:23IA-64
Volmgr.sys6.0.6001.22154148,53610-Apr-200805:23IA-64
Windows Server 2008, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Agp440.sys6.0.6001.2215464,56810-Apr-200805:40x64
Isapnp.sys6.0.6001.2215423,60810-Apr-200805:39x64
Machine.infNot Applicable276,56410-Apr-200800:12Not Applicable
Msisadrv.sys6.0.6001.2215417,97610-Apr-200805:39x64
Mssmbios.sys6.0.6001.2215434,87210-Apr-200805:39x64
Nv_agp.sys6.0.6001.22154126,52010-Apr-200805:41x64
Pci.sys6.0.6001.22154179,76810-Apr-200805:42x64
Rdpdr.sys6.0.6001.22154314,36810-Apr-200803:40x64
Streamci.dll6.0.6001.2215426,68010-Apr-200805:37x64
Swenum.sys6.0.6001.2215415,54410-Apr-200805:37x64
Termdd.sys6.0.6001.2215463,54410-Apr-200805:37x64
Uliagpkx.sys6.0.6001.2215468,15210-Apr-200805:37x64
Volmgr.sys6.0.6001.2215468,66410-Apr-200805:37x64

↑ Back to the top


Workaround

To work around this problem, close and then reopen the virtual channel every time that you establish a new Terminal Services session.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbbug, kbfix, kbhotfixserver, kbqfe, KB950118

↑ Back to the top

Article Info
Article ID : 950118
Revision : 2
Created on : 5/28/2008
Published on : 5/28/2008
Exists online : False
Views : 227