Verify Wmi Npartition Provider Operation; Operational Problems; All Commands: Ordinal Not Found; All Commands: Required Data Unavailable Or Locked - HP Rx2620-2 - Integrity - 0 MB RAM Manual

Integrity servers with microsoft windows server 2003
Hide thumbs Also See for Rx2620-2 - Integrity - 0 MB RAM:
Table of Contents

Advertisement

HP_NParDynamicProfile
HP_NParCellConnectedToIOChassis
HP_NParComponentInSlot
HP_NParIOChassisInSlot
HP_NParCellInSlot
HP_NParSlotInCabinet
HP_NParCellSlotInCabinet
HP_NParIOChassisSlotInCabinet
HP_NParCellSlotInPartition
HP_NParDomainInCabinet
HP_NParLocalPartition
HP_NParRemoteComplex
If an obvious error occurs, or if the output looks significantly different from what is shown above,
you should uninstall and then reinstall the nPartition Provider. This will re-register the provider
with WMI.

Verify WMI nPartition Provider operation

To check if the nPartition Provider is running properly and responding to client requests, open
a command prompt and run the following commands:
set CIM_NAMESPACE=root/cimv2/npar
wmiop ci HP_NParRemoteComplex
When prompted, enter the following information:
[ key ] string Address? <Management Processor hostname or IP>
string Password? <MP Admin password>
If successful, you should see the following message:
Instance [root/cimv2/npar:HP_NParRemoteComplex.Address="<mp address>"]
successfully created!
Otherwise, if you see the following error:
Error: [6] CIM_ERR_NOT_FOUND: The requested object could not be found
This indicates that the nPartition Provider is either not running, or not handling requests
appropriately. Verify that the WMI nPartition Provider service is started. If not, start it from the
Services control panel, or reboot and repeat the test. If the service is started, you should uninstall
and then reinstall the nPartition Provider.

Operational problems

The problems described below are generally associated with the use of specific commands. They
are grouped in alphabetical order, by command, with any generic or non-specific problems listed
at the beginning.

All commands: ordinal not found

This problem might be due to a conflict between the version of the OpenSSL libraries used by
the nPartition commands and nPartition Provider and the versions installed by other tools.
Currently, ActivCard Gold software is one source of this conflict.
This problem manifests itself in other ways too. For a complete description and solution, see
"nPartition Provider fails to start during installation" (page

All commands: required data unavailable or locked

Because of data locking within the MP, issuing an nPartition command might display an error
message stating that required data is temporarily unavailable or locked. For example, this can
happen if multiple daemons, services, applications or administrators are simultaneously accessing
cell information, the stable complex configuration data, or the partition configuration data on
107).
Operational problems
111

Advertisement

Table of Contents
loading

This manual is also suitable for:

Bl860cNpartition

Table of Contents