| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| "Error 5023 bringing resource online" in MSCS |
« View previous topic :: View next topic » |
| Author |
Message
|
| Toot4fun |
 Posted: Mon Dec 10, 2007 7:41 am Post subject: "Error 5023 bringing resource online" in MSCS |
 |
|
Newbie
Joined: 10 Dec 2007
Posts: 1
|
Hello-
I installed MQ in a clustered Windows 2003 Server environment. Everything was fine, but after a reboot, I am unable to bring my IBM MQSeries MSCS resource online. It is in a cluster group with my Cluster IP Address, Cluster Name, Quorum and shared disk. All the other resources come Online, but the MQ resource always shows as Failed. If I try to bring it online, it fails and then tries to fail over to the other node. This also fails and the group flip-flops until the maximum number of retires is reached.
Event Viewer shows errors in the Application log and refers to an .FDC log file. In that log file, I see the following errors:
12/10/2007 10:17:09 - Process(1840.22) User([service_account]) Program(resrcmon.exe)
AMQ6119: An internal WebSphere MQ error has occurred (***CMQMException Caught***: Failed to start QM, status 5023)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 766 --------------------------------------------------------
12/10/2007 10:17:09 - Process(1840.22) User([service_account]) Program(resrcmon.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 1840.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 810 --------------------------------------------------------
12/10/2007 10:17:10 - Process(1840.22) User([service_account]) Program(resrcmon.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Error 5023 bringing resource online.)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 766 --------------------------------------------------------
12/10/2007 10:17:10 - Process(1840.22) User([service_account]) Program(resrcmon.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 1840.
ACTION:
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 810 -------------------------------------------------------- |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Dec 10, 2007 7:50 am Post subject: Re: "Error 5023 bringing resource online" in MSCS |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Toot4fun wrote: |
Event Viewer shows errors in the Application log and refers to an .FDC log file. In that log file, I see the following errors:
12/10/2007 10:17:09 - Process(1840.22) User([service_account]) Program(resrcmon.exe)
AMQ6119: An internal WebSphere MQ error has occurred (***CMQMException Caught***: Failed to start QM, status 5023)
|
FDC files don't look like that, queue manager logs do. Find the FDC files associated with these errors, examine the Probe Id you'll find near the top and search for it via Google and the IBM site. This probe id will give you much more information about the actual error, and the FDC itself (as the log entry says) will be the first thing IBM asks for if you end up raising a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
