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

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

Article ID : 950118
Last Review : May 28, 2008
Revision : 1.0
On This Page

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, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)

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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The Hotfix download available section and the online request forms display 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 name File version File size Date Time Platform
Agp440.sys 6.0.6001.22154 56,376 10-Apr-2008 05:05 x86
Amdagp.sys 6.0.6001.22154 57,400 10-Apr-2008 05:05 x86
Isapnp.sys 6.0.6001.22154 49,720 10-Apr-2008 05:05 x86
Machine.inf Not Applicable 288,444 10-Apr-2008 00:13 Not Applicable
Msisadrv.sys 6.0.6001.22154 16,440 10-Apr-2008 05:05 x86
Mssmbios.sys 6.0.6001.22154 31,288 10-Apr-2008 05:05 x86
Nv_agp.sys 6.0.6001.22154 109,112 10-Apr-2008 05:06 x86
Pci.sys 6.0.6001.22154 151,096 10-Apr-2008 05:06 x86
Rdpdr.sys 6.0.6001.22154 248,832 10-Apr-2008 03:07 x86
Sisagp.sys 6.0.6001.22154 55,864 10-Apr-2008 05:08 x86
Streamci.dll 6.0.6001.22154 25,144 10-Apr-2008 05:08 x86
Swenum.sys 6.0.6001.22154 15,288 10-Apr-2008 05:08 Not Applicable
Termdd.sys 6.0.6001.22154 54,328 10-Apr-2008 05:08 x86
Uliagpkx.sys 6.0.6001.22154 60,984 10-Apr-2008 05:08 x86
Viaagp.sys 6.0.6001.22154 56,888 10-Apr-2008 05:08 x86
Volmgr.sys 6.0.6001.22154 52,792 10-Apr-2008 05:08 x86
Windows Server 2008, Itanium-based versions
File name File version File size Date Time Platform
Agp460.sys 6.0.6001.22154 136,704 10-Apr-2008 02:43 IA-64
Isapnp.sys 6.0.6001.22154 37,432 10-Apr-2008 05:27 IA-64
Machine.inf Not Applicable 270,758 10-Apr-2008 00:10 Not Applicable
Msisadrv.sys 6.0.6001.22154 25,144 10-Apr-2008 05:27 IA-64
Mssmbios.sys 6.0.6001.22154 57,400 10-Apr-2008 05:27 IA-64
Pci.sys 6.0.6001.22154 439,864 10-Apr-2008 05:29 IA-64
Rdpdr.sys 6.0.6001.22154 709,632 10-Apr-2008 03:38 IA-64
Streamci.dll 6.0.6001.22154 46,136 10-Apr-2008 05:23 IA-64
Swenum.sys 6.0.6001.22154 19,256 10-Apr-2008 05:23 Not Applicable
Termdd.sys 6.0.6001.22154 156,216 10-Apr-2008 05:23 IA-64
Volmgr.sys 6.0.6001.22154 148,536 10-Apr-2008 05:23 IA-64
Windows Server 2008, x64-based versions
File name File version File size Date Time Platform
Agp440.sys 6.0.6001.22154 64,568 10-Apr-2008 05:40 x64
Isapnp.sys 6.0.6001.22154 23,608 10-Apr-2008 05:39 x64
Machine.inf Not Applicable 276,564 10-Apr-2008 00:12 Not Applicable
Msisadrv.sys 6.0.6001.22154 17,976 10-Apr-2008 05:39 x64
Mssmbios.sys 6.0.6001.22154 34,872 10-Apr-2008 05:39 x64
Nv_agp.sys 6.0.6001.22154 126,520 10-Apr-2008 05:41 x64
Pci.sys 6.0.6001.22154 179,768 10-Apr-2008 05:42 x64
Rdpdr.sys 6.0.6001.22154 314,368 10-Apr-2008 03:40 x64
Streamci.dll 6.0.6001.22154 26,680 10-Apr-2008 05:37 x64
Swenum.sys 6.0.6001.22154 15,544 10-Apr-2008 05:37 x64
Termdd.sys 6.0.6001.22154 63,544 10-Apr-2008 05:37 x64
Uliagpkx.sys 6.0.6001.22154 68,152 10-Apr-2008 05:37 x64
Volmgr.sys 6.0.6001.22154 68,664 10-Apr-2008 05:37 x64

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


APPLIES TO
• Windows Server 2008 Standard
• Windows Server 2008 Enterprise
• Windows Server 2008 Datacenter
• Windows Server 2008 Datacenter without Hyper-V
• Windows Server 2008 Enterprise without Hyper-V
• Windows Server 2008 for Itanium-Based Systems
• Windows Server 2008 Standard without Hyper-V

Back to the top

Keywords: 
kbautohotfix kbexpertiseinter kbbug kbfix kbhotfixserver kbqfe KB950118

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image

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

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

