Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Our NPrinting server ran out of disk space. The system drive had filled up and it had accumulated 60GB worth of files in the subfolders of %ProgramData%\NPrinting\apps
It looks like NPrinting has been keeping old copies of reports using a folder structure similar to that shown below:
Naturally, this accumulates quickly. Is it safe to delete these old copies? I can write a batch file to do so. We typically run a daily report cycle, and there isn't much interest in reports older than today.
Hi,
Please check the two parameters Days to Keep and Reports to Keep https://help.qlik.com/en-US/nprinting/February2020/Content/NPrinting/DistributionSchedulesAutomation...
If they are greater than 1, Qlik NPrinting will keep more copies of the same report.
Best Regards,
Ruggero
Hi,
Yup, it is set to 1 for both setting.
Even in the NewsStand, I can only view 1 report in the history.
Is it possible that this report was sent in the past to different (other than current) users hence copies of those are still existing for them?
Or maybe you have deleted all users and recreated them which possibly gave them new ID and new allocation to NewStand reports...
No change to the user/recipient list recently...
We do use the "Import" task to import the user from AD. It runs daily to sync the user list. Not sure if that will regenerate the user ID with each run.
Our setting:-
Hi,
I suggest you to open a support ticket and ask to query the Qlik NPrinting Repository to retrieve the complete list of published files and compare it with the files you have in the folder. I expect that the two lists will contain the same files.
Best Regards,
Ruggero
Finally manage to free up the disk space after following the KB article below! (searched the KB before raising the ticket)
https://support.qlik.com/articles/000067475
<add key="cleanup-period" value="1800" /> <add key="cleanup-period-files" value="43200" />
@kevinpintokpa Not sure if you have resolved your disk space issue, but the article above helped me. Give it a try! (If it is relevant to your issue)
A big thanks @Ruggero_Piccoli and @Lech_Miszkiewicz for helping!