Hi!

I try setup an MSMQ receive location, but it seems like something's missing.
.

I create a new receive port and add a new receive location. But in the
transport type drop down list there is no MSMQ! I can chose from EDI, FILE,
FTP, HTTP, SOAP and SQL... But not MSMQ (or MSMQT or whatever??).

What to do? Any ideas!
Thanks for your help!

[ Post a follow-up to this message ]

Samuel,

> I try setup an MSMQ receive location, but it seems like something's
> missing...
>
> I create a new receive port and add a new receive location. But in the
> transport type drop down list there is no MSMQ! I can chose from EDI,
> FILE,
> FTP, HTTP, SOAP and SQL... But not MSMQ (or MSMQT or whatever??).

MSMQT is configured but not actually installed by default. If you want to
use MSMQT you need to add it from the BizTalk Management Console (select the
adapters node, right click -> add new adapter).

If you want to use the MSMQ adapter, you need to download it from here
first:
http://www.microsoft.com/biztalk/ev...lt.msp
x
and install it.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Thanks Tomas... That was it!
Ok, so far so good.

But now I created a send location with the following config:
Transport Type: MSMQT
Address (URI): .\Private$\TestXSLSplitterOut

Works fine to send a message to this queue through this port in BizTalk. But
when I try to access this queue from a .NET assembly it says that it doesn't
exist, even though it contains a message (according to HAT). I try to create
an instance of MessageQueue with the path above.

Any ideas? I am thankful for all comments!

[ Post a follow-up to this message ]

Samuel,

> But now I created a send location with the following config:
> Transport Type: MSMQT
> Address (URI): .\Private$\TestXSLSplitterOut
>
> Works fine to send a message to this queue through this port in BizTalk.
> But
> when I try to access this queue from a .NET assembly it says that it
> doesn't
> exist, even though it contains a message (according to HAT). I try to
> create
> an instance of MessageQueue with the path above.

That's how it is supposed to work 

MSMQT queues are virtual queues, mimicked by the MSMQT service by
implementing the MSMQ protocol at the wire level, so they are not accesible
by the System.Messaging api.

What they support is another MSMQ server sending messages to it or
viceversa, but you probably notice that running side by side MSMQ and MSMQT
is a royal pain. Sounds like in your case you might be better off using the
MSMQ adapter and not MSMQT.

You probably want to check this, btw:
http://blogs.msdn.com/eldarm/archiv.../24/484301.aspx


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]