|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Not Start MQ in cluster |
« View previous topic :: View next topic » |
Author |
Message
|
leo_grv |
Posted: Fri Mar 20, 2009 11:38 am Post subject: Not Start MQ in cluster |
|
|
 Newbie
Joined: 20 Mar 2009 Posts: 5
|
Help Me please,
I have a MSCS cluster in Windows server 2003 with WebSphere MQ 6.0.2.1. I can't run the MQ under MSCS olny with strmqsc command.
This problem only occurred in the first node in the second node work's fine. But the second node have a hardware problem.
I check the fdc file and look me this:
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri March 20 11:40:44 Central Standard Time (Mexico) |
| Host Name :- ISFILE001 (Windows Server 2003, Build 3790: Service |
| Pack 1) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.1 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MC064000 |
| Application Name :- MQM |
| Component :- CMQMServiceMgr::<ctor> |
| SCCS Info :- lib/admin/pc/winnt/mscs/amqmclut/amqmdbgn.cpp, 1.8.1.1 |
| Line Number :- 134 |
| Build Date :- Mar 26 2007 |
| CMVC level :- p600-201-070323 |
| Build Type :- IKAP - (Production) |
| UserID :- i0000406 |
| Process Name :- C:\WINDOWS\cluster\resrcmon.exe |
| Addressing mode :- 32-bit |
| Process :- 00000720 |
| Thread :- 00000003 |
| 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 |
| ((Could not get IMQServiceManager interface, Error: -2147467238)) |
| FDCSequenceNumber :- 0 |
| Comment1 :- (Could not get IMQServiceManager interface, Error: |
| -2147467238) |
| |
I reset the server 2 twice and its the same.
Can someone help me? please. |
|
Back to top |
|
 |
exerk |
Posted: Fri Mar 20, 2009 12:55 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Fix the hardware problem first as that may have a bearing on the issue. If the problem still occurs raise a PMR as the only hits I saw for that Probe Id were for V5.3. _________________ 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. |
|
Back to top |
|
 |
leo_grv |
Posted: Fri Mar 20, 2009 12:55 pm Post subject: |
|
|
 Newbie
Joined: 20 Mar 2009 Posts: 5
|
Hi everybody!
I resolve my problem. With the command AMQMSRVN -user <domain\>NEW_NAME -password <password>.
Someone change the administrator password for the MSCS, for this reason didn't run the MQ
Thanks |
|
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
|
|
|
|