Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026! Turn data into bold moves, April 13 -15: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

EDX Response

Hello All,

I am using EDX 11 to get the list of failed tasks and run those tasks from .net application.

I get the list and run the one by one task using external event trigger.

I have 2 tasks which are failed in QMC.

When I run the QMSEDX.exe, I get the list of failed task as 2 and I run then one after the other.

1. Task A

2. Task B.

Task A runs fine, but fails in publisher and I get the status back as failed.

and Task A runs fine and completes the task in publisher. but unable to get the response in QMSEDX.exe.

When I debug the application, I get an error as

"System.Exception: Could not find a result for the specified execution ID "9ae02224-00fd-4694-b168-75dc0534cedc"

On drilling down more on this issue, I find that

EDXStatus mainTaskResult = PollSingleTask(client, triggerResult.ExecId, _pollIntervall, _timeout);

the triggerResult.ExecId is 49cdf070-86af-4ed1-b7cd-487be212769f

when I give the call to below line

List<EDXStatus> triggeredEDXStatuses = MonitorTriggeredTasks(client, mainTaskResult.TriggeredTasksId);

in the monitortriggeredtasks function

EDXStatus singleResult = PollSingleTask(client, item.ExecId, _pollIntervall, _timeout);

here for item.ExecId, i get the execution id as

"9ae02224-00fd-4694-b168-75dc0534cedc"

and error as

"System.Exception: Could not find a result for the specified execution ID "9ae02224-00fd-4694-b168-75dc0534cedc".

So how to resolve this issue?

1 Reply
jayson_abrams
Contributor
Contributor

Hello,

I'm experiencing the same issue. Starting on 4/25/2015 we started receiving this error.

System.Exception: Could not find a result for the specified execution ID "b40cfc3f-c197-4d29-a36b-d4ad056b4e8e" ||    at QMSBackendCore.Service.ServiceImpl.GetEDXTaskStatus(Guid qdsID, Guid execID)

I've been able to map this to microsoft patches being installed on the same day. I will be reviewing each patch and try to isolate it. (Most likely .NET related).