Mqconn Error 2035
Contents |
mqrc 2035 not authorized security MQRC_NOT_AUTHORIZED mqminfo 2035 2035 2035 2035 Technote (troubleshooting) Problem(Abstract) You are getting MQRC 2035, Not Authorized in your WebSphere MQ application or ('mqcc_failed') reason '2035' ('mqrc_not_authorized') channel. You need to understand what causes this failure. 2035 0x000007f3 MQRC_NOT_AUTHORIZED Cause mq error 2035 completion code 2 MQRC 2035 (MQRC_NOT_AUTHORIZED) is returned when a user is not authorized to perform the function that is attempted. Resolving the mqconn ended with reason code 2035 problem MQRC 2035 (MQRC_NOT_AUTHORIZED) is returned when a user is not authorized to perform the function. Determine which object the user cannot access and provide the user access to the object. Debugging techniques:
The Call To Initialize The User Id Failed With Compcode 2 And Reason 2035.
Use the dspmqaut (display authority command), to determine if the user has the authorization to access the intended object. For more difficult problems a trace of the failure may be necessary. See "Additional information" for trace debugging pointers. For more details on how to take a trace, see: MustGather: Directions to start, end, and format trace Corrective action: Use the setmqaut (set or reset authority) command, to mqrc_not_authorized c# grant access to WebSphere MQ objects. You will then need to restart the queue manager to refresh the security cache, or via runmqsc run "REFRESH SECURITY(*)" to do the same. In some cases you may want to make the user a member of the "mqm" group. That will give the user full access to WebSphere MQ. For further details regarding the WebSphere MQ authority commands, refer to: dspmqaut (display authority) setmqaut (set or reset authority) Additional information Here's a quick overview of WMQ security: Users in the 'mqm' group and the 'mqm' userid (on UNIX) have full authority. Other users and groups need to be given limited authority through the OAM using 'setmqaut'. Imagine that a WMQ application issues a MQOPEN. Here is the sequence of events as that MQOPEN is handled by the application and its agent (note: this is a general flow. The internal routine names or the specific interactions between routines could change without any notification.) Application Agent (amqzlaa0) --> MQOPEN ----> zstMQOPEN ------> ziiMQOPEN --------> zcpSendReceiveAgent Pass request --> by IPC --> --> zlaProcessMessage ----> zlaProcessMQIRequest ------> zlaMQOPEN --------> zsqMQOPEN ----------> kpiMQOPEN ..... ------------> kqiAuthor
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://stackoverflow.com/questions/22456722/mqrc-not-authorized-reason-code-2035 or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it https://www.experts-exchange.com/questions/21863362/HELP-MQ-Series-error-when-using-sample-'amqsput'-reason-code-2035.html only takes a minute: Sign up MQRC_NOT_AUTHORIZED Reason Code 2035 up vote 0 down vote favorite 1 I have set up a MQ Server 7.1 on my local machine. I have set up a Queue Manager : QM_APPLE I am code 2 trying to run the sample .Net Code from the MQ Examples to PUT a message on the Queue : Q1. When I try to instantiate the MQQueueManager, I get the above error. I have tried following the Authorization steps in http://www-01.ibm.com/support/docview.wss?uid=swg21166937 but I am still getting the error. Obviously I am not specifying the parameters correctly here. Can anyone help? websphere-mq mq share|improve this question edited Mar 17 '14 at 14:54 asked Mar 17 '14 at 14:17 Greg 1,16121439 ended with reason This is the cmd line I am trying to use : setmqaut -m QM_APPLE -t qmgr -p greg@xyz-think +alladm ..... where I am the administrator on the machine name xyz-think –Greg Mar 17 '14 at 14:54 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted alladm is administrative privileges. It doesn't work for API privileges. Try with +allmqi. But that's generally not advisable. Try to drill down to specific authorization (like put, get, setid, setall) when you start developing a real application. http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp?topic=%2Fcom.ibm.mq.ref.adm.doc%2Fq083500_.htm share|improve this answer answered Mar 17 '14 at 16:26 Umapathy 593415 I have trawled that page for hours and tried scores of other IBM authored "fixes". Nothing works. I have tried with your suggestion and it doesn't work. The error is still being thrown. The setmqaut tells me the command executed successfully but the error persists. There was another IBM "fix" that said the server administrator couldnt be the admin for a queue manager. Crazy but true. I added a new user to mqm group. Didnt work. Tried doing a get on the message. Didnt work. How can I drill down? Why can a message just be given saying what object needs permission. The logs are just as useless... –Greg Mar 17 '14 at 19:59 First create a normal (non mqm user) and give permissions. mqm and members of mqm are specifically blocked from MQ
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > HELP! MQ Series error when using sample 'amqsput' - reason code 2035 Want to Advertise Here? Solved HELP! MQ Series error when using sample 'amqsput' - reason code 2035 Posted on 2006-05-25 Java App Servers 1 Verified Solution 3 Comments 19,151 Views Last Modified: 2013-12-10 I'm trying to establish exactly why my UNIX user (t20ora) can't "put" messages on and "get" messages from the test queue, (as provided by the MQ Series install), but am up against a brick wall! My UNIX Environment: - Solaris version: SunOS sauron 5.9 Generic_118558-02 sun4u sparc SUNW,Ultra-4 - Websphere MQ Series v5.3 (installed from 'C44J8ML.tar.Z', downloaded directly from IBM's website) -------------------------------------------------------------------------------- Actions undertaken: Running the test 'put' and 'get' from the designated queue: Trying to put & get a test message to the designated queue gives the following problem.... -------------------------------------------------------------------------------- ################################################## - As mqm user (the user whom MQ Series was installed as) sauron:mqm >cd /opt/mqm/samp/bin/ sauron:mqm >./amqsput INPUT_OUTPUT_Q Sample AMQSPUT0 start target queue is INPUT_OUTPUT_Q test message Sample AMQSPUT0 end sauron:mqm >./amqsget INPUT_OUTPUT_Q Sample AMQSGET0 start message