CODEWITHSUNDEEP
ibm-mq
user3586992
user3586992

Reputation: 31

IBM MQ - AMQ6109: An internal WebSphere MQ error has occurred

I am trying to start queue manager on windows but getting error as AMQ6109 - An Internal WebSphere MQ has occurred. 

WebSphere MQ queue manager 'IIB9QMGR' starting.
The queue manager is associated with installation 'Installation1'.
AMQ6109: An internal WebSphere MQ error has occurred.

Verified FDC and I could see below details 

WebSphere MQ First Failure Symptom Report
Date/Time:- Tue October 17 2017 20:31:24 India Standard Time
UTC Time :- 1508252484.533000
UTC Time Offset   :- 330 (UNKNOWN))
Operating System :- Windows 7 Enterprise x64 Edition, Build 7601:SP1
PIDS :- 724H7220
LVLS :- 7.5.0.1
Product Long Name :- WebSphere MQ for Windows
Vendor :-IBM
Installation Path :- C:\Program Files (x86)\IBM\WebSphere MQ
Installation Name :- Installation1    (1)
Probe Id          :- ZC041040
Application Name  :- MQM
Component         :- zcsPipeCreate
SCCS Info         :- F:\build\slot1\p750_P\src\libzc\amqzcsbn.c,
Line Number       :1960
Build Date        :- Mar8 2013
Build Level:-p750-001-130308
Build Type:- IKAP - (Production)
UserID:- spotlapelli
Process Name:- C:\Program Files (x86)\IBM\WebSphere MQ\bin\amqzxma0.exe
Addressing mode   :- 32-bit
Process           :- 00007924
Thread            :- 00000001
QueueManager      :- IIB9QMGR
UserApp           :- FALSE
ConnId(1) IPCC    :- 2
ConnId(2) QM      :- 2
ConnId(3) QM-P    :- 2
ConnId(4) App     :- 2
Last HQC          :- 2.0.0-575228
Last HSHMEMB      :- 4.0.0-22980
Major Errorcode   :- STOP
Minor Errorcode   :- OK
Probe Type        :- HALT6109
Probe Severity    :- 1
Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred
FDCSequenceNumber :- 0

Comment1          :- The filename, directory name, or volume label    syntax is in incorrect 
Comment2          :- \\.\pipe\1\IIB9QMGR\zsocketEC\Zagent

Performed below steps to resolve but did not worked

  1. Restart PC and start queue manager
  2. Uninstall and Install MQ

Upvotes: 1

Views: 9175

Answers (1)

JasonE
JasonE

Reputation: 2026

Given the limited amount of information posted here (no version, platform, other details), its a real challenge (but fortunately I like a challenge...)!

If I've calculated correctly, that probe comes out when a windows queue manager tries to create a named pipe and it fails (Probe 40 from zcsPipeCreate). It is quite rare of that call to fail, and not many causes - the only times it has been seen all turned out to be caused by external influences. A number of times stopping something called SWIFT application services avoided the problem (apparently there's a SWIFT update to it to fix this), although I have no idea what SWIFT Application Services are... If you are not running SWIFT, then you will need to open a PMR with IBM to debug further, although I would recommend updating this question with your full FDC header just in case anything else stands out.

The test program referred to in the link @JoshMc gave is as follows - perhaps try this?

#include <windows.h>
main()
{

  HANDLE hnp;
  int rc=0;

   hnp = CreateNamedPipe("\\\\.\\pipe\\1\\TESTQMGR\\zsocketEC\\Zagent",
        PIPE_ACCESS_DUPLEX, PIPE_TYPE_BYTE|PIPE_WAIT, 1, 1024,1024,
        NMPWAIT_USE_DEFAULT_WAIT, NULL);

    rc=GetLastError();

    if( hnp == INVALID_HANDLE_VALUE )
        printf("CreateNamedPipe failed with %d ",rc );
    else
        printf("NamedPipe created successfully");

}

Upvotes: 1

Related Questions