| Author |
Message
|
| nrameshmq |
 Posted: Sat Aug 26, 2017 4:30 am Post subject: Security error |
 |
|
Apprentice
Joined: 09 Aug 2017
Posts: 35
Location: India, Mumbai
|
when application trying to connect to mq we are getting these issue please hel me
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2063'.
thank you |
|
| Back to top |
|
 |
| nrameshmq |
| Posted: Sat Aug 26, 2017 4:44 am Post subject: The issue got resolved |
|
|
Apprentice
Joined: 09 Aug 2017
Posts: 35
Location: India, Mumbai
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Aug 26, 2017 7:12 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please share with us how the issue was resolved.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| nrameshmq |
| Posted: Sun Aug 27, 2017 11:32 pm Post subject: |
|
|
Apprentice
Joined: 09 Aug 2017
Posts: 35
Location: India, Mumbai
|
I read about this issue on googe and found that it is related SLL error, But in my environment we didn't implemented SSL.
In my case i just restarted the server as it is UAT server. The problem got resolved automatically. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Aug 28, 2017 7:15 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
No doubt, this is a Windows box where all PD (problem determination) ends with: "Hey let's reboot the box".
2063 indicates that MQ asked the OS to look up a user ID's groups and the OS said "Nope, you are not authorized to look up groups".
This can happen when the Qmgr runs with a local ID but the connecting ID is a domain ID. Even when you log into the box with a domain ID, you can get this.
Anyway, I'm just guessing and sharing my experience with 2063.
The best solution to this is, don't use Windows for a server. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Aug 28, 2017 7:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
this and this are usually where windows installs get munged with security problems.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| nrameshmq |
| Posted: Fri Sep 01, 2017 4:03 am Post subject: |
|
|
Apprentice
Joined: 09 Aug 2017
Posts: 35
Location: India, Mumbai
|
| JosephGramig wrote: |
No doubt, this is a Windows box where all PD (problem determination) ends with: "Hey let's reboot the box".
2063 indicates that MQ asked the OS to look up a user ID's groups and the OS said "Nope, you are not authorized to look up groups".
This can happen when the Qmgr runs with a local ID but the connecting ID is a domain ID. Even when you log into the box with a domain ID, you can get this.
Anyway, I'm just guessing and sharing my experience with 2063.
The best solution to this is, don't use Windows for a server. |
Actually we are using AIX 7.1 not windows, I don't why it happend, As per our SME suggetion i restarted the server. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 01, 2017 7:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
| this and this are usually where windows installs get munged with security problems. |
And please don't forget this one either. It is one where I get the most push back... and thankfully with V9 there seems to be a comprehensive explanation as to why those rights are needed... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
