Hello! I have an issue with an HP M5035 with firmware version 48.430.1. End user updated to windows server 2016. All HP's started throwing 49.ff03 errors. I instructed IT to update firmware (red tape sort of situation, not allowed to update firmware for this contract).
He started to update firmware on the M5035 locally and it did not complete.
Upon my arrival, machine states reload firmware and copy and fax functions are unavailable due to a 30.01.34 error.
Shut down, removed back panels and rebooted. cold reset, then after boot finished, same 30.01.34 error and all SCB lights are solid green on board. Power cycled and then I was stuck at the 49.ff03 error with ethernet disconnected. tried booting with no hdd connection, jet direct card, for fax. no change.
Booted without formatter and completed engine test (not sure what this was supposed to prove but it felt necessary).
I am finding little information other than it being a firmware issue. I saw somewhere that he may have completed firmware update but without SCB packet? I'm curious if it is just an incompatibility with windows server 2016 and the m5035, or if the firmware upgrade just got a bit screwed up.
does anyone have any experience with M5035 and windows server 2016?
He started to update firmware on the M5035 locally and it did not complete.
Upon my arrival, machine states reload firmware and copy and fax functions are unavailable due to a 30.01.34 error.
Shut down, removed back panels and rebooted. cold reset, then after boot finished, same 30.01.34 error and all SCB lights are solid green on board. Power cycled and then I was stuck at the 49.ff03 error with ethernet disconnected. tried booting with no hdd connection, jet direct card, for fax. no change.
Booted without formatter and completed engine test (not sure what this was supposed to prove but it felt necessary).
I am finding little information other than it being a firmware issue. I saw somewhere that he may have completed firmware update but without SCB packet? I'm curious if it is just an incompatibility with windows server 2016 and the m5035, or if the firmware upgrade just got a bit screwed up.
does anyone have any experience with M5035 and windows server 2016?

Comment