Troubleshooting c. 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) 2. If 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 3. If 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. Network related SE79:04 Most HP Designjet printers have built-in networking capabilities.
Network settings can be set manually, but in the majority of cases, they are obtained automatically from the printer. These settings include many different fields, such as IP address and subnet mask, available gateways, host and domain names, etc. In some cases, there can be issues in the firmware that can cause a certain value in one of these fields to be interpreted incorrectly, and this can lead to a 79:04 system error. Symptoms There is no single set of symptoms that can absolutely pinpoint a network related 79:04 system error. However, the following guidelines can be applied:
• It can happen at start up or when accessing the Network Configuration section of the FP • In both cases, repeating the action with the LAN cable disconnected does not cause the 79:04 to occur Solutions and workarounds In the majority of cases, these issues will be due to an issue in the printer’s firmware. As soon as the conditions where the issue happens can be understood, it should be escalated to the GBU through the GCC. At the same time, the following short term solutions and workarounds can help the customer to get up and running in the shortest possible time: 34 Chapter 1 Troubleshooting