Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello everyone,
I'm struggling with a very strange issue. I've installed Qlik Sense (September 2019) along with Qlik Dashboard bundle on server 1. On server 2, I installed nPrinting Server (April 2019) and nPrinting Engine (April 2019).
Here's the list of all the things I've already done:
When I look at the JS Console in Chrome, I see this message when the Unable to connect to server window pops up:
I looked through several community posts, instruction documents, YouTube videos and couldn't find a solution.
Has anyone faced this issue before? Is there a solution?
Thanks,
Mikhail B.
Found the issue. I've added a fully qualified domain name of the Qlik Sense server as well as fully qualified domain alias names to the list of trusted origins. I didn't, however, add non-fully qualified domain names. My list of trusted origins was something like this:
What I failed to list are non-qualified domain names:
As soon as I added non-FQDNs, on-demand report button worked like a charm.
Button worked well for the owner of the app, but now users get a Server access blocked by server error message when they click the on-demand button.
Next post, Qlik Sense On-Demand Server Access Blocked by Server...
Found the issue. I've added a fully qualified domain name of the Qlik Sense server as well as fully qualified domain alias names to the list of trusted origins. I didn't, however, add non-fully qualified domain names. My list of trusted origins was something like this:
What I failed to list are non-qualified domain names:
As soon as I added non-FQDNs, on-demand report button worked like a charm.
Button worked well for the owner of the app, but now users get a Server access blocked by server error message when they click the on-demand button.
Next post, Qlik Sense On-Demand Server Access Blocked by Server...
Where did you add the FQDNs? in nprinting somewhere?
In nPrinting. Go to Admin > Settings > On-Demand and click on Add Trusted Origin button.
That worked! Thank you
Thanks!! It worked for me after upgrading NPrinting to the same version of QS (2020JUN). I tried it in an earlier version of NP but it didn't work