An access violation occurs in the Message Queuing Replication service during initialization

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
An access violation occurs in the Microsoft Message Queuing Replication service during initialization. The following error message is reported:
Internal Server Error
CAUSE
The Message Queuing Replication service stops responding because a memory pointer is deleted two times.
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.

Restart Requirement

You must restart your computer after you apply this hotfix.

File Information

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   -----------------------------------------------------------   19-Jun-2003  17:22  5.0.0.778         281,360  Mq1repl.dll         17-Jun-2003  14:33  5.0.0.778          14,096  Mq1sync.exe         26-Mar-2003  13:27  5.0.0.774          75,536  Mqac.sys   19-Jun-2003  17:22  5.0.0.773         217,360  Mqads.dll           30-Oct-2002  13:43  5.0.0.761          25,360  Mqbkup.exe          19-Jun-2003  17:22  5.0.0.778          76,560  Mqdscli.dll         19-Jun-2003  17:22  5.0.0.773          42,256  Mqdssrv.dll         21-Oct-2002  17:31  5.0.0.759          98,064  Mqmig.exe           19-Jun-2003  17:22  5.0.0.759         265,488  Mqmigrat.dll        19-Jun-2003  17:22  5.0.0.740         222,480  Mqoa.dll            19-Jun-2003  17:22  5.0.0.762           8,464  Mqperf.dll          19-Jun-2003  17:22  5.0.0.778         428,816  Mqqm.dll            19-Jun-2003  17:22  5.0.0.778         102,672  Mqrt.dll            19-Jun-2003  17:22  5.0.0.776          70,928  Mqsec.dll           19-Jun-2003  17:22  5.0.0.769         400,656  Mqsnap.dll          19-Jun-2003  17:22  5.0.0.762          23,824  Mqupgrd.dll         19-Jun-2003  17:22  5.0.0.778         110,864  Mqutil.dll          19-Jun-2003  17:22  5.0.0.748          64,784  Msmq.cpl


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
This problem only occurs if the Message Queuing client is installed on a Windows NT 4.0 Microsoft Message Queuing site.
MSMQ
Properties

Article ID: 822727 - Last Review: 02/27/2014 18:44:13 - Revision: 3.3

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