400 Series - HP ProLight Server Troubleshooting Manual

303-Keyboard Controller Error
Audible Beeps: None
Possible Cause: System board, keyboard, or mouse controller failure occurred.
Action:
Be sure the keyboard and mouse are connected.
1.
CAUTION: Only authorized technicians trained by HP should attempt to remove the system board. If you
believe the system board requires replacement, contact HP Technical Support before proceeding.
Run Insight Diagnostics
2.
indicated.
304-Keyboard or System Unit Error
Audible Beeps: None
Possible Cause: Keyboard, keyboard cable, mouse controller, or system board failure.
Action:
Be sure the keyboard and mouse are connected.
1.
CAUTION: Only authorized technicians trained by HP should attempt to remove the system board. If you
believe the system board requires replacement, contact HP Technical Support before proceeding.
Run Insight Diagnostics
2.
indicated.

400 Series

40X-Parallel Port X Address Assignment Conflict
Audible Beeps: 2 short
Possible Cause: Both external and internal ports are assigned to parallel port X.
Action: Run the server setup utility and correct the configuration.
404-Parallel Port Address Conflict Detected...
...A hardware conflict in your system is keeping some system components from working correctly. If you have
recently added new hardware remove it to see if it is the cause of the conflict. Alternatively, use Computer Setup or
your operating system to insure that no conflicts exist.
Audible Beeps: 2 short
Possible Cause: A hardware conflict in the system is preventing the parallel port from working
correctly.
Action:
If you have recently added new hardware, remove it to see if the hardware is the cause of the
1.
conflict.
Run the server setup utility to reassign resources for the parallel port and manually resolve the
2.
resource conflict.
Run Insight Diagnostics
3.
indicated.
("HP Insight Diagnostics" on page 61) and replace failed components as
("HP Insight Diagnostics" on page 61) and replace failed components as
("HP Insight Diagnostics" on page 61) and replace failed components as
Error messages 107