| Author |
Message
|
| NealM |
 Posted: Wed Aug 19, 2015 3:32 pm Post subject: An MQ v7.5 on Windows 10 fix |
 |
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
I recently let Microsoft upgrade my laptop from Win 8.1 64 to Win 10 64. Afterward I realized that some MQ functions like starting a local QMgr no longer worked. So I opened a PMR with IBM and got a suggested solution, with of course an unsupported OS disclaimer, but which solution worked.
So, if you also upgrade to Win 10 and run into this MQ error
| Quote: |
AMQ6119: An internal WebSphere MQ error has occurred ()
exitvalue = 71 |
OS disclaimer aside, try adding permissions to
"HKLM\\SOFTWARE\\Microsoft\\MSDTC\\XADLL" for mqm group: (this key only)
This of course using regedit, and in my case I had to first add the mqm group to the list of users/groups that could have permissions for the XADLL hive. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Aug 19, 2015 10:05 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Why would a registry key releated to
Microsoft Distributed Transaction coordinator
be stopping MQ from working?
Were you running MQ as an XA Transaction Mananger by any chance?
If you wern't then IMHO MS has screwed up their OS even more that I'd thought.
_________________
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 |
|
|
| NealM |
| Posted: Wed Aug 19, 2015 11:03 pm Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
I have no comment on whether MS is screwed up. However if you look in XADLL it does have several MQ objects. Specifically amqmtsxatm.dll, amqmtsxatmc.dll, MQ Client, and every local QMgr, each listing <MQ install path>\bin64\amqmtsxatm.dll in the data column.
My MQ install and setup was nothing special, MQ is just used occasionally for broker flow unit testing (but I don't remember anymore if I needed to specify Win 7 compatibility when I installed MQ over a year ago while my machine was still at Win 8.1; A few MB8 and/or MQ install pieces needed that, IIB 10 did not).
And the fix does work. Prior to the fix I could create a local QM, but I could not start it or any previously created local QMs. Post fix I can start, stop, whatever. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 20, 2015 12:07 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Removing and reinstalling fixed it for me.
_________________
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 |
|
|
| mqjeff |
| Posted: Thu Aug 20, 2015 4:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
As always when working with Windows 10, you should remember that the terms of the license specifically allow Microsoft the rights to harvest whatever data they want from your system.
This is crucial to any system that contains confidential, or even personal data. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 20, 2015 9:33 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
As always when working with Windows 10, you should remember that the terms of the license specifically allow Microsoft the rights to harvest whatever data they want from your system.
This is crucial to any system that contains confidential, or even personal data. |
That means by default everything should be encrypted. AMS is mandatory IMHO 
I am really glad to be retiring before W10 will be rolled out by Corporate IT.
_________________
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 |
|
|
| mqjeff |
| Posted: Thu Aug 20, 2015 9:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
And yet, they could easily capture your private keys.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Aug 20, 2015 9:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| That means by default everything should be encrypted. AMS is mandatory IMHO |
You've got more license budget than me.
A cost effective alternative to Win10's privacy concerns is of course Linux.
The other advantages you get (stability & a system that can be administered effectively by normal humans without additional medical support) are just marginal.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chmod+x |
| Posted: Fri Oct 21, 2016 2:42 pm Post subject: |
|
|
Newbie
Joined: 21 Oct 2016
Posts: 1
|
Thank you NealM!
I've been pulling my hair for hours until I saw your posting. I am running IB10 on my windows 10 dev machine. Today I couldn't restart my integrations or queue managers after a reboot of my laptop and kept getting the error message on the original message.
After I gave everyone the full permission to the key:
HKLM\\SOFTWARE\\Microsoft\\MSDTC\\XADLL
I can start everything!!! Thanks again. |
|
| Back to top |
|
|
|
|
