Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Announcements
BI & Data Trends 2021. Discover the top 10 trends emerging in today. Join us on Dec. 8th REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Contributor III
Contributor III

NPrinting 17.3 Designer Preview-Error: Wrong content node response type

Hello folks,

i recently installed NPrinting 17.3 and wanted to try to generate an easy report with the Sales Demo.qvw. Getting a Connection was no problem. I created a small PixelPerfect-Template (because i don't have an Excel-License yet). But apparently, i am not even able to create a preview out of it. You can see the error below:

I installed the 17.X-Versions a several times before and this is the first time I installed 17.3. So I ask myself, if this is a new Error which only occurs in 17.3 or did i forget something?

Please share your information if you have any Thank you!

Best regards,

Flo

37 Replies
Highlighted
Contributor III
Contributor III

I already tried to reinstall the Designer. Tried to create a report only with labels in it. When i do this, i get the error/warning  in the picture above ("You must enter ....").

Very depressing

Highlighted
Partner
Partner

Can you try to use the designer on your local machine and not on the server?

Highlighted
Not applicable

I've run into the same thing Flo.  I did find out that (at least for me) it only happens when I try to preview through a pdf.  If I look at another type (html, gif, etc.) it seems to work.

Any luck finding an answer to this yet?

Highlighted
Contributor III
Contributor III

@adam linderblood I already tried that. Same error for me as with pdf.

woutermak‌ , i dont have the ressources yet. But I will probably soon can try it on another server.

Highlighted
Not applicable

I have had similar problems. I have found that using autoCalendar fields will not work in NPRINTING and will cause the "Wrong content node response type". I'm using Qlik Sense and NPRINTING 17.3.0.

I have created my own fields for Year and Month in the load script to avoid using autoCalendar.

I have also had problems when using the danish characters æ, ø and å in field or table names, so best to avoid anything but the english standard alphabet.

Highlighted
Not applicable

Error can also be due to an incorrect field used in a filter that is attached to your report. If this is the case, remove the filter or correct filter field names before attaching it back to the report.

Highlighted
Employee
Employee

1 - Please try with latest Qlik NPrinting version June 2017. It could be related to a bug that was fixed.

2 - This error could appear when:

- you are adding an object that is inside a container as an image or as a level

- you applied a filter with an empty dataset as result

Let me know if this helps.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Highlighted
Specialist
Specialist

I also had the issue, for NP 17.3, where I am using a straight table chart as a level in a pixel perfect report and my publish task is setting the output to PDF.  If I can find a way to work around this and still be able to use PDF, I'll share my findings.

Highlighted

Same issue today we re going to upgrade 17.4 June and see if this solves issue

Highlighted
Employee
Employee

Ok, good!

After please remember to check the two conditions mentioned at point no. 2.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.