Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista
Report queues are public queues used to store report messages generated by Message Queuing or connector applications when route tracking is enabled on the source computer by the Message Queuing administrator and tracing is requested for messages by the sending application. When a message is sent with tracing requested from a computer with route tracking enabled, a report message is generated each time the message leaves or arrives at a Message Queuing computer, including a Message Queuing routing server.
Report queues are not limited to report messages. Application-generated messages can be sent to report queues as well.
All report queues must have the following label and queue type identifier:
Label: MQReport Queue.
Queue type identifier (GUID):
Who creates report queues
Report queues are typically created by the Message Queuing administrator using the directory service user interface; however, they can also be generated by an application as long as the correct label and service type identifier are specified when the queue is created. The report queue used for a particular source computer is specified by the Message Queuing administrator. Message Queuing uses the label and queue type identifier to locate and open the appropriate queue when reading report messages.
Multiple Report Queues
Typically a single report queue is specified for the source computer where the message is sent. However, a different report queue can be specified for each Message Queuing computer along a message's route.
|For information on||See|
|Enabling tracing||Tracing Messages|
|Code examples that enable tracing||Tracing Message Examples|
|Other application queues||Application Queues|
|How report messages are sent when multiple report queues are specified along a message's route||Specifying Multiple Report Queues|