Troubleshooting by Using End-to-End Tracing

End-to-end tracing provides valuable information to help
troubleshoot problems with message delivery. It tracks the path of
a message through its life cycle, from the time that an application
sent it to the time that:

An application uses the message.

The message is deleted because of an
error.

The message is put in a dead-letter
queue.

After a message has been sent, you can look at correlated
activities and determine where the message is and why it is
there.

End-to-end tracing is disabled by default. Perform the following
steps to enable it.

Using end-to-end tracing

To enable end-to-end tracing

In Event Viewer, open Applications and Services
Logs.

Where?

Computer Management/Event Viewer/Applications
and Services Logs

In the console tree, double-click Microsoft,
double-click Windows, and then double-click MSMQ.

In the details pane, right-click End2End, and
then click Properties.

On the General tab, select the Enable
logging check box.

Click OK.

After you enable it, you can view end-to-end tracing
events in Event Viewer. Perform the following steps to view these
events.

By default, events for all messages are listed by the
date and time on which they occurred, with the most recent events
listed first. You can diagnose problems more effectively by
correlating the events for each message. Perform the following
steps to correlate events for a given message.