Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
LebogangT
Contributor II
Contributor II

nPrinting "On-Demand" button

Good day

I need to create an "On-Demand" button for my Model but I have an issue. I cannot seem to get the URL right. I have installed all relevant SSL certificates and created connections yet I still get the same result which is "Failed to get data from External Resource". Kindly assist #Qlik Printing, Qlik Sense Business ,

Labels (2)
14 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Wrong again on that screenshot. 
Trusted origins are ok, but in on demand extension component you need to put Nprinting server address with the port. 

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.
LebogangT
Contributor II
Contributor II
Author

LebogangT_0-1642427335044.png

 

I just changed the link to the nPrinting link with the port

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Ok. That is better. 
now what do you see in web browser dev tools?

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.
LebogangT
Contributor II
Contributor II
Author

Developer Toola.png

 

That is what I see

Frank_S
Support
Support

 

@LebogangT

This is issue is common when

  • not using FQDN paths
  • usin FQDN paths for alias addresses associated with certificates not configured correctly for use with NPrinting (ie: there is a password in the NPrinting server .key certificate file)

 

See this article for more:

Now to resolve this today, do not us FQDN paths which use alias addresses. Use the computername FQDN paths for both the NP and Qlik Sense server where applicable. This takes certificate or alias URLs that might have name resolution issues out of the equation. Then this should allow you to avoid the NET:CERR errors. (also make sure to follow ALL) the points in the article above to ensure you have implemented the solution correctly.

 

 

Kind regards...

 

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!