MSMQ

  • Thread starter Thread starter papettip
  • Start date Start date
P

papettip

I' ve installed the msmq extension copying the cab file to the device
and after running it and installing on the device memory.

i create a sample application like this:

if (!msmq.MessageQueue.Exists(".\private$\mobile"))
{
myQueue = msmq.MessageQueue.Create(".\private$\mobile");
}
else
{
myQueue = new msmq.MessageQueue(".\private$\mobile");
}

but i receive and exception : "queue service messages is not
available"

Whats wrong ?
thanks.
 
The cab file only installs the required files, you still need to issue some
commands to start it, and to activate the driver component. See Mark
Ihimoyen's blog for a full sample showing how to get MSMQ up and running.
For .NETCF v2.0 you can remove the CreateProcess P/Invokes and work directly
with the System.Diagnostics.Process class.
http://blogs.msdn.com/ihimmar/archive/2004/06/14/154911.aspx
Peter
 
The cab file only installs the required files, you still need to issue some
commands to start it, and to activate the driver component. See Mark
Ihimoyen's blog for a full sample showing how to get MSMQ up and running.
For .NETCF v2.0 you can remove the CreateProcess P/Invokes and work directly
with the System.Diagnostics.Process class.http://blogs.msdn.com/ihimmar/archive/2004/06/14/154911.aspx
Peter
Click to expand...

Hello Peter.
I've tryied the sample of Mark Ihmoyan but with no success, the
process fail on " if (CreateProcess(MSMQ_ADM, "start")) "
There is a difference from the WebLog that the assembly msmqadmext.dll
is missing in my installation (WM5 on imate kjam)

even when i use the visadm tool on the shortcuts -> status command i
receive an error "Operation failed. Error code C00e000b"

thanks
 
The error codes are defined in the mq.h header (in the Optional Windows
Mobile 5.0 Server Components download package):-
//
// MessageId: MQ_ERROR_SERVICE_NOT_AVAILABLE
//
// MessageText:
//
// The Message Queues service is not available
//
#define MQ_ERROR_SERVICE_NOT_AVAILABLE ((HRESULT)0xC00E000BL)

On first call "start" is expected to fail as the service will not be
running, so can you step through the code which calls ActivateDevice - does
that return a valid handle?

Peter
 
On WM 5.0 you have to resign MSMQ CAB and its content with trusted
certificate or install SDK test cert on to device as that the cert MSMQ bits
are signed with. In other case MSMQ driver won't start and service won't be
available.


--
Best regards,

Ilya

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

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
So are you saying that MSMQ won't start on a WM 5 device unless it is either
certified or the developer's test cert is installed? I am having the same
issue with it not starting automatically and I have to use TaskMgr to start
it manually whenever a reset is done on the device.

Thanks,

John
 
Back
Top