304-Keyboard or System Unit Error audible beeps: none
possible cause: keyboard, keyboard cable, mouse controller, or system board failure. action:
1. be sure the keyboard and mouse are connected.
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. 2. run insight diagnostics (\as indicated. 400 series list of messages:
40x-parallel port x address assignment conflict 404-parallel port address conflict detected 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:
1. if you have recently added new hardware, remove it to see if the hardware is the cause of the conflict.
2.run the server setup utility to reassign resources for the parallel port and manually resolve the resource conflict.
3. run insight diagnostics (\
as indicated. 600 series list of messages:
601-diskette controller error 602-diskette boot record error 605-diskette drive type error
611-primary floppy port address assignment conflict 612-secondary floppy port address assignment conflict 601-diskette controller error audible beeps: none
possible cause: diskette controller circuitry failure occurred. action:
1. be sure the diskette drive cables are connected. 2. replace the diskette drive, the cable, or both.
3. run insight diagnostics (\as indicated.
602-diskette boot record error audible beeps: none
possible cause: the boot sector on the boot disk is corrupt. action:
1. remove the diskette from the diskette drive. 2. replace the diskette in the drive. 3. reformat the diskette. 605-diskette drive type error. audible beeps: 2 short
possible cause: mismatch in drive type occurred.
action: run the server setup utility to set the diskette drive type correctly. 611-primary floppy port address assignment conflict audible beeps: 2 short
possible cause: a hardware conflict in the system is preventing the diskette drive from
operating properly. action:
1. run the server setup utility to configure the diskette drive port address and manually resolve the conflict.
2. run insight diagnostics (\as indicated.
612-secondary floppy port address assignment conflict audible beeps: 2 short
possible cause: a hardware conflict in the system is preventing the diskette drive from operating properly. action:
1. run the server setup utility to configure the diskette drive port address and manually resolve the conflict.
2. run insight diagnostics (\as indicated. 1100 series list of messages:
1151-com port 1 address assignment conflict 1151-com port 1 address assignment conflict audible beeps: 2 short
possible cause: both external and internal serial ports are assigned to com x. action: run the server setup utility and correct the configuration. 1600 series list of messages:
1609 - the server may have a failed system battery. some
1610-temperature violation detected. - waiting 5 minutes for system to cool 1611-cpu zone fan assembly failure detected. either 1611-cpu zone fan assembly failure detected. single fan 1611-fan failure detected
1611-fan x failure detected (fan zone cpu)
1611-fan x failure detected (fan zone i/o) 1611-fan x not present (fan zonecpu) 1611-fan x not present (fan zone i/o)
1611- power supply zone fan assembly failure detected. either 1611-power supply zone fan assembly failure detected. single fan 1611-primary fan failure (fan zone system) 1611-redundant fan failure (fan zone system) 1612-primary power supply failure 1615-power supply configuration error 1615-power supply configuration error
1615-power supply failure, power supply unplugged, or power supply fan failure in bay x 1616-power supply configuration failure
1609 - the server may have a failed system battery. some...
...configuration settings may have been lost and restored to defaults. refer to server documentation for more information. if you have just replaced the system battery, disregard this message.
audible beeps: none
possible cause: real-time clock system battery has lost power. the system will lose its configuration every time ac power is removed (when the system is unplugged from ac power source) and this message displays again if a battery failure has occurred. however, the system will function and retain configuration settings if the system is connected to the ac power source. action: replace battery (or add external battery).
1610-temperature violation detected. - waiting 5 minutes for system to cool audible beeps: none
possible cause: the ambient system temperature exceeded acceptable levels. action: lower the room temperature.
1611-cpu zone fan assembly failure detected. either...
...the assembly is not installed or multiple fans have failed in the cpu zone. audible beeps: none
possible cause: required fans are missing or not spinning.
action:
1. check the fans to be sure they are installed and working.
2. be sure the assembly is properly connected and each fan is properly seated. 3. if the problem persists, replace the failed fans.
4. if a known working replacement fan is not spinning, replace the assembly. 1611-cpu zone fan assembly failure detected. single fan... ...failure. assembly will provide adequate cooling. audible beeps: none
possible cause: required fan not spinning.
action: replace the failed fan to provide redundancy, if applicable. 1611-fan failure detected audible beeps: 2 short
possible cause: required fan not installed or spinning. action:
1. check the fans to be sure they are working.
2. be sure each fan cable is properly connected and each fan is properly seated. 3. if the problem persists, replace the failed fans. 1611-fan x failure detected (fan zone cpu) audible beeps: 2 short
possible cause: required fan not installed or spinning. action:
1. check the fans to be sure they are working.
2. be sure each fan cable is properly connected, if applicable, and each fan is properly seated. 3. if the problem persists, replace the failed fans. 1611-fan x failure detected (fan zone i/o) audible beeps: 2 short
possible cause: required fan not installed or spinning. action:
1. check the fans to be sure they are working.
2. be sure each fan cable is properly connected, if applicable, and each fan is properly seated.