Мы используем mq версии 8.0.0.2, мы используем активную пассивную конфигурацию. В то время как мы переключаем сервер с активного на пассивный узел, мы не можем запустить единый администратор очередей с ошибкой ниже. и у нас есть наблюдатель под ошибкой в журналах администратора очередей и файл FDC. любая помощь в этом критическом приложении.
Ошибка:
Не удалось подключить общую службу «IBM WebSphere MQ (AMHMQ)» (с ошибкой «1057») при попытке запустить службу.
Файл FDC:
| Build Date :- Feb 17 2015 |
| Build Level :- p800-002-150217.2 |
| Build Type :- IKAP - (Production) |
| UserID :- SYSTEM |
| Process Name :- C:\Windows\Cluster\rhs.exe |
| Arguments :- |
| Addressing mode :- 64-bit |
| Process :- 00020948 |
| Thread :- 00000002 |
| Session :- 00000000 |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Last ObjectName :- |
| 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 |
| (***CMQMException Caught***: Failed to start the Service, status=1057) |
| FDCSequenceNumber :- 0 |
| Comment1 :- ***CMQMException Caught***: Failed to start the |
| Service, status=1057
AMQERR01.Log:
----- amqxfdcp.c : 829 --------------------------------------------------------
9/3/2018 01:38:23 - Process(19732.115) User(SYSTEM) Program(rhs.exe)
Host(XXXXXXXXXX) Installation(AMHMQ)
VRMF(8.0.0.2)
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 19732.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 874 --------------------------------------------------------
9/3/2018 01:42:17 - Process(20948.153) User(SYSTEM) Program(rhs.exe)
Host(XXXXXXX) Installation(AMHMQ)
VRMF(8.0.0.2)
AMQ6119: An internal WebSphere MQ error has occurred (Timed-out waiting for
MSCS resource 'QM1', to be terminated)
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 any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 829 --------------------------------------------------------
9/3/2018 01:42:17 - Process(20948.153) User(SYSTEM) Program(rhs.exe)
Host(XXXXXXX) Installation(AMHMQ)
VRMF(8.0.0.2)
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 20948.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 874 --------------------------------------------------------
@ Пожалуйста, помогите по этому вопросу.
@ JoshMc: Да, мы подняли PMR, а также проверяем тот же код ошибки 1057 с командой Windows, которая собирает журналы событий для лучшего понимания.
мы поделились журналами событий Windows с IBM.