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 SupportUnable to Start Queue Manager 9.0 after server restart

Post new topicReply to topic
Unable to Start Queue Manager 9.0 after server restart View previous topic :: View next topic
Author Message
rama91
PostPosted: Mon Jan 20, 2020 8:51 am Post subject: Unable to Start Queue Manager 9.0 after server restart Reply with quote

Novice

Joined: 28 Aug 2019
Posts: 15

MQ Version : IBM MQ 9.0.0.3
Platform : Windows Server 2012 R2 Server Standard Edition
System Type : 64 Bit OS,x64-based processor

Issue Description :- Unable to start IBM MQ Queue manager after a Server Restart. IBM MQ is configured to run under a domain Service account. This Service account has been granted permissions to perform "log on As a Service". The domain Service account exists in mqm/administrators group.

During Service startup, MQ produces loads of FDC's with varying probe ID's ZL047080/ZX165131. AMQ Error logs says "AMQ7227: IBM MQ encountered the following network error: The RPC server is unavailable."

Has someone encountered this issue previously ? Please advice.


Code:

-------------------------------------------------------------------------------
20/01/2020 15:24:53 - Process(2284.1) User(SRVWMBService) Program(amqzmuf0.exe)
                      Host(DV163NFUA009) Installation(BrokerMQ2)
                      VRMF(9.0.0.3) QMgr(IFACES_ADAPTER_QMGR)
                     
AMQ7227: IBM MQ encountered the following network error: The RPC server is
unavailable.

EXPLANATION:
 MQ failed to successfully complete a network operation due to the specified
error. If the error is encountered on systems that are part of a Windows 2000
domain it can indicate incorrect DNS or WINS configuration.
ACTION:
Ensure that your network is functioning correctly. On the Windows platform
check DNS and/or WINS settings to ensure that domain controllers, used for
authentication or authorisation functions, are accessible.
----- amqzfubn.c : 4032 -------------------------------------------------------


Snippet from FDC Files :-

Code:

| Probe Id          :- ZX165131                                               |
| Application Name  :- MQM                                                    |
| Component         :- zmuUtilityManager                                      |
| SCCS Info         :- F:\build\slot1\p900_P\src\lib\zu\amqzmut0.c,           |
| Line Number       :- 1192                                                   |
| Build Date        :- Feb 26 2018                                            |
| Build Level       :- p900-003-180226                                        |
| Build Type        :- IKAP - (Production)                                    |
| UserID            :- SRVWMBService                                          |
| Process Name      :- G:\Program Files\IBM\MQ\bin64\amqzmur0.exe             |
| Arguments         :- -m IFACES_ADAPTER_QMGR                                 |
| Addressing mode   :- 64-bit                                                 |
| Process           :- 00003616                                               |
| Thread            :- 00000001    Restartable                                |
| Session           :- 00000000                                               |
| QueueManager      :- IFACES_ADAPTER_QMGR                                    |
| UserApp           :- FALSE                                                  |
| ConnId(1) IPCC    :- 8                                                      |
| ConnId(2) QM      :- 26                                                     |
| Last HQC          :- 2.0.0-2185792                                          |
| Last HSHMEMB      :- 2.18.18-5184                                           |
| Last ObjectName   :-                                                        |
| Major Errorcode   :- zrcE_UNEXPECTED_ERROR                                  |
| Minor Errorcode   :- OK                                                     |
| Probe Type        :- INCORROUT                                              |
| Probe Severity    :- 2                                                      |
| Probe Description :- AMQ6125: An internal IBM MQ error has occurred.        |
| FDCSequenceNumber :- 0                                                      |
|                                                                             |
+-----------------------------------------------------------------------------+


Code:

