MSMQ Multicast on XPe

[=?iso-8859-1?Q?J=F6rn_Petersen?=]

Hi everybody!

To evaluate the Multicast feature of MSMQ (MicroSoft
Message Queuing) I have written a small apllication that
can create message queues, assign multicast addresses to
them and send and receive messages.

This works fine on XP Pro, but on XP embedded I can only
create the queues and assign the multicast addresses to
them (checked using the MSMQ MMC snap-in). Sending
messages to a multicast address fails (without application
receiving any error message).
The connection should be ok, since I can send and receive
on XPe as long as direct paths are used.
Using MMC I can see, that an Outgoing Queue is created
when trying to send to a Multicast address, but it's state
is kept in "Waiting to connect".

In the event log the following error messages appear when
assigning the multicast address to the queue and/or when
booting:
Source: MSMQ
Category: Kernel
Event ID: 2160
"The queue cannot listen/bind to the multicast address
233.44.55.66:7788 (Error 273c)"

Even though my build contains nearly any software
component (image size after fba 450 MB) something
important seems to be missing.

Has anybody in here successfully used the Multicast
feature of MSMQ and any idea what might be wrong?


Best regards
Jörn

 

[Andy Allred [MS]]

Sorry to ask the obvious but did you add the "Pragmatic General Multicast
(Reliable Multicast protocol) " component?

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


Hi everybody!

To evaluate the Multicast feature of MSMQ (MicroSoft
Message Queuing) I have written a small apllication that
can create message queues, assign multicast addresses to
them and send and receive messages.

This works fine on XP Pro, but on XP embedded I can only
create the queues and assign the multicast addresses to
them (checked using the MSMQ MMC snap-in). Sending
messages to a multicast address fails (without application
receiving any error message).
The connection should be ok, since I can send and receive
on XPe as long as direct paths are used.
Using MMC I can see, that an Outgoing Queue is created
when trying to send to a Multicast address, but it's state
is kept in "Waiting to connect".

In the event log the following error messages appear when
assigning the multicast address to the queue and/or when
booting:
Source: MSMQ
Category: Kernel
Event ID: 2160
"The queue cannot listen/bind to the multicast address
233.44.55.66:7788 (Error 273c)"

Even though my build contains nearly any software
component (image size after fba 450 MB) something
important seems to be missing.

Has anybody in here successfully used the Multicast
feature of MSMQ and any idea what might be wrong?


Best regards
Jörn

 

[=?iso-8859-1?Q?J=F6rn_Petersen?=]

Hi Andy,
PGM is in the build - of course ;-)
You're welcome to ask obvious questions, but I hope that
this was not your (or anybody elses) best shot ;-)

Jörn

 

[Anil Ingle]

Hello,
The error number shows the following description:
The support for the specified socket type does not exist in this address
family.

Not knowing all the details, it seems like the PGM service did not start.
Can you please verify that the service started?
Thanks
-Anil [MS] This posting is provided "AS IS" with no warranties, and confers
no rights.

 

[=?iso-8859-1?Q?J=F6rn_Petersen?=]

Hi Anil,

Not knowing all the details, it seems like the PGM service did not start.
Can you please verify that the service started?

I'm not absolutely sure if I'm doing this correctly, but
when typing "net start" from a Command Prompt, there are
no signs of a PGM service (only the "Message Queuing"
service itself).
However, when trying to start it manually by typing "net
start rmcast" I'm told, that "The requested service has
already been started".

I also tried to stop the PGM service (which also stops
the "Message Queuing" service) and restart it, but the
only thing I could see, was that the "Message Queuing"
service automatically starts the PGM service and that I
get errors in the event log for the queues that should be
bound to the multicast address. The MSMQ service itself
starts fine...

I'd be happy to supply you with further details, so please
ask if you need any other informations.

 

[=?iso-8859-1?Q?J=F6rn_Petersen?=]

Thanks to Doron Juster from Microsoft (he usually answers
in the MSMQ NG) this behaviour actually turned out to be a
bug in XPe.
During the configuration, Winsock is not associated
properly with the RMCast driver. Doron made a little tool
to add that information and after this it works perfectly!

A case has been opened with Microsoft support and some
time in the future there will hopefully be a QFE. But
since I seem to be the only person using this
functionality, this issue may not receive a very high
priority (taken into account that there are a lot of
people waiting for .NET 1.1 - including me ;-) )

 

[Andy Allred [MS]]

Thanks, I'm already working with Doron on this issue. Thank you for your
assistance in verifying the fix! <grin>

Andy

 

[Juhan Palm]

Does this fix also fix the problem with starting MSMQ at all after
FBA on a cloned image?

Juhan Palm

 

[=?iso-8859-1?Q?J=F6rn_Petersen?=]

Hi Juhan,

are you referring to the two missing dependencies (event
log and net.exe) of MSMQ (as discussed in
http://snurl.com/3b9z)?
Or do you have other problems when starting MSMQ?


Jörn