ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » 2035 is NOT AUTHORIZED FOR ACCEESS

Post new topic  Reply to topic
 2035 is NOT AUTHORIZED FOR ACCEESS « View previous topic :: View next topic » 
Author Message
rajmq
PostPosted: Wed Jan 15, 2003 6:45 am    Post subject: 2035 is NOT AUTHORIZED FOR ACCEESS Reply with quote

Partisan

Joined: 29 Sep 2002
Posts: 331
Location: USA

Hi

I want connect to QManager from MQClient(win2k),QMGR running in AIX5.1 box.
I set the variable in client m/c MQSERVER='CHANEL/TCP/ipadress(PORT)
but when try to connect, the reponse code is 2035

2035 is NOT AUTHORIZED FOR ACCEESS

After that i created same userid in AIX Box, and also i given mqm rights.
But again it is failed.

can anyone give me a slou for above probs??

thanks
raj
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Jan 15, 2003 8:25 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Try restarting the queue manager.
Back to top
View user's profile Send private message
mqonnet
PostPosted: Wed Jan 15, 2003 9:19 am    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

On what call do you get 2035... Conn, Open???

Make sure that the logged on userid and the principal you just created on AIX are exactly the same, including the "case".

Also if you are creating a userid/principal on Aix with the same name as the userid on 2k, then make sure that you dont have anything in the MCAUSER attribute of the svrconn channel you are trying to access.

Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rajmq
PostPosted: Wed Jan 15, 2003 9:34 pm    Post subject: Reply with quote

Partisan

Joined: 29 Sep 2002
Posts: 331
Location: USA

Hi

Thanks for all

Thsi Server is running in Production.So it is very difficult to stop & start
QMGR.
In svrconn channel also i am not spcified any MCAUSER attribute.
CASE also exactly same.
Using w2k userid i am able to login ( AIX QMGR Box)
Security Refresh also i did,But still same.

anyother suggestions.

raj
Back to top
View user's profile Send private message
dgolding
PostPosted: Thu Jan 16, 2003 12:26 am    Post subject: Reply with quote

Yatiri

Joined: 16 May 2001
Posts: 668
Location: Switzerland

You didn't say what version MQ you are on, but within runmqsc you can execute:

refresh security

this will reread the group files and your user should be able to get in.

HTH
Back to top
View user's profile Send private message Visit poster's website
XIPO
PostPosted: Thu Jan 16, 2003 1:07 am    Post subject: Security problem Reply with quote

Novice

Joined: 17 Dec 2002
Posts: 13
Location: Spain

I had a similar problem, and finally I created a user in w2K without uppercase (for example "mqmadmin"), and also in AIX.
mqmadmin always belong to mqm group in all our AIXs.
Have you tried MQJExplorer, this program normally hasn´t got problems of authority, if you are login as a user that belongs to mqm group in AIX. This is a problem that I´m triying to solve because in my opinion it´s an important security hole, there is a solution but only for qmgrs in w2K (http://www.kolban.com//mq/Security/security.htm, thanks to Neil Kolban).
Good luck
Tom
Back to top
View user's profile Send private message Send e-mail
mqonnet
PostPosted: Thu Jan 16, 2003 5:56 am    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Did you check if the user you created on AIX has the authority to access QM objects in question?? You could do that using dspmqaut.

Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » 2035 is NOT AUTHORIZED FOR ACCEESS
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.