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 IndexGeneral IBM MQ SupportFailed to launch queue manager after windows 10 upgrade

Post new topicReply to topic
Failed to launch queue manager after windows 10 upgrade View previous topic :: View next topic
Author Message
v4vball
PostPosted: Fri Aug 17, 2018 11:39 am Post subject: Failed to launch queue manager after windows 10 upgrade Reply with quote

Newbie

Joined: 17 Aug 2018
Posts: 6

After upgrading windows 10 to 2018 April update, I can not start queue manager (v8) any more with the windows account used for MQ installation , unless I run strmqm in elevated mode as administrator.

and this use is in Administrators and mqm group


Last edited by v4vball on Fri Aug 17, 2018 8:34 pm; edited 1 time in total
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Aug 17, 2018 3:37 pm Post subject: Re: Failed to launch queue manager after windows 10 upgrade Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8128
Location: US: west coast, almost. Otherwise, enroute.

v4vball wrote:
After upgrading windows 10 to 2018 April update, I can not start queue manager (v any more with the windows account used for MQ installation , unless I run strmqm in elevated mode as administrator.

and this use is in Administrators and mqm group

It would help us help you if you posted the error that you received when you attempted to start the qmgr. You may need to look at the error folder for this qmgr for an error message.
_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
v4vball
PostPosted: Fri Aug 17, 2018 8:33 pm Post subject: Reply with quote

Newbie

Joined: 17 Aug 2018
Posts: 6

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri August 17 2018 16:17:41 Eastern Daylight Time |
| UTC Time :- 1534537061.880000 |
| UTC Time Offset :- 60 (Eastern Daylight Time) |
| Host Name :- SPRING |
| Operating System :- Windows 8 Professional x64 Edition, Build 9200 |
| PIDS :- 5724H7251 |
| LVLS :- 8.0.0.5 |
| Product Long Name :- WebSphere MQ for Windows (x64 platform) |
| Vendor :- IBM |
| O/S Registered :- 1 |
| Data Path :- C:\ProgramData\IBM\MQ |
| Installation Path :- C:\Program Files\IBM\WebSphere MQ |
| Installation Name :- Installation1 (1) |
| License Type :- Production |
| Probe Id :- ZT473001 |
| Application Name :- MQM |
| Component :- zutUpdateQMXADLLEntry |
| SCCS Info :- F:\build\slot1\p800_P\src\lib\zu\amqzutb0.c, |
| Line Number :- 4718 |
| Build Date :- May 19 2016 |
| Build Level :- p800-005-160518.TRIAL |
| Build Type :- IKAP - (Production) |
| UserID :- iibuser |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin64\strmqm.exe |
| Arguments :- IB10QMGR |
| Addressing mode :- 64-bit |
| Process :- 00009080 |
| Thread :- 00000001 |
| Session :- 00000002 |
| QueueManager :- IB10QMGR |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Last ObjectName :- |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (IB10QMGR) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 5 5 |
| Comment1 :- IB10QMGR |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zsllpiStartQM
zslStartQM
zutUpdateQMXADLLEntry
xcsFFST

MQM Trace History
--------{ xusGetLineType
--------} xusGetLineType rc=OK
--------{ xusAddStanzaLineList
---------{ xcsGetMemFn
---------} xcsGetMemFn rc=OK
--------} xusAddStanzaLineList rc=OK
-------{ xcsFreeMemFn
-------} xcsFreeMemFn rc=OK

-------{ xusReadSingleStanza
--------{ xusGetLineType
--------} xusGetLineType rc=OK
--------{ xusAddStanzaLineList
---------{ xcsGetMemFn
---------} xcsGetMemFn rc=OK
--------} xusAddStanzaLineList rc=OK


-------{ xufCloseIniRead
-------} xufCloseIniRead rc=OK
------} xcsBrowseFileCallback rc=OK
-----} xcsBrowseIniCallback rc=OK
----} xcsGetQMDetails rc=OK
----{ xcsFreeMemFn
----} xcsFreeMemFn rc=OK
----{ xcsDestroySharedSubpool
-----{ xstPurgeSharedSubpool
------{ xcsStopSubpoolServer
------} xcsStopSubpoolServer rc=xecI_E_NO_SUCH_SUBPOOL
-----} xstPurgeSharedSubpool rc=OK
----} xcsDestroySharedSubpool rc=OK
----{ xcsFreeMemFn
----} xcsFreeMemFn rc=OK
----{ xstReleaseSubpoolsLock
----} xstReleaseSubpoolsLock rc=OK
----{ xcsDestroyThreadMutexSem
-----{ xcsCloseHandle
-----} xcsCloseHandle rc=Unknown(1)
----} xcsDestroyThreadMutexSem rc=OK
----{ xcsDestroyThreadMutexSem
-----{ xcsCloseHandle
-----} xcsCloseHandle rc=Unknown(1)
----} xcsDestroyThreadMutexSem rc=OK
----{ xcsFreeMemFn
----} xcsFreeMemFn rc=OK
Back to top
View user's profile Send private message
v4vball
PostPosted: Fri Aug 17, 2018 8:48 pm Post subject: Reply with quote

