Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Experts,
Our QlikView is on version May 2021 SR2, and I know I should probably upgrade to a newer version.
We had to switch the Qlikview server authentication from Windows Group based to Digital Certificates as we had new servers in another domain, and digital certs were the only way because of separate domains.
Since the switch to digital certificates, the EDX triggers have stopped working. We have the Alteryx application triggering the tasks in QlikView using EDX triggers, and this stopped working.
Following the article https://community.qlik.com/t5/Official-Support-Articles/QlikView-Connecting-to-QMS-API-using-HTTPS/t..., I exported the QVProxy.pfx from the QMS server and imported in the MMC of the Alteryx server. I couldn't find more steps that I need to perform, so we tested it as it is after importing the certs. We got Error 1 (attached), I updated the config file, and got Error 2. And I have been stuck here trying to solve it.
Has anyone used Alteryx or similar application to trigger EDX when QV is using digital certificate based authentication?
Appreciate any pointers.
Hi @ilyas393
QMSEDX is a third party tool not supported by Qlik, but I found this documentation that might help you :
If that doesn't help it is suggested to contact the developer for further assistance.
Kind Regards.
Hi @NadiaB thanks for your response. I did come across this documentation but couldn't find the QVCertTool.zip file the document is talking about. Do you know where I can find this?
I think there is some configuration step missing in the setup article. After successfully implementing digital certificate authentication across all the nodes in QlikView, I cannot even trigger the EDX directly (manually) from the QMS Server where the EDX setup sits.
I get this error message:
Failed to create a client to the specified Uri.
The request channel timed out while waiting for a reply after 00:00:59.9375180. 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.
Do we need to make changes to the QMSEDX.exe.config file? I have tried https and fully qualified QMS Server name in the endpoint settings and still no luck.
Appreciate any help.
I was able to figure out and fix the specified uri error, and I think I am pretty close to solving it. I am stuck with missing service key. where can I find this or configure this service key?
Here is the error message I am getting now:
Error while starting task with id/name=taskname
Error message: Service key is missing
Failed to start the task!
I have already looked into Solved: Re: Service key is missing - Qlik Community - 1436424 and has behaviorConfiguration="ServiceKeyEndpointBehavior" in the config file
Did you try to call the GetTimeLimitedServiceKey endpoint to get the service key before trying to trigger the task?
Best regards,
Hi @Damien_V,
Thanks for your response. I tried calling it using the below command and it errors out. Any advice what I might be doing wrong and how to fix it?
## URL for the QMS API endpoint
$url = "http://ourservername:4799/QMS/Service"
$service = New-WebServiceProxy -Uri $url -Namespace QlikViewServer -UseDefaultCredential
$serviceKey = $service.GetTimeLimitedServiceKey();
error is attached