Error executing Nprinting task from cmd, Out of memory error

[Xico]

I have a scheduled report that runs periodically throughout the day using a .bat file.

The task is currently scheduled to run every two hours. The .bat file opens Nprinting and executes a task that triggers the entire process.

This functionality worked correctly for over a year, but a few weeks ago it started malfunctioning. When I connect to the server to troubleshoot the problem, I get an "Out of memory" message.

I already checked and the server has enough memory and it's a virtual server.

Please help with this problem, and thank you very much.

[Lech_Miszkiewicz]

HI @Xico 

Troubleshooting this is going to be really hard. Software you are using is not supported for about 6 years and the reality is that a lot has changed since. 

For us to consider this we would have to assume that:

• you didnt do any OS patches or upgrades since 2020
• you still run ms office from that time
• you run compatible version of QlikView (from that time)
• you dont use any current antivirus on this server or any other current software
• in a nutshel it would have to be exactly as it was in 2020 when it was still supported.

This version of NPrinting is 32bit so max memory it can use is 2gb anyway.

Your version is not even the latest available as it is 16.1 which is out of support for probably 7-8 years now. There is not much I can suggest at this point other than:

• reboot the server
• check compatibility of the software (your version of NPrinting vs version of QlikView vs version of MsOffice)

Lastly - if you are strictly on premise with your setup think about moving to currently supported NPrinting version and QlikView/Qlik Sense otherwise depending on your setup and internal requirements maybe cloud solution with Qlik Sense SaaS would be best fit?

cheers

Lech

[Andrea_Bertazzo]

Hi @Xico 

As Lech wrote, NPrinting 16 is not supported anymore, an upgrade is recommended.
In the meanwhile, if I remember correctly (but I may be wrong), NPrinting 16 is a 32 bit application. So it can access only 2GB of RAM on your machine even if more is available. This may explain the problem.
Try to restart the machine and run the task manually. It is possible that the QVW is too large.