Home » HP Manuals » Servers » HP Integrity rx2620 » Manual Viewer

HP Integrity rx2620 HP Integrity Servers with Microsoft Windows Server 2003 Re - Page 23

Troubleshooting Common Issues - drivers

View all HP Integrity rx2620 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 23 highlights

NOTE: On rx1620, Windows Server 2003 supports 256 MB, 512 MB, 1 GB, and 2 GB DIMMS only. 4 GB DIMMs are not supported. When migrating from another OS to Windows Server 2003 on servers where 4 GB DIMMs are installed, replace the 4 GB DIMMs with supported DIMMs. BL860c and BL870c Server Blade Table 1-12 Components supported with BL860c and BL870c Operating System • Windows Server 2003, Enterprise Edition with SP1/SP2 for Itanium-based Systems • Windows Server 2003, Datacenter Edition with SP1/SP2 for Itanium-based Systems I/O Mezzanine Support • Dual Port 4Gb/s FC Mezzanine Card (Q-Logic) (403619-B21) • Direct Adaptor Mezzanine Card for connecting to the Direct Attached Storage Blade (431643-B21) • PCI Express Quad Port Gigabit Server Mezzanine (447883-B21) Troubleshooting Common Issues Read this section completely before installing or running Windows Server 2003 on HP Integrity servers. This section includes workarounds that may save you valuable time and effort. Array Configuration Utility (ACU) verifer.exe causes ACU inaccuracies Issue Servers Workaround ACU reports incorrect results when the Windows Driver Verifier (verifier.exe) is enabled and running in the background. All Integrity There is no workaround at this time. To run the ACU, you must first end the verifier.exe process using the Windows Task Manager, then launch ACU. Do not run both simultaneously. Array Diagnostic Utility (ADU) Uninstall feature not functional Issue Servers Workaround The ADU uninstall feature is not working. All Integrity There is no workaround at this time. Clustering Cluster nodes unable to see messages Issue Servers Workaround Normally in a cluster, when an application in one node logs an event to the Windows Event Log, the message is visible to all nodes in the cluster. However, due to a Microsoft limitation, when events are logged with more than 900 bytes in the lpRawData binary field (as reported by the Microsoft ReportEvent API), only the node that issued the event can see it using the Windows Event Viewer. Other nodes in the cluster are unable to see these messages. Superdome, rx8620, rx7620 There is no workaround at this time. Troubleshooting Common Issues 23

