Troubleshooting Export Tool - HPE XP7 User Manual

Troubleshooting Export Tool

The following table explains possible problems with Export Tool and probable solutions to the
problems.
Possible problems
You cannot run the batch file.
Export Tool stops and the
processing does not continue.
The command prompt window
was displaying progress of the
export processing, but the
window stopped displaying
progress before the
processing stopped. The
progress information does not
seem to be updated anymore.
An error occurs and the
processing stops.
The monitoring data in the
CSV file includes (-1).
When Export Tool
terminated abnormally due
to error, the row of Check
License is shown as
Unmarshal Exception in
the log file.
Export Tool terminated
abnormally because the
processing did not
continue. version
unmatched is shown in the
log file.
100 Exporting Performance Monitor data
Probable causes and recommended action
The path to the Java Virtual Machine (Java.exe) might not be defined in the PATH
environment variable. If this is true, you must add that path to the PATH environment
variable. For information about how to add a path to the environment variable, see
the documentation for your operating system.
An incorrect version of Java Runtime Environment (JRE) might be installed on your
computer. To check the JRE version, enter the following command at the Windows
command prompt or the UNIX console window:
Java -version
If the version is incorrect, install the correct version of JRE.
The command prompt window might be in pause mode. The command prompt
window will be in pause mode if you click the command prompt window when
Export Tool is running. To cancel pause mode, activate the command prompt
window and then press the <ESC> key. If a timeout of RMI occurs during pause
mode, the login will be canceled and an error will occur when you cancel pause
mode after the timeout. The error message ID will be (0001 4011).
If a memory size is not specified in a batch file, the Out Of Memory Error occurs
in JRE, Export Tool might stop and the processing might not continue. Confirm
whether the specified memory size is correct or not.
If the error message ID is (0001 4011), the user is forcibly logged off and the
processing stops because Export Tool did not issue any request to SVP within the
timeout period specified by the -Dmd.rmitimeout parameter of the Java command
(default: 20 minutes). The computer running Export Tool could be slow. Confirm
whether you are using a computer that is not supported, or whether the computer is
slow. To continue running Export Tool, first increase the value of the -Dmd.rmitimeout
parameter (maximum: 1,440 minutes (24 hours), and then run Export Tool. For details
about -Dmd.rmitimeout, see the Operands table for the Java command in
"Operands" (page 82). If the error persists, contact the HPE technical support.
If the error message ID is (0002 5510), probable error causes and solutions are:
An internal processing is being performed in the disk array. Alternatively, another
user is changing configurations. Wait for a while and then run Export Tool again.
Maintenance operations are being performed on the disk array. Wait until the
maintenance operations finish and then run Export Tool again.
If the error message ID is none of the above, see
(page 101).
For details on invalid monitoring data, see
(page 99).
It might be an unsuitable combination of the DKCMAIN/SVP program version and
the Export Tool version. Confirm whether versions of these programs are correct.
"Messages issued by Export Tool"
"Causes of Invalid Monitoring Data"