Neoview Messages Manual (Volume 2) (R2.5)

Recovery Perform manual cleanup of the temporary files. Check the operating system and
POSIX documentation for file-system limits. If the problem persists, contact your HP service
provider.
52015
Unable to allocate memory to store JVM options
Cause Unable to allocate memory for the JVM options.
Effect This condition might be caused by a memory leak. It is unlikely to happen in normal
operating conditions.
Recovery Verify that the format of the resource configuration file is correct and that the
number of JVM options is within limits. If the problem persists, contact your HP service
provider.
52016
Reached maximum limit of num JVM options while reading configuration
file file
Cause Too many options specified. 1024 options are allowed.
Effect This is a fatal startup error. The JVM is not launched.
Recovery Reduce the number of JVM options. If the problem persists, contact your HP service
provider.
52017
Unable to open JVM resource configuration file file
Cause The resource configuration file was not accessible.
Effect This is a fatal startup error. The JVM is not launched.
Recovery Check the resource configuration file path and permissions. Correct the problem
and restart. If the problem persists, contact your HP service provider.
52018
Unable to launch the Neoview Transporter Client due to setup failure.
Error code= err_msg
Cause The Neoview Transporter API encountered an error while creating the JVM.
Effect The first Neoview Transporter API call in the process sets up the JVM. The JVM is
reused later. If the JVM setup fails, subsequent nvtExecute requests also fail.
Recovery Terminate the process and restart the request. Try in-process and out-process
execution modes. Check the exit codes for common problems. If the problem persists, contact
your HP service provider.
52019
Unable to open error message log file file. Error=err_msg
Cause The critical and error messages displayed by the Neoview Transporter Client are
stored in temporary files. These messages are displayed at the end of the nvtExecute call.
Effect The log files are no longer accessible. Some critical error messages will not be displayed.
Recovery Manually clean up the temporary log files if any. If the problem persists, contact
your HP service provider.
52020
NVT_EXEC_INFO Version mismatch. Expected version=ver, Actual version=ver
72 Neoview Transporter Messages (Client Messages 10001 Through 52306, Server Messages 1000 Through 5302)