Mqseries Error Code = 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 channel. You need to understand what causes
Mq Error 2035 Completion Code 2
this failure. 2035 0x000007f3 MQRC_NOT_AUTHORIZED Cause MQRC 2035 (MQRC_NOT_AUTHORIZED) is returned when a user is mq disable channel authentication not authorized to perform the function that is attempted. Resolving the problem MQRC 2035 (MQRC_NOT_AUTHORIZED) is returned when a user is not authorized
The Call To Initialize The User Id Failed With Compcode 2 And Reason 2035.
to perform the function. Determine which object the user cannot access and provide the user access to the object. Debugging techniques: Use the dspmqaut (display authority command), to determine if the user has the authorization to access mqconn ended with reason code 2035 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 grant access to WebSphere MQ objects. You will then need to restart the queue manager to refresh the security cache, or via runmqsc mqrc_not_authorized c# 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 ..... ------------> kqiAuthorityChecks --------------> zfu_as_calculateauthority *** Print useful info! *** <-------------- zfu_as_calculateauthority <------------ kqiAuthorityChecks ..... <---------- kpiMQOPEN <-------- zsqMQOPEN <------ zlaMQOPEN <---- zlaProcessMQIRequest Pass response <-- zlaProcessMessage <-------- zcpSendReceiveAgent <-- by I
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 http://stackoverflow.com/questions/22456722/mqrc-not-authorized-reason-code-2035 About Us Learn more about Stack Overflow the company Business Learn more about http://stackoverflow.com/questions/25911557/websphere-mq-v8-mqrc-not-authorized-2035 hiring developers 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 only takes a minute: Sign up MQRC_NOT_AUTHORIZED Reason Code 2035 code 2 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 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 ended with reason 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 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. Th
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 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 only takes a minute: Sign up Websphere MQ v8 - MQRC_NOT_AUTHORIZED - 2035 up vote 5 down vote favorite 3 I am testing WebSphere on local for development purposes and now i wanted to move to new PC. But i dont remember exactly how i get rid of that error in title. I know there are tons of posts about this error since introduction MQ 7.1 how to disabled security. I remember last time i did runmqsc.exe QM_name -> ALTER CHLAUTH(DISABLED). But its not working anymore?! What else i need to change so anyone can connect to queue? > DIS QMGR CHLAUTH > 2 : DIS QMGR CHLAUTH AMQ8408: Display Queue Manager details. > QMNAME(QueueManager1) CHLAUTH(DISABLED) Thanks. java authentication authorization websphere-mq share|improve this question edited Sep 18 '14 at 16:10 Morag Hughson 3,489229 asked Sep 18 '14 at 11:32 JIV 450620 add a comment| 2 Answers 2 active oldest votes up vote 16 down vote accepted WebSphere MQ V7.1 introduced CHLAUTH rules which by default banned remote access by privileged users. To turn off CHLAUTH you are correct that you can issue ALTER QMGR CHLAUTH(DISABLED) However, you could also very simply allow yourself access on a particular channel as described in CHLAUTH - Allow some privileged admins. IBM MQ V8 introduced Connection Authentication which default demands a password to authenticate a remote privileged user. To make this OPTIONAL (as it is for non-privileged users) you can issue ALTER AUTHINFO(SYSTEM.DEFAULT.AUTHINFO.IDPWOS) AUTHTYPE(IDPWOS) CHCKCLNT(OPTIONAL) rather than turning it off completely with ALTER QMGR CONNAUTH(' ') After either of these commands you'll need to issue the following command for the queue manager to be aware of your changes. REFRESH SECURITY TYPE(CONNAUTH) You mention that this is for development purposes which is fair enough, but remember to turn these features on so that you can make your queue manager secure when using it in production! Also, remember that the queue manager error log will provide you with details about why your application got the 2035, for example, "Channel is Blocked" for CHLAUTH and "Missing password" for CONNAUTH. share|improve this answer edited Sep