We have a Windows Server 2003 network, single domain, including a file/print server. Nothing unusual or out of the ordinary in the network design (that I'm aware of).
We have five printer queue's on one W2k3 server, serving printers of varying makes and models, all printing via TCP/IP ports, all working perfectly--except one.
Recently, the queue for our Xerox Phaser 8400 color printer began having a problem. The queue would spontaneously "freeze"--that is, jobs collect in the queue, but the printer sits completely idle as if nothing has been requested of it. Restarting the oldest job has no effect, neither does restarting the Print Spooler service.
The only work-around available so far is deleting and recreating the queue on the server, but this lasts for a limited time (varying from minutes to 24+ hours).
Event ID 6161 is reported on the server, ending with the ubiquitous and non-specific, "Win32 error code returned by the print processor: 0"
As a test, I created a local queue on an XP client, which continues to work even when the server queue is "frozen", so I don't think the problem lies with the printer.
I can't help feeling this is a printer driver problem since none of our other queues have any issue at all. However, I'm at a loss as to what started the issue since the queue had been working fine for quite some time prior.
Anyone have any insights, experience, or suggestions as to a course of action? Do I have enough here to contact Xerox?
Thanks.
We have five printer queue's on one W2k3 server, serving printers of varying makes and models, all printing via TCP/IP ports, all working perfectly--except one.
Recently, the queue for our Xerox Phaser 8400 color printer began having a problem. The queue would spontaneously "freeze"--that is, jobs collect in the queue, but the printer sits completely idle as if nothing has been requested of it. Restarting the oldest job has no effect, neither does restarting the Print Spooler service.
The only work-around available so far is deleting and recreating the queue on the server, but this lasts for a limited time (varying from minutes to 24+ hours).
Event ID 6161 is reported on the server, ending with the ubiquitous and non-specific, "Win32 error code returned by the print processor: 0"
As a test, I created a local queue on an XP client, which continues to work even when the server queue is "frozen", so I don't think the problem lies with the printer.
I can't help feeling this is a printer driver problem since none of our other queues have any issue at all. However, I'm at a loss as to what started the issue since the queue had been working fine for quite some time prior.
Anyone have any insights, experience, or suggestions as to a course of action? Do I have enough here to contact Xerox?
Thanks.