LJ Pro M454dw -- networked // paper jam (cleared) // print queue still shows Paper Jam

[JohnVoliva]

Going to be a bit long winded. I have searched and searched and searched google and the communities for something like this and my search terms keep giving me advice on *how* to clear a paper jam, which I don't need. 

So -- here's what's going on. Our primary printer is the M454dw -- runs about 90% of the stuff at our business. It is networked and not tied directly to any of our computers. We have 8 computers on the network (all running Win 10 Pro), however, only 6 of them really use the printer -- 99% of printing happens via these six computers.  Lately, we have been getting more paper jams (I am working on a fix for that part) BUT... the bigger issue:

When the jam occurs, all of the computers stop printing and when we open the print queue we see "HP Color Laserjet Pro M453-4 (Paper Jam). The paper jam error persists even once the jam is cleared. Here's the really odd parts:

- Sometimes, the error will clear on it's own, almost immediately once the jam is cleared. Happening less and less frequently now.

- Oftentimes, the error will clear 10-30 minutes after the jam is cleared. Probably, at best, this happens 50% of the time

- More recently, the error never clears. At the point, we do one of three things:

1) Restart the computer -- this solves the issue maybe 50-60% of the time. 

2) Stop and restart the printer spool in Services -- this maybe has worked once or twice.

3) Clear our the spool at C:/Windows/System32/spool/PRINTERS -- this is a nuclear option for us, because oftentimes we will have 10-20 print jobs in there on a single computer and retracing our steps to find out what still needs to be printed once we have cleared all that out is a major PIA. Forgot to mention, our business is a pharmacy, so we are having to try to figure who printed what from which computers and make sure all of our patient's "stuff" has been printed // not lost. We are processing about 100 prescriptions a day, so for each prescription, there are 3 print jobs, spanning 3-6 pages. You can only imagine how hard this is to retrace when all of the computers refuse to print.

Is there a way to completely solve this issue so that once we clear the jam, the computers would recognize that the jam is cleared and resume printing? We have had this issue off and on for about 6 months now, but it has become a MAJOR issue in the last couple of days -- where the nuclear option was the ONLY way to get the computer to print again. 

I am game to uninstalling the printer on all computers and setting it back up again, but, this would be a decent sized PIA -- the initial setup was a bit finicky (had to call a network specialist to get it to set up on one of our computers) and down time, while not totally out the question, does put a major monkey wrench into our operations. If this is the only way to solve the problem, I will do it -- but I want some feedback that doing so will actually work. 

[Repairatrooper]

This is typical behaviour if you are using a WSD port for communication on the print driver. Microsoft print management is famous for not detecting a change in status of a printer. If you are printing direct, better to use a standard TCP/IP port for the printer driver. Also make sure you are using an HP driver and not a Microsoft driver.

[JohnVoliva]

Thanks! I will look into that. I suspect that trying to change from WSD to TCP/IP will require an uninstall/reinstall of the printer, correct?