HP Matrix Operating Environment Software - Manual (Page 54)

The user is unable to log in through the SPM user interface
Symptom–The user is unable to log in through the SPM user interface and commands that attempt
to interact with live storage fail.
Possible cause–SPM cannot properly detect the name of the host on which it is running.
Suggested action–The Storage Administrator must enter the correct host name in the file
HP.Arcadia.ServerWindowsService.exe.userconfig:
1. Stop SPM service by entering sc stop hpsci from the command prompt.
2. In the SPM installation directory, open the HP.Arcadia.ServerWindowsService.exe.userconfig
file in a text editor.
3. Edit the field LocalHostNameOverride so that it contains the correct host name of the server
on which SPM is installed.
4. Save and close the file.
5. Start SPM service by entering sc start hpsci from the command prompt.
Could Not Find User error when entering a user or group name
Symptom–In the Add Users or Groups dialog box, entering a user or group name that you know
is correct results in a Could Not Find User error.
Possible cause–
•
A space was added.
•
The user or group is not a valid user or group.
Suggested action–
•
Enter the user or group name again, but do not include a space.
•
Create a user or group before adding them to SPM.
Experiencing port conflicts or other Command View provider issues
Symptom–You are experiencing port conflicts or other Command View provider issues.
Possible cause–The SMI-S CIMOM is running on a port other than 5989.
Suggested action–Contact HP Service and Support, and refer to support document c01800876.
Cannot communicate with array or import storage volumes
Symptom–When defining a new array in SPM, attempting to import storage volumes, or performing
other array/volume operations, one of the following error messages appear:
•
Communication Error - Unable to communicate with the device (See
log for details)
•
ESA hostname is 'null' — A valid host name must be specified in
HP.Arcadia.ServiceWindowsService.exe.userconfig (
element)
Possible cause–The first error message is the more common issue. It indicates broken communication
paths between SPM and the Extensible Storage Adapter layer that performs the SMI-S operations
or OO workflows, or between ESA and the device manager, or between the device manager and
the device. The log usually contains more information that can help pinpoint the problem. There
could be an issue with the Command View credentials, or the port being used by Command View.
This error also appears if there is a typo in the host name/IP.
Suggested action–There are a variety of possible corrective actions based on the root cause of the
issue (for example, Command View credentials or port usage). Consider the appropriate actions
listed below.
•
Validate the credentials supplied for HP Command View EVA.
•
Determine if HP Command View EVA is running on the same CMS (Central Management
Server) as HP SIM. When they are on the same server, a conflict exists because both Command
View and the HP SIM WMI Server use ports 5988 (unsecure) and 5989 (secure) by default.
54 Troubleshooting