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
Restart PC and start queue manager
Uninstall and Install MQ
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");
}
Related
I'm trying to generate documentation of my HL7 FHIR profiles using IG Publisher (publisher.jar). I'm running it on command line on macOS. I've uploaded the IG resource on Simplifier and it validates with no errors.
The problem is that i'm getting java.lang.NullPointerException. Full output below:
java -jar publisher.jar -ig fsh-generated/resources/ImplementationGuide-nfz.pozplus.json -tx n/a
FHIR IG Publisher Version 1.1.120 (Git# 210e48f945ad). Built 2022-05-13T15:20:39.709Z (8 days old)
Detected Java version: 11.0.10 from /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home on Mac OS X/x86_64 (64bit). 2048MB available
dir = /Users/marcingrudzien/Library/CloudStorage/OneDrive-Osobisty/Praca/iEHReu/NFZ/POZ-Plus/FHIR/sushi-test/NfzTest, path = /Users/marcingrudzien/.gem/ruby/3.1.2/bin:/Users/marcingrudzien/.rubies/ruby-3.1.2/lib/ruby/gems/3.1.0/bin:/Users/marcingrudzien/.rubies/ruby-3.1.2/bin:/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Postgres.app/Contents/Versions/latest/bin
Parameters: -ig fsh-generated/resources/ImplementationGuide-nfz.pozplus.json -tx n/a
Start Clock # sobota, 21 maja 2022 20:56:04 czas środkowoeuropejski letni (2022-05-21T20:56:04+02:00)
API keys loaded from /Users/marcingrudzien/fhir-api-keys.ini (00:00.0027)
Package Cache: /Users/marcingrudzien/.fhir/packages (00:00.0030)
Load Configuration from /Users/marcingrudzien/Library/CloudStorage/OneDrive-Osobisty/Praca/iEHReu/NFZ/POZ-Plus/FHIR/sushi-test/NfzTest/fsh-generated/resources/ImplementationGuide-nfz.pozplus.json (00:00.0053)
Root directory: /Users/marcingrudzien/Library/CloudStorage/OneDrive-Osobisty/Praca/iEHReu/NFZ/POZ-Plus/FHIR/sushi-test/NfzTest/fsh-generated/resources (00:00.0084)
Publishing Content Failed: null (00:00.0086)
(00:00.0087)
Use -? to get command line help (00:00.0087)
(00:00.0087)
Stack Dump (for debugging): (00:00.0088)
java.lang.NullPointerException
at org.hl7.fhir.igtools.publisher.Publisher.initializeFromJson(Publisher.java:2947)
at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:2168)
at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:854)
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:10144)
I hope someone here could help me. I could provide any additional information, if needed.
From the stack dump, you are missing a "path" property in your json config file, but I highly recommend that you switch to using the new set up, a ini file that points to a template and a IG resource. Use something like the sample-ig as a starter (https://github.com/FHIR/sample-ig) or see the how-to (https://build.fhir.org/ig/FHIR/ig-guidance/index.html)
I have a module exporting nat/1 to test/generate natural numbers:
:- module nat.
:- interface.
:- import_module int.
:- pred nat(int).
:- mode nat(in) is det.
:- mode nat(out) is multi.
:- implementation.
:- pragma promise_pure(nat/1).
nat(_::in).
nat(0::out).
nat(X::out) :- nat(Y), X = Y + 1.
and a main module in the same directory to try it out:
:- module main.
:- interface.
:- import_module io.
:- pred main(io__state::di, io__state::uo) is cc_multi.
:- implementation.
:- import_module nat.
main(!IO) :- nat(X), print(X, !IO).
I run mmc --make-int nat.m which successfully generates the interface files, but then when I run mmc main.m I get the following error:
/usr/bin/ld: main.o: in function `<predicate 'main'/2 mode 0>':
main.c:(.text+0x45): undefined reference to `<predicate 'nat.nat'/1 mode 1>'
collect2: error: ld returned 1 exit status
I'm using MMC version 20.06.1, on x86_64-pc-linux-gnu.
Am I missing something obvious? Code improvements are also very welcome.
After "mmc --make-int nat.m", the command you need to run is not "mmc main.m",
but "mmc main.m nat.m". The former compiles only main.m, while the latter also compiles nat.m. Both attempt to build an executable from the resulting
object files, but the former will fail, since the definition of the "nat" predicate would be in the object file it does not generate.
In general, instead of trying to manage the creation of interface files, object files and executables manually, it is much easier to use an automated
build system: either the mmake script, or mmc --make.
As for code improvements, I would suggest replacing io__state with just plain io, which is a lot shorter. We added "io" as a synonym for the "state"
type in io.m specifically to make this possible.
I have created Queue manager on azure file share and when I am starting I getting below error.
I have given all the permission to file share folder.
If specific rights needs to be given to any user or group.
after analyzing log found below content.
11/3/2020 06:14:24 - Process(5044.1) User(wmqvm1) Program(STRMQM.EXE)
Host(wmqvm1) Installation(Installation1)
VRMF(9.2.0.0)
Time(2020-11-03T06:14:24.128Z)
CommentInsert1(Windows Server 2019 Server Datacenter Edition, Build 17763 (MQ Windows (x64 platform) 64-bit))
CommentInsert2(C:\Program Files\IBM\MQ (Installation1))
CommentInsert3(9.2.0.0 (p920-L200710.TRIAL))
AMQ6287I: IBM MQ V9.2.0.0 (p920-L200710.TRIAL).
EXPLANATION:
IBM MQ system information:
Host Info :- Windows Server 2019 Server Datacenter Edition, Build 17763
(MQ Windows (x64 platform) 64-bit)
Installation :- C:\Program Files\IBM\MQ (Installation1)
Version :- 9.2.0.0 (p920-L200710.TRIAL)
ACTION:
None.
----- amqxeida.c : 6604 -------------------------------------------------------
11/3/2020 06:14:24 - Process(5044.1) User(wmqvm1) Program(STRMQM.EXE)
Host(wmqvm1) Installation(Installation1)
VRMF(9.2.0.0)
Time(2020-11-03T06:14:24.127Z)
ArithInsert1(85)
AMQ7125I: There are 85 days left in the trial period for this copy of IBM MQ.
EXPLANATION:
This copy of IBM MQ is licensed for a limited period only.
ACTION:
None.
----- amqxlic0.c : 613 --------------------------------------------------------
C:\Users\wmqvm1>dspmqver
Name: IBM MQ
Version: 9.2.0.0
Level: p920-L200710.TRIAL
BuildType: IKAP - (Production)
Platform: IBM MQ for Windows (x64 platform)
Mode: 64-bit
O/S: Windows Server 2019 Server Datacenter Edition, Build 17763
InstName: Installation1
InstDesc:
Primary: Yes
InstPath: C:\Program Files\IBM\MQ
DataPath: C:\ProgramData\IBM\MQ
MaxCmdLevel: 920
LicenseType: Trial
System Configuration:
Windows 7 professional SP1 (64 bit)
Uninstalled MQ Client 7.5
Later tried installing MQ Client 9.0, downloaded from here.
But installation after running for 2 minutes, failed in the end with the below error. I had choose default setup components.
Blockquote
Error 1713. IBM MQ (Installation1) cannot install one of its required products. Contact your technical support group.
Looked into temp folder installation log files. The installation has failed # CustomAction "iwiInstall32bitRuntime".
MSI (s) (2C:A0) [17:36:55:139]: Note: 1: 2203 2: C:\PATH \IBM
MQ\9.0.0.0-IBM-MQC-Win64\Windows\msi\IBM MQ 32bitSupport.msi 3:
-2147287038
CustomAction iwiInstall32bitRuntime returned actual error code 2 (note
this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (2C:1C) [17:36:55:139]: Note: 1: 1713 2: IBM MQ
(Installation1) 3: 1631
Info 2835.The control ErrorIcon was not found on dialog SetupError.
Error 1713.IBM MQ (Installation1) cannot install one of its required
products. Contact your technical support group. System Error: 1631.
MSI (s) (2C:1C) [17:37:54:336]: Product: IBM MQ (Installation1) --
Error 1713.IBM MQ (Installation1) cannot install one of its required
products. Contact your technical support group. System Error: 1631.
Action ended 17:37:54: iwiInstall32bitRuntime. Return value 3.
Any RESOLUTION for this error?
I found the solution here https://developer.ibm.com/answers/questions/275503/mq-install-on-windows-fails-with-rc1713.html
The 9.0.0.0-IBM-MQC-Win64.zip file has the 32-bit and 64-bit compiler runtime MSI files in the wrong location relative to where Setup (IBM MQ.msi) is looking for them.
To workaround this issue, copy "%mq_install_media_path%\Windows\MSI\x86\IBM MQ 32bitSupport.msi" to "%mq_install_media_path%\Windows\MSI\", and copy "%mq_install_media_path%\Windows\MSI\x64\IBM MQ 64bitSupport.msi" to "%mq_install_media_path%\Windows\MSI\".
(where %mq_install_media_path% contains the unzipped 9.0.0.0-IBM-MQC-Win64.zip files).
When I ran a script on HP-UX server then I am getting below error. Script is calling one executable file( rm1p0018 ) which made by cobol file.
Here is the error message from the log:
Execution error : file 'rm1p0018'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
HP/MF COBOL Version: B.13.50
HP-UX df2hp405 B.11.11 U 9000/800
pid: 12766 gid: 20 uid: 9831
Wed Aug 8 08:52:19 2012
8:52am up 2 days, 11:04, 4 users, load average: 0.01, 0.01, 0.01
Thread mode: No Threads
RTS Error: COBOL
Sync Signals: COBOL
ASync Signals: COBOL
cobtidy on exception: False
Recently oracle database was migrated from HP-UX to AIX server with the upgraded version of 10g from 9i.
Intially application and DB both were resides on HP-UX server but now application is resides on HP-UX and DB is resides on AIX server.
Can someone help me out on this issue.
A little bit hard to guess the cause of this memory violation.
If you are able to recompile the Cobol program, I advice you to trace it using "ready trace." statement along with $set trace directive.
You will be able then to have a trace of all cobol paragraphs executed and deduce the one where the program stopped and raised the error.