You frequently receive "Event ID: 2010" messages on computers that run Message Queuing (327008)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

This article was previously published under Q327008

SYMPTOMS

On Microsoft Windows 2000 Server-based computers that run Microsoft Message Queuing, you frequently receive the following message in Event Viewer:Event Type: Error
Event Source: MSMQ
Event Category: Kernel
Event ID: 2010
Description:
Cannot Route to remote site GUID because it cannot be reached using site links

CAUSE

This issue occurs if the following conditions are true:
  • All Windows 2000 Server-based computers in the enterprise are configured as routing servers.
  • Routing links are not defined.

RESOLUTION

To resolve this issue, define the routing links. To do this, follow these steps:
  1. Click Start, click Run, type Dssite.msc, and then click OK.
  2. On the View menu, click Show Services Node.
  3. Expand Services, right-click MsmqServices, point to New, and then click MSMQ Routing Link.
  4. In the Site 1 list, click the source computer that you want.
  5. In the Site 2 list, click the destination computer that you want.
  6. In the Routing link cost box, type a cost if you want to.

MORE INFORMATION

When Message Queuing cannot send messages directly, Message Queuing uses cost-based routing to forward the messages from the source computer to the destination computer. For the routing algorithm to work correctly, you must define the routing links.

By default, all routing links are assigned a cost of 1. You should only change routing link costs when you have multiple routes and you want to enforce one route instead of another route. In that case, you can assign costs that reflect the differences in the communications costs. Costs can range from 1 to 4,294,967,295.

Modification Type:MajorLast Reviewed:4/19/2005
Keywords:kbprb kbExpertiseAdvanced kbtshoot KB327008 kbAudITPRO