HP Integrity Superdome SX2000 HP Integrity Servers with Microsoft Windows Serv - Page 19

Application Development, Array Configuration Utility ACU, Array Diagnostic Utility ADU, Clustering,

Page 19 highlights

Application Development Application hangs when calling the GetThreadContext function Issue Servers Workaround An application that calls the GetThreadContext function might stop functioning on a system running an Itanium-based version of Windows Server 2003. This can occur when the system is under a heavy workload. All Integrity This is an operating system bug. HP recommends that you apply the Microsoft hotfix to all HP Integrity servers running Windows Server 2003 (both SP1 and SP2). See the Microsoft Knowledge Base article #947504, titled An application that calls the GetThreadContext function may stop responding on a computer that is running an Itanium-based version of Windows Server 2003 at http:// support.microsoft.com/?kbid=947504. 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 Typically, events reported to the Windows Event Log are visible to all nodes connected to the cluster. However, due to a Microsoft limitation, when an event with more than 896 bytes in the data field is reported, only the cluster node that reported the event can see it. Other nodes in the cluster are unable to see this event. All Integrity servers There is no workaround at this time. Device Drivers Missing driver affects Virtual Machines Issue Servers The HP Integrity Baseboard Management Controller Device Driver must be installed on all VMs for the HP Integrity VM Provider to function correctly on these systems. The baseboard Management Controller driver (also known as the HP Health Driver) automatically installs from the Support Pack and Reinstall Media, or can be manually installed from the HP Smart Setup CD. All Integrity Troubleshooting Common Issues 19

  • 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

Application Development
Application hangs when calling the GetThreadContext function
Issue
An application that calls the
GetThreadContext
function might stop
functioning on a system running an Itanium-based version of Windows Server
2003. This can occur when the system is under a heavy workload.
Servers
All Integrity
Workaround
This is an operating system bug. HP recommends that you apply the Microsoft
hotfix to all HP Integrity servers running Windows Server 2003 (both SP1 and
SP2). See the Microsoft Knowledge Base article #947504, titled
An application
that calls the GetThreadContext function may stop responding on a computer that is
running an Itanium-based version of Windows Server 2003
at
http://
support.microsoft.com/?kbid=947504
.
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
Typically, events reported to the Windows Event Log are visible to all nodes
connected to the cluster. However, due to a Microsoft limitation, when an event
with more than 896 bytes in the
data
field is reported, only the cluster node
that reported the event can see it. Other nodes in the cluster are unable to see
this event.
Servers
All Integrity servers
Workaround
There is no workaround at this time.
Device Drivers
Missing driver affects Virtual Machines
Issue
The HP Integrity Baseboard Management Controller Device Driver must be
installed on all VMs for the HP Integrity VM Provider to function correctly on
these systems. The baseboard Management Controller driver (also known as
the HP Health Driver) automatically installs from the Support Pack and Reinstall
Media, or can be manually installed from the HP Smart Setup CD.
Servers
All Integrity
Troubleshooting Common Issues
19