Microsoft KB Archive/817076

= How to avoid routing queries with no routing servers in the site =

Article ID: 817076

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Message Queuing 2.0

-



SYMPTOMS
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

When the client determines that the client site does not have any Microsoft Message Queuing, also known as MSMQ, routing servers, it queries for site links and site gates to learn the enterprise topology. This occurs so the client can make all the routing decisions that are typically made by a routing server. The routing algorithm of Message Queuing uses site links and site gates. These are defined in the Active Directory for inter-site routing. When the Message Queuing service creates an inter-site connection, it first tries to find a site gate in the site link. If none exist, Message Queuing tries to send the message directly. If you have thousands of clients, only several domain controllers, and no site gates, the (failed) queries for site gates can adversely affect the performance of the domain controllers.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information
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:

http://support.microsoft.com/contactus/?ws=support

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 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 --  25-Mar-2003  18:00  5.0.0.766         281,360  Mq1repl.dll 04-Feb-2003 15:51  5.0.0.766          14,096  Mq1sync.exe 19-Feb-2003 17:21  5.0.0.769          75,408  Mqac.sys 25-Mar-2003 18:00  5.0.0.773         217,360  Mqads.dll 30-Oct-2002 16:43  5.0.0.761          25,360  Mqbkup.exe 25-Mar-2003 18:00  5.0.0.750          76,560  Mqdscli.dll 25-Mar-2003 18:00  5.0.0.773          42,256  Mqdssrv.dll 21-Oct-2002 20:31  5.0.0.759          98,064  Mqmig.exe 25-Mar-2003 18:00  5.0.0.759         265,488  Mqmigrat.dll 25-Mar-2003 18:00  5.0.0.740         222,480  Mqoa.dll 25-Mar-2003 18:00  5.0.0.762           8,464  Mqperf.dll 25-Mar-2003 18:00  5.0.0.773         428,304  Mqqm.dll 25-Mar-2003 18:00  5.0.0.765         102,672  Mqrt.dll 25-Mar-2003 18:00  5.0.0.772          70,928  Mqsec.dll 25-Mar-2003 18:00  5.0.0.769         400,656  Mqsnap.dll 25-Mar-2003 18:00  5.0.0.762          23,824  Mqupgrd.dll 25-Mar-2003 18:00  5.0.0.767         110,352  Mqutil.dll 25-Mar-2003 18:00  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. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.



MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

The following registry parameter allows administrators to avoid unnecessary routing queries. Follow these steps, and then quit Registry Editor:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following key in the registry:

 

 On the Edit menu, point to New, and then click DWORD Value. Type IgnoreSiteLinks, and then press ENTER. On the Edit menu, click Modify. Type 1, and then click OK.</li></ol>

If this value is 1, Message Queuing establishes a direct connection. Message Queuing assumes that no site gate exists. Therefore, Message Queuing does not perform an Active Directory query.

This registry setting helps you deploy Message Queuing in a non-standard configuration. The Windows 2000 release notes explicitly state that you must have a routing server in each site. This registry can help if you do not require routing, but want to use public queues.

This problem can be identified when you use Message Queuing diagnostic logging. A text file named Msmq.log is created in the %windir%\debug directory. The log file contains diagnostic information that is specific to Message Queuing. To enable Message Queuing logging, follow these steps:

Follow these steps, and then quit Registry Editor: <ol> Click Start, click Run, type regedit, and then click OK.</li> Locate and then click the following key in the registry:

 

</li> On the Edit menu, point to New, and then click DWORD Value.</li> Type LoggingTypes, and then press ENTER.</li> On the Edit menu, click Modify.</li> Type c00000000, and then click OK.</li></ol>

When logging is enabled, you may receive many log entries similar to the following entry:

 

If the conditions in the &quot;Symptoms&quot; section of this article occur, apply this fix.

This hotfix includes an additional change. It reduces the refresh frequency of the routing data default setting from 3 minutes to 12 hours so that routing data does not change so quickly. To configure this change, follow these steps: <ol> Click Start, click Run, type regedit, and then click OK .</li> Locate and then click the following key in the registry:

</li> On the Edit menu, point to New, and then click DWORD Value.</li> Type routingrefreshinterval, and then press ENTER.</li> On the Edit menu, click Modify.</li> Enter the new value.

The new default is 12 hours.</li></ol>

Keywords: kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB817076

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.