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 II
Contributor II

Some errors occurred during report generation

We have a daily scheduled nprinting task, which has a server connection to a Qlikview report.

One day it is running fine, the other day we get the error "Some errors occurred during report generation" in our mailbox.

There's no logic in when it's running fine and when it goes in error. And if we get an error and I run the task again manually, it's possible it's running fine.

The Qlikview report is running a half hour before the NPrinting report, so it's not that the Qlikview task is still running.


Logging scheduler

Connection navigator=qlikview;documentpath=qvp://....qvw has reached ERROR status

Failed report generation for report ... exception Qlik.Reporting.Reports.Tree.Exceptions.FailedReportException: Report generation failed because node CH18 of type Qlik.Reporting.Reports.Tree.Template.TableNode in level root received an ApplyFailureResponse from request ..... ↓↓unknown ---> System.Exception: unknown↓↓  --- End of inner exception stack trace ---↓↓  at Qlik.Reporting.Reports.Tree.Template.TemplateLeafNode`5.ApplyFailure(FailureContentNodeResponse response, TcTransformationContext transformationCtx)↓↓  at Qlik.Printing.Trees.TcTransformation.ApplyResponse(IContentNodeResponse response)↓↓  at Qlik.Printing.TreeTransformationService.Process(IReportRequest reportRequest, IContentNodeResponse contentNodeResponse)


Logging engine

Navigator stuck or died on connection navigator=qlikview;documentpath=qvp://...qvw, forcing close of resolver.

Forced to close a resolver for connection navigator=qlikview;documentpath=qvp://...qvw.

Error while trying to add a resolver for connection navigator=qlikview;documentpath=qvp://...qvw. ERROR: An exception was thrown while invoking the constructor 'Void .ctor(Engine.N


Version NPrinting is 17.3.1

Version Qlikview is 12.10.20200.0 SR4

Please advice us what we can try or do?

14 Replies
Highlighted
Specialist
Specialist

I am now seeing this exact issue in April 2018 version when I have my automated scheduled NP Publish Task executing.  And the only thing I changed prior to it starting to randomly fail was to rename what I call the App and associated Connection, Report and Publish Task.  I might rebuild all those pieces just to prove there might be an NP bug when it comes to simply renaming items in the NP web console, which would be very disappointing as nothing about the actual connection string nor qvw itself changed.  I even refreshed the NP metadata and restarted my NP server, and still had the issue despite that.

Highlighted

I have not been looking into logs for a long time - maybe i should! Will keep everyone posted if i find anything!

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.
Highlighted
Creator II
Creator II

hi..we have 17.6.0000.0 version and we are experiencing this issue. Was this fixed in any latest version or still users are facing this? 

Highlighted
Creator II
Creator II

Did you solve it anyhow? we are also facing the same issue and resulting in incorrect mails sent to users. Please let me know in case recreating objects or renaming worked

Highlighted
Employee
Employee

Hi,

Please start a new conversation for a new issue. This is 2 years old.

You are using a very old version, so please upgrade to latest by following the instruction in the official help site and in the release notes. Then test your issue again to be sure you are not experiencing a already fixed bug.

Best Regards,

Ruggero



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.

View solution in original post