| Author |
Message
|
| AmolGotarne1234 |
 Posted: Mon Sep 08, 2014 10:41 pm Post subject: MQRC_NOT_Authorised |
 |
|
Newbie
Joined: 08 Sep 2014
Posts: 1
|
I have installed MQ Client in one system and MQ server in another system but when I am tring to connect to remote mq server system it gives me Error code:2035 MQRC_NOT_AUTHORISED....
Please suggest me helpful,or I need any configuration to server or client side... |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Sep 09, 2014 12:18 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Try reading the relevant section of the Secure Messaging Scenarios with WebSphere MQ. It may seem like over-kill but if you get into the habit of doing MQ Security properly the 'pain' diminishes over time.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 09, 2014 12:27 am Post subject: Re: MQRC_NOT_Authorised |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| AmolGotarne1234 wrote: |
Please suggest me helpful,or I need any configuration to server or client side...[/b] |
Also it would help if you told us what platform(s) you are using plus the full version including the fixPack level of both the client and the server software you are using.
finally, a lot of information about resolving this type of problem can be gleaned from the AMQERR01.log file (***). This file is written to by the queue Manager. As you go through the steps needed to authorize the client access the error messages recorded in this file will change.
(***) note that there may be at least TWO files of this name on your system. The one you are looking for is under the Queue manager Data
qmgrs/'qmgr_name'/errors/AMQERR01.log
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Sep 09, 2014 1:37 am Post subject: Re: MQRC_NOT_Authorised |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| smdavies99 wrote: |
| ...finally, a lot of information about resolving this type of problem can be gleaned from the AMQERR01.log file (***). This file is written to by the queue Manager. As you go through the steps needed to authorize the client access the error messages recorded in this file will change... |
Does that not require the MQS_REPORT_NOAUTH variable being set for UNIX systems? And a bounce of the queue manager if not already set?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 09, 2014 2:42 am Post subject: Re: MQRC_NOT_Authorised |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| exerk wrote: |
Does that not require the MQS_REPORT_NOAUTH variable being set for UNIX systems? And a bounce of the queue manager if not already set? |
It might very well be the case but as we don't know the platform yet we can't make that recommendation can we. This was why I asked the poster for the platform of both the client and server.
I've never had to use this variable (when diagnosing similar issues) on Windows despite the link to the note about the variable indicating that it was relevant to Windows as well as Unix/Linux etc.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Sep 09, 2014 2:49 am Post subject: Re: MQRC_NOT_Authorised |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| smdavies99 wrote: |
It might very well be the case but as we don't know the platform yet we can't make that recommendation can we. This was why I asked the poster for the platform of both the client and server.
I've never had to use this variable (when diagnosing similar issues) on Windows despite the link to the note about the variable indicating that it was relevant to Windows as well as Unix/Linux etc. |
The reason I brought it up is because it seems to be 'built-in' to Windows whether the variable is set or not, and if the OP is on *NIX might be somewhat confused if he/she didn't see any auth-related output in the logs but expected to.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
