HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide (web version) (T1780-96078, March 2008)

Troubleshooting
223
Table 10-1 General troubleshooting information
No. Problem Solution
10 DESCRIPTION: The service discovery
feature is not available, because the SLP
service (or the SLP daemon) failed to start
during Device Manager server installation.
CAUSE: An unexpected error occurred
during the SLP service (or the SLP
daemon) startup.
SOLUTION: Set the service discovery feature.
For details about how to do this, see section
A-5.
11 DESCRIPTION: Canceling the SLP service
(or the SLP daemon) failed during Device
Manager server uninstallation.
CAUSE: This problem happens in either of
the following cases:
• When performing uninstallation while
the SLP service (or the SLP daemon) is
running
• When performing uninstallation while
the SLP service is stopped, but is
registered as a Windows service.
SOLUTION: Stop or clear the SLP service (or the
SLP daemon). For details about how to do this,
see section
A-5.
If you use Windows, the OpenSLP file might be
deleted during uninstallation. In that case,
perform the following operations in order, and
then clear the SLP service:
1 In the Services screen, disable the Service
Location Protocol service.
2 Restart Windows.
12 DESCRIPTION: Even though the port
number of SMI-S was entered during
Device Manager server installation, after
installation, the Device Manager server
does not start or communication with SMI-S
Provider is disabled.
CAUSE: The port number entered during
installation is incorrect.
SOLUTION: Change the port number used by
the CIM/WBEM features, and then restart the
Device Manager server.
For details about how to change port numbers,
see subsection
A-3-2-2. When you change a
port number, do not specify the port numbers
described in subsection
5-4-1 .
13 DESCRIPTION: The message
KAIC00114-E An attempt to start
the HTTP server on port "2001"
failed. or KAIC00115-E An attempt
to start HTTPS server on port
"2443" failed. was output to the event
log file for Windows, or the syslog file for
Linux, and Device Manager could not be
started.
CAUSE: The port number is already used
by another program.
SOLUTION: Change the port number used by
the Device Manager web server (2001) or the
port number used for secure HTTP
communication by the Device Manager web
server (2443), and then restart the Device
Manager server.
For details on how to change a port number, see
subsections
8-2-2 and 8-2-3 . When changing a
port number, do not specify the port numbers
listed in subsection
5-4-1 .