| Author |
Message
|
| kopparapusrikanth |
 Posted: Fri Oct 25, 2013 2:19 am Post subject: Regarding remote administration in using MQ explorer |
 |
|
Newbie
Joined: 24 Oct 2013
Posts: 8
|
When I am trying to add a remote queue manager to my MQ explorer it is throwing an error like this "Access not permitted. You are not authorized to perform this operation (AMQ4036)" but the other person is able to add my queue managers to their MQ explorer. I have compared all the groups and users in both the systems. Everything looks to be same.Can anyone please tell me why I am getting this problem?
Note:My MQ explorer is running on Windows7 machine and I am trying to add remote queue manager present on a windows XP machine. |
|
| Back to top |
|
 |
| McueMart |
| Posted: Fri Oct 25, 2013 2:29 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| The first step of troubleshooting issues like these is always to look in the error log of the QM you are trying to connect to. It should have a useful message telling you why you cant connect. |
|
| Back to top |
|
|
| kopparapusrikanth |
| Posted: Fri Oct 25, 2013 6:39 am Post subject: |
|
|
Newbie
Joined: 24 Oct 2013
Posts: 8
|
| Thank you McueMart. My problem is resolved.I have gone through the error logs on the other machine where I am trying to add remote queue manager. The root cause of my problem is due channel authentication. I solved this by configuring the channel authentication records of the remote channel(in this case it is a SYSTEM.DEF.SVRCONN). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 25, 2013 7:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
| kopparapusrikanth wrote: |
| Thank you McueMart. My problem is resolved.I have gone through the error logs on the other machine where I am trying to add remote queue manager. The root cause of my problem is due channel authentication. I solved this by configuring the channel authentication records of the remote channel(in this case it is a SYSTEM.DEF.SVRCONN). |
You should have left the SYSTEM.DEF.SVRCONN alone and configured a different channel for your needs.
SYSTEM.XXX channels are well known and any open channel there may represent a security risk. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Oct 25, 2013 7:32 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| kopparapusrikanth wrote: |
| (in this case it is a SYSTEM.DEF.SVRCONN). |
Don't use that channel - define a new one for your purposes and lock down the SYSTEM.DEF.SVRCONN so nothing can use it to connect.
_________________
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 |
|
|
|
|
