QMSEDX.exe Unhandled exception

[#1]

Hi there.

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 [0]:
   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)

[#2]

hi - I don't have the option to mark your answer as correct, probably because I'm not the original OP!

but thanks very much!

[#3]

Hello David,

Does your latest version correct the error return code 255 ?

Thank you

[amien]

Hi David,

Do you have a BugID by any change? And the only solution was upgrading? There was no work around? Or is that with this code?

  - default timeout set to 24 hours instead of one minute

  - change the qms param from URL to server name

  - default TraceLevel set to Verbose

  - retry on failure (3 times max, 10s betwwen each try)

Can you send me also the source changes for this?

Gr,

Amien

[#5]

I got this error :

Failed to create a client to the specified Uri

Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9844001. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'http://localhost:4799/QMS/Service' has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out

   at System.Net.HttpWebRequest.GetResponse()

   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   --- End of inner exception stack trace ---

   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)

   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

   --- End of inner exception stack trace ---

Server stack trace:

   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)

   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 [0]:

   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.TriggerEDXTask(Guid qdsID, String taskNameOrID, String password, String variableName, List`1 variableValues)

   at QMSEDX.QMSAPI.QMSClient.TriggerEDXTask(Guid qdsID, String taskNameOrID, String password, String variableName, List`1 variableValues)

   at QMSEDX.Program.TriggerTask(IQMS qms, String task, String password, String variableName, List`1 variableValues)

   at QMSEDX.Program.TriggerAndMonitorTask()

     at QMSEDX.Program.Main(String[] args)

[#6]

Hi, I commented that the solution to this problem is also presented me two servers, was to include the user's server
who executed the task in the Windows group "Administrators QlikView."

I hope you serve.

greetings
Leonardo

[alan_richmond]

Is a patch available to allow QMSEDX to operate with QlikView 12?