Article ID: 843285
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you try to use Remote Desktop Connection (Mstsc.exe), an access violation occurs, and Remote Desktop Connection does not respond as expected. This symptom occurs if either of the following conditions is true:
- You installed Remote Desktop Connection from the Microsoft Windows Server 2003 CD-ROM, and you set the FilterQueueType registry value to 0x7.
- You downloaded Remote Desktop Connection from the Windows Server 2003 Web site, and you set the FilterQueueType registry value to 0x7.
CAUSE
This issue occurs if the network port name for the printer contains a null value. Even though a null value is valid for the network port name, Remote Desktop Web Connection does not correctly handle this condition.
RESOLUTION
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, 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:
Note If additional issues occur or 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:
Prerequisites
No prerequisites are required.
Restart requirement
You do not have to restart your 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 tool in Control Panel.
Date Time Version Size File name ---------------------------------------------------------- 19-Jul-2004 09:49 5.2.3790.193 400,384 Mstsc.exe 19-Jul-2004 09:49 5.2.3790.193 681,472 Mstscax.dll
WORKAROUND
To work around this problem, do not use the FilterQueueType registry entry.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For additional information, 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
Keywords: kbbug kbfix kbwinserv2003presp1fix kbhotfixserver kbqfe KB843285