Section	Page
Release Notes	1
Table of Contents	3
About This Document	9
Typographic Conventions	9
HP Encourages Your Comments	9
1 Release 5.5 Overview	11
System Configurations	11
What’s New in Windows Solution 5.5	13
Software Requirements	13
Web Browser	13
TCP/IP and SNMP	13
Utility Meter	13
Supported Components	13
Superdome (with sx1000 or sx2000 chipset)	14
rx8640	15
rx8620	16
rx7640	17
rx7620	18
rx6600	19
rx4640	20
rx3600	20
rx2660	21
rx2620	21
rx1620	22
BL860c and BL870c Server Blade	23
Troubleshooting Common Issues	23
Array Configuration Utility (ACU)	23
verifer.exe causes ACU inaccuracies	23
Array Diagnostic Utility (ADU)	23
Uninstall feature not functional	23
Clustering	23
Cluster nodes unable to see messages	23
Device Drivers	24
Missing driver affects Virtual Machines	24
Drivers missing from RTM media	24
Driver roll back causes crash	24
prlntss.sys installation issue	24
Extensible Firmware Interface (EFI) and EFI-based Setup Utility (EBSU)	25
I/O card firmware values display as unknown	25
QLogic HBA firmware and EFI driver revisions display incorrectly	25
EBSU displays incorrect CPU version	25
EBSU displays incorrect firmware version	25
EBSU changes EFI Boot menu	26
Foundation Agents	26
Memory leak generated by Foundation Agents	26
Hard Disk Configuration	26
Disk configuration lost after reboot	26
HP c-Class Blade System Infrastructure	26
Onboard Administrator displays wrong CPU	26
BL870c SAS controller supports only one mirror	26
Fibre Channel	27
Installation causes MSA 1500 driver to be flagged	27
Support Pack update generates errors	27
Inapplicable errors seen in kit update	27
Redundant entries seen in the Add/Remove Program	27
Emulex HBAs use different driver	27
MSA fails with Storport driver installed	28
LUNs undetected by ACU	28
HBA removal fails	28
HP-SUM hangs on MSA 1500 boot	28
HPVM	29
Patches required on virtual machine guests	29
Installation	29
Attempting installation from a second DVD drive results in system message	29
Japanese QFE package fails to install all QFEs	29
Installation from graphics console may require additional steps	29
Hyper-threading may cause installation failure	29
Component times outs cause installation failure	30
Screen is blank at system startup	30
Use of 16 GB option discouraged	30
Maximum Payload Size parameter must be off	30
Use Esc+8 instead of F8 key on headless server	30
Custom Install option disables Remote Desktop	31
prlntss.sys requires Support Pack Installation	31
IP Console Switch use causes screen to blank	31
Network Interface Cards (NICs)	32
Warning message not a cause for concern	32
Power Management	32
PAL_HALT_LIGHT disables idle power state	32
PAL_HALT_LIGHT status not displayed in HP-SUM, VCRM, and SMS	32
Partition Manager	32
C++ Runtime Library error message can be ignored	32
PXE boot on Intel Dual Core Itanium systems	33
Patch required to enable PXE boot	33
SCSI	33
Ultra 320 firmware update fails	33
Event log entry caused by timeout condition	33
Smart Array	33
640x/530x generates errors in system event log	33
6402 as internal disk drive controller generates errors	33
StorageWorks 43xx enclosures may cause errors	34
Configuration utility may be inaccessible	34
Tools menu radio buttons inactive	34
640x/530x may not load during system boot	35
640x/530x do not rebuild the internal HDD	35
640x hot add not supported	35
6400 cannot be hot-replaced during error message display	36
Command causes machine check abort	36
System Management Homepage (SMH)	36
Components flagged with red exclamation mark	36
Page lacks temperature sensor descriptions	36
Some components not shown	36
SMH fails to open	37
Program terminates after error message	37
Incorrect number of CPUs displayed in System Report	37
Version Control	38
VCRM unsupported components	38
VCRM fails to start	38
VCRM updates wrong support pack	38
Inaccurate VGA information displayed	38
Video	38
Video not displayed	38
vKVM and vMedia	39
Tool bar fails to redraw as expected	39
vMedia drive not immediately accessible	39
vKVM session stops updating	39
2 Installing Windows Server 2003	41
Preinstallation Tasks	41
Installation Tasks	41
Reinstallation Tasks	42
Post-Installation Tasks	42
Tips and Tricks	42
3 Product Support	45
Technical Documentation	45
Technical Support	46
Get Windows-specific firmware, drivers, and utilities	46

Match case Limit results 1 per page

NOTE:

On rx1620, Windows Server 2003 supports 256 MB, 512 MB, 1 GB, and 2 GB DIMMS

only. 4 GB DIMMs are not supported. When migrating from another OS to Windows Server 2003

on servers where 4 GB DIMMs are installed, replace the 4 GB DIMMs with supported DIMMs.

BL860c and BL870c Server Blade

Table 1-12 Components supported with BL860c and BL870c

•

Windows Server 2003, Enterprise Edition with SP1/SP2 for Itanium-based Systems

•

Windows Server 2003, Datacenter Edition with SP1/SP2 for Itanium-based Systems

Operating System

•

Dual Port 4Gb/s FC Mezzanine Card (Q-Logic) (403619-B21)

•

Direct Adaptor Mezzanine Card for connecting to the Direct Attached Storage Blade

(431643-B21)

•

PCI Express Quad Port Gigabit Server Mezzanine (447883-B21)

I/O Mezzanine

Support

Troubleshooting Common Issues

Read this section completely before installing or running Windows Server 2003 on HP Integrity

servers. This section includes workarounds that may save you valuable time and effort.

Array Configuration Utility (ACU)

verifer.exe causes ACU inaccuracies

Issue

ACU reports incorrect results when the Windows Driver Verifier

(

verifier.exe

) is enabled and running in the background.

Servers

All Integrity

Workaround

There is no workaround at this time. To run the ACU, you must first end the

verifier.exe

process using the Windows Task Manager, then launch ACU.

Do not run both simultaneously.

Array Diagnostic Utility (ADU)

Uninstall feature not functional

Issue

The ADU uninstall feature is not working.

Servers

All Integrity

Workaround

There is no workaround at this time.

Clustering

Cluster nodes unable to see messages

Issue

Normally in a cluster, when an application in one node logs an event to the

Windows Event Log, the message is visible to all nodes in the cluster. However,

due to a Microsoft limitation, when events are logged with more than 900 bytes

in the

lpRawData

binary field (as reported by the Microsoft

ReportEvent

API), only the node that issued the event can see it using the Windows Event

Viewer. Other nodes in the cluster are unable to see these messages.

Servers

Superdome, rx8620, rx7620

Workaround

There is no workaround at this time.

Troubleshooting Common Issues