A couple months ago I was testing the MSMQ(C) adapter for BizTalk Server 2004 for a proof of concept I was working on. While overall it worked fine, I did run into a couple of problems with it which I cannot explain fully yet.
As I wrote in a newsgroup post some time ago, I was never able to actually get the adapter to send messages to transactional queues. Non-transactional queues worked fine, as well as receiving messages from a transactional queue, but not the other way around. Here's what I posted at that time:
Has anyone else noticed a problem with sending messages using the recently
released MSMQ adapter to transactional queues?
I've been trying to do it on my machine, and receiving works just fine, but
trying to send messages to a transactional queue keeps failing with the
following entry in the event log:
Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5743
Date: 3/10/2005
Time: 6:23:43 PM
User: N/A
Computer: C-TRESTREPO
Description:
The adapter failed to transmit message going to send port
"FORMATNAME:DIRECT=OS:.\PRIVATE$\ALMACEN1". It will be retransmitted after
the retry interval specified for this Send Port. Details:"No such interface
supported".
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Sending messages to non transactional queues works fine, though....
Any clues?
I tried this in two different machines and ran into the same error, and I know other people are seeing this. However, I have yet to see a useful answer on what the cause is and how to correct it.
The other problem I did run into on one machine, though I couldn't reproduce it was actually even stranger: In my old machine, the BizTalk Application Host would randomly hang during shutdown when the MSMQ adapter was installed on the machine, and the only way to get it to end was to forcefully kill it. Even more strange was that the application host service would hang during startup if I had the MSMQ management console open at the same time!. As soon as I closed it, the problem went immediately away. Talk about bizarro queues...
