| Author |
Message
|
| donnadfrb |
 Posted: Fri Dec 05, 2014 12:22 pm Post subject: AMQ6125An internal WebSphere MQ error... |
 |
|
Newbie
Joined: 05 Dec 2014
Posts: 3
|
OS = Microsoft Windows Server 2012
IBM Websphere MQ v 7.1.0.4
New installation and configuration. Lots of *.FDC Files. This is the first one for the day....
Any suggestions to correct this would be greatly apprecieated.
donnad
-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri December 05 2014 13:16:36 Central Standard Time |
| UTC Time :- 1417806996.206000 |
| UTC Time Offset :- -360 (Central Standard Time) |
| Host Name :- xxxxxxxxxxxxxxxxxx |
| Operating System :- Windows Ver 6.2 (7) Server Standard x64 Edition, Build |
| 9200 |
| PIDS :- 5724H7220 |
| LVLS :- 7.1.0.4 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- E:\Program Files (x86)\IBM\WebSphere MQ |
| Installation Name :- MQ71 (1) |
| Probe Id :- KN717045 |
| Application Name :- MQM |
| Component :- kpiMulticastTask |
| SCCS Info :- lib/lqm/amqkmuma.c, 1.5.1.2 |
| Line Number :- 529 |
| Build Date :- Nov 7 2013 |
| CMVC level :- p710-004-131106 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- E:\Program Files (x86)\IBM\WebSphere MQ\bin\amqzmu |
| c0.exe |
| Addressing mode :- 32-bit |
| Process :- 00002380 |
| Thread :- 00000021 |
| QueueManager :- QM_xxxxxxxxxxxxxxx |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 77 |
| ConnId(2) QM :- 45 |
| Last HQC :- 2.10.10-579080 |
| Last HSHMEMB :- 2.11.11-1925552 |
| Major Errorcode :- xecS_E_MEM_SET_NOT_FOUND |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Dec 05, 2014 12:34 pm Post subject: Re: AMQ6125An internal WebSphere MQ error... |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| donnadfrb wrote: |
| New installation and configuration. Lots of *.FDC Files. This is the first one for the day.... |
Do you have this version of WMQ on any other Win2012 servers? If so, did you follow the same installation procedure? If not, are you sure you've met all the pre-reqs and configured the install accordingly? Specifically:
What user id is running the WMQ software? Does that user have all the rights it needs?
Does the software produce FDC files on start up or under specific circumstances, e.g. when an application connects / puts a message / accesses a database?
Is the server physical or virtual?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Dec 05, 2014 12:40 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Are there any Comment lines in the FDC header?
What's the top part of the function stack, right after the header - just the first few lines.
Obligatory Windows: Did you restart the machine after installing MQ? Are you logged in as a local ID when you need to be using a domain ID or vice versa? |
|
| Back to top |
|
|
| donnadfrb |
| Posted: Fri Dec 05, 2014 1:11 pm Post subject: AMQ6125 An internal WebSphere MQ error... |
|
|
Newbie
Joined: 05 Dec 2014
Posts: 3
|
Thanks for the replies!
Server is Virtual. I did a prior install on the sandbox same OS. No issues! Worked like a champ. Same installation procedure.
This place is so locked down I am not 100% positive that I am authorized. I had someone else check and they confirmed that I do.
I rebooted the machine and the FDC files are created at startup.
Yes, I restarted the machine after installing MQ. MQ is running as a local system account. Does not use a domain id.
The following is the first FDC file after startup.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri December 05 2014 14:54:43 Central Standard Time |
| UTC Time :- 1417812883.951000 |
| UTC Time Offset :- -360 (Central Standard Time) |
| Host Name :- LR3DWVSTAR00 |
| Operating System :- Windows Ver 6.2 (7) Server Standard x64 Edition, Build |
| 9200 |
| PIDS :- 5724H7220 |
| LVLS :- 7.1.0.4 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- E:\Program Files (x86)\IBM\WebSphere MQ |
| Installation Name :- MQ71 (1) |
| Probe Id :- KN717045 |
| Application Name :- MQM |
| Component :- kpiMulticastTask |
| SCCS Info :- lib/lqm/amqkmuma.c, 1.5.1.2 |
| Line Number :- 529 |
| Build Date :- Nov 7 2013 |
| CMVC level :- p710-004-131106 |
| Build Type :- IKAP - (Production) |
| UserID :- SYSTEM |
| Process Name :- E:\Program Files (x86)\IBM\WebSphere MQ\bin\amqzmu |
| c0.exe |
| Addressing mode :- 32-bit |
| Process :- 00002292 |
| Thread :- 00000021 |
| QueueManager :- QM_LR3DWVSTAR00 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 83 |
| ConnId(2) QM :- 45 |
| Last HQC :- 2.10.10-579080 |
| Last HSHMEMB :- 2.11.11-751048 |
| Major Errorcode :- xecS_E_MEM_SET_NOT_FOUND |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
zmuThreadMain
zmuMulticastTask
kpiMulticastTask
xcsFFST
Thanks in Advance,
donna |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Dec 06, 2014 12:09 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As had already been asked but I can't see the answer
Is the System part of a Windows Domain?
If so then you CAN NOT RUN MQ UNDER THE DEFAULT SYSTEM ACCOUNT
I see this a lot with my customers when they try to setup a test server.
To overcome this run the prepare MQ Wizard and enter the username/password of the domain special account as detailed in the documentation.
If as you say, the place is locked down tight then you will have to get the Domain Admins/Security people to set the accounts and groups up for you.
As I said above, I see this quite a lot. I have a document that I give to them that describes in all its gory detail how to setup the groups/accounts for Server 2008 and Server 2012. Sorry, I can't share them with you but there is nothing stopping you from crerating your own so that the domain Admins can do the job properly.
If this isn't the problem then I'd probably wipe MQ totally (including anything in the Regisrty (boo hiss)), reboot and try the installation again.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| donnadfrb |
| Posted: Sat Dec 06, 2014 12:56 pm Post subject: |
|
|
Newbie
Joined: 05 Dec 2014
Posts: 3
|
Thanks!
We are not using a domain account.
I figured out the problem. On the initial install the MUSR_MQADMIN was added to the Administrators group. After the reboot and startup the MUSR_MQADMIN id was removed from the Administrators group. I have to put a change in to get the MUSR_MQADMIN added to the Administrator's group permanently.
Once I added the id back into the Administrators group the issue was resolved.
Seems to me a more descriptve error message could have had me on the right track to resolution.
donna |
|
| Back to top |
|
|
|
|
