Article ID: 821653
Article Last Modified on 10/25/2005
APPLIES TO
- Microsoft Message Queuing 2.0
SYMPTOMS
Microsoft Message Queuing (also known as MSMQ) messages may not be sent if both of the following conditions are true:
- The send permissions for the Everyone group on a public queue have been removed.
- The user who sends the messages belongs to too many groups.
Note The number of the groups may vary.
CAUSE
This problem occurs because a buffer that was passed in a call to NetUserGetGroups was too small for users in many groups.
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. The English version of this fix 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 -------------------------------------------------------------- 28-May-2003 22:39 5.3.16.5 630,832 Windows2000-kb821653-x86-enu-symbols.exe 28-May-2003 22:39 5.3.16.5 987,184 Windows2000-kb821653-x86-enu.exe 28-May-2003 20:52 5.0.0.766 281,360 Mq1repl.dll 04-Feb-2003 15:51 5.0.0.766 14,096 Mq1sync.exe 26-Mar-2003 16:27 5.0.0.774 75,536 Mqac.sys 28-May-2003 20:52 5.0.0.773 217,360 Mqads.dll 30-Oct-2002 16:43 5.0.0.761 25,360 Mqbkup.exe 28-May-2003 20:52 5.0.0.750 76,560 Mqdscli.dll 28-May-2003 20:52 5.0.0.773 42,256 Mqdssrv.dll 21-Oct-2002 20:31 5.0.0.759 98,064 Mqmig.exe 28-May-2003 20:52 5.0.0.759 265,488 Mqmigrat.dll 28-May-2003 20:52 5.0.0.740 222,480 Mqoa.dll 28-May-2003 20:52 5.0.0.762 8,464 Mqperf.dll 28-May-2003 20:52 5.0.0.777 428,304 Mqqm.dll 28-May-2003 20:52 5.0.0.776 102,672 Mqrt.dll 28-May-2003 20:52 5.0.0.776 70,928 Mqsec.dll 28-May-2003 20:52 5.0.0.769 400,656 Mqsnap.dll 28-May-2003 20:52 5.0.0.762 23,824 Mqupgrd.dll 28-May-2003 20:52 5.0.0.767 110,352 Mqutil.dll 28-May-2003 20:52 5.0.0.748 64,784 Msmq.cpl
WORKAROUND
To work around this problem, reduce the number of groups to which the user belongs.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
If Message Queuing logging is enabled, the following information is logged in the Message Queuing log:
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
Keywords: kbbug kbfix kbqfe kbwin2000presp5fix kbhotfixserver KB821653
