<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: QMSEDX error in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441141#M1271863</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello did you find any solution to this error?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Jan 2014 10:23:23 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-01-27T10:23:23Z</dc:date>
    <item>
      <title>QMSEDX error</title>
      <link>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441139#M1271855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using EDX for executing my qlikview publisher jobs using TIDAL enterprise scheduler.&lt;/P&gt;&lt;P&gt;I have noticed a wierd behavior at times. It does not happen always, but only at times:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIDAL executes the QMS EDX command, the publisher job runs and completes fine creating all the required QVD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However QMSEDX exits with exit code 255 and TIDAL send email saying job did not complete succcessfully. Even though in Publisher it went fine and no error.QMSEDX gives this output. Has anyone faced this problem earlier? Please help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;==============&lt;/P&gt;&lt;P&gt;Job Output: Successfully started task with id/name=Product_Daily_Load&lt;/P&gt;&lt;P&gt;Checking the status of task Product_Daily_Load (id=f3ba04fb-d308-4098-aab1-933279cc6037 execId=eb11e495-917e-4b85-8b7e-af48bb9b0bfe)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unhandled Exception: System.ServiceModel.FaultException: Message inspection failed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Server stack trace: &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc&amp;amp; rpc)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exception rethrown at [0]: &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp;amp; msgData, Int32 type)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at QMSEDX.QMSAPI.IQMS.GetEDXTaskStatus(Guid qdsID, Guid executionID)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at QMSEDX.QMSAPI.QMSClient.GetEDXTaskStatus(Guid qdsID, Guid executionID)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at QMSEDX.Program.&amp;lt;&amp;gt;c__DisplayClasse.&amp;lt;PollSingleTask&amp;gt;b__d()&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at System.Threading.SpinWait.SpinUntil(Func`1 condition, Int32 millisecondsTimeout)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at QMSEDX.Program.PollSingleTask(IQMS client, Guid execId, Int32 pollInterval, Int32 timeout)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; at QMSEDX.Program.TriggerAndMonitorTask()&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;&amp;nbsp;&amp;nbsp; at QMSEDX.Program.Main(String[] args)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Raghu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441139#M1271855</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: QMSEDX error</title>
      <link>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441140#M1271860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raghu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you find a solution? &lt;/P&gt;&lt;P&gt;Any clue what the error 255 indicates?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jan 2014 13:59:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441140#M1271860</guid>
      <dc:creator />
      <dc:date>2014-01-17T13:59:18Z</dc:date>
    </item>
    <item>
      <title>Re: QMSEDX error</title>
      <link>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441141#M1271863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello did you find any solution to this error?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jan 2014 10:23:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QMSEDX-error/m-p/441141#M1271863</guid>
      <dc:creator />
      <dc:date>2014-01-27T10:23:23Z</dc:date>
    </item>
  </channel>
</rss>

