01-24-2014 12:04 AM
Power cycling continually, displaying "49 service error - turn off then on" on the screen before cycling.
Printer only does this when connected to the network. Printer quite happy to sit quietly when NOT connected to network.
Solved! Go to Solution.
01-24-2014 01:38 AM
Unplug the network cable from the printer, check and clear all the print queues (there may be a pdf doc sitting in a pc or server print queue)
Once the queues have been cleared, reboot the printer and plug the network cable back in.
If this doesn't cure the problem, then the likely problem is a faulty formatter board.
Good luck !
01-24-2014 06:09 AM
Error 49 usually signifies a firmware error (which could, as Guy1 suggests, be due to a formatter problem), but it can, in some cases, be invoked by some system sending a 'rogue' job to the device; see the following threads for other examples of discussions of similiar problems with similar LaserJet models:
01-24-2014 07:06 AM
Looking through the previous threads I checked the PCs in the same room as the networked printer by disconnecting them one at a time from the network. When I disconnected one particular PC the problem stopped! Looking at that PC's print queue, there were several jobs listed, none of which looked out of the ordinary. However, when I cleared out all those jobs the printer stopped giving the error 49 and stopped initialising. So it looks like that was the problem. Thanks for the advice, Chris.
01-24-2014 07:10 AM
01-17-2015 07:04 AM
Just for reference, regarding bad print jobs occasionally producing 49.xx errors, attached is a small print job which, if the contents are sent to a PCL printer port, may (but may not) cause a 49.xx error.
Results with my two printers:
- LaserJet 1320n: job prints
- Laserjet Pro 400 Colour MFP M475dn (firmware datecode 20120808): printer reboots after reporting "49 Service error Turn off then on"
The print job just contains a few initialisation sequences, and a small raster graphics image.
The image uses adaptive compression, but an extra trailing zero (null) byte has been inserted in each 'block', which makes the data invalid according to the specification.
Also attached are a similar PCL print job, but with valid raster data, and analyses of the two jobs.