Troubleshooting
Startup diagnostics are described in the documentation for service technicians. Contact your authorized service/
support center if you see startup error messages on Command WorkStation or if the Fiery ES does not reach the Idle
state.
Perform basic troubleshooting
These troubleshooting steps can help to resolve the most common issues.
1
Confirm that all the cables required for the Fiery ES are intact and firmly seated in the correct ports.
The most common cause of an issue is a faulty or loose cable.
Warning: Do not remove the covers or otherwise open the Fiery ES hardware. The parts inside the chassis
and internal cables are intended to be serviced by authorized service technicians only.
2
If the Fiery ES cannot power on, confirm that the power cord is intact and adequate power is available at the
power outlet.
3
If the Fiery ES is not visible on the network, confirm that the correct type of Ethernet cable is connected to the
correct network port.
4
Confirm that the Fiery logo is showing on the printer control panel. If not, check the status of the Fiery ES and
the cable connection to the printer.
5
Review any messages showing on the printer control panel.
6
If one or more client computers cannot print to the Fiery ES, confirm that the client computers have the correct
version of the Fiery ES printer driver and utilities installed.
For information about installing the printer driver, see Printing. For information about installing the utilities, see
Utilities.
7
If the Fiery ES is printing slowly or is not managing jobs as expected, review the Fiery ES configuration to confirm
the settings are optimal for your network and print environment.
Any changes to your network environment or workflow may require changes to the Fiery ES configuration.
8
Confirm that the operating system settings on the Fiery ES are not modified and the operating system is not
upgraded (unless approved by technical support).
Changes to the operating system settings or version can cause system problems.
9
Review any error messages showing in the Command WorkStation Servers list.
10
Take a screenshot of the Command WorkStation display and any error messages, then close and reopen
Command WorkStation. If any error messages display when it restarts, contact technical support.
Configuration and Setup
Troubleshooting
37
To Next Page
Loading...