Article ID : 950118
Last Review : May 28, 2008
Revision : 1.1
On This Page

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:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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 name File version File size Date Time Platform
Agp440.sys 6.0.6001.22154 56,376 10-Apr-2008 05:05 x86
Amdagp.sys 6.0.6001.22154 57,400 10-Apr-2008 05:05 x86
Isapnp.sys 6.0.6001.22154 49,720 10-Apr-2008 05:05 x86
Machine.inf Not Applicable 288,444 10-Apr-2008 00:13 Not Applicable
Msisadrv.sys 6.0.6001.22154 16,440 10-Apr-2008 05:05 x86
Mssmbios.sys 6.0.6001.22154 31,288 10-Apr-2008 05:05 x86
Nv_agp.sys 6.0.6001.22154 109,112 10-Apr-2008 05:06 x86
Pci.sys 6.0.6001.22154 151,096 10-Apr-2008 05:06 x86
Rdpdr.sys 6.0.6001.22154 248,832 10-Apr-2008 03:07 x86
Sisagp.sys 6.0.6001.22154 55,864 10-Apr-2008 05:08 x86
Streamci.dll 6.0.6001.22154 25,144 10-Apr-2008 05:08 x86
Swenum.sys 6.0.6001.22154 15,288 10-Apr-2008 05:08 Not Applicable
Termdd.sys 6.0.6001.22154 54,328 10-Apr-2008 05:08 x86
Uliagpkx.sys 6.0.6001.22154 60,984 10-Apr-2008 05:08 x86
Viaagp.sys 6.0.6001.22154 56,888 10-Apr-2008 05:08 x86
Volmgr.sys 6.0.6001.22154 52,792 10-Apr-2008 05:08 x86
Windows Server 2008, Itanium-based versions
File name File version File size Date Time Platform
Agp460.sys 6.0.6001.22154 136,704 10-Apr-2008 02:43 IA-64
Isapnp.sys 6.0.6001.22154 37,432 10-Apr-2008 05:27 IA-64
Machine.inf Not Applicable 270,758 10-Apr-2008 00:10 Not Applicable
Msisadrv.sys 6.0.6001.22154 25,144 10-Apr-2008 05:27 IA-64
Mssmbios.sys 6.0.6001.22154 57,400 10-Apr-2008 05:27 IA-64
Pci.sys 6.0.6001.22154 439,864 10-Apr-2008 05:29 IA-64
Rdpdr.sys 6.0.6001.22154 709,632 10-Apr-2008 03:38 IA-64
Streamci.dll 6.0.6001.22154 46,136 10-Apr-2008 05:23 IA-64
Swenum.sys 6.0.6001.22154 19,256 10-Apr-2008 05:23 Not Applicable
Termdd.sys 6.0.6001.22154 156,216 10-Apr-2008 05:23 IA-64
Volmgr.sys 6.0.6001.22154 148,536 10-Apr-2008 05:23 IA-64
Windows Server 2008, x64-based versions
File name File version File size Date Time Platform
Agp440.sys 6.0.6001.22154 64,568 10-Apr-2008 05:40 x64
Isapnp.sys 6.0.6001.22154 23,608 10-Apr-2008 05:39 x64
Machine.inf Not Applicable 276,564 10-Apr-2008 00:12 Not Applicable
Msisadrv.sys 6.0.6001.22154 17,976 10-Apr-2008 05:39 x64
Mssmbios.sys 6.0.6001.22154 34,872 10-Apr-2008 05:39 x64
Nv_agp.sys 6.0.6001.22154 126,520 10-Apr-2008 05:41 x64
Pci.sys 6.0.6001.22154 179,768 10-Apr-2008 05:42 x64
Rdpdr.sys 6.0.6001.22154 314,368 10-Apr-2008 03:40 x64
Streamci.dll 6.0.6001.22154 26,680 10-Apr-2008 05:37 x64
Swenum.sys 6.0.6001.22154 15,544 10-Apr-2008 05:37 x64
Termdd.sys 6.0.6001.22154 63,544 10-Apr-2008 05:37 x64
Uliagpkx.sys 6.0.6001.22154 68,152 10-Apr-2008 05:37 x64
Volmgr.sys 6.0.6001.22154 68,664 10-Apr-2008 05:37 x64

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


APPLIES TO
• Windows Server 2008 Standard
• Windows Server 2008 Enterprise
• Windows Server 2008 Datacenter
• Windows Server 2008 Datacenter without Hyper-V
• Windows Server 2008 Enterprise without Hyper-V
• Windows Server 2008 for Itanium-Based Systems
• Windows Server 2008 Standard without Hyper-V

Back to the top

Keywords: 
kbautohotfix kbexpertiseinter kbbug kbfix kbhotfixserver kbqfe KB950118

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image