Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Trigger load in QVMC by external event (EDX)

Hi all,

I want to trigger a task in QVMC (reload of a QV report) by running a .bat file.

  • I have downloaded the QMSEDX.exe and QMSEDA.exe.config
  • I have created the task which is triggered by EDX and the password is 000

My problem:

I cant seem to get the .bat file to work properly and trigger the reload in QVMC.

My .bat file looks like this:

"<filepath>QMSEDX.exe -task="Test EDX.qvw" -qms=http://<QVserverName>:4799/QMS/Service -password=000"

exit

Can anyone give me a "step-by-step" for dummies ?

Thanks in advance

12 Replies
Not applicable
Author

Hi,

Thank you! You guys are the best!

Getting close I think

Now I got this error message:

Unhandled Exception: System.ServiceModel.FaultException: Authorization failed fo
r user Test/User, required access level is QlikViewEDX

Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRunt
ime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean on
eway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan tim
eout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCall
Message methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage req
Msg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgDa
ta, 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, St
ring 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)

Peter_Cammaert
Partner - Champion III
Partner - Champion III

The user that is running QMSEDX must be a member of a specific local group on the QlikView Server. Otherwise he/she will not be able to access the EDX interface.

Normally, membership of local group QlikView Administrators is enough to access the Management API. But not for EDX. To trigger tasks by way of EDX, your user must be member of local group "QlikView EDX". Create that local group on the QlikView Server if it doesn't exist, and make the user that tries to run QMSEDX a member of this group.

All technical information about EDX in v11 is available here: Using EDX in QlikView 11

Best,

Peter

gdevarashettyhf
Contributor III
Contributor III

Hi Thorsen, I think creating the Qlikview EDX group and adding the user to that group will fix your issue.

All, I have a similar issue, I opened another thread but noticed this one. I think mine is not working because my HTTP and HTTPS both pointing to 4799..Here is my thread EDX Command Line trigger not working and I am also pasting my issue below...Can someone give some guidance or how to change HTTP to use a different port while HTTPS looks like using 4799.

I am using command line EDX run. did the following.

1. Created a QMC Task with EDX trigger and password

2. Copied the EDX command program onto a machine (even on server).

3. executing below in cmd (admin mode)

   qmsedx -task="ABC.qvw" -qms="http://PUB:4799/QMS/Service"  -password=Password123 -verbosity=3

4. Get below error message followed by an exception trace:

Failed to create a client to the specified Uri.

The request channel timed out while waiting for a reply after 00:00:59.8979898.

Increase the timeout value passed to the call to Request or increase the SendTim

eout value on the Binding. The time allotted to this operation may have been a p

ortion of a longer timeout.

5. If I give https://PUB:4799/QMS/Service  (https instead of http), the following error comes up

Failed to create a client to the specified Uri.
The provided URI scheme 'https' is invalid; expected 'http'.
Parameter name: via

Unhandled Exception: System.ArgumentException: The provided URI scheme 'https' i
s invalid; expected 'http'.

6. If enter http://PUB:4799/QMS/Service URL in browser, there is no response (timeout). If I enter https://PUB:4799/QMS/Service  URL in browser, a certificate message shows up but webpage opens up.

Just checking if anyone? One thing I am thinking is the QMS port number is the same for both HTTP and HTTPS. Is that an issue? Is that the reason that HTTPS works but HTTP does not?