Article ID: 832716
Article Last Modified on 4/7/2006
APPLIES TO
- Microsoft Message Queue Server 1.0
SYMPTOMS
Performance may be slow on a Primary Site Controller (PSC) that runs Microsoft Message Queuing. This problem occurs when no relevant business processes are running on the server.
CAUSE
This problem occurs because a memory leak occurs when a server receives a BAD_SIGNATURE non-acknowledgement response to a replication message. When a server that is running Message Queuing receives a BAD_SIGNATURE negative acknowledgement, the number of frames replicated between Message Queuing site controllers increases significantly.
RESOLUTION
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.
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-Sep-2002 02:51 11,163 Crdbsp7.sql 23-Sep-2002 02:50 19,968 Mq2ndnd.exe 02-Jul-2003 02:02 1.0.0.337 61,584 Mqac.sys 23-Sep-2002 02:27 1.0.0.336 34,064 Mqcertui.dll 02-Jul-2003 02:02 1.0.0.337 34,064 Mqdbmgr.dll 02-Jul-2003 02:02 1.0.0.337 59,152 Mqdscli.dll 02-Jul-2003 02:02 1.0.0.337 56,592 Mqdssrv.dll 24-Nov-2003 04:44 1.0.0.338 237,456 Mqis.dll 02-Jul-2003 02:02 1.0.0.337 16,144 Mqkeyhlp.dll 02-Jul-2003 02:02 1.0.0.337 142,096 Mqoa.dll 02-Jul-2003 02:02 1.0.0.337 8,464 Mqperf.dll 02-Jul-2003 02:02 1.0.0.337 509,200 Mqqm.dll 02-Jul-2003 02:02 1.0.0.337 110,352 Mqrt.dll 23-Sep-2002 02:45 1.0.0.336 1,831,320 Mqsetup.dll 02-Jul-2003 02:02 1.0.0.337 14,096 Mqsvc.exe 02-Jul-2003 02:02 1.0.0.337 106,768 Mqutil.dll 23-Sep-2002 02:27 1.0.0.336 62,224 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 additional 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
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 kbqfe kbhotfixserver KB832716
