| Author |
Message
|
| mrlazy |
 Posted: Mon May 08, 2006 10:57 am Post subject: QMgr unable to start |
 |
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
When I try to start one of our QMgrs, it says "WebSphere MQ was unable to display an error message 7017.".
We rebooted the system, but still the same problem. Infact other QMgr are running fine ..
Any thoughts please??
I tried to see the error logs, but could not find any error log located in this QMgr folder. Even in FDC erro file, it says the same thing and an internal MQ error. It does not give any other useful error code. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Mon May 08, 2006 11:16 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
what platform? anything in AMQERR01.LOG? any FFST's thrown? ...might it be AMQ7017:
| Quote: |
AMQ7017Log not available.
Severity:
40 : Stop Error
Explanation:
The queue manager was unable to use the log. This could be due to a log file being missing or damaged, or the log path to the queue manager being inaccessible.
Response:
Ensure that the LogPath attribute in the queue manager configuration file is correct. If a log file is missing or otherwise unusable, restore a backup copy of the file, or the entire queue manager
|
_________________
-wayne |
|
| Back to top |
|
|
| mrlazy |
| Posted: Mon May 08, 2006 11:26 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
It's on Windows (MQ5.3 csd5)
Heres a prt of FDC file:
Process Name :- D:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe
Major Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0
At MQ task bar,folowing is displayed:
Unable to recover QM_WBI/Queue Manager WebSphere MQ service.
The WebSphere MQ service has attempted to recover QM_WBI/Queue Manager, but all
attempts have failed. There will be no more attempts to recover this service.
Use WebSphere MQ Services to investigate why the service failed and could not
be restarted.
Should I change any thing (like log path, if so please let me know where should I do tht) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 08, 2006 11:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mrlazy wrote: |
| Should I change any thing |
No.
You should troubleshoot until you know what the problem is.
THEN you will know what to change.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon May 08, 2006 11:34 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
It would be useful to see the ENTIRE FDC header...
_________________
-wayne |
|
| Back to top |
|
|
| mrlazy |
| Posted: Mon May 08, 2006 11:36 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon May 08 14:23:11 Central Daylight Time 2006 |
| Host Name :- ********** (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.5 CSD05 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- HL083112 |
| Application Name :- MQM |
| Component :- mqlpgrlg |
| Build Date :- Sep 27 2003 |
| CMVC level :- p530-05-L030926 |
| Build Type :- IKAP - (Production) |
| UserID :- mqsiuid |
| Process Name :- D:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00004212 |
| Thread :- 00000001 |
| QueueManager :- QM_WBI |
| Major Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
|
| sandiksk |
| Posted: Mon May 08, 2006 11:41 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005
Posts: 133
|
|
| Back to top |
|
|
| mvic |
| Posted: Mon May 08, 2006 11:44 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| mrlazy wrote: |
| 530.5 CSD05 |
This problem is being reported against a very old level of the MQ code. May I propose upgrading to the latest CSD, as this issue might have been found and fixed in the last 2.5 years since CSD05. |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon May 08, 2006 12:00 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Do you actually see the AMQ7017 error in the AMQERR01.LOG file (or event viewer)?
Can you make the csd upgrade as mvic suggests?
_________________
-wayne |
|
| Back to top |
|
|
| mrlazy |
| Posted: Mon May 08, 2006 12:14 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Guys, Thanks a lot for your replies.
Following the link that you provided made every thing work fine.
Once again thansk a LOT for your help. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Mon May 08, 2006 1:21 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
This is not an issue, but just to follow from now on:
What should I be looking into the FDC file when a serious error occurs?Is it the Probe ID which might be useful in trouble shooting the problem or MajorErrorCode or any other combination of attributes?? |
|
| Back to top |
|
|
| mvic |
| Posted: Mon May 08, 2006 1:29 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| mrlazy wrote: |
This is not an issue, but just to follow from now on:
What should I be looking into the FDC file when a serious error occurs?Is it the Probe ID which might be useful in trouble shooting the problem or MajorErrorCode or any other combination of attributes?? |
.FDC files are intended for use by IBM Support people when analysing what has happened "deep inside" MQ. It is occasionally possible to use the information without opening a ticket with IBM though. Just browse through it, and check for (eg.) filenames, system error codes. The meanings for the system error codes are generally to be found in OS vendor manuals.
With an error code like "hrcE_MQLO_UNEXPECTED_OS_ERROR" in this case, it is likely that the system gave an error on return from a system call when MQ called it. The error code itself should hopefully be recorded further down the file.
Ultimately, though, these files are intended to contain information that supports detailed technical analysis of the internals of MQ. The format isn't documented fully for the user. If the contents of the .FDC file are a cause for concern, then it is best to call Support and get advice. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 08, 2006 1:33 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Usually, I start by searching the probeId on the support pages of IBM, to see if other incidents have come up and been logged by that id.
Sometimes you can read the errors and figure it out yourself - but as mvic says you should always be prepared to open a PMR when you have an FDC thrown.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
