System Error Codes

cThe printer can reboot normally

dWhen the data is accessed again (typically, under the same conditions as in step “b”), the 79:04 system error is displayed again

Solutions and workarounds

Many times, data related 79:04 errors are resolved by means of hardware intervention. Since data is stored in physical components (RAM, EEROM and Hard Disk), replacing these components with new ones which are empty usually solves the problem. However, there are quicker and more effective solutions to these types of errors:

1Clear all information that has been introduced by the user using the standard tools available in the printer:

a Delete all jobs from the queue (from the Front Panel or the EWS)

b Reset to factory defaults to clear the user’s configurations and calibrations

a Delete any non standard paper preset in the printer (both the ones that have been created by the user and the ones that have been installed as OMES profiles through the EWS or the HP Printer Utility)

2If step 1 did not resolve the issue, you can use Service Tools to clear additional information that could be causing the issue:

a Start the printer in Diagnostics Boot Mode b Perform an EEROM reset

3If step 2 did not resolve the issue, it is possible to completely clear the information on the Hard Disk and the different EEROMs, leaving them in an equivalent state to a new part:

a Access the Service Utilities Menu

b In the Secure Disk Wipe menu, set the Sanitize level to “Unsecure mode”

c Execute the Disk Wipe. This takes 45-75 minutes and it will completely clear all partitions in the Hard Disk which contain user data, including the partition where the Operating System is installed. After the disk wipe has completed, a backup firmware version will automatically be installed from a backup partition to allow the unit to start up. This firmware version is very old.

d The firmware in the printer should be upgraded to the latest official version as soon as the printer has restarted.

After step “c”, any 79:04 which is caused by corrupt data in the printer will be solved.

Important note:

It is possible that the corrupt data came to be in the printer as a consequence of some activity in the customer’s workflow. In this case, it is possible that the issue will happen again. In these cases, it is very important to understand the sequence of events in the customer’s workflow that led to the error occurring. Once the error can be traced in the customer’s workflow, escalate the issue to the GBU (through the GCC). This is done to implement any changes in the printer’s firmware that can prevent these issues occurring again.

2-36

HP Designjet T Series — Service Manual