I have a file/print server that is exhibiting some strange printing behavior.
Server 2003 std SP1 patched.
The server has 25 or so printers setup, mostly HP's, a couple Sharp multi-functions,
a Dell and a Okidata.
I'll use the HP 9150 as the offending printer in my question.
The majority of them print just fine. But a handful of them don't print.
The client doens't receive an error when the print job fails; it looks like it spools and prints just fine.
The event log however tell a different story.
Event ID: 6161
The document Microsoft Word - Personnel Policies 2006.doc owned by user failed to print on printer network printer. Data type: NT EMF 1.008. Size of the spool file in bytes: 32240. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\X.X.X.X. Win32 error code returned by the print processor: 0. The operation completed successfully.
I have an open call with MS about this problem, and have tried so many things I can't remember them all. With no luck.
Here is where it gets interesting.
These same printers are setup on another server and print just fine.
When I add the user to the local admin group on the server, they can print. Take them back out, no luck.
When I change the print drivers on the server from HP 9150 PCL6 (not inbox) to an inbox Laserjet 4,
the printer spits out a blank page. So at this point SOMEthing is getting spooled.
Printing to the IP address works fine.
Things I've tried:
Every iteration of print drivers I could get my hands on. MS wants me to use the inbox drivers. I've tried almost all of them. Can't get any more generic than the Laserjet 4. That thing will print to anything.
Full control on C:\WINDOWS\system32\spool\PRINTERS on the server.
Changed the print processor from hpzppXXX to WinPrint, RAW data type.
Disabled bidirectional support.
I'm stumped folks. And apparently MS is too. This has been an ongoing issue for more than a few weeks.
So, any suggestions are welcome.