I want to trigger a task in QVMC (reload of a QV report) by running a .bat file.
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"
Can anyone give me a "step-by-step" for dummies ?
Thanks in advance
If you run this command from the DOS command line, what does the QMSEDX program return?
Edit: add -verbosity=5 to your command line to get the largest amount of feedback.
A step-by-step guide can be found here: Trigger QV Task using command line arguments
Searching for a specific term like "QMSEDX" with just type "Documents" marked, will always return useful information from the extensive resource library in this community.
This is what you get when you run the bat/cmd file. Instead, open a CMD prompt window and enter your command line (starting with "pathtoprogram\QMSEDX.exe...") and add the -verbosity=5 command line option.
There you have it: your copy of QMSEDX is either broken or not suitable to run on your OS. Can you download the latest copy again (1.0.4 I guess), check the zip for any errors and extract a new copy of QMSEDX?
BTW, thank you so much for your help!
Now I got a different error message running the .bat:
"D:\QlikView Storage\EDX\QMSEDX.exe" -task="4_Development\Test EDX.qvw" -qms="http://10.120.0.400:4799/QMS/Service.htm" -password="123"
I suspect it may be that I do not have the correct QV server box (ref your post)
10.120.0.400 is the server address
I have tried to follow the recipie from your post,to find the QV Server box (properties on my computer), but the computer name there does not work either.
this is the error message
Failed to create a client to the specified Uri.
There was no endpoint listening at http://10.120.0.400:4799/QMS/Service.htm that
could accept the message. This is often caused by an incorrect address or SOAP
action. See InnerException, if present, for more details.
Unhandled Exception: System.ServiceModel.EndpointNotFoundException: There was no
endpoint listening at http://10.120.0.400:4799/QMS/Service.htm that could accep
t the message. This is often caused by an incorrect address or SOAP action. See
InnerException, if present, for more details. ---> System.Net.WebException: The
remote server returned an error: (404) Not Found.
--- End of inner exception stack trace ---
Server stack trace:
eption(WebException webException, HttpWebRequest request, HttpAbortReason abortR
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeS
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message messag
e, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean on
eway, ProxyOperationRuntime operation, Object ins, Object outs, TimeSpan tim
Message methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at :
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.Main(String args)
I don't think your server software is at fault. However, check the following:
I would also recommend using localhost if you are running this on the server.
You can verify the address from QMC like this:
System/Setup: Click on Management Service.
In Summary on the right you will see :
"To connect to the API of this Management Service use: https://<server>:4799/QMS/Service "