| Author |
Message
|
| MQFard |
 Posted: Fri Aug 04, 2006 10:13 am Post subject: Error 2035 - Not authorized for access |
 |
|
Novice
Joined: 07 Oct 2004
Posts: 17
Location: VSP.COM
|
We are running WebSphere MQ 5.3 fix pact 8 on Windows 2003 server. I have a queue manager called TVSPQUE running on the server. I have installed a client on an NT desktop. When trying to connect to the queue manager via the client I’m receiving the following message:
AMQ8077: Entity 'morero' has insufficient authority to access object 'TVSPQUE'.
EXPLANATION:
The specified entity is not authorized to access the required object. The
following requested permissions are unauthorized: connect
ACTION:
Ensure that the correct level of authority has been set for this entity against
the required object, or ensure that the entity is a member of a privileged
group.
I have added morero to the MQM group and I’m still receiving this error.
For the past two days I’ve been looking through manuals and searching the MQSeries.net database and everything says that if the User Id is in the MQM it should work.
I have others defined in the MQM group and have no issues. We have tried changing the character case of the logon Id. We have created a new Id of the same name. I have deleted and installed the client and still receive the same results.
Looking for help. 
_________________
To Fard
WebSphere MQ Administrator |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Fri Aug 04, 2006 10:21 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
I think this is in the wrong forum old chap....however.....
Do you have an MCA Userid specified on the Server Conn channel? If so is this sufficiently authorised?
*Warning* If you have this, this is not a very secure way of doing things. |
|
| Back to top |
|
|
| MQFard |
| Posted: Fri Aug 04, 2006 10:25 am Post subject: |
|
|
Novice
Joined: 07 Oct 2004
Posts: 17
Location: VSP.COM
|
Yes I realized I put in the wrong form after I submitted it. Sorry.
The MCA user is blank.
_________________
To Fard
WebSphere MQ Administrator |
|
| Back to top |
|
|
| bbburson |
| Posted: Fri Aug 04, 2006 11:33 am Post subject: Re: Error 2035 - Not authorized for access |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| MQFard wrote: |
| I have added morero to the MQM group and I’m still receiving this error. |
Did you restart the queue manager or use REFRESH SECURITY after adding the user to the group? Not sure about Windows, but I know for UNIX queue managers one or the other is required for the change to take effect. |
|
| Back to top |
|
|
| MQFard |
| Posted: Fri Aug 04, 2006 11:36 am Post subject: |
|
|
Novice
Joined: 07 Oct 2004
Posts: 17
Location: VSP.COM
|
I’ve never had to do that before, but I will give it a try and see.
Thanks,
_________________
To Fard
WebSphere MQ Administrator |
|
| Back to top |
|
|
| MQFard |
| Posted: Fri Aug 04, 2006 12:19 pm Post subject: |
|
|
Novice
Joined: 07 Oct 2004
Posts: 17
Location: VSP.COM
|
Bruce,
Thanks so much for your help. The refresh security of the queue manager worked. Lesson learned. It’s interesting that I’ve never had to do this before.
Thanks again, 
_________________
To Fard
WebSphere MQ Administrator |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 04, 2006 3:29 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You only have to refresh security when the OS group membership has changed and you don't want to wait until the qmgr is restarted.
That is, if you add someone to a group, then you need to refresh security.
If you issue a new setmqaut command, you don't need to refresh security.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
