Network printers printed blank pages.

[maidenpriest87]

Earlier today my HP 4000 and 5000 network printers were printing blank
pages. I tried going to different machines, and printing from different
programs, but it did not help the situation. Finally I rebooted the
print server and that seemed to remedy the problem. I would still
however like to know, what caused that? If anyone else has had similar
problems, I'd like to hear about them, because I'd like to get to the
root cause of such an issue. Thanks.

Evan.

 

[Alan Morris [MSFT]]

are there any system eventlog entries? If this is Win2k server the event #
is 61. Server 2003 SP1 changed to 6161 and logs more data.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[maidenpriest87]

Yes I looked through the event log. I've seen some 6161 (It's a 2000
server with service pack 4) no 61s. Also some of the prints that failed
and printed a blank, show up as successfuly printed jobs. Thanks for
the suggestion. However if there is anything else that I could look
into to discover what the malfunction was, please let me know.

Evan.

 

[Alan Morris [MSFT]]

what is the win32 error code in the event?


net on the printer is down
Win32 error code returned by the print processor: 2250. This network
connection does not exist.

user canceled job or net on the server is busy
Win32 error code returned by the print processor: 259. No more data is
available.

Something in GDI failed but never propagated the return code to the spooler
Win32 error code returned by the print processor: 0. The operation completed
successfully.






--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[maidenpriest87]

Error 119s I read that 119's are driver issues, but we've never had an
issue with the drivers before. I'll still have to look up more about
it. It still doesn't completely explain the jobs that appear to have
went through, but printed blank. Thanks for the help.

 

[Alan Morris [MSFT]]

the win32 error 119

119 ERROR_BAD_DRIVER_LEVEL


Are these postscript, unidrv, or monolithic vendor drivers?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[maidenpriest87]

I believe they are Post Script drivers.

 

[Alan Morris [MSFT]]

what is the pscript5.dll version (windows\system32\spool\drivers\w32x86\3)
on the server? Are all the printers exhibiting this behavior postscript?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[maidenpriest87]

The file version is 0.3.1282.1

 

[maidenpriest87]

Oops, I forgot to say if all the printers are post script with the
problem. The HP's with the problem are, but not all of our postscript
printers (or HP's for that matter) experienced problems.

 

[Alan Morris [MSFT]]

It sounds like the HP printers experiencing the issue require a different
version of pscript5. HP has a license to redistribute base drivers. I'd
say that a driver version was installed that does not support some of their
functions.

My ps driver version running Win2k SP4 is 5.1.2600.1106.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[maidenpriest87]

Hmm... That's very possible since we have added non-HP printers since
this issue occured. Thanks for the info.