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 IndexIBM MQ API SupportGetting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error

Post new topicReply to topic
Getting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error View previous topic :: View next topic
Author Message
nageshr99
PostPosted: Thu Jun 29, 2017 8:54 pm Post subject: Getting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error Reply with quote

Novice

Joined: 30 May 2017
Posts: 24

Hi,

We are getting the error as shown below:
"Getting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error " - when we run the execution file of the sample C++ program - imqsputc.cpp after compilation using GCCver 4.8.5 on linux scientific version 7.2.

Its a 64 bit - non threaded compilation.
we run the sample program using the below command:

imqsputc_64 q1 qm1 'svrch1/tcp/192.168.2.226(1414)'

where q1=input parameter 1 - local q created using MQ explorer version 8.0
where qm1 = input parameter 2 - Queue manager created using MQ explorer version 8.0
where 'svrch1/tcp/192.168.2.226(1414)' = input parameter 3- which mentions the server-connection channel name along with protocoltype/IP address/portnumber - which is created using MQ explorer version 8.0


Pls let us knw how to resolve this issue.

Thanks.
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Thu Jun 29, 2017 10:39 pm Post subject: Reply with quote

Sentinel

Joined: 17 Nov 2005
Posts: 835
Location: New Zealand

...and do you think you ought to be authorised to connect to this Queue Manager ? What authentication is it using ? It is an MQ v8 Queue Manager so CHLAUTH is in force....or have you switched it off ? Does this Queue Manager just allow anybody to connect ? Clearly that is not a good idea in the long term.

It might be better to give us the details you do know and what you've tried rather than just asking everyone what is wrong.

MQ Security is quite a big subject. Luckily there are lots of blogs about which give guidance on configuring MQ authorities and authentication. If you just Google 'MQ Authentication' you'll find quite a few hits.

Cheers,

Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
JosephGramig
PostPosted: Fri Jun 30, 2017 6:56 am Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1143
Location: Derby City, USA

@PaulClarke,

I will risks being too big for my pants...

Just because MQ Explorer 8 is in use, does not mean the Qmgr is V8.

dspmqver output from the Qmgr would be helpful as a starter.

The following would also be helpful (replace <QmgrName> with the actual Qmgr name):

echo dis qmgr|runmqsc <QmgrName>
Back to top
View user's profile Send private message AIM Address
fjb_saper
PostPosted: Fri Jun 30, 2017 10:25 am Post subject: Reply with quote

Grand Poobah

Joined: 18 Nov 2003
Posts: 19204
Location: LI,NY

So you got a not authorized response...

Why would you have expected anything else??

Did you do anything at all to obtain authorization??
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
nageshr99
PostPosted: Sun Jul 02, 2017 8:12 pm Post subject: Reply with quote

Novice

Joined: 30 May 2017
Posts: 24

Thanks.

It finally some how worked after executing the below command:

ALTER QMGR CHLAUTH(DISABLED) CONNAUTH(' ')
REFRESH SECURITY TYPE(CONNAUTH)
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Sun Jul 02, 2017 8:17 pm Post subject: Reply with quote

Sentinel

Joined: 17 Nov 2005
Posts: 835
Location: New Zealand

Bear in mind that CHLAUTH is there for a reason. The correct solution to security problems is rarely to just switch off the check.

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
nageshr99
PostPosted: Mon Jul 03, 2017 7:50 pm Post subject: Reply with quote

Novice

Joined: 30 May 2017
Posts: 24

PaulClarke wrote:
Bear in mind that CHLAUTH is there for a reason. The correct solution to security problems is rarely to just switch off the check.

Cheers,
Paul.


infact this CHLAUTH command alone did not work.CONNAUTH(' ') command along with the REFRESH SECURITY TYPE(CONNAUTH) command did the trick.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexIBM MQ API SupportGetting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error
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.