| Author |
Message
|
| Jimmy3 |
 Posted: Thu Jun 28, 2007 6:56 am Post subject: Reason code 2035 when creating Domain |
 |
|
Novice
Joined: 08 May 2007
Posts: 16
|
Hi
While creating a domain in the Broker Tolkit, providing the queue manager and port, I am getting error:
User xxxx is not authorized to connect to queue manager 'Queue_manager_name' (MQ reason code 2035 while trying to connect)
This queue manager is created using SaveQMgr utility. (i donno if that makes any difference or not).
Also I am included in the mqm and mqbrkrs group, and I have admin rights too. Can anybody help me? |
|
| Back to top |
|
 |
| marcin.kasinski |
| Posted: Thu Jun 28, 2007 6:58 am Post subject: Re: Reason code 2035 when creating Domain |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
It just means MQRC_NOT_AUTHORIZED.
Have you checked it ?
_________________
Marcin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 28, 2007 7:03 am Post subject: Re: Reason code 2035 when creating Domain |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Jimmy3 wrote: |
This queue manager is created using SaveQMgr utility. (i donno if that makes any difference or not).
|
You can't create a queue manager with saveqmgr, just restore the objects
| Jimmy3 wrote: |
Also I am included in the mqm and mqbrkrs group, and I have admin rights too. Can anybody help me? |
Display the ACL lists and make sure the user id you're using is listed with the right authorities, and if not add them. We've had examples here where a user id who's a member of those groups has got a 2035 trying to access the ConfigMgrProxy until a specific ACL was added.
Bug? Feature? We sort of lost interest after we fixed it! But the Toolkits affected are at 6.0.2 Interim Fix 005 if some nice IBMer wants to look.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 28, 2007 7:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should never get a 2035 for anything involving MQSI ACLs, as far as I understand it.
2035 should only ever be returned for problems with OAM permissions.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 28, 2007 7:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
You should never get a 2035 for anything involving MQSI ACLs, as far as I understand it.
2035 should only ever be returned for problems with OAM permissions. |
You know, I agree with you. I saw it happen, fixed it by adding an ACL but I still agree with you.
A solid 5.8 on my Weird-O-Meter 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Jimmy3 |
| Posted: Thu Jun 28, 2007 8:13 am Post subject: |
|
|
Novice
Joined: 08 May 2007
Posts: 16
|
Thanks Guys.
First thing, I actaully created the objects for MQ using SaveQMgr. I correct this.
Well I tried the following for providing rights:
mqsicreateaclentry <configmgr_name> -u <userid> -m <machine> -x F -p
I got the following errors:
BIP8075E: A Java exception was caught from class 'ConfigurationACLGroup.CreateACLGroup'. The text is 'java.lang.NoSuchFieldError: msgToken'. A Java exception was caught via the JNI.
Check preceding messages for related errors and retry the operation. If the exception still occurs, contact your IBM support center.
Nothing seems to be going my ways  . |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Thu Jun 28, 2007 11:38 am Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
Hi,
mqrc 2035 refers to MQ.
Your command refers to message broker.
Fix it with setmqaut command.
_________________
Marcin |
|
| Back to top |
|
|
|
|
