| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| queue manager failed to start with amq6119 error code. |
« View previous topic :: View next topic » |
| Author |
Message
|
| smakkuri |
 Posted: Thu Mar 16, 2006 7:36 pm Post subject: queue manager failed to start with amq6119 error code. |
 |
|
Newbie
Joined: 16 Mar 2006
Posts: 1
|
I am not able to start the queue manager.
I get the following error in the FDC file.
I am running on O/S W2K3, MQ Series 5.3 CSD 09. I have setup MSCS cluster but have not added mq queue manager to the cluster yet. I changed the identity of IBM MQSeries service component (dcom) to use a domain account who is part of the local mqm group.
Any sugestions??
| PIDS :- 5724B4100 |
| LVLS :- 530.9 CSD09 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- AD028000 |
| Application Name :- MQM |
| Component :- adiOpenFile |
| Build Date :- Dec 13 2004 |
| CMVC level :- p530-09-L041213 |
| Build Type :- IKAP - (Production) |
| Process Name :- C:\IBM\MQSeries\bin\amqzxma0.exe |
| Process :- 00002584 |
| Thread :- 00000001 |
| QueueManager :- RAS00170 |
| 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 |
| (Rc=1336 from CreateFile) |
| FDCSequenceNumber :- 0 |
| Comment1 :- Rc=1336 from CreateFile |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Mar 17, 2006 12:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
CSD09 I hope you don't plan on using JMS on this qmgr.
Can you move to a more recent CSD like CSD11 or CSD12 ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Mar 17, 2006 2:03 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Windows eh,.....
My first suggestion is reboot the server. That resolves 99% of all problems on a Windows Server.
Otherwise, have a look at the information in the FFST header you posted. Pay particular attention to:
Component :- adiOpenFile (hint)
Process Name :- C:\IBM\MQSeries\bin\amqzxma0.exe (I wonder)
Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC (hmmm...)
Oh and there's alway the Event Viewer and hey, how about that Task Manager thingy... Pretty handy tools provided to you by Bill Gates and Company at no extra charge.
They're just there. All you have to do is look at them and apply a little aquired knowledge.
If none of that works, try Google or gosh, I dunno IBM's Support & Dowloads web site....
That's free too. All you have to do is go to http://www.ibm.com/support/us/ and past the Probe Id in the thingamajig and click "Search".
It's truely amazing what you can accomplish if you apply yourself but then I digress. Your talking about a Window OS so rebooting the server should fix it.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Mar 17, 2006 3:03 am Post subject: Re: queue manager failed to start with amq6119 error code. |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| smakkuri wrote: |
| Rc=1336 from CreateFile |
Further down in the FDC it should say which file failed to be opened/created. The Win32 error number is given, so we have a chance to understand what has gone wrong : the error message "An internal WebSphere MQ error has occurred" in the FDC is a generic don't-understand-how-to-handle-this message, and in this case is potentially misleading because it's actually an operating system condition that is being reported.
Looking up 1336 in Visual Studio .NET, I get "The access control list (ACL) structure is invalid." so check out possible corruption of the file, its security metadata, or filesystem in the region of this file. csmith28 says reboot; if this forces a self-mending disk check it might well solve the problem. I think you can run a disk check without rebooting - though I have not used W2K3 myself (only W2K, XP, ...) so I could be wrong. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
