We are using QMSEDX.exe to trigger document re-loads from an external scheduler. Prior to our recent purchase of a Publisher licence we were directly triggering the .qvw document and things were working well.
Following the purchase of Publisher we are now triggering the task and have started to get unhandled exception errors returned from QMSEDX.exe.
Typically we are getting "System.ServiceModel.FaultException: System.Exception: Could not find a result for the specified execution ID" or "System.ServiceModel.FaultException: Message inspection failed"
The task is triggered and runs to completion on the server but evidently with the above problem we are unable to see this from the result of the QMSEDX job. We only have a single QlikView server and the QMSEDX job is running on the same server. Server OS is Windows 2008 R2 SP1 with QlikView v11 SP1
QV Support are suggesting the problem is with QMSEDX.exe (possibly not "thread safe"??) and since it is not a supported utility are unable to help.
Has anyone else seen similar problems and does anyone have any ideas?
Typical output from the QMSEDX job below.
Any help gratefully received!
Successfully started task with id/name=OMP_SDWH_QVDs
Unhandled Exception: System.ServiceModel.FaultException: System.Exception: Could not find a result for the specified execution ID "d302bfec-f6c7-4232-866b-ed32ff2734ea"
Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object ins, Object outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at : at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at QMSEDX.QMSAPI.IQMS.GetEDXTaskStatus(Guid qdsID, Guid executionID) at QMSEDX.QMSAPI.QMSClient.GetEDXTaskStatus(Guid qdsID, Guid executionID) at QMSEDX.Program.<>c__DisplayClasse.<PollSingleTask>b__d() at System.Threading.SpinWait.SpinUntil(Func`1 condition, Int32 millisecondsTimeout) at QMSEDX.Program.PollSingleTask(IQMS client, Guid execId, Int32 pollInterval, Int32 timeout) at QMSEDX.Program.TriggerAndMonitorTask() at QMSEDX.Program.Main(String args)
I am having the same trouble, as far as I can tell.
My scenario is that I try to trigger a reload of the QVW from the AJAX client (i.e. when the document has been been distributed to the Access Point). Running QMSEDX from the command line works fine, but when started from within a macro, which in turn is started by clicking a button in the web browser/AJAX client, I get the same error as you report.
I have patched QMSEDX.exe to add a simple "retry if it fails" in the PollSingleTask() function and it seems to work now but It has been in production for only one week so it may require some more time... It someone is interested I can attach the patched file.