Corrupted packet causes access violation in Packet Initialization Code (303270)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

This article was previously published under Q303270
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

You may see an access violation in the Microsoft Message Queuing CQMPacket code.

CAUSE

When the Message Queuing Queue Manager processes a corrupted packet, the corrupted offset information can cause it to generate incorrect pointers, resulting in an access violation in the Queue Manager.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date          Time    Version        Size   File name     Platform
   ------------------------------------------------------------------
   May-29-2001   14:22   5.0.0.735    71,120   Mqac.sys      x86
   Jul-26-2001   23:38   5.0.0.735   214,288   Mqads.dll     x86
   Jul-26-2001   23:38   5.0.0.735    41,744   Mqdssrv.dll   x86
   Jul-26-2001   23:38   5.0.0.737   418,064   Mqqm.dll      x86
   Jul-26-2001   23:38   5.0.0.737    91,920   Mqrt.dll      x86
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
This fix adds mandatory checking of the message packet header sections to validate that the sections fall within the bounds of the message packet. If this check fails, the packet is discarded, its storage is freed, and the session is closed. As a result, messages may appear to become "stuck" on the sender computer.

This fix also adds an optional check to examine the sender Queue Manager globally unique identifier (GUID) for a variable number of NULLs. This is controlled by a new registry entry. Having NULLs in a Queue Manager GUID may be valid. You should not implement this optional check unless you know the maximum number of NULLs in any Queue Manager GUID that may send messages.

To implement the Queue Manager GUID NULL check, add the following registry DWORD value, setting it to the maximum number of NULLs that are allowed for a sender Queue Manager GUID.

After you apply this fix, make the following registry key nonzero to turn on the translation feature:

Location: HKLM\Software\Microsoft\MSMQ\Parameters
Value: NullsInGUID (REG_DWORD)


Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbprb kbQFE KB303270