HP PageWide Enterprise Color 556 error codes with quick guide
– Compatible Printer model: HP PageWide Enterprise Color 556
– HP PageWide Enterprise Color 556 Error Codes with instructions guide:
HP PageWide Enterprise Color 556
- Code: 11.00.01, 11.00.02
- Description: Internal clock error This message indicates a problem with the formatter’s real time clock. The product real time clock has experienced an error. 01=dead clock 02=dead real time clock
- Remedy: 1. Whenever the product is turned off and then turned on again, set the time and date on the control panel. 2. If the error persists, you might need to replace the formatter.
- Code: 15.00.00
- Description: Unknown Jam A paper jam has occurred in the printer at an unknown location.
- Remedy: 1. Follow jam removal instructions on the screen.2. Open all doors and trays and remove all paper from the paper path.3. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page).
- Code: 15.A0.01
- Description: Input Jam, Tray 1 An input jam occurred from Tray 1 but sensor and condition are unknown. No Pick ‘Did not pick page from tray 1”. This jam occurs when the paper does not reach the Feed roller REDI sensor [1] for Tray 1 in designated amount of time after the start of paper pick-up from Tray 1.
- Remedy: 1. Follow jam removal instructions on the screen.2. Clear all possible paper jam locations (remove paper stack, open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door ).3. Verify the paper meets the specifications for the tray.4. Ensure that the tray width setting is set to your paper being installed into the tray. The arrow on the guide should line up exactly with the line connected to paper size designation.5. Make sure the tray is not overload above the marking shown on the tray side guide. 6. Check the Tray 1 feed roller for wear, damage or paper dusk. Clean or replace the rollers as needed.7. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page).8. Replace the Mech Kit.
- Code: 15.A0.02
- Description: Input Jam, Tray 2 An input jam occurred from Tray 2 but sensor and condition are unknown. No Pick ‘Did not pick page from tray 2”. This jam occurs when the paper does not reach the Feed roller REDI sensor [1] for Tray 2 in designated amount of time after the start of paper pick-up from Tray 2.
- Remedy: 1. Follow jam removal instructions on the screen.2. Clear all possible paper jam locations (Open paper cassette remove paper, open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door).3. Verify the paper meets the specifications for the tray.4. Ensure that the tray width setting is set to your paper being installed into the tray. The arrow on the guide should line up exactly with the line connected to paper size designation.5. Make sure the tray is not overload above the marking shown on the tray side guide. 6. Check the Tray 2 pickup and feed rollers for wear, damage or paper dusk. Clean or replace the rollers as needed. Order P/N: CN598–67018 Separator Pick Assembly kit tray 27. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page).8. Replace the Mech Kit.
- Code: 15.A0.03
- Description: Input Jam, Tray 3 An input jam occurred from Tray 3 but sensor and condition are unknown. No Pick ‘Did not pick page from tray 3”. This jam occurs when the paper does not reach the Tray 3 separation REDI sensor in designated amount of time after the start of paper pick-up from Tray 3.
- Remedy: 1. Follow jam removal instructions on the screen.2. Clear all possible paper jam locations (Open paper cassette remove paper, open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door ).3. Verify the paper meets the specifications for the tray.4. Ensure that the tray width setting is set to your paper being installed into the tray. The arrow on the guide should line up exactly with the line connected to paper size designation.5. Make sure the tray is not overload above the marking shown on the tray side guide. 6. Ensure the Pick sensor flag is not out of position. If it is found to be out of position, gently move the lever to the correct position. 7. Check the Tray 3 pickup and feed rollers for wear, damage or paper dusk. Clean or replace the rollers as needed. Order P/N: CN598-67071 Separator pick assembly kit Tray 3 8. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page). 9. Replace the Mech Kit.
- Remedy: 1. Clear all possible paper jam locations (Open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door ).2. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page).3. Run the Advance Jam Recovery Utility using a heavy paper on tray 1 (Administration / Troubleshooting / Advance Jam Recovery). It is recommended to run it a few times in order to clear jams at the print zone.4. If the issue persists, replace the Mech Kit.
- Code: 15.C0.0Z
- Description: Switchback area Jam from Tray X An output jam occurred while printing from indicated tray or area.•15.C0.01 . Switchback jam from Tray 1•15.C0.02 . Switchback jam from Tray 2•15.C0.03 . Switchback from Tray 3•15.C0.0D . Switchback from Duplexer
- Remedy: 1. Clear all possible paper jam locations (Open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door).2. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page). 3. Check the 2 mirror labels for the optical REDI reflection sensor on the inside of products left door. If one or more of the mirror labels it found to be missing or out of place, this error could occur. 4. Reposition the mirror label if it is found to be out place. If the mirror label will not stick or is missing, replace the Left door / Tray 1 Assembly B (HP Part #: B5L04-67916).
- Code: 15.C0.F0
- Description: Jam in left door at Power On An jam occurred in the left door at Power On.
- Remedy: 1. Clear all possible paper jam locations (Open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door ).2. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page).3. Run the Advance Jam Recovery Utility using a heavy paper on tray 1 (Administration / Troubleshooting / Advance Jam Recovery). It is recommended to run it a few times in order to clear jams at the print zone.4. If issue persists, replace the Mech Kit.
- Code: 15.E0.0Z
- Description: Output jam from Tray X An eject jam occurred from the tray designated.•15.E0.01 . Output jam from Tray 1•15.E0.02 . Output jam from Tray 2•15.E0.03 . Output jam from Tray 3•15.E0.0D . Output jam from Duplexer
- Remedy: 1. Clear all possible paper jam locations (Open left door, remove ICU, lower flap, clear paper, raise flap, install ICU, close door ).2. Run Paper Path Diagnostics to move paper from tray to output bin (Administration / Troubleshooting / Paper Path Page).3. Replace Mech Kit.
- Code: 17.0X.00
- Description: Failed Cartridge The indicated cartridge is detected but its data is corrupt or invalid in some way.•17.00.00 . Black Cartridge•17.01.00 . Cyan Cartridge•17.02.00 . Magenta Cartridge•17.03.00 . Yellow Cartridge
- Remedy: 1. Remove the cartridge, reinstall it and close the ink door.2. Turn the product off, and then on again.3. Replace the failing cartridge.4. Replace the Mech Kit.
- Code: 17.0X.34
- Description: Counterfeit or refilled cartridge installed The supply being used is either a counterfeit or refilled cartridge.•17.00.34 . Black Cartridge•17.01.34 . Cyan Cartridge•17.02.34 . Magenta Cartridge•17.03.34 . Yellow Cartridge
- Remedy: To avoid this condition – always use genuine HP cartridges. The user must replace with a genuine HP cartridge OR approve the use of refilled cartridges before printing can continue. If you believe you purchased a genuine HP supply, go to www.hp.com/go/anticounterfeit. Any print quality repair required as a result of using used cartridges is not covered under warranty. Supply status and features depending on supply status are not available.
- Code: 17.0X.35
- Description: Incompatible <supply> The indicated supply is not compatible with this product.•17.00.35 . Black Cartridge•17.01.35 . Cyan Cartridge•17.02.35 . Magenta Cartridge•17.03.35 . Yellow Cartridge
- Remedy: To avoid this condition – always use genuine HP cartridges. The user must replace with a genuine HP cartridge OR approve the use of refilled cartridges before printing can continue.
- Code: 17.0X.36
- Description: Non-Startup cartridge at startup Non-Startup cartridge at startup. A trade cartridge has been installed before purge has been completed.•17.00.36 . Black Cartridge•17.01.36 . Cyan Cartridge•17.02.36 . Magenta Cartridge•17.03.36 . Yellow Cartridge
- Remedy: To avoid this condition – always use the startup cartridges that shipped with the product. Do not override and use trade cartridges unless absolutely necessary. If the user later finds the startup cartridges after initialization, these startup cartridges will be unusable on this device.
- Code: 17.0X.37
- Description: Startup Cartridge after startup completed Startup cartridge is being used after startup completed.•17.00.37 . Black Cartridge•17.01.37 . Cyan Cartridge•17.02.37 . Magenta Cartridge•17.03.37 . Yellow Cartridge
- Remedy: To avoid this condition, always use trade cartridges after initialization has completed and the original startup cartridges are spent. Startup cartridges can only be used the first time the product is initialized. Once a startup cartridge has been used for initialization it’s memory tag contents are changed to indicate it will now behave and be detected as a trade cartridge.
- Remedy: There several possible outcomes when this condition is detected:1. The user removes the cartridge from the printer and replaces it with a non-empty cartridge.2. The user touches gOKh and approves the use of the gPossibly Emptyh cartridge.• Printer attempts to pump/prime ink but is unsuccessful. The cartridge is declared as gEmptyh.• Some ink was previously stranded due to tilt and the pump/prime is successful. The cartridge is declared as • Lowh or possibly • Very Lowh.• Cartridge has been refilled and now after printing some number of pages, the cartridge will be declared as Refilled.
- Code: 17.0X.39
- Description: Use new cartridges The Startup-Trade cartridge override feature has been enabled and a partially used Cyan Cartridge has been installed before the ink initialization process completed. The cartridge might not be able to complete the ink initialization. Using a new cartridge allows the process to complete in one session, preventing the user from leaving and coming back to find the process incomplete.•17.00.39 . Black Cartridge•17.01.39 . Cyan Cartridge•17.02.39 . Magenta Cartridge•17.03.39 . Yellow Cartridge
- Remedy: Touch “OK” to continue or use a new cartridge. If a “Too Low to Prime” condition occurs, use the following steps.1. The engine has determined that there is probably not enough ink in the installed trade cartridge to complete the initialization (ink purge) process.2. The user can touch “OK” to proceed anyway (they may see this same message again once the current cartridge is depleted).3. The user can replace the partially full trade cartridge with a replacement that is full.
- Code: 17.0X.42
- Description: General printing error Printer failure or the indicated cartridge SHAID too early. • 17.00.42 . Black Cartridge • 17.01.42 . Cyan Cartridge • 17.02.42 . Magenta Cartridge • 17.03.42 . Yellow Cartridge NOTE: Condition does not distinguish between SHAID Too Early and a failure in the ink delivery system.
- Remedy: 1. Turn the product off, and then on again. 2. Replace the cartridge. 3. Replace the Mech kit.
- Code: 17.0X.52
- Description: Supply upgrade detected The indicated supply upgrade was detected. • 17.00.52 . Black Cartridge • 17.01.52 . Cyan Cartridge • 17.02.52 . Magenta Cartridge • 17.03.52 . Yellow Cartridge
- Remedy: Touch “OK” to continue or change cartridge.
- Code: 17.0X.53
- Description: Supply upgrade successful The indicated supply upgrade was successful. • 17.00.53 . Black Cartridge • 17.01.53 . Cyan Cartridge • 17.02.53 . Magenta Cartridge • 17.03.53 . Yellow Cartridge
- Remedy: No action necessary.
- Code: 17.0X.54, 17.0X.55
- Description: Supply upgrade problem The indicated supply encountered an upgrade problem. The requested upgrade (addition of a new cartridge to the list of supported cartridges stored in the engine NVRAM) using a gTradeh cartridge did not succeed. The formatter does not know why the failure occurred, only that it did fail.•17.00.54 . Black Cartridge•17.01.54 . Cyan Cartridge•17.02.54 . Magenta Cartridge•17.03.54 . Yellow Cartridge•17.00.55 . Black Cartridge•17.01.55 . Cyan Cartridge•17.02.55 . Magenta Cartridge•17.03.55 . Yellow Cartridge
- Remedy: 1. Replace the failed cartridge with one that is known good and then reinsert the upgrade cartridge and try again.2. Turn the product off, and then on again.3. Remove the upgrade cartridge and go back to using the cartridge(s) supported at release.4. Replace the Mech Kit.
- Code: 17.0X.56
- Description: Ink sensor warning The indicated cartridge has printed past approximately 150% of its expected capacity and there has been no SHAID event. The ink sensor might not be able to detect when supplies are empty or the cartridge has been refilled.•17.00.56 . Black Cartridge•17.01.56 . Cyan Cartridge•17.02.56 . Magenta Cartridge•17.03.56 . Yellow Cartridge
- Remedy: 1. If print quality issues exist, replace the cartridge.2. Check cartridge warranty and manufacture date. Check event log for low on ink code. If user acknowledges, assume cartridge has been refilled.
- Code: 17.0X.57
- Description: HP Cartridge Protection enabled The indicated cartridge that has been protected using the HP cartridge protection feature has been detected. The target cartridge has been locked to a different printer and cannot be used on this device.•17.00.57 . Black Cartridge•17.01.57 . Cyan Cartridge•17.02.57 . Magenta Cartridge•17.03.57 . Yellow Cartridge
- Remedy: 1. Replace the indicated cartridge with one that has not been “protected” on another device.2. Once a cartridge is locked to a given device there is no way to unlock the cartridge.
- Code: 17.0X.60
- Description: Cartridge Low Warning The indicated cartridge is low.•17.00.60 . Black Cartridge•17.01.60 . Cyan Cartridge•17.02.60 . Magenta Cartridge•17.03.60 . Yellow Cartridge
- Remedy: No action necessary.
- Code: 17.0X.65, 17.0X.80
- Description: Install Supply The indicated cartridge is not installed or missing or has a damaged acumen.•17.00.65 . Black Cartridge•17.01.65 . Cyan Cartridge•17.02.65 . Magenta Cartridge•17.03.65 . Yellow Cartridge•17.00.80 . Black Cartridge•17.01.80 . Cyan Cartridge•17.02.80 . Magenta Cartridge•17.03.80 . Yellow Cartridge
- Remedy: 1. Reinstall the supply.2. Replace the indicated supply with a replacement.
- Code: 17.0X.69
- Description: Cartridge Very Low The indicated cartridge is very low.•17.00.69 . Black Cartridge•17.01.69 . Cyan Cartridge•17.02.69 . Magenta Cartridge•17.03.69 . Yellow Cartridge
- Remedy: The target cartridge has been depleted and the only ink remaining is in the X chamber and print head. The cartridge can be replaced in this state without any loss of ink to the system.
- Code: 17.0X.70
- Description: Printing past very low The indicated cartridge is printing past very low.•17.00.70 . Black Cartridge•17.01.70 . Cyan Cartridge•17.02.70 . Magenta Cartridge•17.03.70 . Yellow Cartridge
- Remedy: The print quality should not degrade in any way when the ink cartridge approaches end-of-life as the product will halt printing when all of the usable ink has been depleted. Customers should have a spare cartridge on-hand as the indicated cartridge will transition to Empty in just a few pages. If print quality is not acceptable replace the indicated cartridge.
- Code: 17.31.60
- Description: Ink Collection Unit Warning Ink Collection Unit almost full. The percentage of life remaining is 2%. The product’s Ink Collection Unit (ICU) collects unused ink for later disposal. The life tracking on this supply is accomplished via a numeric percent life remaining (PLR) that starts at 100% and decreases in 1% increments as pages are printed. The engine counts the number of ink droplet that go into the ICU and reports this information to the formatter as a percentage of life remaining. The expected life of the ICU is nominally 120,000 page but this will vary depending on printing patterns.
- Remedy: A new ICU should be ordered and printing can continue. NOTE: There is no sensor that indicates when the ICU has been replaced. For this reason the user will be asked near end of ICU life if the ICU has been replaced each time the left door closes or a power-on occurs.
- Code: 17.31.65
- Description: Install Supply Ink Collection Unit The Ink Collection Unit (ICU) is not installed.
- Remedy: Install the ICU, make sure it is aligned and installed correctly. If message continues to appear, install a replacement ICU.
- Code: 17.31.69
- Description: Ink Collection Unit full The Ink Collection Unit is full. This is the second warning that the ICU life is almost depleted. The percentage of life remaining is 1% or less. The products Ink Collection Unit (ICU) collects unused ink for later disposal. The life tracking on this supply is accomplished via a numeric percent life remaining (PLR) that starts at 100% and decreases in 1% increments as pages are printed. The engine counts the number of ink droplet that go into the ICU and reports this information to the formatter as a percentage of life remaining. The expected life of the ICU is nominally 120,000 page but this will vary depending on printing patterns.
- Remedy: Replace the ICU or continue printing until stop occurs.
- Code: 17.31.70
- Description: Ink Collection Printing past full Ink Collection Unit (ICU) printing past full.
- Remedy: Replace the ICU. Replacement can occur at this point or the user can continue until halted.
- Code: 17.31.71
- Description: Reinstall Ink Collection Unit The product has prompted the user to remove and reinstall the Ink Collection Unit (ICU) to maintain print quality.
- Remedy: Remove and reinstall ICU, make sure it is aligned and installed correctly.
- Code: 17.31.72
- Description: Ink Collection Unit reinstalled The user removed and reinstalled the Ink Collection Unit (ICU) to maintain print quality.
- Remedy: No action necessary.
- Code: 17.31.73
- Description: New Ink Collection Unit The Ink Collection Unit (ICU) counter has been reset.
- Remedy: There is no sensor that indicates when the ICU has been replaced. For this reason the user will be asked near end of ICU life if the ICU has been replaced each time the left door closes or a power-on occurs. When “YES” is selected the reset will be performed.
- Code: 17.31.80
- Description: Replace Ink Collection Unit Ink Collection Unit (ICU) is full and must be replaced.
- Remedy: Replace the ICU.
- Code: 17.99.31
- Description: Non-HP supply in use Non-HP supply in use. If any of these bits are set, the event could be posted. This message does not distinguish between supplies.
- Remedy: No action necessary.
- Code: 17.99.32
- Description: Previously used HP Supply installed An original HP supply that started its life in another product is in use. This message does not distinguish between supplies.
- Remedy: No action necessary.
- Code: 17.99.40
- Description: Supplies installed Transition of at least one non-HP to all genuine. This message does not distinguish between supplies.
- Remedy: No action necessary.
- Code: 17.99.49
- Description: Startup Cartridge Override User has overridden using Startup cartridges. This message does not distinguish between supplies.
- Remedy: No action necessary.
- Code: 17.99.58
- Description: HP Cartridge Protection enabled A user enabled the HP Cartridge Protection Feature, protecting their cartridges and restricting the cartridges to only be usable in the product that originally protected them.
- Remedy: No action necessary.
- Code: 20.00.00
- Description: Insufficient memory: <Device> Event log error message 20.00.00. The product does not have enough memory to print the page. The product received more data than can fit in the available memory. You might have tried to transfer too many macros, soft fonts, or complex graphics.
- Remedy: Touch the OK button to print the transferred data. Some data might be lost. Reduce the page complexity or add product memory.
- Code: 21.00.00
- Description: Page Too Complex Event log error message 21.00.00. The product displays this message to indicate that the page decompression process was too slow for the product.
- Remedy: Touch the OK button to continue. There may be some data loss on the page that was being formatted when the error occurred.
- Code: 21.1C.2D
- Description: Page complex error Event log error message 21.1C.2D. The product displays this message to indicate that the page decompression process was too slow for the product.
- Remedy: Touch the OK button to continue. There may be some data loss on the page that was being formatted when the error occurred.
- Code: 30.01.01
- Description: The flatbed cover sensor was interrupted. The scanner flatbed cover is open. Message appears only in the event log and is not posted on the control panel. The control panel will read Flatbed Cover Open.
- Remedy: No action necessary. This error message should automatically clear. If the error persists, open the Scanner Tests to test the flatbed cover sensor.1. If the cover is closed, check the cover sensor at the right rear of the scanner for correct mechanical functionality, using the scanner sensor test in the Administration / Troubleshooting / Diagnostics / Scanner Tests Menu.2. Check the connectors on the scanner control board (SCB) for loose connections.3. Replace the scanner control board (SCB).4. Replace the integrated scanning assembly (ISA).
- Code: 30.01.02
- Description: Scanner calibration failure The scanner calibration failed.
- Remedy: 1. Turn the product off, and then on again. 2. After the product warms up, repeat the calibration process. Device Maintenance / Calibrate-Cleaning / Calibrate Scanner 3. If the error persists, clean the scanner glass and calibration strips. NOTE: Dust might appear on the underside of the glass, but this cannot be cleaned. a. Press the power button to turn the product off, and then disconnect the power cable from the electrical outlet. b. Open the scanner lid. c. Use a soft, lint-free cloth moistened with water to clean the calibration white strips and reflector plate (see call-outs). Also clean the document feeder glass, flatbed glass and plastic lid backing. NOTE: If needed, lens cleaner or nonabrasive glass cleaner can be applied to the cloth before cleaning the glass. Spray only onto the cloth and not directly onto the glass or device. Do not spray water or glass cleaner on the glass as it can seep under it and possibly damage the printer. Do not use abrasives, acetone, benzene, ethyl alcohol, or carbon tetrachloride on the glass; these can damage it and/or leave residue on the glass resulting in degraded copy/scan quality. 4. If the error persists, replace the Integrated Scanning Assembly (ISA).
- Code: 30.01.08
- Description: Home position error The scanner optic failed to return to the home position.
- Remedy: 1. Turn the product off, and then on again. 2. Observe the movement of the optics assembly. 3. If the error persists, run the scanner motor test under component test. Administration/ Troubleshooting/Scanner tests/Flatbed motor test 4. If issue still remains and firmware has been upgraded replace scanner control board (SCB). IMPORTANT: Check all cables on SCB for proper connection and seating before replacing any parts and test. 5. If the error persists, replace the integrated scanning assembly (ISA).
- Code: 30.01.14
- Description: Scan system EEPROM error Scanner control board (SCB) EEPROM error.
- Remedy: 1. Turn the product off, and then on again.2. Ensure all connectors on the SCB are connected and properly seated.3. Ensure the MFP has at latest SCB firmware version.4. Replace the SCB.
- Code: 30.01.15
- Description: Scanner error Scanner did not initialize (internal error). The scanner failed to be initialized due to an internal error.
- Remedy: 1. Turn the product off, and then on again.2. Verify that all covers are installed correctly and that the ADF and ADF jam cover are closed.3. Check all sensors on the scanner to ensure they are not blocked.4. Look through the vents on back of scanner check to see if GREEN SCB LEDs are lit.5. Check all connections for SCB to print engine and make sure they are properly seated.6. Replace the SCB.
Solved HP PageWide Enterprise Color 556 Error codes
- Code: 30.01.18
- Description: Scanner Error Scanner internal optical sensor error.
- Remedy: 1. Turn the product off, and then on again.2. Make sure that all the connectors on the SCB are properly seated.3. Make sure that the MFP has the latest SCB firmware version.4. Replace the SCB.5. If the error persists, replace the integrated scanning assembly (ISA)
- Code: 30.01.19
- Description: Scanner lamp error Scanner internal lamp sensor error.
- Remedy: 1. Turn the product off, and then on again.2. Determine if the scanner lamp turns on and off approximately 12 second after the product turns on.3. Test the lower lamp using the scanner test located in the Diagnostics menu.4. Re-seat the interconnect cables between the optical carriage and the SCB.5. Replace the integrated scanning assembly (ISA)
- Remedy: Turn the product off, and then on again. Check all connections on the SCB. Replace the SCB.
- Code: 30.01.36
- Description: Upgrade Error Try downloading upgrade again Scanner firmware upgrade error.
- Remedy: 1. Re-send the scanner firmware upgrade. 2. If the error persists, replace the SCB.
- Code: 30.01.41, 30.01.44, 30.01.45
- Description: Scanner error The formatter lost connections with the SCB or communication was corrupted. Scanner control board (SCB) communication error.
- Remedy: 1. Have the customer turn the printer off, and then on to see if error persists. 2. If issue persists, turn the printer off and remove and then re-seat the formatter then turn the printer back on. 3. If issue persists, Upgrade the firmware. 4. Replace the scanner control board (SCB). IMPORTANT: Add notes for On-Site technician to verify that all cables are connected to the product and to the interconnect board, and scanner control board (SCB) before replacing any parts. 5. Replace the formatter. 6. Verify that all cables are connected to the product and to the interconnect board / formatter and SCB.7. Verify that the scanner control board (SCB) has power.8. Replace the scanner control board (SCB).
Service Technician: 1. Turn the printer off, and then on to see if error persists.2. If issue persists, turn the printer off and remove and then re-seat the formatter then turn the printer back on.3. If issue persists, Upgrade the firmware. 4. Verify that all cables are connected to the product and to the interconnect board / formatter and SCB.5. Verify that the scanner control board (SCB) has power.6. Replace the scanner control board (SCB). 7. Replace the formatter.
- Code: 30.01.42
- Description: Scanner error Internal product communication error.
- Remedy: 1. Turn the product off, and then on again.2. If the error persists, turn the product off, and then check all scanner control board (SCB) connectors are fully seated.3. If this error occurs after a formatter, fax card or hard disk has been replaced, check that the formatter connectivity LED (smile face icon on the formatter) is illuminated. Check the fax card for proper seating on the formatter. (If fax card is not properly seated it can prevent the formatter from seating properly in the product. 4. Verify that all cables are connected to the product and to the interconnect board / formatter and SCB. 5. If the error persists, replace the scanner control board (SCB).
- Code: 30.01.43
- Description: Scanner memory failure Scan memory error.
- Remedy: 1. Turn the product off, and then on again. 2. If the error persists, turn the product off, and then re-seat the formatter. 3. If the error persists, replace the formatter.
- Code: 30.01.46
- Description: Scanner Error The firmware cannot find the copy processor board (CPB).
- Remedy: 1. Turn the product off, and then on again. 2. If the error persists, turn the product off, and then re-seat the formatter. 3. If the error persists, replace the scanner control board (SCB).
- Code: 30.01.48
- Description: Scanner error Scanner error. Scanner power is not connected.
- Remedy: 1. Turn the product off, and then on again. 2. If the error persists, use another known good power cord, make sure printer is connected to a known good dedicated power outlet and not to UPS or surge protector. 3. If the error persists, turn the product off, and then check the scanner wire-harness connectors and the scanner power supply fan. 4. If the error persists, replace integrated scanning assembly (ISA). IMPORTANT: On-Site Technicians need to check the scanner wire-harness, All SCB connectors and the scanner power before replacing any parts.
- Code: 30.01.50
- Description: Scanner error Internal scanner control board (SCB) error.
- Remedy: 1. Turn the product off, and then on again.2. Upgrade the firmware (FW).3. If the error persists, replace the SCB.
- Code: 30.03.14
- Description: A non-fatal error has occurred. A scanner EEPROM (NVM) error has occurred.
- Remedy: This is an informational message, and no action is required.
- Code: 30.03.XX
- Description: XX 30.03.20 : The copy processor board firmware cannot communicate with the PCA on the optical assembly.30.03.22 : Front side illumination calibration failure. The scan module cannot see the illumination module, or marginal illumination. The optical assembly may not be parked under the calibration strip.30.03.23 : Flatbed alignment calibration error.30.03.30 : Flatbed motor shutdown. The scanner control board (SCB) cannot communicate with the flatbed scanner motor.30.03.45 : Scanner control board (SCB) firmware assertion failure. SCB firmware assert controls the scan head motor.
- Remedy: 1. Turn the product off, and then on again. As the product turns on, verify that the scan head moves. 2. Check the service event log for other scanner errors, and then resolve those errors. 3. Upgrade the firmware. 4. Verify that the drive belt is in the correct position. 5. Run diagnostics on the flatbed scanner to see if the scan bar moves. 6. Replace the integrated scanning assembly (ISA).
- Code: 31.01.47
- Description: Document feeder not detected The document feeder was not detected, the document feeder might not be connected. The flatbed glass is still available for scanning.
- Remedy: 1. Turn the product off and then on. 2. If error persists, replace document feeder NOTE: Before replacing the document feeder, technicians should verify that the connections between the document feeder and the product are fully seated. Check One flat cable (callout 1), one ground screw (callout 2), and five connectors (callout 3).
- Code: 31.03.14
- Description: Backside scanner EEPROM (NVM) error. A non-fatal error has occurred.
- Remedy: This is an informational message, and no action is required.
- Code: 31.03.20
- Description: Backside scanner not detected Backside scanner not detected.
- Remedy: 1. Turn the product off, and then on again. 2. Verify the cables between scanner and scanner control board (SCB) are connected. (connection 6 — ADF (side 2) FFC) 3. Replace the document feeder assembly
- Code: 31.03.22
- Description: Scanner calibration failure Backside illumination calibration failure.
- Remedy: 1. Turn the product off, and then on again. 2. After the product warms up, repeat the calibration process. Device Maintenance / Calibrate-Cleaning / Calibrate Scanner 3. If the error persists, clean the scanner glass and calibration strips. NOTE: Dust might appear on the underside of the glass, but this cannot be cleaned. a. Press the power button to turn the product off, and then disconnect the power cable from the electrical outlet. b. Open the scanner lid. c. Use a soft, lint-free cloth moistened with water to clean the calibration white strips and reflector plate (see call-outs). Also clean the document feeder glass, flatbed glass and plastic lid backing. NOTE: If needed, lens cleaner or nonabrasive glass cleaner can be applied to the cloth before cleaning the glass. Spray only onto the cloth and not directly onto the glass or device. Do not spray water or glass cleaner on the glass as it can seep under it and possibly damage the printer. Do not use abrasives, acetone, benzene, ethyl alcohol, or carbon tetrachloride on the glass; these can damage it and/or leave residue on the glass resulting in degraded copy/scan quality. 4. If the error persists, replace the Integrated Scanning Assembly (ISA).
- Code: 31.03.30, 31.03.31, 31.03.32
- Description: 31.03.30: The document feeder pick motor is not turning. 31.03.31: The document feeder feed motor is not turning. 31.03.32: The document feeder de-skew motor is not turning.
- Remedy: 1. Verify that the paper meets the product specifications. 2. Make sure that the feed tray is not overloaded. 3. Check the event log for document feeder errors, and then resolve any errors first. 4. Open and close the top cover to see if the pick motor turns without posting this error. If the motor turns, then the motor is good. 5. Verify that the motor cables are connected. 6. Re-seat the document feeder to the scanner control board (SCB). 7. Replace the document feeder assembly.
- Code: 31.03.33
- Description: Backside scanner calibration area dirty The white area used for backside scanner calibration is dirty.
- Remedy: 1. Remove the white background and clean it. 2. If the error persists, clean the scanner glass and calibration strips. NOTE: Dust might appear on the underside of the glass, but this cannot be cleaned. a. Press the power button to turn the product off, and then disconnect the power cable from the electrical outlet. b. Open the scanner lid. c. Use a soft, lint-free cloth moistened with water to clean the calibration white strips and reflector plate (see call-outs). Also clean the document feeder glass, flatbed glass and plastic lid backing. NOTE: If needed, lens cleaner or nonabrasive glass cleaner can be applied to the cloth before cleaning the glass. Spray only onto the cloth and not directly onto the glass or device. Do not spray water or glass cleaner on the glass as it can seep under it and possibly damage the printer. Do not use abrasives, acetone, benzene, ethyl alcohol, or carbon tetrachloride on the glass; these can damage it and/or leave residue on the glass resulting in degraded copy/scan quality. 3. Clean the backside scanner glass. 4. If issue remains replace the document feeder assembly.
- Code: 31.03.34
- Description: Background missing The removable background for the backside scanner is either missing or not fully snapped into place.
- Remedy: 1. Remove the white background and clean it. 2. Clean the backside scanner glass. 3. If issue remains replace the document feeder assembly.
- Code: 31.13.00
- Description: Document feeder multi-pick error A multiple pick error was reported by the document feeder assembly.
- Remedy: 1. Open the document feeder cover, pull ALL the sheets back into the tray and then resume the job. 2. Verify that the paper meets the product specifications. 3. Make sure that the input tray is not overloaded and the tray guides are properly aligned to both edges of the media. 4. Check and clean the rollers and separation pad, and test the registration sensor. If needed, replace pickup roller assembly and separation pad. 5. Verify that the motor cables are connected. 6. Re-seat the document feeder to the scanner control board (SCB). 7. Replace the document feeder assembly.
- Code: 31.13.00, 31.13.01, 31.13.02
- Description: • 31.13.00: Document feeder multipick error. • 31.13.01: Sensor location 4 . Document feeder job error, pick error. Paper pick was initiated, but the page didn’t did not make it to the pick success sensor. • 31.13.02: Sensor location 4 and 5 . Document feeder job error, feed jam. The paper passed the pick success sensor, and then jammed in the document feeder paper path.
- Remedy: 1. Open the document feeder lid, pull sheets back into input tray, and then resume the job. 2. Check the paper guides and make sure that they are set to the correct paper width. 3. Make sure that the input tray is not overloaded and the tray guides are properly aligned to both edges of the media. 4. Check the document feeder page count for roller life. 5. Verify that the paper meets the product specifications. 6. Clean the document feeder pick and feeder rollers and clean separation pad If worn or damage replace roller kit. 7. Open the following menus: • Administration • Troubleshooting • Diagnostic Tests • Scanner Tests 8. Actuate the Pick-Success Sensor. If the sensor does not show functionality when tested, replace the document feeder assembly.
- Code: 31.13.13
- Description: The document feeder jam access door is open.
- Remedy: 1. Verify that the jam access cover is closed. 2. Verify that the flag is not broken off. 3. Open the following menus: • Administration • Troubleshooting • Diagnostic Tests • Scanner Tests 4. Actuate the document feeder Jam Cover Sensor. If the sensor does not show functionality when tested, replace the document feeder assembly. IMPORTANT: Before replacing the document feeder, technicians should verify that the connections between the document feeder and the product are fully seated. Check One flat cable (callout 1), one ground screw (callout 2), and five connectors (callout 3).
- Code: 31.13.14
- Description: Document feeder job error, over current. This is a feed jam in the document feeder, and the motor is not turning.
- Remedy: 1. Verify that the paper meets the product specifications. 2. Make sure that the document feeder input tray is not overloaded. 3. Check the event log for document feeder errors, and then resolve any errors first. 4. Open and close the top cover to see if the pick motor turns without posting this error. If there is no error, then the motor is good. 5. Verify that the connections between the document feeder and the product are fully seated. Check One flat cable (callout 1), one ground screw (callout 2), and five connectors (callout 3).6. Re-seat the document feeder to the scanner control board (SCB).7. Replace the document feeder assembly.
- Code: 32.1C.XX
- Description: XX 32.1C.05 (event code) The restore job ticket was submitted with invalid credentials.32.1C.06 (event code) The backup job ticket was submitted with invalid credentials.32.1C.07 (event code) Backup restore permissions error. There was an error during the creation, read, or write of the restore file.32.1C.08 (event code) Not enough disk space to perform backup/restore or network share issue. There was an error during the creation, read, or write of the backup file.32.1C.09 (event code) Tried to restore a backup file that was not valid for this product. The data in the backup file specified in the restore job ticket is no longer valid due to a corruption of the data or no loner present.32.1C.0A (event code) Backup file is invalid. The data in the backup file specified in the restore job ticket is no longer valid due to a corruption of the data or no loner present.32.1C.0D (event code) Backup/restore failed, auto-reboot failed, or the product might be busy.32.1C.11 (event code) Backup/restore timeout while communicating with the engine. The backup was aborted because the product is busy.32.1C.13 (event code) and 32.1C.14 (event code) Not enough space exists to perform the backup. The backup was aborted because the disk is at a critical level or full. Scheduled backup failure.32.1C.15 (event code) Restore aborted because the backup file was created by a previous version of firmware no longer supported by the feature.32.1C.2E (event code) The restore was aborted because the product is busy.32.1C.2F (event code) Reset failure32.1C.40 (event code) The backup operation completed successfully (informational).32.1C.41 (event code) The backup operation encountered an error (informational).32.1C.42 (event code) The backup operation completed, but with a warning message (informational).32.1C.43 (event code) A component in the backup file is not supported by the current version of firmware and will not be restored (informational).32.1C.44 (event code) A component in the backup file is not transferable to another product and will not be restored (informational). 32.1C.45 (event code) Some data was not included in the backup file (informational).32.1C.46 (event code) An expected component could not be found and was thus not backed up. Because components should be known on backups, this code is a warning (informational).32.1C.47 (event code) Some data was not restored from the backup file (informational).32.1C.48 (event code) The backup job ticket was submitted using an invalid network path.32.1C.49 (event code) The backup job ticket was submitted with a bad encryption.32.1C.4A (event code) An error occurred when creating the temporary directories used to store the backup files in transition to and from the compressed (ZIP) file.32.1C.56 (event code) Reset aborted. Backup/restore in progress (informational).32.1C.57 (event code) Reset aborted (informational).32.1C.58 (event code) Unknown reset error (informational).32.1C.60 (event code) The restore operation completed successfully (informational).32.1C.61 (event code) The restore operation encountered an error.32.1C.62 (event code) The restore operation completed, but with a warning message.32.1C.68 (event code) The restore job ticket was submitted using an invalid network path.32.1C.69 (event code) The restore job ticket was submitted with a bad encryption personal identification number (PIN).32.1C.6A (event code) An error occurred when creating the temporary directories used to store the restore files in transition to and from the compressed (ZIP) file. 32.1C.6D (event code) An unusual error occurred when running the restore.
- Remedy: 32.1C.05 (event code) Verify the credentials that were submitted. Check the domain, user name, and password.32.1C.06 (event code) Verify the credentials that were submitted. Check the domain, user name, and password.32.1C.07 (event code) Retry the job.32.1C.08 (event code)• Retry the job.• Remove stored jobs and retry.• Use a larger capacity storage device.• Check the network share. Remove any stored jobs, and then retry. If the error persists, try using a larger capacity storage device and check the network share settings.32.1C.09 (event code) Use a valid backup file.32.1C.0A (event code) Use a valid backup file. Reboot, and then observe the state of the product. If the error persists, perform a partition clean from the Preboot menu.32.1C.0D (event code) Reboot, and then retry the backup/restore.32.1C.11 (event code) Wait until the product is idle, and then try again.32.1C.13 (event code) and 32.1C.14 (event code) Free up disk space, and then try again.32.1C.15 (event code) – Use the current backup file.32.1C.2E (event code) Wait until the product is idle, and then try again. Turn the product off then on, and then retry.32.1C.2F (event code) Turn the product off then on, and then retry.32.1C.40 (event code) No action necessary.32.1C.41 (event code) No action necessary.32.1C.42 (event code) No action necessary.32.1C.43 (event code) No action necessary.32.1C.44 (event code) No action necessary.32.1C.45 (event code) No action necessary.32.1C.46 (event code) No action necessary.32.1C.47 (event code) No action necessary.32.1C.48 (event code) Check that a share was provided as part of the network path (not blank). Check that the server and the share exists. Check that the user has permission to access the share on the provided server.32.1C.49 (event code) Verify that the encryption personal identification number (PIN) meets the restrictions for the product.32.1C.4A (event code) Retry the job. If this does not resolve the issue, turn the product off then on again and retry the job. If the error persists, perform a Partial Clean using the Preboot menu.32.1C.56 (event code) No action necessary.32.1C.57 (event code) No action necessary.32.1C.58 (event code) No action necessary.32.1C.60 (event code) No action necessary.32.1C.61 (event code) Review the error log to see specific details about the failure.32.1C.62 (event code) Review the error log to see specific details about the failure.32.1C.68 (event code) Check that a share was provided as part of the network path (not blank). Check that the server and the share exist. Check that the user has permission to access the share on the provided server. Check that the path includes the compressed (ZIP) file name as part of the path32.1C.69 (event code) Verify the encryption personal identification number (PIN) is the same PIN used to encrypt the backup file.32.1C.6A (event code) Retry the job.32.1C.6D (event code) Retry the job.
- Code: 33.02.01
- Description: Used board/disk installed Used board disk installed. An encrypted board or disk with existing data previously locked to a different product has replaced the original. If you continue, data is permanently lost.
- Remedy: 1. Reinstall the used board or disk back into its original printer. 2. To save the data on the board or disk, turn the product off. Replace the board or disk with another board or disk. 3. To delete the data on the board or disk and continue, touch the OK button.
- Code: 33.03.03
- Description: Incompatible formatter installed. This is and EFI BIOS event to prevent booting with the wrong formatter installed.
- Remedy: Power down the printer and install the correct formatter in the device. NOTE: If it is believed that the formatter is the correct part number and model for this printer, replace the formatter again and return the formatter in question to HP for evaluation.
- Code: 33.03.XX
- Description: • 33.03.01: Save recover engine storage ID unexpected length. • 33.03.02: Data size mismatch unable to recover DCC MVRAM.
- Remedy: Power the printer off then back on. If issue is not resolved replace the ICB and return to HP for evaluation.
- Code: 40.00.01
- Description: USB I/O buffer overflow To continue, touch “OK” The USB buffer has overflowed.
- Remedy: 1. Touch the OK button to print the transferred date (some data might be lost). 2. Check the host configuration.
- Code: 40.00.02
- Description: Embedded I/O buffer overflow To continue, touch “OK” The product has experienced a JetDirect buffer overflow.
- Remedy: 1. Touch the OK button to print the transferred date (some data might be lost).2. Check the host configuration.
- Code: 40.00.03
- Description: EIO <X> buffer overflow To continue, touch “OK” Too much data was sent to the EIO card in the specified slot (x). An incorrect communications protocol might be in use.
- Remedy: Touch the OK button to print the transferred date (some data might be lost).
- Code: 40.00.04
- Description: EIO <X> bad transmission To continue, touch “OK” The connection between the product and the USB device has been broken.
- Remedy: 1. Touch the OK button to clear the error message and continue printing.2. Remove, and then reinstall the USB device.
- Code: 40.00.05
- Description: Embedded I/O bad transmission To continue, touch “OK” The USB device has been removed.
- Remedy: 1. Touch the OK button to clear the error message (data will be lost).2. Install the USB device.
- Code: 40.08.0X
- Description: USB storage accessory removed X = 0 or 1; information code. Secure file erase is enabled.
- Remedy: No action necessary.
- Code: 40.0X.05
- Description: USB storage accessory removed X = 1, 2, 3, 5, or 6; information code. The USB storage accessory was removed.
- Remedy: No action necessary.
- Code: 41.03.YZ
- Description: Unexpected size in tray <X> The product detected a different paper size than expected. Y = Type, Z = Tray• Y = 0 Size mismatch. Detected media is longer or shorter than expected.• Y = A Size mismatch. Detected media too long.• Y = B Size mismatch. Detected media too short.• Y = C Size mismatch. Inter-page gap error.• Z = D Source is the duplexer.• Z = 1 Source is Tray 1.• Z = 2 Source is Tray 2.• Z = 3 Source is Tray 3.
- Remedy: 1. Touch OK to use another tray.2. Make sure that the tray is loaded with the correct paper size and that the sliding paper guides are correctly adjusted.3. Use the Tray/Bin manual sensor test to verify that the cassette media switch is correctly functioning.4. If the issue persists, replace the Mech kit.
- Code: 44.01.XX
- Description: Error Event log message (Multifunction product only.) A digital send error has occurred.
- Remedy: Try to send the job again. No action necessary. This error message should automatically clear.
- Code: 44.02.XX
- Description: Error Event log message (Multifunction product only.) Personal address book error has occurred.
- Remedy: Try to send the job again. Check Digital Send configuration and address book.
- Code: 44.03.XX
- Description: Error Event log message (Multifunction product only.) A digital send error has occurred.
- Remedy: Try to send the job again. Check the Digital Send configuration.
- Code: 44.04.XX
- Description: Error Event log message (Multifunction product only.) Digital Send Email error has occurred.
- Remedy: Try to send the job again. Check the Digital Send configuration.
- Code: 44.05.XX
- Description: Error Event log message (Multifunction product only.) Digital Send Folder Job error has occurred.
- Remedy: Try to send the job again. Check the Digital Send configuration.
- Code: 44.07.XX
- Description: Error Event log message (Multifunction product only.) Digital Send Remote Printer Job Error has occurred.
- Remedy: Try to send the job again. Check the Digital Send configuration.
- Code: 44.08.XX
- Description: Error Event log message (Multifunction product only.) SharePoint Job Error has occurred.
- Remedy: 1. If this is the first time the error has occurred, cancel and then restart the job.2. If the error occurs repeatedly, reboot the engine and retry the job.3. If error still persists, reset to factory settings. Upgrade to most current firmware.
- Code: 44.10.XX
- Description: Error Event log message (Multifunction product only.) A send to email error has occurred.
- Remedy: Try to send the job again. Check the Digital Send configuration.
- Code: 44.11.0E
- Description: Error Event log message (Multifunction product only.) The attachment filename already exists at the destination, and the flag to fail on filename collisions was set. This file will not be sent.
- Remedy: 1. If this is the first time the error has occurred, use a different filename or verify that the filename is not already in use.2. If the issue persists, use a unique filename or disable the flag to fail on filename collision.
- Code: 44.11.XX
- Description: Error Event log message (Multifunction product only.) A Digital Send error has occurred.
- Remedy: Try to send the job again. Check the Digital Send configuration.
- Code: 44.12.0E
- Description: Error Event log message (Multifunction product only.) Digital Send, the attachment filename already exists at the destination, and the flag to fail on filename collisions is set. This file will not be sent.
- Remedy: 1. If this is the first time the error has occurred, use a different filename or verify that the filename is not already in use.2. If the issue persists, use a unique filename or disable the flag to fail on filename collision.
- Code: 44.12.XX
- Description: Error Event log message (Multifunction product only.). A Digital Send error has occurred.
- Remedy: Recommended action Try to send the job again. Check the Digital Send configuration.
- Code: 44.16.01
- Description: Error Event log message (Multifunction product only.) A Digital Send error has occurred while trying to create file type. XX =• 01 . RTF File• 03 . CSV File• 04 . HTML File• 05 . XML File• 06 . XPS File• 07 . PDF File
- Remedy: 1. Try to send the job again.2. Check Digital Send configuration.
- Code: 44.16.02
- Description: Error Event log message (Multifunction product only.) The destination URL was found to be invalid or unreachable.
- Remedy: 1. If this is the first time the error has occurred, cancel and then restart the job.2. If the error persists, turn the product off and then on and retry the job.3. If error still persists, reset to factory settings. Upgrade to current version of firmware.
- Code: 44.16.03
- Description: Error Event log message (Multifunction product only.) The destination URL is not a SharePoint site.
- Remedy: 1. If this is the first time the error has occurred, verify settings in job configuration and then restart the job.2. If the error persists,• Check network connection settings.• Verify access to the SharePoint site.
- Code: 44.16.04
- Description: Error Event log message (Multifunction product only.) Credentials associated with the SharePoint destination were found to be invalid or missing.
- Remedy: 1. If this is the first time the error has occurred, verify settings in job configuration and then restart the job.2. If the error persists,• Check network connection settings.• Verify access to the SharePoint site.
- Code: 44.16.05
- Description: Error Event log message (Multifunction product only.) Credentials do not have write access to the SharePoint destination.
- Remedy: 1. If this is the first time the error has occurred, verify settings in job configuration and then restart the job.2. If the error persists,• Check network connection settings.• Verify access to the SharePoint site.
- Remedy: 1. If this is the first time the error has occurred, send fewer pages in the job, lower the DPI of the scanned pages, or select a file type that splits pages into separate files (for example, jpeg).2. If the error persists repeatedly, contact the SharePoint site administrator to increase the Web server’s maximum form submission length.
- Remedy: 1. If this is the first time the error has occurred, make space on the SharePoint site by deleting some files, and then retry the job.2. If the error occurs repeatedly, contact the SharePoint site administrator to increase the storage quota limit.
- Remedy: 1. If this is the first time the error has occurred, check the destination URL and filename in the SharePoint job configuration to verify no folder or filename exceeds the maximum of 128 characters.2. If the error occurs repeatedly, try sending to a different folder on the SharePoint site or changing the filename (which could include prefix or suffix).
- Remedy: 1. If this is the first time the error has occurred, verify that the filename used by the job is not checked out on the SharePoint site.2. If the error occurs persists, use a different filename for the job.
- Remedy: 1. If this is the first time the error has occurred, set the job to overwrite existing files.2. If the error occurs persists, use a different filename for the job.
- Code: 44.16.0D
- Description: Error Event log message (Multifunction product only.) Encountered an unexpected processing error while transferring attachments to the destination SharePoint.
- Remedy: 1. If this is the first time the error has occurred, verify settings in job configuration and restart the job.2. If the error persists, turn the product off, and then on and retry the job.3. If error continues, reset to factory settings. Upgrade to current version of firmware.
- Code: 44.16.0E
- Description: Error Event log message (Multifunction product only.) The attachment filename already exists at the destination, and the flag to fail on filename collisions was set. This file will not be sent.
- Remedy: 1. If this is the first time the error has occurred, use a different filename or verify that the filename is not already in use.2. If the issue persists, use a unique filename or disable the flag to fail on filename collision.
- Code: 44.16.0F
- Description: Error Event log message (Multifunction product only.) Not enough memory to process the current SharePoint Job.
- Remedy: 1. If this is the first time the error has occurred, cancel and/or restart the job, breaking it up into small jobs.2. Repeat this process if the error persists until job goes through.
- Code: 44.16.10
- Description: Error Event log message (Multifunction product only.) SharePoint server is using an invalid certificate.
- Remedy: 1. If this is the first time the error has occurred, send the SharePoint job to a non-secure address, or send the job to a SharePoint server that has a valid certificate.2. If the error occurs repeatedly, send the job to a different, trusted SharePoint server.
- Code: 44.16.FF
- Description: Error Event log message (Multifunction product only.) Unexpected error occurred in the SharePoint resource device code.
- Remedy: 1. If this is the first time the error has occurred, verify settings in job configuration and restart the job.2. If error persists, turn the product off, and then on and retry the job.3. If error continues, reset to factory settings. Upgrade to current version of firmware.
- Code: 44.34.XX
- Description: Error Event log message (Multifunction product only.) A fax error has occurred.
- Remedy: 1. Try to send the job again.2. Check the fax configuration
- Code: 44.90.XX, 44.91.XX, 44.92.XX
- Description: 44.90.XX Error Event log message – 44.91.XX Error Event log message – 44.92.XX Error Event log message (Multifunction product only.) A fax error has occurred.
- Remedy: 1. Try to send the job again.2. Check the fax configuration.
– Get more error code list with quick guide to fix printer product, https://nguyendangnam.com/error-code
– About get help with reseting Epson inkpad or others, https://nguyendangnam.com/reset-epson-inkpad
- Code: 45.00.YZ
- Description: Event log entry only All 45.00.YZ events are OXPd/Webkit informational log entries.
- Remedy: No action necessary.
- Code: 47.00.XX
- Description: Back channel internal error.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Code: 47.02.XX
- Description: Job parser internal error.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Code: 47.03.XX
- Description: Print job internal error.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Code: 47.04.XX
- Description: Print spooler 9100 internal error.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Code: 47.05.00
- Description: Print spooler framework internal error.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Code: 47.06.XX
- Description: Print application internal error.
- Remedy: 1. Turn the product off, and then on again.2. Resend the print job.3. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu.
- Remedy: 1. Turn the product off, and then on again.2. If the error persists over multiple power cycles frequently and consistently on a unit then do the following.• In the Administration/Troubleshooting/Diagnostics, run the hard disk tests to validate health of the device. Fix any issue found with the mass storage device3. If the error persists, reload the firmware.4. If the error persists, clear the active partition by using the Partial Clean item in the Preboot menu then reload the firmware.
- Code: 48.XX.YY
- Description: A job framework internal error has occurred.
- Remedy: 1. No action should be necessary.2. If the error persists, upgrade the product firmware.3. If the issue persists, continue troubleshooting with the flowcharts for either Intermittent or Persistent 49 error troubleshooting (whichever is appropriate) in document c03122817, “HP LaserJet FutureSmart Devices – 49 Error Troubleshooting (Persistent and Intermittent)”.
- Code: 49.XX.YY
- Description: Error To continue turn off then on A firmware error occurred. Corrupted print jobs, software application issues, non-product specific print drivers, poor quality USB or network cables, bad network connections or incorrect configurations, invalid firmware operations, or unsupported accessories can cause this error.
- Remedy: 1. Turn the product off, and then on. 2. If the error persists, check the following: • The error might be caused by a network connectivity problem, such as a bad interface cable, a bad USB port, or an invalid network configuration setting. • The error might be caused by the print job, due to an invalid print driver, a problem with the software application, or a problem with the file being printed. • Upgrading the product firmware might help resolve the error. See the product user guide for more information. When a 49 error occurs, the user sees a 49.XXXX message on the control panel (where XXXX is replaced by a combination of letters and numbers). A 49 error might happen at any time for multiple reasons. Although some types of 49 errors can be caused by hardware failures, it is more common for 49 errors to be caused by printing a specific document or performing some task on the product. 49 errors most often occur when a product is asked to perform an action that the product firmware is not capable of and might not have been designed to comply with, such as: • Printing files with unsupported programming commands • A unique combination of user environment and user interactions with the product • Interfacing with a third-party solution that was not designed to work with the product • Specific timing, network traffic, or concurrent processing of jobs Each of these interactions could cause the product firmware to initiate an action that the product cannot accomplish. In situations like this, the product might present the error if it has no other option. When these errors occur, the only way to recover is to turn the product’s power off and back on. NOTE: LaserJet formatter PCAs are rarely the root cause of 49 service errors. Please do not replace the formatter or flash unless troubleshooting has identified the formatter as the root cause. If the error persists, continue troubleshooting with the flowcharts for either Intermittent or Persistent 49 error troubleshooting (whichever is appropriate) in document c03122817, gHP LaserJet FutureSmart Devices – 49 Error Troubleshooting (Persistent and Intermittent).
- Code: 54.30.00
- Description: Calibration error An engine calibration has failed. Details of which calibration and failure reason can be found in the payload. 610000AC Sensor_Cms_Calibrate_Unknown_Sensor Tried to start a page calibration scan with an unknown sensor ID. Only Zim and BDD sensors are recognized. 610000AD Sensor_Cms_Calibrate_Invalid_Sensor A sensor other than Zim was specified for the pen calibration scan. 610000AE Sensor_Cms_Calibrate_Overshoot The paper advanced too far during a page calibration such that the printed artifact could not be scanned. This assert could happen if the mech wasn’t able to stop the paper movement accurately.
- Remedy: 1. Turn the power off on the product by pressing the power button and holding it for more than 3 seconds. 2. Unplug power cord from back of product and wait 30 seconds. 3. Plug power cord back into product. 4. Turn the power on to the product using power button. 5. If the error condition is cleared then the issue is resolved, if not continue to step 6. 6. Repeat steps 1 & 2. 7. Remove the formatter, check formatter thoroughly for any loose connections and reseat them, then reinstall the formatter. 8. Repeat steps 3 & 4. 9. If the error condition is cleared then the issue is resolved, if issue is not resolved replace the Mech Kit. NOTE: It is critical to either print the event log after power cycle clears issue, or access the event log through EWS and capture the 8 character fail code value corresponding to the 61.00.0X and log it into the case. Look for the last 61.00.0x error that occurred which also has the 8 character value under the text . This value is critical in HP understanding the failure and debugging potential field issues.
- Code: 58.10.02
- Description: Ink Sensor Failure SHAID electrical failure.
- Remedy: 1. Turn the power off on the product by pressing the power button and holding it for more than 3 seconds. 2. Unplug power cord from back of product and wait 30 seconds. 3. Plug power cord back into product. 4. Turn the power on to the product using power button. 5. If the error condition is cleared then the issue is resolved, if not continue to step 6. 6. Repeat steps 1 & 2. 7. Remove the formatter, check formatter thoroughly for any loose connections and reseat them, then reinstall the formatter.8. Repeat steps 3 & 4.9. If the error condition is cleared then the issue is resolved, if issue is not resolved replace the Mech Kit.
- Code: 61.00.01
- Description: Print Engine Error 61.00.02 Print Engine Error 61.00.03 Print Engine Error The print engine has encountered an error. The payload data will be included which will be with the error code, and string. Service_Station_Cap_Home_Long (6100000D) Paper_Load_Tray1_Pick_Motor (6100002D) Paper_Load_Pick_Tire_Index_Sensor (6100002E) Service_Station_Cap_Home_Short (6100000E) SS_Restricted_Movement_Error (61000011) Lift_Restricted_Movement_Error (61000012) Carriage_Restricted_Movement_Error (61000013) Service_Move_To_Tranny_State (610000C8) DPU_Printbar_Crash_Into_Service_Station (610000D3) DPU_Service_Station_Under_Print_Bar (610000D4) Printbar_Clutch_Slippage (61000035) Service_Station_Pen_Too_Cold (6100000B) Service_Station_Home_Failure (6100000C) Service_Carriage_Home_Invalid (610000C9) Pen_Start_Up_Spits_Already_Done (6100004E)
- Remedy: 1. Turn the power off on the product by pressing the power button and holding it for more than 3 seconds.2. Unplug power cord from back of product and wait 30 seconds.3. Plug power cord back into product. 4. Turn the power on to the product using power button. 5. If the error condition is cleared then the issue is resolved, if not continue to step 6. 6. Repeat steps 1 & 2. 7. Remove the formatter, check formatter thoroughly for any loose connections and reseat them, then reinstall the formatter. 8. Repeat steps 3 & 4. 9. If the error condition is cleared then the issue is resolved, if issue is not resolved replace the Mech Kit. NOTE: It is critical to either print the event log after power cycle clears issue, or access the event log through EWS and capture the 8 character fail code value corresponding to the 61.00.0X and log it into the case. Look for the last 61.00.0x error that occurred which also has the 8 character value under the text . This value is critical in HP understanding the failure and debugging potential field issues.
- Code: 81.WX.00
- Description: Wireless Network Error To continue turn off then on A wireless network component on the product has failed. 81.02.00 Wireless network Event 81.07.00 Internal Wireless Networking event
- Remedy: 1. Turn the product off then on. 2. Turn the product off, reseat the wireless network component and turn the product back on. 3. If error persists, replace the wireless network component.
- Code: 81.WX.YZ
- Description: Embedded Jetdirect Error To continue turn off then on The product experienced an embedded HP Jetdirect print server critical error. 81.01.00 EIO Event 81.03.00 Access Point Wireless Network event 81.04.00 JetDirect inside Network event 81.06.00 Internal EIO Networking event 81.08.00 Internal Access Point Wireless Network event 81.09.00 Internal JetDirect inside Network event
- Remedy: 1. Turn the product off then on.2. Turn the product off, reseat the EIO accessory and turn the product back on.3. If error persists replace the formatter.
- Code: 82.73.45
- Description: Disk Successfully cleaned. Event log only, disk successfully cleaned.
- Remedy: No action necessary.
- Code: 82.73.46, 82.73.47
- Description: A hard disk or compact flash disk cleaning failed. This error is usually caused by a failure of the disk hardware.
- Remedy: 1. Turn the product off, and then on.2. Use the Clean Disk item in the Preboot menu.3. Reload the firmware.
- Code: 98.00.01, 98.01.00
- Description: Corrupt data in firmware volume Data corrupt has occurred in the firmware volume.
- Remedy: 1. Turn the product off, and then on.2. Use the Clean Disk item in the Preboot menu.3. Reload the firmware.
- Code: 98.00.02
- Description: Corrupt data in the solutions volume Data corruption has occurred in the solutions volume.
- Remedy: 1. Turn the product off, and then on.2. Use the Clean Disk item in the Preboot menu.3. Reload the firmware.
- Code: 98.00.03
- Description: Corrupt data in the configuration volume Data corrupt has occurred in the configuration volume.
- Remedy: 1. Turn the product off, and then on.2. Download the firmware again, and then attempt the upgrade again.3. Use the Clean Disk item in the Preboot menu.4. Reload the firmware.
- Code: 98.00.04
- Description: Corrupt data in the job data volume Data corrupt has occurred in the job data volume.
- Remedy: 1. Turn the product off, and then on.2. Rerun the file erase function.
- Remedy: Download the RFU file, and then attempt the upgrade again.
- Code: 99.00.02
- Description: Upgrade not performed timeout during receive A remote firmware upgrade (RFU) was not performed. The issue is an I/O timeout when reading the header number and size. It indicates a problem with the network environment, not the product.
- Remedy: The most common cause is an issue with the network environment. Make sure that there is a good network connection to the product, and then attempt the firmware upgrade again, or upgrade using the USB walk-up port.
- Code: 99.00.03
- Description: Upgrade not performed error writing to disk A remote firmware upgrade (RFU) was not performed. This is a disk error. It might indicate a problem or a hard disk failure. It might be necessary to check the connection to the hard disk or replace the hard disk.
- Remedy: 1. Download the RFU file, and then attempt the upgrade again.2. If the error persists, run the Clean Disk process from the Preboot menu. You will need to download the firmware from the Preboot menu.3. If the error persists, replace the hard disk.
- Code: 99.00.04
- Description: Upgrade not performed timeout during receive A remote firmware upgrade (RFU) was not performed. The issue is an I/O timeout when reading the header.
- Remedy: The most common cause is an issue with the network environment. Make sure that there is a good network connection to the product, and then attempt the firmware upgrade again, or upgrade using the USB walk-up port.
- Remedy: The most common cause is an issue with the network environment. Make sure that there is a good network connection to the product, and then attempt the firmware upgrade again, or upgrade using the USB walk-up port.
- Code: 99.00.06
- Description: Upgrade not performed error reading upgrade A remote firmware upgrade (RFU) was not performed. The issue is an unexpected read error when reading the header number and size.
- Remedy: 1. Download the RFU file, and then attempt the upgrade again.2. If the error persists, replace the hard disk.
- Code: 99.00.07
- Description: Upgrade not performed error reading upgrade A remote firmware upgrade (RFU) was not performed. The issue is an unexpected read error when reading the rest of the header.
- Remedy: 1. Download the RFU file, and then attempt the upgrade again.2. If the error persists, replace the hard disk.
- Remedy: 1. Download the RFU file, and then attempt the upgrade again.2. If the error persists, replace the hard disk.
- Code: 99.00.09
- Description: Upgrade canceled by user A remote firmware upgrade (RFU) was not performed. The RFU was canceled by the user.
- Remedy: Resend the RFU.
- Code: 99.00.10
- Description: Upgrade canceled by user A remote firmware upgrade (RFU) was not performed. The RFU was canceled by the user when reading the header number and size.
- Remedy: Resend the RFU.
- Code: 99.00.11
- Description: Upgrade canceled by user A remote firmware upgrade (RFU) was not performed. The RFU was canceled by the user when reading the rest of the header.
- Remedy: Resend the RFU.
- Code: 99.00.12
- Description: Upgrade not performed the file is invalid A remote firmware upgrade (RFU) was not performed. The header number is 1, but the header size does not match version 1 size.
- Remedy: Download the RFU file again. Make sure that you download the file for the correct product model, and then resend the RFU.
- Code: 99.00.13
- Description: Upgrade not performed the file is invalid A remote firmware upgrade (RFU) was not performed. The header number is 2, but the header size does not match version 2 size.
- Remedy: Download the RFU file again. Make sure that you download the file for the correct product model, and then resend the RFU.
- Code: 99.00.14
- Description: Upgrade not performed the file is invalid A remote firmware upgrade (RFU) was not performed. The file is invalid.
- Remedy: Download the RFU file again. Make sure that you download the file for the correct product model, and then resend the RFU.
- Code: 99.00.2X
- Description: There is a compatibility issue with the firmware. The specific message varies depending on the cause, but the solution for each message is the same. •99.00.20 (event log) The bundle is not for this product.•99.00.21 (event log) The bundle is not signed with the correct signature, or the signature is invalid.•99.00.22 (event log) The bundle header version is not supported by this firmware.•99.00.23 (event log) The package header version is not supported by this firmware.•99.00.24 (event log) The format of the bundle is invalid.•99.00.25 (event log) The format of the package is invalid.•99.00.26 (event log) A CRC32 check did not pass.•99.00.27 (event log) An I/O error occurred while downloading the bundle.
- Remedy: 99.00.27 only:1. Turn the product off, and then on.2. Resend the firmware upgrade.3. If the error persists, try installing the upgrade by another method (USB or Embedded Web Server).
- Code: 99.01.XX
- Description: A firmware install error has occurred. The specific message varies depending on the cause, but the solution for each message is the same.•99.01.00•99.01.10•99.01.20•99.01.21
- Remedy: Reload the firmware.
- Code: 99.02.01
- Description: Firmware installation was successful.
- Remedy: No action necessary.
- Code: 99.02.09
- Description: Firmware upgrade cancelled by user.
- Remedy: No action necessary.
- Code: 99.09.60
- Description: Unsupported disk This is a Preboot menu error. The hard disk currently installed is not recognized or supported by the product.
- Remedy: Install the correct hard disk for this product.
- Code: 99.09.61
- Description: Unsupported disk This is a Preboot menu error. The installed disk is installed in a product configured for an encrypted hard disk.
- Remedy: Access the Preboot menu, and then select Lock Disk to lock the disk.
- Code: 99.09.62
- Description: Unknown disk This error indicates that there is an encryption mismatch between the HDD and the formatter. This typically happens because an HDD was swapped into a device from another device.
- Remedy: Install a new disk or use the Preboot menu unlock the disk. If a disk is to be reused in a different product, execute the Clean Disk procedure from the Preboot, and then reload the firmware and lock the disk.
- Code: 99.09.63
- Description: Incorrect disk This error indicates that the expected encrypted HDD is not present. This is expected behavior when installing a new HDD in a device where the previous HDD was encrypted.
- Remedy: Follow the procedure to load firmware on a new hard disk, and then lock the disk to this product.
- Code: 99.09.64
- Description: Disk malfunction A fatal hard disk failure has occurred.
- Remedy: Replace the hard disk.
- Code: 99.09.65
- Description: Disk data error Disk data corruption has occurred.
- Remedy: Use the Clean Disk procedure from the Preboot menu, and then resend the RFU.
- Code: 99.09.66
- Description: No disk installed A disk drive is not installed in the product.
- Remedy: 1. Install a compatible hard disk drive.2. If a compatible hard disk is installed, reseat the hard disk to make sure that it is connected correctly.3. If the error persists, replace the hard disk drive.
- Code: 99.09.67
- Description: Disk is not bootable please download firmware This is an error indicating that there is no firmware installed on the disk. This is usually the result of installing a new disk or performing a Clean Disk operation from the Preboot menu.
- Remedy: 1. Press any button to continue to the main Preboot menu.2. Press the Help button to see the help text for the error.3. Select the Administration menu. NOTE: If there is a password assigned to the administrator, a prompt to enter the product displays. Enter the password to proceed. 4. Select the Download item, and then download the latest firmware. The user can now download a new firmware bundle to the product.
- Code: 99.XX.YY
- Description: A message of this form indicates a firmware installation error.
- Remedy: Reload the firmware.
– Get more information about Epson XP 15000 troubleshooting, https://nguyendangnam.com/troubleshooting
– Buy cheap key of Epson WIC Reset Tool, https://shop.nguyendangnam.com/product-category/wic-reset/
– Key Epson Adjustment Program, https://shop.nguyendangnam.com/product-category/adjustment-program/
https://dnasofts.com/download-epson-xp-6100-driver-firmware-and-manuals/
Contact us to get support with HP PageWide Enterprise Color 556 Error case
Telegram: https://t.me/hyperaktiv
Facebook: https://www.facebook.com/dngnm/
Source:
https://dnasofts.com
https://shop.nguyendangnam.com/
https://nguyendangnam.me/