I got the JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED') message after clicking the Test button while configuring the SampleMDBConnectionFactory in WebSphere MQ Messaging Provider.

I have the MQ Server 8.0 (Trial) on the same Windows 8 machine with WebSphere Application Server installed. I am just trying to complete the exercise on the article: Using WebSphere MQ V7 as JMS Provider for WebSphere Application Server V7, V8.0 and V8.5.

I have the administrator rights on this machine and the ports from1414 to 1420 are opened in Windows Defender firewall. Also I have added myself to the 'mqm' MQ Admin group. And the dspmqaut shows I have all the following authorizations: get, browse, put, inq, set, crt, dlt, chg, dsp, passid, pasall, setid, setall, clr

Not sure where else to check. Appreciate any help. Thank you.

Getting to this late but wanted to at least provide a reply in case others have similar issues.

• First, go download the MS0P SupportPac and unzip it into the MQ Explorer drop-ins folder and restart Explorer if it is running.  If the extension loads correctly you should now see a new option when right-clicking on an event queue: Format Events.


• Go to the QMgr's Properties page in Explorer, select Events and enable Authorization Events.


• Recreate the error.


• Browse to the SYSTEM.ADMIN.QMGR.EVENT queue in Explorer.  It should now have at least two events.


• Right click and select Format Events to bring up the MS0P extension.


• Drill down to the authorization event you just generated.

The event message will have all the details of the auths error.  In this case it will probably either show that the app server's service account is not authorized, or that the connection is using an admin account but the CHLAUTH rule disabling remote admin access has not been overriden for this specific channel with a rule to permit admin access.

There are several other, less likely, possibilities.  In any case, enabling auths events and formatting them to human-readable form is one of the most effective ways top diagnose 2035 errors.

T.Rob, thanks for your explanation - worked perfectly for me. I was searching for a solution to a problem I'd encountered in one project with my dedicated development team and you saved me a lot of time with your solution.