in these cases. These random issues tend to occur in very specific corner cases, and cannot be
reproduced unless the exact conditions of the workflow are replicated. They normally happen when
sending files generated by external applications (RIPs, third-party drivers, and so on).
Solution
Random 79:04 errors are, by far, the most complex ones to diagnose and to fix. The only solutions available
in these cases are as follows.
1. Identify the root cause (either in the files or in the firmware) and fix it in the code, which requires the
intervention of the GBU.
2. Test any options available to modify the customer’s workflow and see if any combination of them
solves the issue.
In both cases, a profound understanding of the customer’s workflow is necessary. The following information
should be obtained.
●
The front-panel settings
●
The application, and the RIP or driver that are being used
●
The application/RIP/driver settings
●
The type of output files that this application, RIP or driver is generating
●
Some sample files that are representative of what the customer is using
●
The operating system
●
The method of connection to the printer
●
A description of the normal flow when the issue occurs and the typical frequency of occurrence (for
instance, once every hour when sending several files non-stop, each of them with multiple copies)
With this information, the environment can be replicated in order to try to find workarounds. This is also the
information that will be needed at the GBU to investigate and fix the root cause of this issue once it is
escalated.
Hardware-related SE 79:04
Hardware is, by far, the least likely cause of a 79:04 system error. Replacing hardware components does not
normally fix the issue and increases the total turnaround time in finding a workable solution.
In some cases, a failure in a component in the printer’s electronics may cause a 79:04 system error, since the
printer’s electronics are involved in the execution of the firmware and the processing of jobs. However,
hardware failures in the electronics tend to produce specific system errors that point directly to the
component that is failing.
Some hardware causes that could be behind a 79:04 error are as follows.
●
Defective clusters on the hard disk. If these clusters are used to execute the firmware or to process a
job, they may produce a 79:04 error. However, most 79:04 errors that are solved by a hard disk
replacement are in fact, data-related 79:04 errors that could have been solved more efficiently and
quickly by following the recommendations for such an error.
●
Defective memory segments. If the RAM memory has some defective segments, a 79:04 error may
occur when these segments are used.
●
Intermittent defects in the electronic components that are involved in the processing of a job: Carriage
PCA, Trailing Cable, Formatter and PrintMech PCA. This is a highly unlikely cause, since defects in these
components will produce subsystem-specific errors.
30 Chapter 2 Troubleshooting ENWW