Microsoft KB Archive/264054

= XCON: Understanding Queue States in Exchange 2000 Server =

Article ID: 264054

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q264054



SUMMARY
This article provides a basic understanding of Queue states in Exchange 2000 server, some related concepts, and how they can be changed.



MORE INFORMATION
You can choose to either enable or disable the state of a link queue connection. (If the connection is disabled, all the other task items appear dimmed except Enable Connection.)

You do not specify what state the connection should take after you enable a link. You can, however, manually change connections by using the context menu on each link queue. Changing a queue state to Active (by using the Force Connection command) immediately enables a connection for it, which in turn sends the messages from that queue. You can directly enforce only the Active and Disabled states. Possible states of a connection are: Active, Ready, Remote, Frozen, Retry, and Scheduled. If the link is disabled, the state of the connection is Disabled.

The states of a queue can change in the following ways:
 * You can change queues in the Retry or Scheduled state to Active (with the Force Connection command). This causes the queue to function as if the retry interval had passed or the scheduled time was reached. This method may not always work, however. Remember that the properties of a queue can indicate a specific reason for a queue to be in Retry.
 * In some cases, queues in the Remote state (that is, queues waiting for a remote server to connect and issue a dequeue command) cannot be changed to Active. However, in all cases they can be frozen.
 * Freezing an Active queue immediately ends the transport sessions for that queue. Although freezing a queue prevents outbound messages, new messages can be added.

Additional query words: xmrp

Keywords: kbinfo KB264054

-

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

© Microsoft Corporation. All rights reserved.