Newbie

Joined: 17 Aug 2018
Posts: 6

I had no trouble creating or stopping any queue manager with the same account either with mq explorer or MQ commands.

I also created a new account as a member of both Administrators and mqm group,still no luck.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Aug 18, 2018 12:09 pm Post subject: Reply with quote

Grand Poobah

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

Windows is like that. For some things you just have to use an elevated command prompt or the system will block some of the things you are attempting to do...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
bruce2359
PostPosted: Sat Aug 18, 2018 12:23 pm Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8128
Location: US: west coast, almost. Otherwise, enroute.

v4vball wrote:
I had no trouble creating or stopping any queue manager with the same account either with mq explorer or MQ commands.

This is confusing. Are you saying that you could start and stop other qmgrs on WIN 10 platform, but just not this one?
_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
v4vball
PostPosted: Sat Aug 18, 2018 12:48 pm Post subject: Reply with quote

Newbie

Joined: 17 Aug 2018
Posts: 6

bruce2359 wrote:
v4vball wrote:
I had no trouble creating or stopping any queue manager with the same account either with mq explorer or MQ commands.

This is confusing. Are you saying that you could start and stop other qmgrs on WIN 10 platform, but just not this one?




let me reiterate, with a regular account, i had no trouble "creating" and "stopping", but "starting".

there are three different commands involved , crtmqm endmqm and strqmq.

it seems the windows update has made the regular account lose some sort of privileges needed for strqmq


Last edited by v4vball on Sat Aug 18, 2018 1:08 pm; edited 1 time in total
Back to top
View user's profile Send private message
v4vball
PostPosted: Sat Aug 18, 2018 12:55 pm Post subject: Reply with quote

Newbie

Joined: 17 Aug 2018
Posts: 6

fjb_saper wrote:
Windows is like that. For some things you just have to use an elevated command prompt or the system will block some of the things you are attempting to do...


the thing is ,everything was fine until this particular windows update.

it actually has happened to two of my computers.

previously , any windows account in the group of mqm can run strmqm command.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Aug 18, 2018 3:12 pm Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8128
Location: US: west coast, almost. Otherwise, enroute.

Adding to my confusion. Didn't you say you upgraded to Win 10 in April 2018? Or have I misunderstood?

v4vball wrote:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri August 17 2018 16:17:41 Eastern Daylight Time |
| UTC Time :- 1534537061.880000 |
| UTC Time Offset :- 60 (Eastern Daylight Time) |
| Host Name :- SPRING |
| Operating System :- Windows 8 Professional x64 Edition, Build 9200 |
| PIDS :- 5724H7251 |
| LVLS :- 8.0.0.5 |
| Product Long Name :- WebSphere MQ for Windows (x64 platform) |
| Vendor :- IBM |
| O/S Registered :- 1 |
| Data Path :- C:\ProgramData\IBM\MQ |
| Installation Path :- C:\Program Files\IBM\WebSphere MQ |
| Installation Name :- Installation1 (1) |
| License Type :- Production |
| Probe Id :- ZT473001 |
| Application Name :- MQM |
| Component :- zutUpdateQMXADLLEntry |
| SCCS Info :- F:\build\slot1\p800_P\src\lib\zu\amqzutb0.c, |
| Line Number :- 4718 |
| Build Date :- May 19 2016 |
| Build Level :- p800-005-160518.TRIAL |
| Build Type :- IKAP - (Production) |
| UserID :- iibuser |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin64\strmqm.exe |
| Arguments :- IB10QMGR |
| Addressing mode :- 64-bit |
| Process :- 00009080 |
| Thread :- 00000001 |
| Session :- 00000002 |
| QueueManager :- IB10QMGR |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Last ObjectName :- |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (IB10QMGR) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 5 5 |
| Comment1 :- IB10QMGR |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zsllpiStartQM
zslStartQM
zutUpdateQMXADLLEntry
xcsFFST

