Article ID: 899470 - Last Review: March 23, 2007 - Revision: 2.4

FIX: Message Queuing 3.0 may generate excessive network traffic when you try to connect to a remote computer that is offline

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows registry

On This Page

Expand all | Collapse all

SYMPTOMS

In Microsoft Windows Server 2003, when you try to connect Microsoft Message Queuing 3.0 to a remote computer, Message Queuing 3.0 may generate excessive network traffic. This problem occurs when the remote computer is offline.
Back to the top

CAUSE

By default, Message Queuing 3.0 tries to connect to an offline remote computer every 5 seconds.
Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100  (http://support.microsoft.com/kb/889100/ ) How to obtain the latest service pack for Windows Server 2003
Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed on the computer.

Restart requirement

You must restart the 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
   --------------------------------------------------------
   11-May-2005  22:00  5.2.1916.1807   90,520  Mqac.sys
   11-May-2005  22:00  5.2.1916.1807  161,688  Mqad.dll         
   11-May-2005  22:00  5.2.1916.1807  207,256  Mqads.dll        
   11-May-2005  22:01  5.2.1916.1807   36,248  Mqbkup.exe       
   11-May-2005  22:00  5.2.1916.1807   15,768  Mqcertui.dll     
   11-May-2005  22:00  5.2.1916.1807   86,424  Mqclus.dll       
   11-May-2005  22:00  5.2.1916.1807   39,320  Mqdbodbc.dll     
   11-May-2005  22:00  5.2.1916.1807   56,216  Mqdscli.dll      
   11-May-2005  22:00  5.2.1916.1807   58,264  Mqdssrv.dll      
   11-May-2005  22:00  5.2.1916.1807   73,624  Mqdssvc.exe      
   11-May-2005  22:01  5.2.1916.1807   53,144  Mqgentr.dll      
   11-May-2005  22:00  5.2.1916.1807   35,736  Mqise.dll        
   11-May-2005  22:00  5.2.1916.1807   48,024  Mqmig.exe        
   11-May-2005  22:00  5.2.1916.1807  230,296  Mqmigrat.dll     
   11-May-2005  22:00  5.2.1916.1807  246,680  Mqoa.dll         
   11-May-2005  21:59  5.2.1916.1807   88,472  Mqoa.tlb
   11-May-2005  21:59  5.2.1916.1807   43,416  Mqoa10.tlb
   11-May-2005  21:59  5.2.1916.1807   61,848  Mqoa20.tlb
   11-May-2005  22:00  5.2.1916.1807   22,424  Mqperf.dll       
   10-May-2005  00:44                  10,110  Mqperf.ini
   10-May-2005  00:44                   2,755  Mqprfsym.h
   11-May-2005  22:00  5.2.1916.1807  841,112  Mqqm.dll         
   11-May-2005  22:00  5.2.1916.1807  186,776  Mqrt.dll         
   11-May-2005  22:00  5.2.1916.1807  131,992  Mqrtdep.dll      
   11-May-2005  22:00  5.2.1916.1807  148,888  Mqsec.dll        
   11-May-2005  22:00  5.2.1916.1807  546,200  Mqsnap.dll       
   10-May-2005  00:44                  33,171  Mqsnap.hlp
   11-May-2005  22:00  5.2.1916.1807   14,744  Mqsvc.exe        
   10-May-2005  00:45                     353  Mqsysoc.inf
   11-May-2005  22:01  5.2.1916.1807   40,856  Mqtgclus.dll     
   10-May-2005  00:45                      41  Mqtgsvc.cfg
   11-May-2005  22:01  5.2.1916.1807   92,568  Mqtgsvc.exe      
   11-May-2005  22:01  5.2.1916.1807  146,840  Mqtrig.dll       
   11-May-2005  22:01  5.2.1916.1807   60,312  Mqupgrd.dll      
   11-May-2005  22:00  5.2.1916.1807  427,928  Mqutil.dll       
   10-May-2005  00:44                 565,728  Msmqcons.chm
   10-May-2005  00:44                 483,199  Msmqconw.chm
   11-May-2005  22:01  5.2.1916.1807  258,968  Msmqocm.dll      
   10-May-2005  00:45                   6,846  Msmqocms.inf
   10-May-2005  00:45                   6,061  Msmqocmw.inf
   10-May-2005  00:44                  21,026  Msmqs.chm
   10-May-2005  00:45                   8,978  Msmqtrc.mof
   10-May-2005  00:44                  72,885  Msmqw.chm
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
Back to the top

MORE INFORMATION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you apply this hotfix, you can use the following DWORD registry entry to change the connection retry interval time:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSMQ\Parameters\TryConnectInterval
To change the connection retry interval time, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\MSMQ\Parameters
  3. On the Edit menu, click New, and then click DWORD Value.
  4. Type TryConnectInterval, and then press ENTER.
  5. Right-click TryConnectInterval, and then click Modify.
  6. In the Edit DWORD Value dialog box, type the time in milliseconds that you want for the connection retry interval time, and then click OK.

    Note For example, type 10000 for 10 seconds.
  7. On the File menu, click Exit.
For more information about the TryConnectInterval registry entry in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
303293  (http://support.microsoft.com/kb/303293/ ) You cannot establish a session on slow networks with latency delays that are longer than one minute
For more information about the terminology that Microsoft uses when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft Message Queuing 3.0, when used with:
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
    • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Back to the top
Keywords: 
kbautohotfix kbhotfixserver kbwinserv2003sp2fix kbqfe kbbug kbfix kbprb KB899470
Back to the top