ISNAT Messages 1700-1799
1700
ERROR: Audit plugin error = val
Description
The audit postop operation failed with the val error from the audit plugin.
Action
Look in the userlog for additional error messages from the audit plugin.
1703
ERROR: Invalid config SECURITY setting for -E option
Description
The SECURITY setting in tuxconfig file is not USER_AUTH or greater.
Action
Modify the SECURITY setting to be USER_AUTH, ACL, or MANDATORY_ACL.
1712
ERROR: Could not add workstation information: error code errorcode
Description
When transforming a buffer to workstation format, the ISH
could
not add workstation information. Save errorcode to give to
BEA Customer Support.
Action
Please contact BEA Customer Support.
See Also
ISH
1713
ERROR: Could not add message information: error code val
Description
When transforming a buffer to native format, the ISH
could
not add information. Save errorcode to give to BEA
Customer Support.
Action
Please contact BEA Customer Support.
See Also
ISH
1736
ERROR: Handler received message of unknown format
Description
A message arrived at the ISH with an unknown format.
Action
Contact BEA Customer Support.
1746
ERROR: Invalid network address specified for -n option, val
Description
The argument passed with the -n option is not a valid
network address.
See the description of the -n option on the
ISL
Action
Correct the CLOPT for the ISL and re-boot the server.
See Also
ISL
1747
ERROR: Unable to get server group information for ISL, errno = errno_val
Description
The IIOP Server Listener process encountered an error while trying to
obtain server group information about itself from shared memory.
The numeric value of errno_val
is printed as part of the
error message; you can convert this value to a symbolic value by
examining <atmi.h>
.
Action
Examine the user log for a prior message indicating a more exact cause of the error. Contact BEA Technical Support.
1748
ERROR: Unable to get machine information for ISL, errno = errno_val
Description
The IIOP Server Listener process encountered an error while trying to
obtain machine information about itself from shared memory.
The numeric value of errno_val
is printed as part of the
error message; you can convert this value to a symbolic value by
examining <atmi.h>
.
Action
Examine the user log for a prior message indicating a more exact cause of the error. Contact BEA Technical Support.
1750
ERROR: SSL certificate not present in SSL Handshake
Description
During an SSL Handshake operation, the IIOP Listener/Handler detected that an SSL certificate was missing from the certificate chain that was presented to it by a remote client program or by a remote IIOP Listener/Handler.
Action
Examine the user log for a prior message indicating a more exact cause of the error. Ensure that all certificates in the certificate chain are accessible to the application. Contact your Certificate Authority or contact BEA Customer Support.
1751
ERROR: failed to extract version from SSL CA certifcate
Description
An error occurred when trying to determine the version of an X.509 certificate for a Certificate Authority.
Action
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid certificates. Contact your Certificate Authority or contact BEA Customer Support.
1752
ERROR: SSL CA certificate contains no BasicConstraints extension
Description
A certificate for a Certificate Authority was found to contain no BasicConstraints extension, as is required for X.509 version 3 certificates.
Action
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid and properly conforming. Refer to the TUXEDO documentation or release notes for information on how to adjust the level of BasicConstraints enforcement performed by TUXEDO. Contact your Certificate Authority or contact BEA Customer Support.
1753
ERROR: failed to retrieve BasicConstraints from SSL CA certificate
Description
An error occurred when trying to retrieve the BasicConstraints information from an X.509 certificate for a Certificate Authority.
Action
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid certificates. Contact your Certificate Authority or contact BEA Customer Support.
1754
ERROR: the BasicConstraints extension in an SSL CA certificate is not marked as critical
Description
The BasicConstraints extension in a certificate for a Certificate Authority was not marked as a critical extension, as is required for X.509 version 3 certificates.
Action
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid and properly conforming. Refer to the TUXEDO documentation or release notes for information on how to adjust the level of BasicConstraints enforcement performed by TUXEDO. Contact your Certificate Authority or contact BEA Customer Support.
1755
ERROR: failed to parse BasicConstraints extension in an SSL CA certificate
Description
An error occurred when trying to parse the BasicConstraints information from an X.509 certificate for a Certificate Authority.
Action
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid certificates. Contact your Certificate Authority or contact BEA Customer Support.
1756
ERROR: the BasicConstraints extension in an SSL CA certificate is not marked as a CA
Description
The BasicConstraints extension in a certificate for a Certificate Authority was not marked to indicate that the certificate does in fact belong to a Certificate Authority.
Action
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid and properly conforming. Refer to the TUXEDO documentation or release notes for information on how to adjust the level of BasicConstraints enforcement performed by TUXEDO. Contact your Certificate Authority or contact BEA Customer Support.
1757
INFO: IPv6 not enabled.
Description
The IPv6 address is used but IPv6 is not enabled.
Action
Enable IPv6 by setting environmentriable variable TMUSEIPV6=Y
1759
ERROR: IIOP message size IIOP_size exceeds limit val.
Description
The received IIOP message size is too large. Malicious message from hacker may cause ISL to allocate unnecessary large memory blocks and then impact the system performance, even cause ISL cannot handle any service. ISL will close the connection.
Action
Check if ISL is under attack. If it is not, adjust the ISL CLOPT parameter (-U).