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: 
kdmarkee
Specialist
Specialist

NPrinting 18 - ERROR: All documents failed to generate: Exceeded maximum number of retries

I just upgraded to NP April 2018 and am continuing to see inconsistent behavior with NP publish tasks. Half of the time tasks are launched per their schedule and run fine, and half of the time they fail but if continue to retry the task it eventually works.

For instance:

np publish task.PNG

The 8am run was launched by the scheduled time in the task, the 8:59am run was launched manually, and then the 9:33am run was launched manually, and finally successful.

Both times this failed it gave me:  "ERROR: All documents failed to generate: Exceeded maximum number of retries"

np publish task log.PNG

I see some older posts regarding reloading metadata and the error "Exceeded maximum number of retries", but not much that has been helpful in terms of NP publish tasks.  Any insight anyone can provide is appreciated.  Thanks.

21 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi Kris,

I will not be able to help you much, but am interested in this topic. Do you have a Qlik support case in regards to this issue?

thanks

Lech

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.
kdmarkee
Specialist
Specialist
Author

I don't have a case this time, trying the Community first, but if I learn anything I'll report back.

kdmarkee
Specialist
Specialist
Author

I attached scheduler and engine log detail for the highlighted task below.  Maybe someone can help with this more detailed info.  My scheduled NP publish task for my report failed the last 2 days (but when I manually ran them they worked), and then today the report ran just fine from the scheduled NP publish task.  (I have NP April 2018 and QV 12.10 SR6).  (If this happens again in the near future I'll add the DEBUG mode detail, but I didn't save that info from 4/29 and so the log files were overwritten).Thanks.

20180429 web console.PNG

kdmarkee
Specialist
Specialist
Author

Ok, attached is a debug mode log file associated to the issue.  Can anyone help?  Thanks.

Vigneshvaran
Partner - Contributor
Partner - Contributor

Hi,

Am also facing the same issue. Please let me know if someone could provide more details on the issue.

Ruggero_Piccoli
Support
Support

Your issue has a different cause, based on what we can see from the logs.

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.
Ruggero_Piccoli
Support
Support

Hi,

It seems an issue due to a QlikView server overload.

Are you trying to open a really big .qvw? You should try to open the same .QVW from a Qlik NPrinting Engine computer by using QlikView Desktop directlly. Check the performances in that case, for example remove all saved filters. If the cause is a Qlik Server performance issue you should experience bad performances also when using the same document via QlikView Desktop. Keep an eye on the QlikView Server resources usage as CPU and RAM percentage.

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.
kdmarkee
Specialist
Specialist
Author

My app used in my NP connection is small.  I have a qvw that has all of the data in it that is made available to end users for analytics, but then I reduce that same app on a field in my QV Publisher Task to only include the data I need for my daily NP report, which is usually less than 300 rows of data.  Side note...My case with Qlik is still open on this matter.

Ruggero_Piccoli
Support
Support

Hi,

Did you do the test I suggested in my previous post?

Please remember to add the app and the Qlik NPrinting templates to the case you opened with the support so we can try to replicate the issue here. Skip my suggestion if you already send the environment.

Best Regards,

Ruggero

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

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. 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.