EDX Command Line trigger not working

[gdevarashettyhf]

*****************************************************  NOTE *******************************************************************************************

I posted this in wrong forum looks like. Updated the thread to Deployment forum. Also attached a word document that tells how to do but I am not able to find the QVCertTool.zip file. Anyone knows where can I find the zip file please. THANK YOU. Ganesh

*****************************************************  NOTE ******************************************************************************************

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.

Any help is greatly appreciated.

Thank you,

Ganesh

Message was edited by: Ganesh Devarashetty Added a Word Document that lists how to do it. But I am not able to find the QVCertTool.zip file. Anyone knows where can I find the zip file please. THANK YOU. Ganesh

[gdevarashettyhf]

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?

Appreciate any insight.

[cleite2014]

Hi Ganesh,

Did you get the EDX Command Line Trigger working? I am beginning to look at this at my company and am looking for a complete beginning to end setup process to accomplish this task.

Any help would be greatly appreciated.

Thank you,

Craig Leite

[gdevarashettyhf]

Hi Craig, Good for you. No I still haven't solved this issue. But I feel my issue is mainly due to the use of certificates. If you are not using certificates, you can make this work using a simple BATCH file setup, available in the forums.

URL - Using EDX in QlikView 11

Ganesh

[Bill_Britt]

Hi Ganish,

Try qmsedx -task="ABC.qvw" -qms= PUB  -password=Password123 -verbosity=3

Also, the task ID is  "Task Name" not the abc.qvw

Bill

[maheshacharya12]

Hi Ganesh,

were you able to resolve this issue ?

We recently moved from AD authentication to Certification method, and our QMSEDX setup has stopped working with below error:

Failed to create a client to the specified Uri.
The request channel timed out while waiting for a reply after 00:00:59.6249970. 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.

Any help from your side would be really appreciated.

Thanks,

Mahesh

[martinzalloccodxc]

Hi Mahsh/Ganesh, we are experiencing the same issue after changing to use certificates. Did you have any response or were you able to fix the issue? If so, could you please share the resolution? Thanks

[maheshacharya12 · Accepted solution]

Hello,

We were able to fix the issue.

you need to put a config file(named QMSEDX.exe.config) in the same directory where u put QMSEDX.exe utility.

I am attaching file we are using as .txt as .config is not supported for upload here, you can remove .txt and use.

you need to replace things at two places:

First: 

Replace <endpoint address="http://qmsserver:4799/QMS/Service" with your qmsserver address at both occurences.

Second:

Replace clientCertificate findValue in below row with thumbprint of your certificate.

<clientCertificate findValue="b12ea7cd78f5c2825cb29bcd4f732f3b99cff326" x509FindType="FindByThumbprint" storeLocation="CurrentUser" storeName="My" /> 

Third:

The command to run QMSEDX should go like this(mind https:)

"D:\Program Files\QlikView\QMSEDX\Utility\qmsedx" -qms="https://qmsserver:4799/QMS/Service" -task="Reload_QMSEDX_Task" -timeout=30000 -verbosity=5 > "D:\Program Files\QlikView\QMSEDX\Logs\Reload_QMSEDX_Task.log"

Let me know if it helps you or if you need more information.

Thanks,

Mahesh

[martinzalloccodxc]

I am trying to implement the workaround you provided. Thank you Mahesh!

I do have a question. Regarding "Replace clientCertificate findValue in below row with thumbprint of your certificate." I am not sure where to find/check for that required value. Would you please guide me how can I know what that value is? 

Thank you again!!

[maheshacharya12]

Steps to get certificate thumbprint:

1. Login with QlikView Service Account to the server where QMSEDX utility is installed( ideally the same server where QMS service is installed).

2. Under Microsoft Management Console(mmc.exe), File-->Add Remove Snap-in, Choose Certificates-->Add , Select "My user account" option(this is the default)-->Finish-->OK

3. Under Certificates-Current User-->Personal-->Certificates, find a certificate issued by your organization to the QlikView service account( with the same name of service account).

4. Double click the certificates, Under Details tab, find Thumbprint attribute, here you see the thumbprint value of the certificate, avoid copy-paste as that does not go well, try to read and write down the thumbprint value from here to the configuration file.

That's all...Let me know if you further see any issues.

Thanks,

Mahesh