Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
1 |
ERROR: Unknown hash algorithm algorithm-id | |
|
Description |
An unknown hash algorithm was found on a certificate. The algorithm identifier is algorithm-id |
Action |
Contact BEA Customer Support. | |
2 |
ERROR: Unable to digest message errorcode | |
|
Description |
The system was unable to digest a certificate. The error code was errorcode. |
Action |
Contact BEA Customer Support. | |
3 |
ERROR: Unable to decrypt digest errorcode | |
|
Description |
The system was unable to decrypt the digest value of a certificate. The error code was errorcode. |
Action |
Contact BEA Customer Support. | |
4 |
ERROR: Unable to parse digest information errorcode | |
|
Description |
The system was unable to parse information contained in the encrypted digest of a certificate. The error code was errorcode. |
Action |
Contact BEA Customer Support. | |
5 |
ERROR: Unable to acquire cache mutex (function-name/errorcode) | |
|
Description |
While attempting to encrypt or decrypt a message, the system was unable to acquire a mutex. The function this occurred in was function-name, and the error code was errorcode. |
Action |
Contact BEA Customer Support. | |
6 |
ERROR: Unable to release cache mutex (function-name/errorcode) | |
|
Description |
While attempting to encrypt or decrypt a message, the system was unable to release a mutex. The function this occurred in was function-name, and the error code was errorcode. |
Action |
Contact BEA Customer Support. | |
7 |
INFO: Setting cache size of sealers to cache-size | |
|
Description |
A cache of sealer information is maintained by the system. This cache size can be modified with the EVSEALERCACHESIZE environment variable. This message indicates that a new cache size has been set to cache-size. The default cache size is twenty. |
Action |
None. | |
8 |
INFO: Setting cache size of signers to val | |
|
Description |
A cache of signer information is maintained by the system. This cache size can be modified with the EVSIGNERCACHESIZE environment variable. This message indicates that a new cache size has been set to cache-size. The default cache size is twenty. |
Action |
None. | |
9 |
INFO: Setting cache size of signer/sealer information to val | |
|
Description |
A cache of pkcs7 information is maintained by the system. This cache size can be modified with the EVSSCACHESIZE environment variable. This message indicates that a new cache size has been set to cache-size. The default cache size is twenty. |
Action |
None. | |
10 |
ERROR: Invalid return from implementation. cds_cert=0xcert-val, cds_cert_size=cert-size, cds_principal_name=0xname cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid certificate descriptor. The possible output fields in the certificate descriptor are cert-val, cert-size, name and usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
| |
11 |
ERROR: Proof mapping failure: errorcode | |
|
Description |
The plug-in method that maps configured names has returned a failure code of errorcode. |
Action |
Ensure the plug-in function | |
See Also |
| |
12 |
ERROR: Process initialization failure: errorcode | |
|
Description |
The plug-in public key initialization method has returned a failure code of errorcode. |
Action |
Ensure the plug-in function | |
See Also |
| |
13 |
ERROR: Could not find valid decryption key | |
|
Description |
An encrypted message was received by the system, but the system could not find a valid decryption key. |
Action |
Ensure the process attempting to decrypt the message has a valid decryption key. | |
See Also |
| |
14 |
ERROR: No license for signature verification or generation | |
|
Description |
There is no installed license for signature verification or generation. |
Action |
Install a proper signature license. If you believe you have a valid license for public key signatures, contact BEA Customer Support. | |
15 |
ERROR: No license for public key encryption or decryption | |
|
Description |
There is no installed license for public key encryption or decryption. |
Action |
Install a proper public key encryption license. If you believe you have a valid license for public key encryption, contact BEA Customer Support. | |
16 |
ERROR: Maximum certificate chain depth of max-depth exceeded | |
|
Description |
A certificate chain starts with a normal certificate (called a leaf) and ends with either an implicitly trusted certificate authority certificate or a self-signed certificate. Generally, these chains rarely exceed a depth of three or four. However, the system is attempting to access a chain greater than max-depth deep. |
Action |
Ensure there is no security problem on the system where this error occurs. If there is a need to have a maximum chain depth greater than max-depth, the environment variable EVMAXCERTDEPTH can be set to the maximum depth of a certificate chain. | |
See Also |
| |
17 |
ERROR: Invalid return from implementation. Returned Private Key=0xprivate-key, cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid private key. The possible output fields of the private key and associated certificate are private-key and usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
| |
18 |
ERROR: Invalid return from implementation. Returned Public Key=0xpublic-key, cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid public key. The possible output fields of the public key and associated certificate are public-key and usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
| |
19 |
ERROR: Invalid return from implementation. cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid certificate descriptor. The invalid output field of the certificate descriptor is usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
| |
20 |
ERROR: Deadlock detected | |
|
Description |
The security system has detected an invalid access pattern of public keys.
An example would be an attempt to change the property of a key while
inside of a callback function. For example, it is invalid to call
|
Action |
Ensure the code in the plug-in complies with the allowable access pattern of keys. Otherwise, Contact BEA Customer Support. | |
See Also |
| |
21 |
ERROR: Memory allocation error in function, code location | |
|
Description |
An attempt to allocate memory with |
Action |
Check that your system has enough physical or virtual memory to complete the operation. If you believe your system has enough memory for the operation and that the malloc arena has not been corrupted by user code, contact BEA Customer Support. | |
22 |
ERROR: Unable to realize the _ec_sec_map_proof interface implementation val. Error code (val) | |
|
Description |
The registry was unable to properly realize an implementation for the
|
Action |
Ensure the registry is in a valid state. If the registry is valid and the implementation appears to be known to the system, contact your Customer Support. | |
See Also |
| |
23 |
ERROR: Unable to realize the _ec_sec_pki_init interface implementation val. Error code (val) | |
|
Description |
The registry was unable to properly realize an implementation for the
|
Action |
Ensure the registry is in a valid state. If the registry is valid and the implementation appears to be known to the system, contact your Customer Support. | |
See Also |
| |
31 |
ERROR: Encryption keys cannot have conflicting algorithms (alg1/alg2) or bit sizes (bit-size1/bit-size2) | |
|
Description |
Only one bulk data encryption algorithm can be used on a single message. If the buffer was marked with more than one algorithm or bit size, this error is raised. The conflicting algorithms are alg1 and alg2 or bit sizes bit-size1 and bit-size2 |
Action |
Ensure that every message has only been marked with one encryption algorithm or bit strength. | |
See Also |
| |
32 |
ERROR: Invalid return from _ec_sec_cert_by_name error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_cert_by_name returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
33 |
ERROR: Invalid return from _ec_sec_cert_by_dsn error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_cert_by_dsn returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
34 |
ERROR: Invalid return from _ec_sec_prs_get_principal error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_prs_get_principal returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
35 |
ERROR: Invalid return from _ec_sec_prs_get_issuer error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_prs_get_issuer returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
36 |
ERROR: Invalid return from _ec_sec_val_cert error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_val_cert returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
37 |
ERROR: Invalid return from _ec_sec_val_trust error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_val_trust returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
38 |
ERROR: Invalid return from _ec_sec_key_open_private_key error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_open_private_key returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
39 |
ERROR: Invalid return from _ec_sec_key_open_public_key error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_open_public_key returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
40 |
ERROR: Invalid return from _ec_sec_key_copy_key error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_copy_key returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
41 |
ERROR: Invalid return from _ec_sec_key_close error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_close returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
42 |
ERROR: Invalid return from _ec_sec_key_getinfo error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_getinfo returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
43 |
ERROR: Invalid return from _ec_sec_key_setinfo error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_setinfo returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
44 |
ERROR: Invalid return from _ec_sec_key_digest error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_digest returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
45 |
ERROR: Invalid return from _ec_sec_key_encrypt_digest error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_encrypt_digest returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
46 |
ERROR: Invalid return from _ec_sec_key_decrypt_digest error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_decrypt_digest returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
47 |
ERROR: Invalid return from _ec_sec_key_encrypt_session_key error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_encrypt_session_key returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
48 |
ERROR: Invalid return from _ec_sec_key_decrypt_session_key error-code | |
|
Description |
The implementation of the plug-in function _ec_sec_key_decrypt_session_key returned an unexpected error code of error-code. |
Action |
Ensure that the registry has not been compromised. Contact your Security Provider Interface supplier and report the error. Contact your BEA Customer Support. | |
See Also |
| |
49 |
ERROR: Unable to acquire credentials. Error code val1, minor_status val2 | |
|
Description |
The system was unable to acquire credentials for a process attempting to log in to the system. The error code val1 is an engine error code, while val2 is the minor status, as defined by the GSSAPI. Where two BEA TUXEDO Release 7.1 applications are communicating through GWTDOMAIN (domain gateway) processes, and both are using the default authentication plug-ins, a mismatch between the CONNECTION_PRINCIPAL_NAME parameter and the the DOMAINID parameter for the local domain access point can prevent the local domain gateway process from booting. |
Action |
For BEA TUXEDO Release 7.1 applications communication through a GWTDOMAIN process and using the default authentication plug-ins, ensure that the CONNECTION_PRINCIPAL_NAME parameter for the local domain access point (as defined in the DM_LOCAL_DOMAINS section of the local DMCONFIG file) is the same as the DOMAINID parameter for the local domain access point. You may need to consult with your AAA security provider. If you are using the default AAA security provider provided by BEA Systems, then contact BEA Customer Support. | |
50 |
ERROR: Unable to process pkcs7 packaged data (val1/val2/val3) | |
|
Description |
The system was attempting to process data packaged as ASN.1 type PKCS7. A failure was encountered during the decoding process. |
Action |
Contact BEA Customer Support. Be sure to have val1, val2 and val3 to give to the support person. | |
51 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The auditing fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support. Be sure to have val to give to the support person. | |
52 |
ERROR: Unable to allocate array of val handles | |
|
Description |
A call to calloc failed while attempting to allocate an array of val handles. |
Action |
Check that your system has enough physical or virtual memory to complete the operation. If you believe your system has enough memory for the operation and that the malloc arena has not been corrupted by user code, contact BEA Customer Support. | |
53 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The auditing fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support. Be sure to have val to give to the support person. | |
54 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The public key initialization fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support. Be sure to have val to give to the support person. | |
55 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The public key validation fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support. Be sure to have val to give to the support person. | |
56 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The public key validation fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support. Be sure to have val to give to the support person. | |
60 |
ERROR: Invalid return from implementation. cds_cert=0xcert-val, cds_cert_size=cert-size, cds_principal_name=0xname cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid certificate descriptor. The possible output fields in the certificate descriptor are cert-val, cert-size, name and usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
| |
61 |
ERROR: Invalid return from implementation. Returned Private Key=0xprivate-key, cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid private key. The possible output fields of the private key and associated certificate are private-key and usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
| |
62 |
ERROR: Invalid return from implementation. Returned Public Key=0xpublic-key, cds_usage=0xusage | |
|
Description |
The implementation of a plug-in function has returned an invalid public key. The possible output fields of the public key and associated certificate are public-key and usage. |
Action |
Modify the code in the plug-in implementation to comply with the input/output criteria. | |
See Also |
|