Questions and Errors using IRCMD

[Anon]

Hi
We are trying to use IRCMD utility to push some configuration (threshold) into prognosis, also list online configuration. Unfortunately each time we are pushing a file with IRCMD, we do no have any output in the command line window and also no error in the stderr..

I found something in the log: ./Prognosis/Server/Log/ircmd.log saying:

------ Integrated Research Abend Node MN101 Thu Nov 17 13:05:10 2016
Exec: E:\Prognosis\Server\ircmd.exe
Module: E:\Prognosis\Server\irfrmwrk.dll
Exception_code: C0000005 ACCESS_VIOLATION
Fault_address: 74E9DAFE 00000001:0002CAFE
Stack_Trace:
Address Frame
----------------------------------------------------------------

Any idea why this module is making a memory violation ?

[GeraldC]

Hi There, Here's something to try initially just in case it is syntax or something:

1. Get a config from an already running threshold, let's pretend there's one called TH-NAME for this example. Then in a DOS command prompt:
CD \Prognosis\Server\Configuration
copy con GetThresholdConf.txt
LIST THRESHOLD "TH-NAME"
(press Ctrl Z to save it)
..\ircmd GetThresholdConf.txt
(the "..\" is required in the command)
(expected result is that it outputs the text of the running threshold)

2. Then pipe it to a file, and insert into the first line "START "
..\ircmd GetThresholdConf.txt > ThresholdConf.txt
(open ThresholdConf.txt in notepad, delete the first 2 lines, and insert START. For example:
Prognosis Command-Line Utility < - - - delete this line
------------------------------ < - - - - delete this line

START THRESHOLD "TH-NAME" < - - - START inserted
(save, close, back to the DOS command prompt to start the threshold)

3. start the threshold to see if it will start now without crashing ircmd:
..\ircmd ThresholdConf.txt

(expected result:
E:\Prognosis\Server\Configuration>..\ircmd ThresholdConf.txt
Prognosis Command-Line Utility
------------------------------
THRESHOLD STARTED... \node.TH-NAME \node
E:\Prognosis\Server\Configuration>
)

HTH

[Anon]

Thanks, my bad was to run the ircmd from /server instead of \Prognosis\Server\Configuration

[GeraldC]

That's a gotcha. Glad you've cracked it.