BUG: Transactional Messages Sent Offline Are Not Delivered (186193)

SYMPTOMS

If transactional Microsoft Message Queue Server (MSMQ) messages are sent while the sending computer is physically disconnected from the network, and the MSMQ service is subsequently stopped and started before reconnecting to the network, the messages will be discarded to the sending computer's Transactional Dead Letter queue and marked with the negative acknowledgement "Bad Destination."

STATUS

Microsoft has confirmed this to be a problem in Microsoft Message Queue Server version 1.0. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

WORKAROUND

There are two workarounds and a hotfix available. You can use any of them.

Use a Direct Format Name

Address the message using a direct format name as in this example:

   DIRECT=TCP:111.222.333.444\queue_name

The drawback to this approach is that you lose the routing and privacy features of MSMQ.

Do Not Restart MSMQ Service

Do not allow the MSMQ service to be restarted at the sending computer until the messages have been delivered. The drawback to this approach is that there is a period of time during which a computer failure or similar event may force a reboot. The application must compensate by including recovery code to inspect the Transactional Dead Letter queue for discarded messages and resend them.

Hotfix

A hotfix to the Mqqm.dll file is available and addresses the problem. You should use one of the workarounds listed above until a service pack is available. However, if neither workaround is acceptable, you can request the hotfix.