1

I have an HP LaserJet M401 network printer that is randomly giving a ‘paper jam’ error when there is no paper jam. I can restart the print spooler service on the File/Print Share server (Windows 2008 R2 - service pack 1) and that clears the error and allows printing to continue. Anyone have any similar experience to this, and if so, find a solution?

3 Spice ups
2

  1. Check the type of paper. I assume it’s just a regular sheet, but sometimes people try to put cardstock through these things.

  2. If it’s under warranty, quit fighting it and have the thing replaced / fixed.

  3. If not, typically this happens because of a bad sensor. Try printing to a different tray and see if that works.

3 Spice ups
3

Its a single tray using regular printer paper. I’ll check the warranty but I think I’ll be out of luck there.

4

Are you running the latest firmware? It might be possible an update might help. Other than that I agree that you probably have a wonky sensor.

2 Spice ups
5

Will double-check. Definitely out of warranty. Might be time to replace the thing.
Thanks

6

Heh. I guess i’m chopped liver!

1 Spice up
7

I have a printer with over a million prints on it, in fact the majority of my printers are over 10 years old and have high page counts. Small things like a sensor that could be stuck or the paper setting being wrong are easy fixes that don’t warrant simply replacing the entire printer. Parts are available and reasonably priced for that model printer. If it isn’t working now, what do you have to lose by trying to fix it? Who knows you could bring it back to life and save a couple hundred dollars.

Trouble-Shooting Manual

Repair Manual

8

I have a similar issue. The driver on the computer says, “Paper Jam,” but the printer has no errors and can print demo pages without a problem. I’m going to look for the firmware update and check for driver updates, but I think my “toner low” message on my printer is triggering a bogus “paper jam” error in the driver. Some one use a put when they should have used a get or put a 0 where it should have been a 1. :slight_smile: I’ll update if anything exciting happens.

Jeff