random errors on 4301 color laser F0.03.0F.03 and F0.01.04.0C

[cswilson]

some things print some dont. its random. and the event logs on printer are filled with these errors

9/18/23, 8:28 AM EDT

Warning

F0.01.04.0C

App DOX healthHeartBeat reason irregular heart beat at 5943 systemPulseCount at 6400 requestType 0

6.12.1.12-202306030312

9/22/23, 1:40 PM EDT	Error	F0.03.0F.03	wsPrinterCreatePrintJob2: InValid Request	6.12.1.12-202306030312
9/22/23, 1:39 PM EDT	Error	F0.03.0F.03	wsPrinterCreatePrintJob2: InValid Request	6.12.1.12-202306030312
9/22/23, 1:39 PM EDT	Error	F0.03.0F.03	wsPrinterCreatePrintJob2: InValid Request	6.12.1.12-202306030312
9/22/23, 1:39 PM EDT	Error	F0.03.0F.03	wsPrinterCreatePrintJob2: InValid Request	6.12.1.12-202306030312

[kosuth]

We are having the same issue. Our printer is an HP Color LaserJet Pro 4201 that we purchased less than a month ago. Same error log and everything, no seeming pattern to the errors

[FLIT]

Same exact issues with multiple units, multiple locations. New purchases and the replacements sent by HP.  Honestly not even sure where to go from here. This model is having some issues.  Hoping for a solution. Screen says "Printer error occurred F0.01.01.04    A critical system error has occurred....."

Firmware is 6.12.1.12.202306030312 also.

Edit to add:

We have to power cycle to start printing again.  Later in the day the error comes back up after a few jobs go through.  We've tried the HP support steps of power cycle, unplug and discharge, firmware reset, firmware update, more resets, replacement printers which have the same issue. Other printers of the same model at different office locations with the same issue despite different programs doing the printing (formats / document types.)  The only common denominator is this printer model and error.

[Logan53]

FLIT - 

Unfortunately you have described the exact same issues we have recently encountered with our printer. It has been out of the box for a month, working flawlessly, until last night some users started getting Windows printer notifications which said "The printer is in an error state" when they attempted to print standard PDF documents. The printer would "spin up" but ultimately not print. It was not displaying an error message on the control panel, but after a restart it has shown an error message which said it was fatal error and required the printer to restart. 

The printer in question is a HP Color LaserJet Pro MFP 4301fdn. Firmware: 6.12.1.12-202306030312.
We are printing from Windows 10 Pro, trying PDFs on an up-to-date Adobe Acrobat. We are connected via ethernet in a locally hosted AD domain setting but I am not requiring authentication to use the printer.

In the event log we are seeing these multiple times per minute:

Warning

F0.01.04.0C

App DOX healthHeartBeat reason irregular heart beat at 328 systemPulseCount at 368 requestType 0

This error also occurred multiple times in a row for ~8 minutes span but has since stopped. I think that this coincides with an attempt to print.

Error

F0.03.0F.03

wsPrinterCreatePrintJob2: InValid Request

Neither of these error codes pull up any solution or explanation when I have looked them up on HP's website.

Has anyone tried to roll back firmware? Perhaps the latest firmware version is a bad release.
HP is also issuing us a replacement, but it sounds like this issue has continued for those affected even with a replacement unit. Unfortunately, prior to this issue occurring, we ordered a second unit, so it will be interesting to see if this occurs on that unit as well. 

We have also had small success power cycling and then being able to print once or twice but do end up running into the error again. HP asked us to perform a factory reset and this has not fixed the issue. It sounds like user FLIT has done firmware resets - but is this just refreshing the same version or attempting an older firmware version?

Hoping someone discovers a solution.

[cswilson]

still no luck with this and hp support has been useless sofar

[Logan53]

Possibly relevant - Are any of you also using fax features on the printer? We have an Axacore fax bridge attached using Nextiva's vFax service. This could be trying to send a connection heart beat potentially? Unfortunately the language of that warning does not much of anything to me. The faxes are actually printing when received with zero problems though. It's the Windows 10 desktops that get errors when we try to print. 

[cswilson]

Not using the fax function here.

[FLIT]

The firmware flashes have all been using the current unfortunately. I believe that's all we have access to currently?  We do have a fax line connected. Simple POTS line from the telco, no VoIP adapter boxes or custom setup.

Reboots get us a few prints before this randomly happens again.  It almost seems time based rather than print job based.  When we reboot, we can throw quite a few jobs immediately through while testing, with no issue.  (This makes jumping through the HP support steps extra aggravating since it's fine until you disconnect the chat.) Then a few minutes to an hour later, error on one single job.

[Logan53]

Ok. Probably not fax related then with 3 of us having different scenarios there. I looked at the downloads that are available for firmware and I think you are right about the current being the only one we have access to. It's either the first and only firmware released for these printers or they only make available the most current version. 

Our experience is very similar with being able to get jobs through until a period of time has elapsed, then it's no-go until you reboot. 

If this will eventually require a new firmware to be released in order to correct this issue, whatever it is, we can't really wait until then. If our replacement encounters the same issues again when we receive on Monday, perhaps we should propose that HP replace with a different, higher-end or equivalent model that is known to be stable. I'm not sure if this unit in question is returnable at all since it was bought via MSP requisition, but it is certainly within the warranty period.

[FLIT]

Same situation here, this is hanging up production as it is sitting behind a customer facing counter. We really need an actual solution. Replacing with a different model seems like the next avenue for us as well.  I'll say our replacement did work for about a week before the first error.