Printing Error State

[abillybob]

Hey Guys,

 

Been trying my best to sort this but don't know where else to turn now. We have around 5 networked printers that are on a print server which also has papercut installed. All the other printers are working fine but just this one seems to be going into error state every time someone prints to it. The printers are dished out to clients using GPP.

I have tried all the normal stuff like restarting the print spooler and all papercut services but to no avail.

 

Anyone know anything else I can try??

[Oaktech]

Tried replacing the driver? I had a Samsung 3470 that did something similar (but no papercut) untill I used the specific driver rather than the generic pcl6 one.

[Steve21]

Is it actually stopping printing? Only reason I ask is pretty much ours always sits in Error state as if any single document is upset it'll show error for everyone, but it doesn't impact anyone but the one with dead document

 

Steve

[Joanne]

as @Oaktech said, check your drivers on the server and make sure you have 32bit and 64bit ones on there.

[abillybob]

Thanks guys for all you help. How do I re-install / update the new driver? The thing I can't understand is that it's worked flawlessley for the past 3 months without any problems so I presumed it couldn't be the driver? @Steve21 yeah unfortunatley so. It won't print anything.

[Steve21]

Any options been changed on it if they have access to it? Things like A4 vs Letter can break MFDs if they aren't set to deny it etc And can be changed by users!

 

Steve

[abillybob]

I've just checked the printer and it all seems to be ok!? Also the printer is locked down so they need to use an admin password to send those things to it. After checking papercut i've discovered there are a few copies of printers on the papaercut dashboard even thought those printers are no where to be seen on either server scdc or scdc2!?

[abillybob]

Hmm I'm going to try by reinstalling the driver. HP and their driver website grrrr!

[abillybob]

GRRRRRRRR!!!!!!!!!! Words cannot describe how angry and stressed I am now. This stupid HP printer is still doing the same thing. I have uninstalled all drivers from the print server and re-installed the driver again, restarted the entire print server, re-named the share of the printer and re-deployed it all through GP and the Mac Server. It has been working completely fine since this morning and then it's done it again.

 

I've spent 5 Hours working on this thing and I'm sick of looking at it. I swear to god if I don't get a beer soon that flaming printer will go out of the window so fast it might kill someone!!!!

 

What else can I try I really don't know anymore.

[Joanne]

you changed the network cable?

[abillybob]

Think I might be closer to the issue for anyone who get as frustrated as me when messing round with HP printers:

1. Right click the printer and go to Printer Properties.

2. Select Ports Tab

3. Find the port your printer is using and instead of using the windows generic WDS one install the full driver (with software suite) to get a new port on that list

4. Check that port and apply the settings.

 

Seems to be working again now. Hmmmm.

[Joanne]

is the port not the network one which you set up when adding a 'local' networked printer? eg/

 

I mean... I don't use papercut, so it might be different.

[Oaktech]

Think I might be closer to the issue for anyone who get as frustrated as me when messing round with HP printers:

1. Right click the printer and go to Printer Properties.

2. Select Ports Tab

3. Find the port your printer is using and instead of using the windows generic WDS one install the full driver (with software suite) to get a new port on that list

4. Check that port and apply the settings.

 

Seems to be working again now. Hmmmm.

 

Can I claim the winning answer for 'use the full driver package'?