Jump to content

Recommended Posts

Posted

Hi all.

 

Not sure where to put this one so thought I'd try dropping it here. I have never seen this before, but we have a new HP Colour Laserjet M553 which is deciding to ignore print jobs. Hoping that someone might have an idea that I've not tried.

 

Background:

Printer connected to network. Share on our print server (2008 R2) with PaperCut. Share is a replacement of the old printer which worked without issue. There are 8 PCs in the room. All are identical hardware and imaged the same. Some computers send jobs and nothing comes out. Some computers work.

 

Testing:

Set the print driver on the server to both a generic HP PCL6 drive and the specific printer model driver.

Test page from server always works.

When a user print, PaperCut logs it even if the job does not print.

Jobs always show up in print queue. Flash off after a second. Same seems to happen no matter if the job succeeds or not.

I have tried a few print processors, and that seems to have no affect.

I have enabled / disabled advanced features with the same results.

All users have permissions to print.

There is another mono HP printer in the room. This is connected to the clients using the same method with no issues.

 

I have factory reset everything. No new firmware available. Drives are the most recent version.

 

If I had hair, I'd have pulled that out too!

 

Has anyone seen anything like this before or have any ideas. I though I'd seen everything a printer could (or couldn't do) before, but this is new!

 

Thanks in advance.

Posted
We this this sometimes and I have no idea why. We have seen jobs sent to one printer, mysteriously appear on a completely random printer. I think the fact that is is a new printer might be a clue. Our randomness started when it was decided to rename all of the printers in the college.
Posted

Well, timing might be everything on this. I was working on another unrelated printer issue which resulted in me looking in the Event Viewer under Applications and Services Logs / Microsoft Windows / Print Service / Admin. Loads of errors matching up with the failed prints!

 

How did I not know that log was there????

 

Everything reporting Event ID 372 with code: 2147500037 from the print processor. Bit of Googling and found reference to changing the print processor to RAW (FF Auto). So far so good. But I will know more when staff are using it.

 

Adding here for reference if it helps anyone in the future. Will update if I find this hasn't worked when in full use.

 

Cheers.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...