HP ProLiant DL980 HP ProLiant Servers Troubleshooting Guide - Page 64

ROM problems

Page 64 highlights

• Check for overwritten files. Refer to the application documentation to find out which files are added by the application. • Reinstall the application. • Be sure you have the most current drivers. ROM problems Remote ROM flash problems General remote ROM flash problems are occurring Action: Be sure you follow these requirements for using the Remote ROM flash utility: • A local administrative client system that is running the Microsoft® Windows NT® 4.0, Windows® 2000, or Windows Server™ 2003 operating system • One or more remote servers with system ROMs requiring upgrade • An administrative user account on each target system. The administrative account must have the same username and password as the local administrative client system. • All target systems are connected to the same network and use protocols that enable them to be seen from the administrative client. • Each target system has a system partition that is at least 32 MB in size. • Verification that the ROM version to which you are upgrading can be used for all the servers or array controllers that you are upgrading. • Follow the instructions for the Remote ROM Flash procedure that accompany the software. Command-line syntax error If the correct command-line syntax is not used, an error message describing the incorrect syntax is displayed and the program exits. Correct the syntax, and then restart the process. Access denied on target computer If you specify a networked target computer for which you do not have administrative privileges, an error message is displayed describing the problem, and then the program exits. Obtain administrative privileges for the target computer, and then restart the process. Be sure the remote registry service is running on a Windows®-based system. Invalid or incorrect command-line parameters If incorrect parameters are passed into command-line options, an error message describing the invalid or incorrect parameter is displayed and the program exits (Example: Invalid source path for system configuration or ROMPaq files). Correct the invalid parameter, and then restart the process. Software problems 64

  • 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

Software problems 64
Check for overwritten files. Refer to the application documentation to find out which files are added
by the application.
Reinstall the application.
Be sure you have the most current drivers.
ROM problems
Remote ROM flash problems
General remote ROM flash problems are occurring
Action
: Be sure you follow these requirements for using the Remote ROM flash utility:
A local administrative client system that is running the Microsoft® Windows NT® 4.0,
Windows® 2000, or Windows Server™ 2003 operating system
One or more remote servers with system ROMs requiring upgrade
An administrative user account on each target system. The administrative account must have the
same username and password as the local administrative client system.
All target systems are connected to the same network and use protocols that enable them to be seen
from the administrative client.
Each target system has a system partition that is at least 32 MB in size.
Verification that the ROM version to which you are upgrading can be used for all the servers or
array controllers that you are upgrading.
Follow the instructions for the Remote ROM Flash procedure that accompany the software.
Command-line syntax error
If the correct command-line syntax is not used, an error message describing the incorrect syntax is
displayed and the program exits. Correct the syntax, and then restart the process.
Access denied on target computer
If you specify a networked target computer for which you do not have administrative privileges, an error
message is displayed describing the problem, and then the program exits. Obtain administrative
privileges for the target computer, and then restart the process. Be sure the remote registry service is
running on a Windows®-based system.
Invalid or incorrect command-line parameters
If incorrect parameters are passed into command-line options, an error message describing the invalid or
incorrect parameter is displayed and the program exits (Example: Invalid source path for system
configuration or ROMPaq files). Correct the invalid parameter, and then restart the process.