Things to Check When Troubleshooting Message Queuing

[AWS]

The following recommendations should be followed when troubleshooting Message Queuing problems in the Microsoft Windows Vista and Windows Server 2008 operating systems.

 

Check the Windows event logs for errors and warnings

 

Check the Windows event logs of the Message Queuing computer(s) for errors. Search for error or warning events with a Source that contains the text MSMQ, for example "MSMQ(MSMQ)" or "MSMQ Cluster Resource". Sort events in the Event Viewer by Source to quickly locate events that contain the text "MSMQ". Then search Microsoft Help and Support for the corresponding Event ID, text in the error or warning description, or any error codes that are returned as EventData in the details of the event.

For more information about using Event Viewer see the Windows online help.

 

Use End-to-end tracing to troubleshoot problems with message delivery

 

Consider enabling End-to-End tracing to troubleshoot problems with message delivery.

For more information see the Windows Vista or Windows Server 2008 help topic "Troubleshooting by Using End-to-End Tracing".

 

Verify computer connectivity

 

No matter what the connectivity symptom or problem, using the ping utility to test a computer is always a good idea. The amount of time that ping takes to respond can indicate a problem, as can the fact that ping only succeeds intermittently. Intermittent success indicates issues such as network overload or failure in name resolution, which forces the computer to broadcast for name resolution.

Verify that ping resolves the full DNS name of the problem computer. If it does not, check your DNS server.

 

Note:

Windows Firewall disables ICMP echo messages (ping) by default. If you are using ping to verify name resolution then you may need to temporarily allow ICMP requests and responses through Windows Firewall first.

 

Read Things to Check When Troubleshooting Message Queuing