HP DL320s - ProLiant 9TB SATA Storage Server NAS Release Notes page 7

Issue:
JRE-dependent applications or web sites prompt for JVM installation, or it is not properly
displayed
Description
Workaround
Issue:
VDS provider for MSA does not refresh after volume creation fails
Description
Workaround
Issue:
Storage Manager for SAN stops responding when Subsystem is selected
Description
Workaround
Issue:
NfsSvr logs an error in the event log
Description
Workaround
System installation and recovery process
This section describes issues related to installing the operating system on a storage server or performing
the recovery process.
Additional applications and utilities
A web site or application that is dependent on Java Virtual Machine (JVM) is not
displayed properly with Internet Explorer. A message prompts you to install JVM.
Uninstall the Java Runtime Environment (JRE) using the Control Panel and Add or
Remove Programs. Reinstall the JRE from the c:\hpnas\components\JRE
folder.
Creating a LUN and volume using the Create a New LUN wizard using Storage
Manager for SAN results in the volume creation failing and displays a warning
icon on the created volume in the Storage Manager for SAN user interface.
The warning icon continues to display even after closing and re-opening the HP
Storage Server Management console. Attempting to delete the LUN results in the
Storage Manager for SAN user interface becoming unresponsive and unable to
proceed past the delete LUN dialog box.
Do one of the following:
• Restart the system to load the LUNs and to refresh Storage Manager for SAN.
• Use the Array Configuration Utility (ACU) to create the LUN on the MSA, and
then use the Disk Manager utility on the Windows storage server to create
the LUN volume.
When Subsystem is clicked in Storage Manager for SAN, the system stops
responding and displays the message MMC has detected an error in a
snap-in and will unload it. This behavior is seen only when any of the
MSA subsystem volumes are being expanded.
Use the Array Configuration Utility (ACU) to access the MSA subsystem when
volumes are being expanded.
On systems with Windows Storage Server 2003 R2, the event log may contain an
error stating that Server for NFS failed to initialize on a non-existent drive letter.
For example:
Event Type: ErrorEvent
Source: NfsSvr
Event Category: None
Event ID: 1066
Description: Server for NFS failed to initialize
on volume with drive letter F:
This error does not affect the performance of NFS. The issue will be resolved in a
later HP ProLiant Storage Server release.
Storage Server release notes
7