NPrinting on-demand button (in Qlik Sense) only work if user log into NPrinting in other tab
We implemented on-demand button in some Qlik Sense apps. They worked well. However, on-demand button only work if we logged into NPrinting server in another tab. Otherwise, it gave error 'Server access blocked by server'. This happened to our Qlikview users before, and we solved it by installing SSL certificates on both NPrinting server and Qlikview server. And we already have SSL certificate installed on our Qlik Sense server. But why did this happen again?
Your post is very confusing as once you are talking about Qlik Sense OnDemand button and suddenly you jump to QlikView and certificates. Qlik Sense and QlikView have completly different requirements in terms of OnDemand setup...
So as usual - first and foremost:
what versions of software are you using? (make sure you state version of OnDemand extension button)
did you recently upgrade Qlik Sense?
have you searched community for the same error?Would below be similar to your case?
Thanks for your reply and sorry about confusing. I thought the issue might be related to SSL certificates. That's why I mentioned Qlikview in my post. It looks like that's not the situation. So please ignore the Qlikview part.
To answer your questions, I don't know how to find out extension version. We installed on-demand extension as part of bundle which is included in June 2019 release. And yes, we upgraded both NPrinting server and Qlik Sense server to June 2019 version last month.
That post mentioned the same situation that, NPrinting users need to log into NPrinting server in order to use on-demand button in Qlik Sense app. But this is exactly what we are trying to solve. We want users be able to use on-demand button without having to log into NPrinting first. Is it possible?
When I pointed you to that post I wanted you to understand that there are already people looking at this issue. If you read whole conversation there you see that there is Qlik support case and there is a bug reported. So what you can do is to follow up on the post previously linked and continue conversation there.
Given that this issue potentialy is a bug I do not have a resolution for it yet, and we have to wait until Qlik fixes it.
The other thing you can do is open support ticket directly with Qlik and let them deal with it.
On community though there is no point opening new thread for the same thing as it only creates confusion. The usual approach would be:
I have a problem with for example NPrinting
I go to community and i search if there is anyone else having the same problem
If YES - I follow up under the same thread
If NO - I create a new question/conversation providing all possible information (especially versions of software as each version is different and solves a lot of bugs)
cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.