NPrinting Sept 2018 - publish task seems stuck and never finishes

[kdmarkee]

I have had a pixel perfect report with levels executing just fine until recently, and I can't seem to find anything in the logs that help.  Out of the blue, the publish task for this report starts but doesn't' finish...it since it runs longer than I know it should, I decide to Abort it.  Does anyone see anything in my log that would help?  This log is everything from the publish task start time to the time I aborted it.  Thanks.

[Frank_S]

Hi @kdmarkee 

Please zip and add the NP Engine and NP web engine dev logs here as well. Only June 6, 2019 logs only..thx.

[kdmarkee]

I attached a second zip to the original question.  Note that engine_dev was no longer available since it was last week, so I just have the basic for that...webengine_dev did exist however.

Additionally, I think I have narrowed it down to one of detail bands in my pdf pixel perfect report.  I have a detail band that has 2 "name like" text fields in it from a Level node and 1 date field in it from a Table node (the date field is from  the Table node because it is the only way I have been able to format it properly).  Nothing has changed; it has worked in the past but now just causes the report to hang.

[Frank_S]

I recommend checking the qwv called Month End NPrinting.qvw found in the following qvp path shown below for potential newly added unsupported items.

qvp://prdqlikdes2/LocalUserPublishedDocuments/

Unprocessed requests errors could mean that NPrinting is stuck 'possibly' on an on open trigger (some sheet trigger) an 'always one selected list value' or perhaps some other action in QlikView that is preventing NPrinting from processing the QVW. Perhaps a newly added macro 'could' be interfering as well.

I suggest checking all of the above. For more information regarding with unsupported items to check, visit the following article: https://support.qlik.com/articles/000026081

Qlik.NPrinting.Engine 18.29.7.0 Qlik.NPrinting.Engine.Consumer.ContentResolver 20190610T100202.399-05:00 WARN PRDNPRINTING 0 0 0 0 0 0 0 0 Navigator stuck or died on connection navigator=qlikview;documentpath="qvp://prdqlikdes2/LocalUserPublishedDocuments/Month End NPrinting.qvw", forcing close of resolver. 1 unprocessed request(s) will be reenqueued. ERROR: Qlik.Reporting.Engine.Messages.Exceptions.NavigatorDiedException: Navigator navigator=qlikview;documentpath="

I also found a calculated conditional causing the following error:

Engine.Navigator.QlikView.QV.QlikViewDocument.[1516]::navigator=qlikview;documentpath="qvp://prdqlikdes2/LocalUserPublishedDocuments/Month End NPrinting.qvw";qlikviewversion=12.20.20700 20190607T163003.021-05:00 ERROR PRDNPRINTING 0 0 0 0 0 0 0 0 The columns calculation of conditional information failed for sheet object Document\CH251. System.Runtime.InteropServices.COMException (0x800706BA)

For NPrinting reporting purposes, particularly with Pixel Perfect, it might be better to ensure CH251  is made permanently visible during the processing of the NPrinting report. You can force CH251 to conditionally show as well using OS User syntax equally your NPrinting service account as a conditional expression to conditionally show the chart to your NPrinting service account with generates your reports as a background service.

If neither of these resolves the issue I would suggest starting as support case with the Qlik Support desk.

[kdmarkee]

There is something about adding a particular field to my straight chart that the Level in my report doesn't like.  I have confirmed it is that through various testing, but cannot explain why it causes the issue.

[Lech_Miszkiewicz]

Hi Kris,

To get out of the way actual values of that field you could run Autonumber() function on it during load script and try using auto-numbered integer values in your level. If it successful then we know that problem sits in actual field values (and not in the model/structure) of your report.

Make sure that you add a field as dimension without = sign (sometimes when you typing in field name in dimension entity it adds automatically "=" sign)

[kdmarkee]

Thanks for the tips!