Print Error when Printing from Windows 2003 Server

Mike Schumann · External Since: Dec 17, 2003 Posts: 11

I have an HP Laserjet attached to the parrallel port on a Windows 98
computer. I am printing to this printer from a Windows 2003 Server.

This worked fine until about two weeks ago. Now, randomly, I get 6161 print
errors when I print to this device. The Server event log includes the
following information:

The document Sales Order owned by XXXYYY failed to print on printer
\\ZZZ\RECEIPT. Data type: NT EMF 1.008. Size of the spool file in bytes:
63820. Number of bytes printed: 0. Total number of pages in the document: 1.
Number of pages printed: 0. Client machine: \\SERVER. Win32 error code
returned by the print processor: 0. The operation completed successfully.

Does anyone have any ideas what might be the problem and how I can
troubleshoot this issue?

Thanks,
--
Mike Schumann

zaipai · Joined: Nov 10, 2003 Posts: 1

We are having the same issue, we are seeing many 6161 errors on all of our Windows2000 and Windows2003 print servers. We are working with Microsoft and HP to resolve them but so far no one has come up with the answer. The only thing in common with all of them is the network. I have read where a busy network switch / hub could be the issue. I will post back when we figure it out.

RichardT · Joined: Mar 26, 2008 Posts: 1

Hi

Yes, the 6161 error. I have struggled with those too. I run W2003 on several servers, with a print server and two terminal servers.

I found I was getting random "failed" prints (looking in Event Viewer) with 6161 codes - some saying "..printed sucessfully" and some " .. access denied" at the end (nothing had printed).

Laserjet's never seem to go wrong, mostly HP inkjets. I suspect the drivers are partly to blame. As we have many users printing to these printers, perhaps they aren't robust enought to deal with this multi user environment.

I found the HP Business Inkjet printers the worst - and strange that once one HP BI printer had an issue, they all stopped working. (solution was to end the HPZENG.. process, stop/start spooler, maybe delete some files from the spool directory)

I have tried all manor of fixes - and try to use the latest driver (provided there is a good up-to-date one available).

One that seemed to help was related to the permissions in the registry ...

I still have issues this this occationally, and have been watching my spool directory. The "choice" of filename is bizarre. I expected the file names to increment, but they seem to be "reused" a certain degree - perhaps there is some confusion between the drivers/spooler which filename to use, and when the file is creates - it already exists (and is in use) by another print.

Could this be my "access denied" issue - in the same way you can't delete spool files that are in use.

I hope you find a solution to your problems - it's very frustrating. If HP and Microsoft can't work it out ... ? For me, it's forums, and trial and error.

Regards
Richard
IT Manager