![]() |
![]() |
|
|
6200 |
ERROR: Invalid buffer passed to workstation encode/decode routine | |
|
Description |
An invalid buffer was passed by the system into an internal encoding routine. |
Action |
Contact BEA Customer Support. | |
6201 |
ERROR: Unable to get bulletin board parameters | |
|
Description |
While attempting to initialize the public key subsystem, a process attempted to get bulletin board parameter to determine the proper SEC_PRINCIPAL_NAME, SEC_PRINCIPAL_LOCATION, or SEC_PRINCIPAL_PASSVAR variable to use. However, the process failed to retrieve the bulletin board parameters. |
Action |
Contact BEA Customer Support. | |
6202 |
ERROR: Invalid environment. Check TUXCONFIG in environment and UBBCONFIG. | |
|
Description |
While attempting to initialize the public key subsystem, a process attempted to get bulletin board parameter to determine the proper SEC_PRINCIPAL_NAME, SEC_PRINCIPAL_LOCATION or SEC_PRINCIPAL_PASSVAR variable to use. However, the environment of the process was incorrect. |
Action |
Ensure that your TUXCONFIG environment variable matches the TUXCONFIG variable for the local machine in the UBBCONFIG. | |
See Also |
| |
6203 |
ERROR: Unable to initialize registry | |
|
Description |
The system was unable to initialize the registry. |
Action |
Contact BEA Customer Support. | |
See Also |
| |
6204 |
ERROR: Could not initialize public key subsystem | |
|
Description |
An error occurred while initializing the public key subsystem. Causes for this failure can include a user implementation of a plug-in function returning a failure code. |
Action |
Ensure the registry is in a valid state using | |
See Also |
| |
6205 |
WARN: Server initialization function did not call tx_open() or tpopen() or this call failed | |
|
Description |
This single-threaded server is part of a group that has an associated
resource manager,
and the server initialization function |
Action |
Include a call to | |
See Also |
| |
6206 |
WARN: Server thread initialization function did not call tx_open() or tpopen() or this call failed | |
|
Description |
This multi-threaded server is part of a group that has an associated
resource manager, and the server thread initialization function
|
Action |
Include a call to | |
See Also |
| |
6207 |
WARN: Destruction of public-key subsystem failed | |
|
Description |
An error occurred while trying to destroy the public key subsystem. The plug-in point implementing the destructor function may have failed. |
Action |
Contact your Security Service Interface Provider to get more information on the functionality of the public key subsystem destructor. | |
6212 |
WARN: Unable to invoke audit postop on security failure | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. In addition, because of the authentication failure, if the failure was not intended, check the registration, authentication configuration, and returns from the authentication security functions. | |
See Also |
| |
6213 |
WARN: Unable to invoke audit postop on security failure | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the
default supplied plugin, check the userlog file and filesystem space. If the
plugin used is not the default supplied plugin, check with the supplier of
the plugin code.
In addition, because of the | |
See Also |
| |
6214 |
WARN: Unable to invoke audit postop on service completion | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
See Also |
| |
6215 |
WARN: Unable to invoke audit postop on security failure | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the
default supplied plugin, check the userlog file and filesystem space. If the
plugin used is not the default supplied plugin, check with the supplier of
the plugin code.
In addition, because of the | |
See Also |
| |
6216 |
WARN: Unable to invoke audit preop on service invocation | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
See Also |
| |
6217 |
WARN: Unable to invoke audit postop on service invocation failure | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
See Also |
| |
6218 |
WARN: Unable to invoke audit postop on sevice completion | |
|
Description |
A call to the |
Action |
Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code. | |
See Also |
| |
6219 |
WARN: Destruction of audit subsystem failed | |
|
Description |
A call to the destroy function of the auditing plugin security function failed. This call was being attempted while a server was shutting down. |
Action |
Check the registration of the auditing plugin. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to ensure proper implementation of the destructor function. | |
See Also |
| |
6220 |
WARN: Destruction of authorization subsystem failed | |
|
Description |
A call to the destroy function of the authorization plugin security function failed. This call was being attempted while a server was shutting down. |
Action |
Check the registration of the authorization plugin. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to ensure proper implementation of the destructor function. | |
See Also |
| |
6221 |
WARN: Destruction of authentication subsystem failed | |
|
Description |
A call to the destroy function of the authentication plugin security function failed. This call was being attempted while a server was shutting down. |
Action |
Check the registration of the authentication plugin. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to ensure proper implementation of the destructor function. | |
See Also |
| |
6222 |
ERROR: Unable to read key | |
|
Description |
The system was unable to read the key from the TUXCONFIG file. The TUXCONFIG file may be corrupted. |
Action |
If the TUXCONFIG file is not corrupted, contact BEA Customer Support. | |
6223 |
ERROR: Unable to generate decryption schedule | |
|
Description |
The system was unable to generate a decryption schedule. |
Action |
Contact BEA Customer Support. | |
6224 |
ERROR: Unable to decrypt password | |
|
Description |
The system was unable to decrypt a SEC_PRINCIPAL_PASSWORD value from the TUXCONFIG file. This may happen if the TUXCONFIG file has been corrupted. |
Action |
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support. | |
6225 |
ERROR: Unable to open TUXCONFIG file to Resources section | |
|
Description |
The system was unable to open the TUXCONFIG. Either it has been removed, or has been corrupted. |
Action |
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support. | |
6226 |
ERROR: Unable to open Resources section of TUXCONFIG file | |
|
Description |
The system was unable to read the TUXCONFIG. Either it has been removed, or has been corrupted. |
Action |
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support. | |
6227 |
ERROR: Possibly corrupted key in database | |
|
Description |
The key used to encrypt passwords in the TUXCONFIG file is corrupted. |
Action |
Regenerate your last TUXCONFIG file from a UBBCONFIG file. | |
6228 |
ERROR: Error while decrypting password | |
|
Description |
The system could not decrypt a password found in the TUXCONFIG file. The TUXCONFIG file may have been corrupted. |
Action |
If the TUXCONFIG file is not corrupted, contact your Tuxedo System Technical Support. | |
6230 |
ERROR: Could not acquire authorization token | |
|
Description |
A fatal error occured while retrieving an authorization token from the AAA provider. |
Action |
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support. | |
6231 |
ERROR: Could not acquire auditing token | |
|
Description |
A fatal error occured while retrieving an auditing token from the AAA provider. |
Action |
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support. | |
6232 |
ERROR: FML32 error val adding AAA tokens with code val | |
|
Description |
A system error occurred when trying to attach the authorization and auditing tokens to a message during the sending of the message. |
Action |
If the plugin used is the default supplied plugin, contact BEA Customer Support. If the plugin used is not the default supplied plugin, check with the supplier of the plugin code to be sure the format of the tokens is valid. | |
6233 |
ERROR: Memory allocation failure with code val | |
|
Description |
An attempt to allocate space for a security token failed. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. | |
6234 |
ERROR: Authentication fails with error code val | |
|
Description |
A process that authenticates with itself, such as a server or a native client, was unable to complete the authentication. |
Action |
Contact BEA Customer Support. Report the value of val to technical support. | |
6235 |
ERROR: Error interoperating with older site. Error code val | |
|
Description |
The system was unable to interoperate with a site older than Tuxedo Release 7.1. The error code is val. This usually happens when a server receives a request from an older site. |
Action |
Contact BEA Customer Support. Report the value of val to technical support. | |
6236 |
WARN: Unable to invoke audit postop on service invocation failure | |
|
Description |
The audit postop for a service invocation failed. |
Action |
Contact your AAA (authentication, authorization, auditing) security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support. | |
6237 |
ERROR: Memory allocation error | |
|
Description |
An attempt to allocate space for an authorization token failed. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. | |
6238 |
ERROR: Memory allocation error | |
|
Description |
An attempt to allocate space for an auditing token failed. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. | |
6239 |
ERROR: Use -t server option to interoperate with sites older than 7.1 | |
|
Description |
A request from a site older than BEA Tuxedo Release 7.1 arrived at a server. However, the -t servopts option was not specified. In order to close a possible security hole, the administrator must explicitly tell the server that it is allowed to accept requests from older sites. |
Action |
If you wish to allow the server to interoperate with sites older than 7.1 then the CLOPT for the server must contain -t before the -- option. | |
See Also |
| |
6240 |
ERROR: Unable to acquire credentials. Error code val1, minor_status val2 | |
|
Description |
The workstation client or workstation handler was unable to acquire credentials. The engine error code was val1 and the GSSAPI minor status code was val2. |
Action |
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support. | |
6241 |
ERROR: Unable to get machine information for administrative client | |
|
Description |
Administrative clients acquire their name from the *MACHINE section of the TUXCONFIG file. This administrative client was unable to read the TUXCONFIG file. |
Action |
Contact BEA Customer Support. | |
6242 |
ERROR: Invalid user password | |
|
Description |
The password in the TPINIT->data field was incorrect. Either the AUTHSVR rejected the password or the corresponding user is unknown to the system. |
Action |
Try a different user name or password. | |
6243 |
ERROR: Unable to establish security context. Error code val, minor_status val | |
|
Description |
The workstation client or workstation handler was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2. |
Action |
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support. | |
6244 |
ERROR: Application password does not match | |
|
Description |
The password in the TPINIT->passwd field was incorrect. |
Action |
Verify the password and retry the operation. | |
6245 |
ERROR: User data is invalid | |
|
Description |
The password in the TPINIT->data field was incorrect. Either the AUTHSVR rejected the password or the corresponding user is unknown to the system. |
Action |
Verify the user name or password and retry the operation. | |
6246 |
ERROR: Insecure protocol detected | |
|
Description |
An insecure security protocol has been detected between two different processes. The Tuxedo System registry is misconfigured. |
Action |
Contact BEA Customer Support. | |
6247 |
ERROR: Unable to establish security context. Error code val, minor_status val | |
|
Description |
The native client or server was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2. |
Action |
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support. | |
6248 |
ERROR: Insecure protocol detected | |
|
Description |
An insecure security protocol has been detected between two different processes. The Tuxedo System registry is misconfigured. |
Action |
Contact BEA Customer Support. | |
6249 |
ERROR: Unable to establish security context. Error code val1, minor_status val2 | |
|
Description |
The native client or server was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2. |
Action |
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support. | |
6250 |
ERROR: The WSH does not posses the proper application password | |
|
Description |
The workstation client has discovered that the WSH does not posses the application password. The WSH may be an imposter, or data corruption may have occured on the wire. |
Action |
The WSH was not able to authenticate itself to the workstation client. A security attack may be underway. Contact BEA Customer Support. | |
6251 |
ERROR: A workstation client does not have a proper application password | |
|
Description |
The password in the TPINIT->passwd field of a workstation client was incorrect. |
Action |
A security attack may be underway. The client should be given the proper application password. Contact BEA Customer Support. | |
6252 |
ERROR: A workstation client does not have a proper application password | |
|
Description |
The password in the TPINIT->passwd field of a workstation client was incorrect. |
Action |
A security attack may be underway. The client should be given the proper application password. Contact BEA Customer Support. | |
6253 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The authorization fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support and report val. | |
6254 |
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 your BEA Customer Support. | |
6255 |
ERROR: Unable to resolve interception sequence (val) | |
|
Description |
The authorization fan-out implementation could not discover the list of intercepting implementations. |
Action |
Contact BEA Customer Support and report val. | |
6256 |
ERROR: tpsvrthrinit() failed | |
|
Description |
A call to |
Action |
Check prior specific | |
See Also |
| |
6257 |
ERROR: tpsvrthrinit() returned in transaction mode | |
|
Description |
An application server dispatched thread has been placed in transaction mode
during its initialization in an application-defined |
Action |
Fix the coding of the application-define | |
See Also |
| |
6258 |
ERROR: tpsvrthrinit() failed with outstanding message handles | |
|
Description |
A call to |
Action |
Fix the coding of the application-defined | |
See Also |
| |
6259 |
ERROR: tpsvrthrinit() failed with open conversations | |
|
Description |
A call to |
Action |
Fix the coding of the application-defined | |
See Also |
| |
6260 |
ERROR: tpsvrinit() failed with open conversations | |
|
Description |
A call to |
Action |
Fix the coding of the application-defined | |
See Also |
| |
6261 |
ERROR: An application association may not issue tpgetrply(TPGETANY) concurrently with tpgetrply for a specific cd | |
|
Description |
In a multithreaded application, two threads associated with the same
BEA Tuxedo context issued concurrent |
Action |
Change the coding of the application so that this case does not
occur. One possibility is to specify a specific handle on all
| |
See Also |
| |
6262 |
ERROR: An application association may not issue multiple concurrent tpgetrply(TPGETANY) calls | |
|
Description |
In a multithreaded application, two threads associated with the same
BEA Tuxedo context issued concurrent |
Action |
Change the coding of the application so that this case does not
occur. One possibility is to specify a specific handle on all
| |
See Also |
| |
6263 |
ERROR: An application association may not issue tpgetrply for a specific cd concurrently with tpgetrply(TPGETANY) | |
|
Description |
In a multithreaded application, two threads associated with the same
BEA Tuxedo context issued concurrent |
Action |
Change the coding of the application so that this case does not
occur. One possibility is to specify a specific handle on all
| |
See Also |
| |
6264 |
ERROR: Unable to establish security context. Error code val, minor_status val | |
|
Description |
The native client or server was unable to establish a security context. The engine error code was val1 and the GSSAPI minor status code was val2. |
Action |
Contact your AAA (authentication, authorization, auditing) security service provider. If you are using the default AAA security service from BEA, contact BEA Customer Support. Report val1 and val2 to technical support. | |
6265 |
ERROR: Invalid return from _tmpresend2. Required size (required) less than given size (given) | |
|
Description |
The |
Action |
Fix the implementation of _tmpresend2 to ensure more data is asked for than given. | |
See Also |
| |
6266 |
ERROR: Token container error string-val/numeric-val | |
|
Description |
The AAA security features pass tokens in an FML32 buffer. However, when construction this buffer, and FML32 error occurred. string-val is the string version of the FML error, while numeric-val is the numeric version of the error. |
Action |
Contact BEA Customer Support. | |
See Also |
| |
6267 |
ERROR: Memory allocation error | |
|
Description |
An attempt to allocate memory has failed. This occured while attempting to allocate memory in the server for a security token. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine. | |
6268 |
ERROR: Token container error string-val | |
|
Description |
An attempt to initialize the AAA container buffer with |
Action |
Contact BEA Customer Support. | |
See Also |
| |
6269 |
ERROR: Token container error string-val | |
|
Description |
An attempt to initialize the AAA container buffer with |
Action |
Contact BEA Customer Support. | |
See Also |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|