These troubleshooting steps can help to resolve the most common issues.

1. Confirm that all the cables required for the Fiery server 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 server hardware. The parts inside the chassis and internal cables are intended to be serviced by authorized service technicians only.
2. If the Fiery server cannot power on, confirm that the power cord is intact and adequate power is available at the power outlet.
3. If the Fiery server is not visible on the network, confirm that the correct type of Ethernet cable is connected to the correct network port.
4. If the Fiery server is printing slowly or is not managing jobs as expected, review the Fiery server 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 server configuration.
5. Confirm that third-party applications are not installed on the Fiery server.

   Third-party applications are not supported on the Fiery server and can cause system problems. This includes multimedia messaging service (MMS) applications (they can be installed on client computers or on the network).

6. Confirm that any anti-virus application used to scan the Fiery server is set to run upon request only, and is not in continuous operation.
7. Confirm that the operating system settings on the Fiery server 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.
8. Confirm that the Windows firewall has not been disabled.
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.
11. You can use the Preflight option to check for errors. For more information, see Fiery Command WorkStation Help.
12. Reboot the Fiery server. If the Fiery server does not reach the Idle state or any other issues remain, collect the related information and contact technical support.