Remote Desktop Connection software may cause an access violation if FilterQueueType is set

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

This article was previously published under Q329756

SYMPTOMS

The Terminal Services Advanced Client software (or Microsoft Internet Explorer if it is hosting the Terminal Services Advanced Client ActiveX control) may experience a general protection fault if you have set the FilterQueueType registry key to 7 as described in the following Microsoft Knowledge Base article:

302361 (http://support.microsoft.com/kb/302361/EN-US/ ) Multifunction Printers That Use DOT4 Ports Are Not Redirected By Using Remote Desktop

Back to the top

CAUSE

Although a null value is valid for a network port name, the client software does not handle this condition correctly.

Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 (http://support.microsoft.com/kb/322389/EN-US/ ) How to obtain the latest Windows XP service pack

Back to the top

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.The English version of this hotfix has the file attributes (or later) 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    Service pack
   ---------------------------------------------------------------------
   07-Nov-2002  17:14  5.1.2600.105   503,808  Mstscax.dll  none
   07-Nov-2002  20:34  5.1.2600.1137  599,552  Mstscax.dll  SP1

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. This problem was first corrected in Microsoft Windows XP Service Pack 2.

Back to the top

MORE INFORMATION

If Dr Watson-enabled symbols are installed on the computer, the register state and the call stack in the Drwtsn32.log file or in the debugger are similiar to:

   0:008> r
   eax=00000000 ebx=00000007 ecx=00000000 edx=5fdd855c esi=5fdfb470 edi=00000000
   eip=5fdeff8c esp=010afc84 ebp=010afc90 iopl=0         nv up ei pl zr na po nc
   cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00010246
   mstscax!_wcsnicmp+35:
   5fdeff8c 668b01           mov     ax,[ecx]              ds:0023:00000000=????

   ChildEBP RetAddr  
   010afc90 5fdd85ac mstscax!_wcsnicmp+0x35
   010afcb0 5fdd9067 mstscax!W32DrAutoPrn::ShouldAddThisPrinter+0x32
   010aff34 5fdd95f6 mstscax!W32DrAutoPrn::Enumerate+0x1d5
   010aff54 5fdd97f7 mstscax!W32ProcObj::AnnounceDevicesToServerFunc+0x46
   010aff5c 5fdd9815 mstscax!W32ProcObj::_AnnounceDevicesToServerFunc+0xd
   010aff74 5fdd99c1 mstscax!W32ProcObj::DispatchAsyncIORequest_Private+0x19
   010aff80 5fdd970c mstscax!W32ProcObj::_DispatchAsyncIORequest_Private+0x11
   010aff98 5fdd997a mstscax!W32ProcObj::CheckForQueuedOperations+0x12
   010affb0 5fdd99ad mstscax!W32ProcObj::ObjectWorkerThread+0x62
   010affb4 77e802ed mstscax!W32ProcObj::_ObjectWorkerThread+0x9
   010affec 00000000 kernel32!BaseThreadStart+0x37

Back to the top