NPrinting log is often incomplete

[Anonymous]

We experience that the daily NPrinting log is often incomplete. E.g. a big gap in time or log for a task stops, and another task log continues. We mainly trigger NPrinting job/tasks by external events. Anyone else experience this?

We scrape the logs to monitor SLA compliance. Though .result files seem more reliable, they do not hold as much info about email subject etc. Better means of achieving this?

[Anonymous · Accepted solution]

Fixed with newest NPrinting update 16.4 some months ago actually. Logs are now split into multiples, removing the risk of lock/no write.

Release notes: https://da3hntz84uekx.cloudfront.net/NPrinting/16.0/16400/QlikView%20NPrinting%2016.4%20Release%20No...

"NPrinting Server log stops for no reason

During a scheduled job execution, logs stop being written without any reason and the job finishes successfully. Starting from this release, if the current log file is locked (for example because it is in read only mode), NPrinting will create a new log file for the current date with a new progressive number."

[avinashelite]

Cool mark the correct answer and close this thread so that it will be helpful for other who are having similar question