README for HP Neoview Release 2.5 (R2.5)

Password encryption is required. Please check client version.
Indicates that the Neoview platform requires password encryption, but the login request came
from an ODBC or JDBC driver that does not encrypt passwords. Install a newer version of the
ODBC or JDBC driver no older than version 2.93.
JDBC Client Error Messages
The following client-side errors related to password encryption and certificate management can
be returned to a JDBC application and are potentially visible in error messages displayed by
those applications.
SQLSTATE: 38001
SQLCODE: error-code
*** ERROR[error-code] error-text
Indicates that an error occurred during password processing. The following table lists possible
errors and what you can do about them.
Description and RecoveryError Code and Text
The certificate file does not exist in the location given by the values
of the JDBC connection properties certificateDir and certificateFile
or, if those properties were not specified for the connection, in the
corresponding default location. One possibility is that certificateFile
specifies a directory name rather than a filename. Another
possibility is that the name specified in the connection attribute
was misspelled.
This error will occur only if the password encryption policy
prohibits automatically downloading a new certificate.
To recover, you must either deploy a new certificate to the location
given by certificateFile or the corresponding default location (or
change the setting of certificateFile to specify the location where
the certificate actually resides).
[29713] Certificate file name is not found.
The certificate file is missing from the location given by the
certificateFile property or its corresponding default, or the file
could not be opened for reading. To recover, check the file
permissions on the indicated file. If the permissions are correct,
delete the existing file, and install a new certificate in the location
given by certificateFile or the corresponding default location.
[29709] Error reading the certificate file name
The driver is attempting to download a certificate to the
workstation, but the file specified by the certificateFileActive
property could not be opened for writing.
To recover, ensure that the specified location is secured to permit
writing, and try again.
[29716] Error writing to the certificate file
name.
The specified certificate file is corrupted. Delete it from the location
specified by certificateFileActive or the corresponding default
value, and allow a new certificate to be downloaded from the
server, or if auto-download is off, install a new certificate in the
location given by certificateFile or the corresponding default
location.
If this error occurs repeatedly or affects multiple workstations
connecting to the same Neoview platform, there might be a
problem with the server certificate. In this case, you might need
to generate a new self-signed certificate or deploy a new CA
certificate.
[29701] Failed to retrieve the public key from
the certificate file name.
[29721] The certificate file name is corrupted.
[29729] Failed to open the certificate file name.
The password you typed was too long. If you mistyped, try again.
If you have an especially long password—longer than 70 bytes if
you use 1024-bit encryption or 128 bytes if you use 2048-bit
encryption—create a shorter one.
[29704] The password was too long.
New Features in Release 2.5 27