Qlikview NPrinting Server Logs - Error : Error: Exception of type 'System.OutOfMemoryException' was thrown

[#1]

Hi Guys,

I am getting below error when NPrinting jobs runs by NPrinting Server .

When I run that report by NPrinting Designer it runs successfully.

Report Details:

1. Report Type : Power Point report

2. Output : Power point

JFYI, Other reports of the same format are running successfully.

Thanks,

Nitin

[pauljohansson]

check https://community.qlik.com/docs/DOC-17327#comment-49327

[nvankorlaar]

Hi, i have an similar error, but this document is closed for me.

Is it possible to open up this document?

[Chanty4u]

is that file size is big?

try to check once and any chart overlapping?

[itec_pao]

Hi all,

If you're using NPrinting 16, the problem is that it is only in 32 Bit (also NPrinting 17). Therefore can only have max 4 GB RAM. Try to optimize the QlikView application by reducing data (years of data), fields, etc. Other than that you could have some optimizations in NPrinting also:

-  Use Page feature to split by dimension per page

-  Use filters to reduce amount of data

Regards,

Oktay

[Anonymous]

Hello, please see Article 000045598 in Qlik's Support Portal.

The error " System.OutOfMemoryException " seems to happen because the process is unable to find a large enough section of *contiguous* unused pages in its virtual address space to do the requested mapping (not because of the total amount of memory, but rather contiguous unused space), or because a directory or template path is no longer valid. This may cause a memory leak. If the logs do not show an error related to "output producer", than it's usually because of the former.

The error "Error: QlikView NPrinting can't find a supported reporting output producer for the file" in the NPrinting logs demonstrates that there is a directory or template path that is no longer valid, or there is a duplicate template, as these will cause memory leaks... and the customer should update the path.

If you encounter an issue where the NPrinting execution remains in a running status forever, this was a bug (OP-5692) in NPrinting, and the resolution is to upgrade to the November 2017 release or newer. In summary, the report preview execution remained in "running" status forever due to an un-handled and not logged OutOfMemoryException error in Qlik NPrinting Scheduler, which is fixed, and an NPrinting (and QlikView/Qliksense) update to the latest version should be performed.

If the QlikView services are crashing when NPrinting tasks are executed, then it's likely that your QlikView documents are extremely large, charts are maximized, etc... so QlikView Server uses a lot of machine resources and it goes down right when the request from NPrinting is sent. You should try to schedule NPrinting when the Server has more resources. NPrinting uses the QlikView Desktop APIs. If the QlikView Server can't get back to QlikView Desktop, NPrinting shows the error.

Finally, ensure that the .NET Framework is updated, as Microsoft has confirmed memory leak issues which are addressed in the latest releases of the .NET Framework.