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

Problem description

When a client determines that the client site has no Microsoft Message Queuing (also known as MSMQ) routing servers, the client queries for site links and site gates to learn the enterprise topology. This occurs so that 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 directory service for intersite routing. When the Message Queuing service creates an intersite connection, it first tries to find a site gate in the site link. If no site gate 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.

If you are not sure whether this problem exists in your environment, see the "How to determine whether this problem exists" section.

Resolution

To resolve this problem, install the latest service pack for Microsoft Windows 2000. If you cannot install the latest service pack for Windows 2000 for some reason, you can obtain a hotfix that will also fix this problem. After you install either the service pack or the hotfix, go to the "More information" section for information about how to set a registry parameter that will avoid unnecessary routing queries.

How to obtain the service pack

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more 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

How to obtain the hotfix

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

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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 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 item 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 in the "Applies to" section. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

More Information

To avoid unnecessary routing queries, administrators can set a registry parameter. To have us set this registry parameter for you, go to the "Fix it for me" section. If you would rather do this yourself, go to the "Let me fix it myself" section.

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

Fix it for me

To set the registry parameter automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.





Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Now go to the "How to configure an additional change in this service pack and hotfix" section.

Let me fix it myself

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Follow these steps, and then quit Registry Editor:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
    hklm\software\microsoft\msmq\parameters
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type IgnoreSiteLinks, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Type 1, and then click OK.
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 you want to use public queues.

Now go to the "How to configure an additional change in this service pack and hotfix" section.

How to determine whether this problem exists

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

Follow these steps, and then quit Registry Editor:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
    hklm\software\microsoft\msmq\parameters\debug
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type LoggingTypes, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Type c00000000, and then click OK.
When logging is enabled, you may receive many log entries that resemble the following entry:
mqdscore/dsads/69. (&(objectCategory=CN=MSMQ-Site-Link,CN=Schema,CN=Configuration,DC=company,DC=com)(mSMQSite1=CN=location,CN=Sites,CN=Configuration,DC=company,DC=com))

If the conditions in the "Symptoms" section occur, apply this fix.

How to configure an additional change in this service pack and hotfix

This service pack and hotfix include 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:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:
    hklm\software\microsoft\msmq\parameters\
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type routingrefreshinterval, and then press ENTER.
  5. On the Edit menu, click Modify.
  6. Enter the new value.

    The new default is 12 hours.

Did this fix the problem?

Check whether the problem is fixed. If it is fixed, you are finished with this article. If it is not fixed, you can contact support.
Rekvizīti

Raksta ID: 817076. Pēdējo reizi pārskatīts: 2013. gada 3. sept.. Pārskatījums: 1

Atsauksmes