MQSeries.net :: View topic - Queue Manager not starting up.

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Queue Manager not starting up.

Queue Manager not starting up.

« View previous topic :: View next topic »

Author

Message

pnmraju

Posted: Fri Oct 24, 2008 12:20 pm Post subject: Queue Manager not starting up.

Novice

Joined: 28 Jun 2007
Posts: 19

We are having an issue while starting the Queue Manager. The problem we encountered was, There was a sudden surge in the power and the server got down and once the server got re-booted we were not able to start the Queue Manager. We are getting the following error.
"C:\Documents and Settings\Pakalapati.Raju>strmqm QMPRD.BODI.ATN.REG.MBK
WebSphere MQ queue manager 'QMPRD.BODI.ATN.REG.MBK' starting.
AMQ6119: An internal WebSphere MQ error has occurred ()"

We are getting the following error in the mq explorer
****************************************
* Command: amqmdain qmgr start QMPRD.BODI.ATN.REG.MBK
****************************************
WebSphere MQ queue manager 'QMPRD.BODI.ATN.REG.MBK' starting.
WebSphere MQ was unable to display an error message 893.
exitvalue = 71

Please help me in resolving this issue. using MQ version 6 on windows.

SAFraser

Posted: Fri Oct 24, 2008 2:22 pm Post subject:

Shaman

Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA

Were any FDC files created when you tried to start the qmgr?

What is the screen output if you try to start the qmgr from a command line with strmqm?

pnmraju

Posted: Fri Oct 24, 2008 3:08 pm Post subject:

Novice

Joined: 28 Jun 2007
Posts: 19

SAFraser

Posted: Fri Oct 24, 2008 5:19 pm Post subject:

Shaman

Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA

From the probe ID, the exit level, and the minor error code, I'd guess that either file permissions were corrupted or MUSR_MQADMIN's security was corrupted or the mqm group's security was corrupted.

I would definitely be interested in some other opinions on this.

If I were pretty sure there was little chance that there were messages of any volume on the queues, I'd delete the entire MQ installation, including data, and I'd clean the registry. I'd reinstall MQ, recreate the qmgr, and recreate the objects.

Failing that, I'd start with the easy stuff and work forwards. I'd make sure the mqm group is still intact and that files permissions on MQ directories are intact. I'd create a new local user, put it in the mqm group, and try to start the queue manager. If it generated the same error, I might try fooling with a new group, but that's a bit dicier.

I may be misreading the clues, and perhaps others will hypothesize that the log files are corrupted. If so, you can search this site for some ideas about creating a queue manager of the same name elsewhere and trying to use those new log files to start your queue manager.

Perhaps you should raise a PMR?

fjb_saper

Posted: Sat Oct 25, 2008 6:23 am Post subject:

Grand High Poobah

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

It could still be file/directory permissions on the log directory/ files.
Especially if somebody changed those permissions...
Worst case scenario: allocated file space full.
Is you logging linear or circular. If your logging is linear, what support pack are you using to maintain the linear logs?

Enjoy

_________________
MQ & Broker admin

kirankumar_hm

Posted: Sun May 16, 2010 10:57 pm Post subject:

Newbie

Joined: 16 May 2010
Posts: 1

WebSphere MQ was unable to display an error message 893.
exitvalue = 71

It was resolved.
Even I also faced the same problem/error. This problem will not come in the Websphere MQ 5.3 but you can see in V6.x and V7.

I tried to give all the permission as had the administrator privilages in Windows XP. Still did not worked for me. Finally I changed the user name.

Solution is :
If you logged as Administrator in Windows XP, problem will not occur. But if you are a user of windows and you have all the Administrator priviliges but your name has spaces(Example: "James Smith"), you need to change your name as without any space(Example: "JamesSmith")

It worked for me.

exerk

Posted: Sun May 16, 2010 11:21 pm Post subject:

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

kirankumar_hm wrote:

Thank you for sharing with us, but I think the original poster probably solved his/her issue nearly two years ago

_________________
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.

ashley5

Posted: Mon Aug 23, 2010 5:51 am Post subject:

Novice

Joined: 20 Feb 2006
Posts: 14

We got a funny on our Production server this weekend, and the error above is the closest I've managed to find (even though it's Version 6, not 5.3).

Firstly, I know we're not even vaguely up to date, but we unfortunately don't get to dictate upgrades... especially when the business are adamant that they're phasing MQ out... more than a year past their deadline, and we're still going strong...

