Cause
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 time or when accessing the Network Configuration section of the front panel.
●
In both cases, repeating the action with the LAN cable disconnected does not cause the 79:04 to occur.
Solution
In the majority of cases, these issues will be due to an issue in the printer’s firmware. As soon as the
conditions in which 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.
1. Disconnect the network cable to be able to start the printer and change network settings.
2. In the Network configuration menu in the Front Panel, disable any protocols that you are not using,
including IPv6, SNMP and WebServices.
3. If step 2 does not work, try configuring the printer manually.
a. Enter the correct subnet mask and an IP address in the valid range.
b. In the Gateway field, set the same value as in the IP address field.
c. Do not set a host name or a domain name.
4. If step 3 does not work and the customer is using the network card built into the printer, try using an
accessory Jetdirect card instead.
User-interaction-related SE 79:04
In some cases the printer may not react as expected when a certain set of conditions coincide. In these cases,
if the printer doesn’t know how to react, it may simply display a 79:04 system error and force a restart. Here
are some examples (not real) that may help to illustrate this.
●
An error occurs when a job is cancelled when it is at the “Finishing print” state and when the queue is
disabled.
●
An error occurs if the Window is opened while the printer is checking the printheads.
These errors will probably happen only in very specific corner cases that have not been identified during the
development or the qualification of the printer. Therefore they do not normally impact the customer
severely, as they do not affect their usual workflows.
Cause
The symptoms here are as numerous as the number of possible interactions between the user and the
printer. In any case, it’s possible to identify the steps that caused the error to occur and avoid them as the
steps will always be the same with no variance.
Solution
First identify the state the printer was in at the time the error was displayed. For example, an action taken
when the printer is drying can produce an error, whereas the same action when the printer is doing
something else (or is idle) may not produce any error.
When you have identified the steps that caused the error, proceed as follows.
28 Chapter 2 Troubleshooting ENWW
To Next Page
Loading...