In my company we're using Nprinting to handle all of our Qlikview reporting, on a Windows 2012 server.
Currently we have 12 NSQ files loaded in the Nprinting server, and probably ~20 reports in those files.
Most of the reports are scheduled to run every 10-20 minutes.
Recently I've started experiencing Nprinting freezing. For no particular reason Nprinting's scheduler stops working, though the service is still alive. The log isn't helpful - no indication for errors in there.
The only thing I see that might be related is in the windows events viewer -
DirectoryServiceConnector - Search aborted: no resources
During the times that Nprinting is ok, this problem doesn't appear.
Any idea if the things are related, and if so what can be done?
Thanks a lot,
Solved! Go to Solution.
I found out the problem - Qlikview has that innocent looking option of "close when finished" checkbox. If you uncheck it (say for debugging purposes), nprinting will never finish the document reload == Nprinting service will seem to be running, but will actually be stuck as no other tasks will be excecuted.
This is of course a misuse of QlikView by me, but I'd like to think that Nprinting would take this not-so-far-fetched scenario into consideration.
I have noticed this happening of late as well and and planning on investigating this week.
What version of NPrinting are you using ? I'll check what version I am using tomorrow.
You may be aware that Nprinting uses qlikview desktop to open the documents, so if you are running Nprinting Server on Qlikview Server and reloading the nsq files there might be a possibility of shortage of resources. It may be clashing with qlikview server reload or other user activities like users opening apps through access point. Please check how if Qlikview desktop instance is running in the background.
Another thing to check is if Nprinting Service account and Qlikview Service account are the same if they are on the same machine. It is advisable to use different accounts for both services.
Hi Amit, thanks for your quick response.
Why do you mean by "Nprinting Service account"? The actual windows user account under which Nprinting is executed?
I am using NPrinting 18.104.22.168 on Windows Server 2008 R2 Enterprise.
One thing I just noticed was that our Test NPrinting had "frozen" over Easter, and by that I mean:
On killing the qv.exe process [but not restarting the NPrinting Service] the scheduled reports started running again ok.
Have you ever noticed anything similar ?
Best Regards, Bill