Anyway, I also need to point out that our MQ Logs and QM are sitting on EMC Storage for easy (*cough*) migration to our failover server.

Here is the FDC at the initial failure:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sun August 22 03:32:18 South Africa Standard Time 201 |
| Host Name :- DUMMY_SERVER (Windows Ver 5.2 Build 3790: Service Pack 2) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- KY322000 |
| Application Name :- MQM |
| Component :- Amqmsrvn :: WinMain |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqmsrvn.exe |
| Process :- 00001904 |
| Thread :- 00000001 |
| Major Errorcode :- OK |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- DCOM object configured with Interactive/Launching user |
| id |
| Comment2 :- Configure DCOM object to use specific user id |
| |
+-----------------------------------------------------------------------------+

Now looking at that error, it seems that it's a DCOM issue with MQ setup, but that seems to only be related to first time installs? Also, we've been on CSD12 for close on 2 years now, so why all of a sudden?

This is after our IT department rolled out patches to this box (still trying to establish what, as they don't seem to know either), so I suppose something they installed broke MQ?

When we tried to start it manually later, this is the error we got:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sun August 22 13:33:07 South Africa Standard Time 201 |
| Host Name :- DUMMY_SERVER (Windows Ver 5.2 Build 3790: Service Pack 2) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- HL081010 |
| Application Name :- MQM |
| Component :- mqlpgolf |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00003884 |
| Thread :- 00000001 |
| QueueManager :- DUMMY_QM |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- hrcE_MQLO_ACCD |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806822) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545286178 20806822 |
| |
+-----------------------------------------------------------------------------+

Now I've seen messages saying this Probe ID is a result of the logpath changing, but it hasn't since this server went live (>2 years ago).

But here's the kicker. I cannot start the Queue Manager via the Windows MQ Services Snap-in... keeps giving :
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2059

The "solution" to this problem, is to run strmqm -c <QMGR_NAME>, which I did, and returned this:
Creating or replacing default objects for DUMMY_QM.
Default objects statistics : 0 created. 31 replaced. 0 failed.
Completing setup.
Setup completed.

So I figure I'll try to start the QM via the Command Line, and I do, without ANY issue.... Except the MQ Services report the Listener and Channel Initiator as stopped.

So I read some more, and see I should be using AMQMDAIN top stop and start the QM, but that does not work (although further reading today leads me to believe I may have made some mistakes in the commands).

Anyway, I'm wondering if anyone has any idea why I cannot start MQ from Windows, but I can from the command line.

Vitor

Posted: Mon Aug 23, 2010 6:40 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ashley5 wrote:

This is after our IT department rolled out patches to this box (still trying to establish what, as they don't seem to know either), so I suppose something they installed broke MQ?

You think? It runs for 2 years without issues, WMQ doesn't change but the OS does and suddenly it stops working?

One of the many risks of running OOS software like WMQv53 is that IBM stop testing it against new OS patches. You might want to mention that to the powers that be, and suggest that if they're going to run historic software they keep the rest of the software stack equally historic?

ashley5 wrote:

Anyway, I'm wondering if anyone has any idea why I cannot start MQ from Windows, but I can from the command line.

Does the service run as the same user id that's issuing the command line?
_________________
Honesty is the best policy.
Insanity is the best defence.

ashley5

Posted: Mon Aug 23, 2010 7:04 am Post subject:

Novice

Joined: 20 Feb 2006
Posts: 14

Quote:

You think? It runs for 2 years without issues, WMQ doesn't change but the OS does and suddenly it stops working?

I suppose I had that coming....

The service is running as mqadmin (local user), and we even log onto the box as mqadmin to to manage the Queue Manager. The QM is set to Manual start due to the EMC storage, so we always have to log on to start the QM.

One thing I have noticed. Currently we're running the Queue Manager from the Command Line, and Task Manager reports it running as user mqadmin. But there 1 single amqmsrvn.exe running as MUSR_MQADMIN.

Now, if I look at one of our test machines, all the amqxxxx.exe processes are running as MUSR_MQADMIN. The IBM WebSphereMQ service runs as Local System.

fjb_saper

Posted: Mon Aug 23, 2010 12:17 pm Post subject:

Grand High Poobah

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

Rerunning the post installation wizard should fix your problem with the dcom Id.
Have fun

_________________
MQ & Broker admin

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Queue Manager not starting up.

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