HP Storage Provisioning Manager (SPM) Version 1.2 User Guide

Addressing common issues
The following sections describe common issues you may encounter while configuring or using the
SPM. They are either related to SPM itself, or have to do with using Insight Dynamics Storage Pools.
Storage Provisioning Manager issues
A general purpose web service call results in an error
Symptom–A general purpose web service call results in an error.
Possible cause–Client does not have permission to make the call, according to the access control list
of the entities involved.
Suggested action–If appropriate, add the client to the list of entities.
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.Ser verWindowsSer vice.exe.userconfig:
1. Stop SPM service by entering sc stop hpscifrom 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.
Troubleshooting66