N Printing 17.1 error

[Anonymous]

Hi All,

when ever i try to preview N printing Report, it throws below exception.

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

Error

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

The preview request failed with message:

Report generation failed because node CH10 of type

Qlik.Reporting.Reports.Tree.Template.ImageNode in level root.CustomerRepName_Level

received an ApplyFailureResponse from request 20708117-7a91-4268-b427-ff1eaec9563a.

Object reference not set to an instance of an object

Could some one suggest me how to debug or fix this issue.

Regards,

Krishna

[Lech_Miszkiewicz]

Hi ,

Upgrade worked for me as well.

Re your issue, did you try to rebuild app-->connection-->report-->template or you have used the same which was created in 17.2.0? I quess it could be corrupted?

I would suggest to do clean/fresh start.

Let us know how it goes

regards

Lech

[dewan_abdullah]

I rebuilt app, connection, report and template. Also I tried using another Qlik sense app, but I still had the same issue.

[woutermak]

Hi

I had a also the following problem: Object reference not set to an instance of an object.

I tried many things. At the end, I tried to create a new Connection. This connection pointed to the same Source document. I used exactly the same fields in the report as the old connection. My report present now the data as I Expected.

[Lech_Miszkiewicz]

What version of QlikSense are you on?

[duzunic88]

We had the same issue, but it looks like it is related to the connection settings.  My proxy address was not in the correct format.  After I fixed this, everything worked in pixelperfect including images Good luck!

[fmarvnnt]

It is currently happening to me on my QS 3.2.1 + NP 17.3 System.

[fmarvnnt]

Sorry, could you explain us better?

Thank you in advance,

FM

[vvvvvvizard]

17.3.1 or 2 i think , getting the same error , busy trying to rebuild cache. 

Using Qlikview

[Anonymous]

Hi, I had the same problem. It was solved when I deleted a field with error.

Regards,

[fabio_ribeiro]

If you remove some field in your app, you must reload metadata again.

If for some reason you redo reload metadata and errors persists, change your path on connection path with something like

qvp://xxxxxx.xxxxxxxxx.xxxxxxx.123.qvw.

This will broke a connection and purge cache connection. Then redo a correctly path and try reload again.