Page 1 of 1

unable to print (produce) PDF via shared network printer.

Posted: Mon Apr 16, 2012 7:54 am
by spoon
My novapdf printer was setup at Win2008R2 64 bit Enterprise Sever and and is normally functioning.
However, one of my client PCs is occasionally unable to connect to the printer. It usually happens after weekend and failed on Monday.

The config of client PC: Win2003SP2 Enterprise version.

Symptom: Printing normally -> idle for week end -> unable to print (produce pdf) on Monday -> restart client machine -> working again.

Error message (captured at server after timeout at around 5 mins at Windows Event Log):
Event ID: 6161
"The document Test Page owned by *USER ID* failed to print on printer COLD PDF Printer. Data type: NT EMF 1.008. Size of the spool file in bytes: 196608. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\*CLIENT MACHINE* Win32 error code returned by the print processor: 0. The operation completed successfully.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

Anyone meet the similar case?

Re: unable to print (produce) PDF via shared network printer

Posted: Wed Apr 18, 2012 7:45 am
by Claudiu (Softland)
Hello, we have tried to reproduce the issue from our end but the printer does not error out on the client when connecting to the Printer. We will however try this for a number of times perhaps it will happen if the issue is occurring occasionally.

Thank you.

Re: unable to print (produce) PDF via shared network printer

Posted: Wed Apr 18, 2012 9:53 am
by spoon
Thanks. But perhaps "time" is matter. Usually it happens on Mondays after idled for two days.

Re: unable to print (produce) PDF via shared network printer

Posted: Fri May 11, 2012 3:52 pm
by PaulDuncan
I'm having the same problem, Monday always brings this problem up. Has anyone found any solution yet?

Re: unable to print (produce) PDF via shared network printer

Posted: Mon May 14, 2012 7:49 am
by Claudiu (Softland)
Hello, are you having the same configuration as described in the above posts? We need this to figure out on which OS is the issue happening.