Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We have a number of Autosys jobs to trigger QVD reloads.
Even after the job succeeds ( which we can verify by checking the status on server), the corresponding Autosys job fails.
Below is the error message from script log :
Error while checking the status of task reload ABC.qvw (id=<some id>)
execID=<some id>, retries=3
Error Message : Message inspection failed
The task execution ended.
Can someone advise?
Check the document log file ABC.qvw.log for errors. If that doesn't exist (in the same place as ABC.qvw) then open ABC.qvw and check in the Document Properties that the option Generate Logfile is enabled.
Above error which I posted is from ABC.qvw log
I very much doubt that. Post that log file.
I think the issue is with old version of QMSEDX , though I am not quite sure.
Below is the error from script standard output file :
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at QMSEDX.Program.TriggerAndMonitorTask()
at QMSEDX.Program.Main(String[] args)
201401.qvw
Checking the status of task Reload of RD_201401.qvw (id=b07dffbd-483a-454a-af09-497e54f3456f execId=d487e135-817a-4885-8850-8b731eb35596)
Error while checking the status of task Reload of RD_201401.qvw (id=b07dffbd-483a-454a-af09-497e54f3456f execId=d487e135-817a-4885-8850-8b731eb35596), retries=3
Error message: Message inspection failed
Error while checking the status of task Reload of RD_201401.qvw (id=b07dffbd-483a-454a-af09-497e54f3456f execId=d487e135-817a-4885-8850-8b731eb35596), retries=2
Error message: Message inspection failed
Error while checking the status of task Reload of RD_201401.qvw (id=b07dffbd-483a-454a-af09-497e54f3456f execId=d487e135-817a-4885-8850-8b731eb35596), retries=1
Error message: Message inspection failed
Unable to get task status.
The task execution ended.
That's not from the log file ABC.qvw.log.
ABC.qvw log shows no error.
That is the reason task status is succeeded on server
I think so too. At least I used to get the same type of error with an older version of QMSEDX a long time ago.
You can eaqsily check whether this is due to the old QMSEDX version by installing a newer version (1.2 latest release) on your desktop/laptop and running it with the same parameters as the Autosys job does.
Peter