MQM Trace History
--------{ xusGetLineType
--------} xusGetLineType rc=OK
--------{ xusAddStanzaLineList
---------{ xcsGetMemFn
---------} xcsGetMemFn rc=OK
--------} xusAddStanzaLineList rc=OK
-------{ xcsFreeMemFn
-------} xcsFreeMemFn rc=OK

-------{ xusReadSingleStanza
--------{ xusGetLineType
--------} xusGetLineType rc=OK
--------{ xusAddStanzaLineList
---------{ xcsGetMemFn
---------} xcsGetMemFn rc=OK
--------} xusAddStanzaLineList rc=OK


-------{ xufCloseIniRead
-------} xufCloseIniRead rc=OK
------} xcsBrowseFileCallback rc=OK
-----} xcsBrowseIniCallback rc=OK
----} xcsGetQMDetails rc=OK
----{ xcsFreeMemFn
----} xcsFreeMemFn rc=OK
----{ xcsDestroySharedSubpool
-----{ xstPurgeSharedSubpool
------{ xcsStopSubpoolServer
------} xcsStopSubpoolServer rc=xecI_E_NO_SUCH_SUBPOOL
-----} xstPurgeSharedSubpool rc=OK
----} xcsDestroySharedSubpool rc=OK
----{ xcsFreeMemFn
----} xcsFreeMemFn rc=OK
----{ xstReleaseSubpoolsLock
----} xstReleaseSubpoolsLock rc=OK
----{ xcsDestroyThreadMutexSem
-----{ xcsCloseHandle
-----} xcsCloseHandle rc=Unknown(1)
----} xcsDestroyThreadMutexSem rc=OK
----{ xcsDestroyThreadMutexSem
-----{ xcsCloseHandle
-----} xcsCloseHandle rc=Unknown(1)
----} xcsDestroyThreadMutexSem rc=OK
----{ xcsFreeMemFn
----} xcsFreeMemFn rc=OK

_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
v4vball
PostPosted: Sat Aug 18, 2018 4:47 pm Post subject: Reply with quote

Newbie

Joined: 17 Aug 2018
Posts: 6

bruce2359 wrote:
Adding to my confusion. Didn't you say you upgraded to Win 10 in April 2018? Or have I misunderstood?
MemFn rc=OK
[/quote]


The OS on this brand new computer has always been windows 10 . i guess it makes sense, MQ 8 was first released in 2014, when windows 10 wasn't on the market. that is why it shows as "Windows 8" in the log.

btw, "Windows 10 2018 April" is actually the name of the latest windows 10 upgrade package. The upcoming one is called "windows 10 2018 October"
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Aug 19, 2018 10:46 am Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8128
Location: US: west coast, almost. Otherwise, enroute.

v4vball wrote:
MQ 8 was first released in 2014, when windows 10 wasn't on the market. that is why it shows as "Windows 8" in the log.


Id think that MQ internals interrogate the o/s VRM to determine features available. My Win 10 Pro shows Win 10 Pro.
_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Aug 19, 2018 4:08 pm Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8128
Location: US: west coast, almost. Otherwise, enroute.

Did you research Probe Id ZT473001 ?

Have you opened a PMR with IBM.
_________________
I would tell you a UDP joke, but you might not get it.
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 IndexGeneral IBM MQ SupportFailed to launch queue manager after windows 10 upgrade
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.