Article ID: 311482
Article Last Modified on 2/22/2007
APPLIES TO
- Microsoft Message Queuing 2.0
This article was previously published under Q311482
SYMPTOMS
A remote access service (RAS) thread runs in an infinite loop on a workgroup installation.
CAUSE
When the Microsoft Message Queuing, also known as MSMQ, 2.0 service starts, it starts a thread that waits for RAS notification. This is part of the topology mechanism that enables Message Queuing 2.0 to find the present site and connection. When Message Queuing 2.0 finds its present site, it closes this thread. When you use a workgroup configuration, you do not run the topology code, but the RAS thread is created and never shuts down.
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
-------------------------------------------------------
Jul-27-2001 12:38 5.0.0.720 278,800 Mq1repl.dll
May-29-2001 15:22 5.0.0.720 14,096 Mq1sync.exe
May-29-2001 15:22 5.0.0.735 71,120 Mqac.sys
Jul-27-2001 12:38 5.0.0.735 214,288 Mqads.dll
May-29-2001 15:23 5.0.0.720 21,776 Mqbkup.exe
Jul-27-2001 12:38 5.0.0.720 29,456 Mqcertui.dll
Jul-27-2001 12:38 5.0.0.720 49,424 Mqclus.dll
Jul-27-2001 12:38 5.0.0.720 29,968 Mqdbodbc.dll
Jul-27-2001 12:38 5.0.0.720 75,536 Mqdscli.dll
Jul-27-2001 12:38 5.0.0.735 41,744 Mqdssrv.dll
May-29-2001 15:23 5.0.0.720 98,064 Mqmig.exe
Jul-27-2001 12:38 5.0.0.720 263,952 Mqmigrat.dll
Jul-27-2001 12:38 5.0.0.720 223,504 Mqoa.dll
Jul-27-2001 12:38 5.0.0.720 7,952 Mqperf.dll
Jul-27-2001 12:38 5.0.0.737 418,064 Mqqm.dll
Jul-27-2001 12:38 5.0.0.720 8,464 Mqrperf.dll
Jul-27-2001 12:38 5.0.0.737 91,920 Mqrt.dll
Jul-27-2001 12:38 5.0.0.720 70,416 Mqsec.dll
Jul-27-2001 12:38 5.0.0.720 400,144 Mqsnap.dll
May-29-2001 15:23 5.0.0.720 14,096 Mqsvc.exe
Jul-27-2001 12:38 5.0.0.720 24,336 Mqupgrd.dll
Jul-27-2001 12:38 5.0.0.737 108,304 Mqutil.dll
Jul-27-2001 12:38 5.0.0.720 64,784 Msmq.cpl
Jul-27-2001 12:38 5.0.0.720 159,504 Msmqocm.dll
STATUS
Microsoft has confirmed that this is a problem in Message Queuing 2.0.
MORE INFORMATION
The purpose of the RAS thread is to find the Internet Protocol (IP) address of the RAS server, so the topology code does not perform a broadcast call, but rather checks for a specific address. The RAS thread and the RAS notification is not needed in Workgroup mode.
Keywords: kbprb kbqfe KB311482
