Msmq network transport error logging

We have multi-casting one way messaging through a remote msmq server using wcf services for our system. 

One day one of our many environments got a message to multicast…and didn’t send anything out.  We have a pipeline step to audit the incoming message, topic properties to move msmq messages to a dead letter queue after a specific amount of time, and a service policy to move messages to the failed neuron db table after a specific amount of time/retries (matching the msmq network properties to move to a dead letter queue), only if the message can’t be delivered to the service connector.  When the multi cast didn’t work, we didn’t see any failed messages in the db, and the multicast event message didn’t get to any of the subscribers.  The message got to the outbound queue on the esb server (and was in the audit db to publish), but never got delivered the msmq remote server to be delievered to the subscribers.

My question is: if msmq can’t move a message from esb outbound queue to the remote msmq, does that get logged anywhere?  I had to look at the esb msmq outbound messages in conjunction with esb dead leader queue to conclude what was going on.  There was no indication from esb (like in the logs folder or esb application event log) that a message couldn’t be delivered from the esb server outbound queue to the remote msmq server.

We do windows updates on our servers which brings down the esb services every once in a while.  We speculate that this could be a potential cause of what was going on.  We added a dependency to esb service to have msmq service to be running before esb starts up.  But I more interested in where msmq logs if anything happens, especially since we rely on this transport system which our whole application is based on.

-Nick N