Q:MSMQ cant't open a Queue
Michael Kipcke
I've develop om am NT Workstation 4.0 (SP3) with VB a little MSMQ App. On
the Workstation I've installed a MSMQ Indi Client. I've worked with it and
the deinstall the indi client. Some days later I installed the indi client a
second and test it with the API Sample commin up with the MSMQ SDK. I create
a Message Queue on my local mashine and if I try to open it for receive, I
get the following Error Message: "MQOpenQueue failed, Error code=0x00e0025"
So, what went wrong. What can I do ? MS say's , it's a support problem, but
I thing , there is a Bug.
Please help,
Michael
Frank Boyne
<O8NAzjg...@uppssnewspub05.moswest.msn.net>...
> I create
> a Message Queue on my local mashine and if I try to open it for receive,
I
> get the following Error Message: "MQOpenQueue failed, Error
code=0x00e0025"
According to mq.h, 0x00E0025 is MQ_ERROR_ACCESS_DENIED.
> So, what went wrong. What can I do ? MS say's , it's a support problem,
but
> I thing , there is a Bug.
The SDK has the following description for MQ_ERROR_ACCESS_DENIED:: Access
to the specified queue or computer is denied. Verify the access rights for
the operation (for example, creating, setting properties, or deleting a
queue). To change access rights for a queue, call MQSetQueueSecurity.
Perhaps the easiest way to get this error is to create the queue while
logged on under account A and then later try to receive from the queue
while logged on under account B. The default security for a queue allows
anyone Send access to it but only the creator has Receive access.
The quickest way to check this is to run MSMQ Explorer, and right click on
the queue in question. Select Properties from the menu and select the
Security tab on the resulting dialogue. Click on the Permissions button.
This will allow you to view the permissions defined for the queue. Check
that the account you are logged on under when you try to receive at least
has the Rq permission.
Michael Kipcke
I tried it with the Explorer and there I've found the Message : "Cannot open
Queue: Unknown Error (0xc00e000b)" in the SDK in found the description
MQ_ERROR_SERVICE_NOT_AVAILABLE =>Application was unable to connect to the
Queue Manager
i used the API Program from the MSMQ samples. I created a queue and try to
open the Queue for receive. The program denied with "MQ_ERROR_ACCESS_DENIED"
and in the explorer I red the Message above. This all happens since I
deinstall the independent client and install him again. I don't know what
can I do now. I don't want to install my system ( WinNt and so on ) again.
Do you have any suggestions ?
Bye the way, I only use the ActiveX and VB.
Thx,
Michael
Frank Boyne schrieb in Nachricht <01bdba53$4b88cb70$3ce43bc0@mv_boynefg>...
Frank Boyne
> Do you have any suggestions ?
Not really I'm afraid. It sounds like your MSMQ Independant Client is
really mixed up. When you run Explorer it gives you the
MQ_ERROR_SERVICE_NOT_AVAILABLE error which implies that the MQ service
isn't running, yet when you run the API program it allows you to create a
queue which implies that the MQ service *is* running.
I suppose you could use Settings | Control Panel | Services to check
whether or not the Microsoft Message Queue Service is started, but I'm not
sure what good that really does you.
You could also use Administrative Tools (common) | Event Viewer to check
your Event Log. On my NT workstation running Independant Client, I get two
log entries soon after the system boots up.
The first is event ID 2060, source MSMQ and has the description "Found an
information sever (PEC, PSC, or BSC). The MSMQ service now is online and
fully operational. " The second is event ID 2028, source MSMQ with the
description "Initialization completed successfully. ".
The only other thing I can suggest is that you uninstall the Independant
Client and try installing it a third time in the hope that the problem goes
away as mysteriously as it came :-(
Frank Boyne
<epkELLs...@uppssnewspub05.moswest.msn.net>...
> Do you have any suggestions ?
One other question occurs to me.
Are you using TCP/IP or IPX to communicate with your PEC/PSC? If you are
using IPX, then you might look at
http://support.microsoft.com/support/kb/articles/q186/1/89.asp. The
symptoms aren't exactly the same as yours, but they are close.