BUG: MSMQ Service Without Messages Takes Long Time to Start Up (267324)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

This article was previously published under Q267324

SYMPTOMS

The Microsoft Message Queuing (MSMQ) Service may take 20 minutes or more to start up on a Domain Controller (DC) with hundreds of sites and subnets.

CAUSE

When MSMQ starts, and then by default every hour after startup, the MSMQ Directory Service creates an association list between subnets and Active Directory (AD) site globally unique identifiers (GUIDs). However, the site GUID is not stored in the AD; only the site's Distinguished Name is stored in the AD. As a result, the MSMQ Directory Service must execute a query to obtain each site's GUID for every subnet.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

REFERENCES

The Windows 2000 Help For MSMQ

Modification Type:MajorLast Reviewed:12/23/2000
Keywords:kbbug KB267324