I see some discussion about MSMQ 3.0 support from
http://groups.google.com/group/rhino-tools-dev/browse_thread/thread/cb32e290cdcf73d4/1d4e9b0193bc584e,
but I'm not sure if it was ever resolved.

My sample project runs fine on my Win7 machine with MSMQ 5, but when I
move it to a windows 2003 server I get the following exception:

Unhandled Exception: System.Messaging.MessageQueueException: Invalid
queue path
name.
   at
System.Messaging.MessageQueue.ResolveFormatNameFromQueuePath(String
queueP
ath, Boolean throwException)
   at System.Messaging.MessageQueue.get_FormatName()
   at System.Messaging.MessageQueue.Purge()
   at RhinoESBTest.Core.PrepareQueues.PurgeSubqueue(String queuePath,
String sub
queueName) in D:\Projects\RhinoESBTest\RhinoESBTest.Core
\PrepareQueues.cs:line 6
1
   at RhinoESBTest.Core.PrepareQueues.PurgeSubqueues(String queuePath,
QueueType
 queueType) in D:\Projects\RhinoESBTest\RhinoESBTest.Core
\PrepareQueues.cs:line
43
   at RhinoESBTest.Core.PrepareQueues.Prepare(String queueName,
QueueType queueT
ype) in D:\Projects\RhinoESBTest\RhinoESBTest.Core
\PrepareQueues.cs:line 19
   at RhinoESBTest.Core.Requester..ctor() in D:\Projects\RhinoESBTest
\RhinoESBTe
st.Core\Requester.cs:line 21

It does create a videoencoder private queue on the machine, but it
looks like it's failing right after that, creating the subqueues for
errors and subscriptions and such.

Was the patch for 3.0 compatibility ever applied?

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en.

Reply via email to