| Probe Id          :- ZL047080                                               |
| Application Name  :- MQM                                                    |
| Component         :- zllRegisterAsyncProcess                                |
| SCCS Info         :- F:\build\slot1\p900_P\src\lib\lqm\amqzlla0.c,          |
| Line Number       :- 358                                                    |
| Build Date        :- Feb 26 2018                                            |
| Build Level       :- p900-003-180226                                        |
| Build Type        :- IKAP - (Production)                                    |
| UserID            :- SRVWMBService                                          |
| Process Name      :- G:\Program Files\IBM\MQ\bin64\amqzxma0.exe             |
| Arguments         :- -m IFACES_ADAPTER_QMGR -u SRVWMBService@ADDEV          |
| Addressing mode   :- 64-bit                                                 |
| Process           :- 00003424                                               |
| Thread            :- 00000001    ECMain                                     |
| Session           :- 00000000                                               |
| QueueManager      :- IFACES_ADAPTER_QMGR                                    |
| UserApp           :- FALSE                                                  |
| ConnId(1) IPCC    :- 2                                                      |
| ConnId(2) QM      :- 2                                                      |
| ConnId(3) QM-P    :- 2                                                      |
| ConnId(4) App     :- 2                                                      |
| Last HQC          :- 2.0.8-6075712                                          |
| Last HSHMEMB      :- 2.19.19-4224                                           |
| Last ObjectName   :-                                                        |
| Major Errorcode   :- STOP                                                   |
| Minor Errorcode   :- OK                                                     |
| Probe Type        :- HALT6109                                               |
| Probe Severity    :- 1                                                      |
| Probe Description :- AMQ6109: An internal IBM MQ error has occurred.        |
| FDCSequenceNumber :- 0                                                      |
|                                                                             |
+-----------------------------------------------------------------------------+
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jan 20, 2020 11:34 am Post subject: Reply with quote

Poobah

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

Why the server reboot? What changes to the o/s? What changes to MQ?
_________________
My life flows on in endless song;
How can I keep from singing?
Back to top
View user's profile Send private message
rama91
PostPosted: Mon Jan 20, 2020 12:11 pm Post subject: Reply with quote

Novice

Joined: 28 Aug 2019
Posts: 15

A Security patch was applied to the windows Server and was restarted. After which IBM MQ failed to start throwing out "The RPC server is unavailable" error.

Service account has all necessary permissions on DC Side to query the group membership with delegate authority.

Windows Server is able to talk to Domain Controller and RPC windows services (TCP/IP 135 ) all seem to be enabled.Still MQ wont start.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jan 20, 2020 12:24 pm Post subject: Reply with quote

Poobah

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

... and all of this was working before the security patch reboot?
_________________
My life flows on in endless song;
How can I keep from singing?
Back to top
View user's profile Send private message
rama91
PostPosted: Mon Jan 20, 2020 1:54 pm Post subject: Reply with quote

Novice

Joined: 28 Aug 2019
Posts: 15

Yes all were working before restart. Thanks this has been sorted out now. Broker/MQ Servers were missing DNS entries to talk to Domain Controller. Adding FQDN DNS Suffix to IPv4 Advanced DNS entires, allowed Server to perform successful RPC calls to Domain Controller.

Able to start queue Manager now.
Back to top
View user's profile Send private message
hughson
PostPosted: Mon Jan 20, 2020 2:38 pm Post subject: Reply with quote

Grand Master

Joined: 09 May 2013
Posts: 1307
Location: Bay of Plenty, New Zealand

rama91 wrote:
Yes all were working before restart. Thanks this has been sorted out now. Broker/MQ Servers were missing DNS entries to talk to Domain Controller. Adding FQDN DNS Suffix to IPv4 Advanced DNS entires, allowed Server to perform successful RPC calls to Domain Controller.

Able to start queue Manager now.


Pretty good error message from the queue manager all in all then?

Code:
-------------------------------------------------------------------------------
20/01/2020 15:24:53 - Process(2284.1) User(SRVWMBService) Program(amqzmuf0.exe)
                      Host(DV163NFUA009) Installation(BrokerMQ2)
                      VRMF(9.0.0.3) QMgr(IFACES_ADAPTER_QMGR)
                     
AMQ7227: IBM MQ encountered the following network error: The RPC server is
unavailable.

EXPLANATION:
 MQ failed to successfully complete a network operation due to the specified
error. If the error is encountered on systems that are part of a Windows 2000
domain it can indicate incorrect DNS or WINS configuration.
ACTION:
Ensure that your network is functioning correctly. On the Windows platform
check DNS and/or WINS settings to ensure that domain controllers, used for
authentication or authorisation functions, are accessible.
----- amqzfubn.c : 4032 -------------------------------------------------------

_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportUnable to Start Queue Manager 9.0 after server restart
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.