"Access Violation" error message occurs when Message Queuing connects to a remote server that is running Message Queuing but does not send established packet

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
You receive an "Access Violation" error message when Message Queuing (also known as MSMQ) successfully connects to a remote server that is running Message Queuing (a successful connection of the Windows Sockets API Connect function) but then does not successfully send the established packet (the first packet in the session establishment handshake).
CAUSE
This problem may occur if the session object is freed prematurely during a pending read operation.
RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

You must 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   ---------------------------------------------------   23-Jul-2003  20:11  5.0.0.778  281,360  Mq1repl.dll         17-Jun-2003  14:33  5.0.0.778   14,096  Mq1sync.exe         21-Jul-2003  14:00  5.0.0.779   76,112  Mqac.sys   23-Jul-2003  20:11  5.0.0.773  217,360  Mqads.dll           30-Oct-2002  13:43  5.0.0.761   25,360  Mqbkup.exe          23-Jul-2003  20:11  5.0.0.778   76,560  Mqdscli.dll         23-Jul-2003  20:11  5.0.0.773   42,256  Mqdssrv.dll         21-Oct-2002  17:31  5.0.0.759   98,064  Mqmig.exe           23-Jul-2003  20:11  5.0.0.759  265,488  Mqmigrat.dll        23-Jul-2003  20:11  5.0.0.740  222,480  Mqoa.dll            23-Jul-2003  20:11  5.0.0.762    8,464  Mqperf.dll          23-Jul-2003  20:11  5.0.0.780  428,816  Mqqm.dll            23-Jul-2003  20:11  5.0.0.778  102,672  Mqrt.dll            23-Jul-2003  20:11  5.0.0.776   70,928  Mqsec.dll           23-Jul-2003  20:11  5.0.0.769  400,656  Mqsnap.dll          23-Jul-2003  20:11  5.0.0.762   23,824  Mqupgrd.dll         23-Jul-2003  20:11  5.0.0.778  110,864  Mqutil.dll          23-Jul-2003  20:11  5.0.0.748   64,784  Msmq.cpl
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
Properties

Article ID: 824801 - Last Review: 02/27/2014 18:44:33 - Revision: 4.2

  • Microsoft Message Queuing 2.0
  • kbnosurvey kbarchive kbbug kbfix kbqfe kbwin2000presp5fix kbhotfixserver KB824801
Feedback