View Message Queuing Events
Applies To: Windows Server 2008
Use this procedure to view Message Queuing events.
You can use this procedure to view Message Queuing events.
Message Queuing logs information about its operation to the event logs. Message Queuing events are located in the Source column under "MSMQ." Most events are written to the Application Log. Security-related events are written to the security log, and service-related events are written to the system log.
There are three types of application events for Message Queuing in the Application Log, as follows:
Informational events. Infrequent, significant events that describe successful operations.
Warnings. Not necessarily significant events, but indicative of potential problems.
Errors. Events generated for significant problems.
Some application events are not logged at each occurrence. For example, if a Message Queuing server cannot establish a session with the destination computer, an event is logged for the first failure only and another event is logged after the session is established.
There are two types of security-related events for Message Queuing in the security log, as follows:
Success Audit. Generated when selected objects are successfully accessed.
Failure Audit. Generated when access to a selected object is denied.
For more information about access auditing, see Additional references.
Membership in the local Users group, or equivalent, is the minimum required to complete this procedure.
To view Message Queuing events
Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.
In the console tree, click to expand Windows Logs and click Application.
In the details pane, click the Source column to gather the MSMQ and MSMQTriggers events together.
Scroll until you see MSMQ and MSMQTriggers events listed in the column.
When viewing events in Event Viewer, you can sort, filter, and search for events, based on event properties.
Message Queuing service events can be located with the same procedure, by clicking System in the console tree, instead of Application.