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

Cause Unable to locate contemplate.txt because the NVTHOME environment variable
is not set nor is the -temp option specified.
Effect Control File Generator terminates.
Recovery Either set the NVTHOME environment variable or specify the -temp option.
51015
Control File Generator terminates without generating control file
Cause Control File Generator terminates.
Effect None.
Recovery This is an informational message only; no corrective action is needed.
51016
Exception encountered while generating control file. exception
Cause One or more errors occurred while writing the control file to stream. Neoview
Transporter either could not locate the file or does not have the permission to write to file.
Effect The Control File Generator terminates.
Recovery Check the exception, and rerun the Control File Generator.
51017
A driver exception encountered while creating connection: exception
Cause The specified JDBC driver class is corrupted or missing.
Effect The Control File Generator terminates.
Recovery Verify that the hpt4jdbc.jar file exists in the NVTHOME/lib directory, and
rerun the Control File Generator. If the problem persists, contact HP Support and report this
condition.
51018
Exception encountered while reading template file: template-file
exception
Cause An error occurred while reading the template file. Neoview Transporter might not
have permission to access the template file.
Effect The Control File Generator terminates.
Recovery Check the template file, and rerun the Control File Generator. If the problem
persists, contact HP Support and report this condition.
52001
Job recovery is not supported for control files of string format
Cause The recovery action is not supported for control files that are provided in string format.
Effect Recovery is not possible for the job.
Recovery Submit the control file in file format to allow recovery in case of errors.
52002
Unable to create the JVM
Cause The JNI invocation API JNI_CreateJavaVM encountered an error for the in-process
execution mode. The error may be platform-specific and related to the JNI configuration or
the Java VM (virtual machine) library.
69