Qlik NPrinting

[JustinDallas]

Hello Everyone,

So for a while, my NPrinting stack was working just fine. Then something happened to the QVServer over the weekend and NPrinting refuses to act right.  I noticed that in my log report that gets sent out, I had these kinds of errors.

Errors

Job: Exec Report Job
Task: Exec Report - All
Message: Error: QlikView NPrinting PDF Printer timeout:
a print job for E:\04.NPrinting\Temp\NPrinting_Temporary_094622DBB39E43F496D73D63A0A65634\O00001-F00001.pdf
started but never ended

I attributed that to the QVServer acting up.  But after the server restart this morning,I encountered more errors when attempting to run the jobs manually.

The first problem I encountered is that the NPrinting process gets queasy about connecting to the server.  Below is a screenshot of the image.

Choosing any of the options (NT Identity, Anonymous, Alternate Identity) all fail.

When this window is closed, I am then greeted by this warm and cozy error message.

Not sure what this means, as the server is up and running along with it's Access Point.

At the end of my NPrinting designer run, it tells me that an Access Violation has occurred of some sort.  I've attached the log file to this post.

Any help on this is GREATLY appreciated.

[Frank_S · Accepted solution]

Please check that you have configured your NPrinting server service account correctly:

Troubleshooting: NPrinting Server Service and Schedules

It is likely that you do not have a dedicated NPrinting Service account and that you do not have a dedicated named CAL manually assigned to the dedicated nPrinting server service account.

If you continue to have issues after checking the above, please log a case via the Qlik Support site in order to effectively assist you with the issue.

http://www.qlik.com/us/services/support/product-support

If you do not have access to the support site, you can request access (if you have a support maintenance agreement) with the Qlik Support Qoncierge at the link below:

Qlik Support

Never the less, checking and updating your configuration via the information above is certain to resolve your issue.