Discussion Board for collaboration on Qlik NPrinting.
We upgraded to Qlik Sense June 2019. We're using Nprinting June 2019.
Our Nprinting On-Demand returns this error message "Server access blocked by server"
Does anyone know how to fix this?
Seems like the Nprinting extension is not prompting the user to update their Nprinting credentials. For example, when they change their password. Does this workaround fix that issue? Meaning, does the extension prompt users when their Nprinting credentials are required?
I dont think NPrinintg OnDemand Extension uses NPrinting credentials. It only uses Windows NTLM authentication and as far as I am aware this is the only authentication method supported at the moment
@Arthur_Marseuti have you been able to get the extension object working as designed (in any other way than by the workarounds suggested of using the extension from the April version or just clicking quick report), and if not, has it been escalated?
Please check the following article to ensure that the environment has been configured fully. In many cases we see this message if something is missed in the setup and configuration around NPrinting On Demand reporting with Qlik Sense.
Note: If you do not have a valid certificate that is securing the NP server, then you can take the following steps to workaround. These steps also apply to Qlik Sense and the help documentation will be updated to reflect this soon.
Section: Accepting the Qlik NPrinting web console certificate
I just wanted to give the notification that the "Server Access Blocked by Server" error message is fixed in the Qlik Sense June 2019 Patch 2 release.
The knowledge article has been updated to show this information:
Finally!! Tested - this works!!! 😎
Since I could not upgrade whole environment i just installed locally Qlik Sense Desktop June 2019 SR2. Then I just took extension and re-import it to Qlik Sense Enterprise. Worked like a charm!
btw ( i also had to switch off auto installer so the old extension bundle will not get installed every time i do repository backup and restart services)
Did you use extension from desktop version? Because we replaced extension version (June 2019) by April 2019 and I receive error Invalid extension.