asked Jun 11, 2013 at 3:01pm
Hp HP LaserJet 4

HP 5200 DTN getting 49.4C02 error

Greetings, folks.

We own 5 HP LaserJet 5200 DTNs. One of them has been getting the 49.4C02 error. While this happens frequently enough to dissuade people from using the printer, it does not happen every time or on demand.

Our environment is 98\% Macintosh based.

I've been researching and troubleshooting the issue for a while now. Here is what I can determine.

1) Does not appear to be particular jobs / applicaitons that cause this. A particular job might cause it, but reprinting it after a reboot will work fine.

2) Does not appear to be network cabling. I moved the printer, swapping with a known good printer. The known good printer worked fine in the new location with all the old cabling, while the problem printer continued to have problems with new users and new print jobs.

3) Does not appear to be 3rd party RAM related. The problem printer gets the error with known good RAM installed, while the RAM from the problem printer works fine in a known good printer. The problem printer also gets the error with no extra RAM installed.

4) Does not appear to be firmware related. I was able to update the firmware to the lastest without any reported issues. Still gets the error.

5) There are no EIO devices installed.

6) I have removed and swapped the formatter board (HP Q6498-69006) with a known good printer's board, to try an isolate if that was the issue. The problem printer contines to get the 49.4C02 error.

7) I have done a Cold Reset, including clearing the JetDirect / neworking info. No apparent effect.

Now I'm open to any/all suggestions on what to try next.

Update the firmware with the latest version - have had several models throw that error and updating the firmware corrected the error.

by Ocicat on Jun 11, 2013 at 3:15pm Add comment
Please see #4. I already updated the firmware to the latest version. The update went fine, but it didn't affect the issue.
by Chanfan on Jun 11, 2013 at 3:30pm Add comment
"Does not appear to be particular jobs / applicaitons that cause this. A particular job might cause it, but reprinting it after a reboot will work fine."

Yo Chan-meister, you just contradicted yourself. I'll see if my crystal skull will reveal anything about your problem. Like I said, the crystal skull contains the knowledge of the entire universe, but it can be moody.
by eric111 on Jun 11, 2013 at 10:25pm Add comment
Sorry, what I meant was - when the error appears, if you reboot, the job in queue doesn't cause the error to re-appear.

I shouldn't have said "a particular job might cause it".
by Chanfan on Jun 11, 2013 at 11:25pm Add comment
Yes, I did see # 4 - I have had to run an update several times to actually get a clean update.

The 49.xxxx error involves the firmware and sometimes in conjunction with settings for Postscript drivers (usually with Acrobat 8.0), ALM (Alternate Letterhead Mode), Disabling of Reverse DNS lookup, and also can be caused by using some TTF fonts such as Papyrus and Franklin Gothic on MAC systems.

The 49 errors can be a pain - just trying to help.

by Ocicat on Jun 12, 2013 at 10:33am Add comment
Okie dokie, that's good info. I can certainly try re-updating it. Also interesting on the reverse DNS, wacky.
by Chanfan on Jun 12, 2013 at 10:48am Add comment
Looks potentially promising, I may need to eat crow soon!

FTP / Mac printer utility attempts to re-send the upgrade would send, but the printer display would end up with a 49:4C18 error.

Sending via Windows DOS copy to a direct USB connection seems to have gone through the process without spawning such an error. Now, I just have to wait and see if the error appears during normal printing.
by Chanfan on Jun 12, 2013 at 1:52pm Add comment
This is a general description for the 49.xxxx error

A critical firmware error has occurred that caused the processor on the formatter to abort the operation. This type of error can be caused by invalid print commands, corrupt data, or invalid operations. In some instances, electrical noise in the cable can corrupt data during transmission to the printer. Other causes include poor quality parallel cables, poor connections, or specific software programs. Remove all EIO devices and firmware DIMM if installed. Restart printer. If error is gone replace each EIO device until error appears. Replace device which triggers error. May also be formatter.
Firmware updates are available for some machines at and clicking on the drivers and software tab. Also try printing from a different application. If that works go back to the first application and try printing a different file to determine if the problem is file related. You may need to reseat the memory DIMM's or replace the firmware DIMM or formatter board.

by Ocicat on Jun 12, 2013 at 2:09pm Add comment
Alas, I would have rather eaten crow. The error was back this AM.

I am suspecting it may be one of the other PC boards, or the cabling that connects them.
by Chanfan on Jun 13, 2013 at 9:00am Add comment
Just a thought before replacing boards. Have you reseated the firmware DIMM in problem printer or tried the DIMM in a different printer to see if the error follows?
by Ocicat on Jun 14, 2013 at 9:17am Add comment
The firmware DIMM? Nope, I'll have to see how difficult that is.
by Chanfan on Jun 14, 2013 at 1:17pm Add comment
You said that you removed and replaced the formatter board. The firmware DIMM plugs into it.
by moe on Jun 14, 2013 at 4:37pm Add comment
I may be off base here but I do not think the firmware is a replaceable chip on the formatter. I believe it is self contained soldered on the formatter. HP does not have a part number for the firmware either in the service manual or on the parts web site so I think you are all barking up a wrong tree here. I still think the issue is driver or document related.
by dmzcompute on Jun 14, 2013 at 5:47pm Add comment
The reason I don't think the issue is driver or document related is that, when the printers are swapped, the "bad" printer has issues with new users/jobs, while the "good" printer has no such issues with the old jobs/users.

If the firmware DIMM is on the formatter board, then yes, I have already swapped them out (by virtue of swapping entire formatters).
by Chanfan on Jun 14, 2013 at 8:24pm Add comment
When you swap the printers are you changing the ip address to match the other printer or just changing the printer each user uses. If the later, then you are still using the same driver which may be corrupt. If changing the ip address, the only item I can think of is the dc controller which interacts with the formatter and is maybe causing the issue.

Also I found this which says the issue was corrected with the latest firmware update, however, maybe there is another font or the issue was corrected with one upgrade and the next (latest firmware) does not have the fix so some printers will work and others will not. If the case you need to compare firmware versions between printers since the printers that are working may have older versions which work ok.

HP LaserJets and Color LaserJets with Mac OS 10.5 - Display a 49.4c02 Error when Printing the Papyrus Font
Some HP LaserJets and Color LaserJets will display a 49.4c02 error on the front panel, when printing a document containing the Papyrus font, that ships with Mac OS 10.5.x.

This issue is resolved in the latest version of printer firmware. Upgrade the device to most recent version of firmware available on HP website.

Click here to view HP website at

Additional link which may help:\% 3a8\%3a\%23USA&LanguageCode=en&DocId=emr_na-c03383941
by dmzcompute on Jun 15, 2013 at 5:01am Add comment
In all cases (both the physical printer swap, and when I swapped formatter boards) the IP address / other network info was driven by the physical location of the device. So, I did change the IP address / network names of the devices if I moved them.

I have installed the latest firmware that I am aware of. I have not attempted to mitigate things with the auto-reboot feature.

I'll double check on the Papyrus font. I feel confident this is not the issue, however.

The troubleshooting document is interesting in it's frankness. I certainly wish the error was of a more reproducible kind.
by Chanfan on Jun 17, 2013 at 9:31am Add comment
No luck with the auto-reboot feature, a 49.4C02 error won't reboot via that - at least in this case.
by Chanfan on Jun 21, 2013 at 1:45pm Add comment