Intel SR1530CL User Guide - Page 135

Problems with Application Software that Ran Correctly

Page 135 highlights

Problems with Application Software that Ran Correctly Earlier Problems that occur after the system hardware and software have been running correctly sometimes indicate equipment failure. However, they can also be caused by file corruption or changes to the software configuration. Check the following: • If you are running the software from a CD-ROM or DVD-ROM, try a different disk. • Check your system for a virus infection. • Uninstall and reinstall the software. Make sure all necessary files are installed. • If the problems are intermittent, there may be a loose cable, dirt in the keyboard (if keyboard input is incorrect), a marginal power supply, or other random component failures. • If you suspect that a transient voltage spike, power outage, or brownout might have occurred, reload the software and try running it again. Symptoms of voltage spikes include a flickering video display, unexpected system reboots, and the system not responding to user commands. Note: Random errors in data files: If you are getting random errors in your data files, they may be getting corrupted by voltage spikes on your power line. If you are experiencing any of the above symptoms that might indicate voltage spikes on the power line, you may want to install a surge suppressor between the power outlet and the system power cord. Devices are not Recognized under Device Manager (Microsoft Windows* Operating System) The Microsoft Windows* operating systems do not include all of the drivers for the Intel® chipsets, onboard NICs, and other components. See "Server System References" on page ix for a link to the current drivers and chipset files. Hard Drive(s) are not Recognized Check the following: • Make sure the drive is not disabled in BIOS Setup. • Make sure the drive is connected correctly and that is plugged into the power supply. • Make sure the drive is compatible. See "Server System References" on page ix for a link to the tested drives. • Make sure you have not exceeded the power budget for the server. See "Server System References" on page ix for a link to software to check your power budget. • If using ATA drives, verify that the master/slave settings are set correctly. See your drive documentation for details on setting the master/slave settings. Server System User Guide 113

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194

Server System User Guide
113
Problems with Application Software that Ran Correctly
Earlier
Problems that occur after the system hardware and software have been running correctly
sometimes indicate equipment failure. However, they can also be caused by file
corruption or changes to the software configuration.
Check the following:
If you are running the software from a CD-ROM or DVD-ROM, try a different disk.
Check your system for a virus infection.
Uninstall and reinstall the software. Make sure all necessary files are installed.
If the problems are intermittent, there may be a loose cable, dirt in the keyboard (if
keyboard input is incorrect), a marginal power supply, or other random component
failures.
If you suspect that a transient voltage spike, power outage, or brownout might have
occurred, reload the software and try running it again. Symptoms of voltage spikes
include a flickering video display, unexpected system reboots, and the system not
responding to user commands.
Note:
Random errors in data files: If you are getting random errors in your data files, they may
be getting corrupted by voltage spikes on your power line. If you are experiencing any of
the above symptoms that might indicate voltage spikes on the power line, you may want to
install a surge suppressor between the power outlet and the system power cord.
Devices are not Recognized under Device Manager
(Microsoft Windows* Operating System)
The Microsoft Windows* operating systems do not include all of the drivers for the Intel
®
chipsets, onboard NICs, and other components. See
“Server System References” on
page ix
for a link to the current drivers and chipset files.
Hard Drive(s) are not Recognized
Check the following:
Make sure the drive is not disabled in BIOS Setup.
Make sure the drive is connected correctly and that is plugged into the power supply.
Make sure the drive is compatible. See
“Server System References” on page ix
for a
link to the tested drives.
Make sure you have not exceeded the power budget for the server. See
“Server
System References” on page ix
for a link to software to check your power budget.
If using ATA drives, verify that the master/slave settings are set correctly. See your
drive documentation for details on setting the master/slave settings.