| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ XMS .NET CWSMQ0044E error: connection not authorized |
« View previous topic :: View next topic » |
| Author |
Message
|
| rKrull |
 Posted: Fri Jan 11, 2008 9:43 am Post subject: MQ XMS .NET CWSMQ0044E error: connection not authorized |
 |
|
Newbie
Joined: 11 Jan 2008
Posts: 1
|
| I have set up MQ Series for Windows Server 2003. I have followed all the directions to use a Domain Controller. The Sample application runs if I default through the User ID field. But when I supply a User ID that I have defined to the Domain Controller, added it to the "domain mqm" group, etc. I get the CWSMQ0044E error: connection not authorized to the queue manager. I have gone through all the steps creating authority records for the queue manager, refreshing the Authorization Service, but still I get the error. Any suggestions would be appreciated. |
|
| Back to top |
|
 |
| VivekMeshram |
| Posted: Sun Jan 13, 2008 3:42 pm Post subject: |
|
|
Voyager
Joined: 25 Mar 2002
Posts: 83
|
Hi,
CWSMQ0044E is due to MQ [completion code 2, reason code 2035] this is due to MQ security issue. Check your user is the part of mqm group. If not add this user to the mqm group. If authorization has been set up correctly then try to stop/start QM. This should solve the problem. Also do check authorization on qm/queues using setmqaut. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jan 13, 2008 7:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| VivekMeshram wrote: |
| Check your user is the part of mqm group. If not add this user to the mqm group. |
NO.
Check that your user has the correct permissions, added by using setmqaut.
DO NOT add users willy-nilly to mqm group, exactly like one does not add users willy-nilly to the root/Administrators group.
MQM permissions on one queue manager generally translates to full permissions on every qmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 14, 2008 8:39 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| VivekMeshram wrote: |
| If authorization has been set up correctly then try to stop/start QM. This should solve the problem. |
If authorization has been set up correctly there is no need to bounce the QM. setmqaut commands are executed and applied in real time.
If you change group membership at the O/S level then you need to tell MQ to refresh its security cache to recognize these group membership changes. As of MQ 5.3 this can be accomplished using the REFRESH SECURITY command; there is no need to bounce a QM whe dealing with security problems (unlike MQ 5.2 and older versions).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
