|
|
2002 |
ERROR: Unable to send gssapi token message | |
|
Description |
An attempt to send a message to the workstation handler with security tokens during the authentication exchange failed. |
Action |
Check to see if the workstation handler process still exists and that there are no network problems with the connection to the handler. | |
2003 |
ERROR: Unable to get reply to gssapi token message | |
|
Description |
An attempt to get a reply off the network from the workstation handler during the authentication exchange failed. |
Action |
Check to see if the workstation handler process still exists and that there are no network problems with the connection to the handler. | |
2004 |
ERROR: Received message not intended for this client | |
|
Description |
A message received off the network from the workstation handler during the authentication exchange failed. The message did not have the proper id for exchange to this client. |
Action |
Check that there are no network problems with the connection to the handler as the message may have been corrupted. Contact BEA Customer Support. | |
2005 |
ERROR: gssapi function returned failure val | |
|
Description |
Calling of the |
Action |
Determine if the authentication failure was in error. If the failure was in error, take one of the following actions depending on whether the default supplied plugin is used. If the plugin used is the default supplied plugin, check the userlog for possible causes of the failure. If the plugin used is not the default supplied plugin, check any logfiles written by the plugin, then check with the supplier of the plugin code as required. | |
2006 |
ERROR: Unable to allocate space to save session key | |
|
Description |
An attempt to dynamically allocate memory from the operating system using
|
Action |
Ensure that 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 on the machine. | |
2007 |
ERROR: gssapi token reply returned an error | |
|
Description |
A message received over the network from the workstation handler during the authentication exchange returned with an error. The authentication exchange failed. |
Action |
If the authentication plugin used is the default supplied plugin, check other userlog messages for cause of security failure. If the plugin used is not the default supplied plugin, check logfiles, if any, or contact the supplier of the plugin code. | |
2008 |
ERROR: Unable to save the password | |
|
Description |
The call to save and encrypt the password failed. |
Action |
Check the userlog for any applicable messages. If no messages apply, contact BEA Customer Support. | |
2009 |
ERROR: Unable to initialize public key subsystem | |
|
Description |
An error occurred while initializing the public key subsystem. Possible causes for this failure include a user implementation of a plug-in function returning a failure code. |
Action |
Ensure that the registry is in a valid state with | |
See Also |
| |
2010 |
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, contact 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 return from the | |
See Also |
| |
2011 |
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, contact 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 return from the | |
See Also |
| |
2012 |
ERROR: The thread used for unsolicited message receipt failed to start | |
|
Description |
The Tuxedo application has specified THREAD as the notification method. However, the system is unable to create the thread used for unsolicited message receipt by the workstation client program. |
Action |
Make sure you have not exceeded the system defined limit of threads that can be run in the system. If you have not exceeded this limit, then contact BEA Customer Support. | |
See Also |
| |
2013 |
WARN: Could not join with the unsolicited message thread | |
|
Description |
The workstation client program is attempting to leave an application by calling tpterm() in a Tuxedo application that uses the THREAD notification method. The thread attempting to call tpterm() is unable to join the unsolicited message receipt thread. As a result, the unsolicited message receipt thread may still be running, and the system may be unable to reclaim resources used by this thread. |
Action |
Contact BEA Customer Support. | |
See Also |
| |
2015 |
ERROR: Security exchange failure val | |
|
Description |
The GSSAPI security token exchange ended in unexpected failure of code val. |
Action |
Contact your AAA security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support. | |
2016 |
WARN: Unable to invoke audit postop on security failure | |
|
Description |
The post-operation audit point for a login failure failed. |
Action |
Contact your AAA security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support. | |
2017 |
ERROR: Support for security connection has been moved to a plug-in interface | |
|
Description |
A special source-code facility of workstation clients was connection to a third-party security interface. This feature has been removed, and replaced with a plug-in interface. |
Action |
If your workstation client has need to connect to a security service, this can be achieved underneath a plug-in interface point. | |
2018 |
ERROR: Must set WSINTOPPRE71 to 'yes' in order to interoperate with handlers prior to release 7.1 | |
|
Description |
In order to close a potential security hole, clients must explicitly set this variable if they wish to allow interoperation with older workstation listeners and workstation handlers. If this variable is not set, then the workstation client will only run the newer, GSSAPI compliant security exchange. |
Action |
If your workstation client needs to talk to older workstaition listeners or workstation handlers then the WSINTOPPRE71 variable must be set to 'yes'. | |
2019 |
ERROR: Unable to send init request | |
|
Description |
The workstation client was unable to send the initialization opcode to the workstation handler. |
Action |
Check your network connection. If the network connection is valid, contact BEA Customer Support. | |
2020 |
ERROR: Unable to get reply to init request | |
|
Description |
The workstation client was unable to recieve the reply to the initialization opcode from the workstation handler. |
Action |
Check your network connection. If the network connection is valid, contact BEA Customer Support. | |
2021 |
ERROR: Invalid reply from init request | |
|
Description |
The workstation client recieved a reply from the workstation handler for the initialization opcode, but the reply was invalid. |
Action |
Check your network connection. If the network connection is valid, contact BEA Customer Support. | |
2022 |
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 |
| |
2023 |
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 |
| |
2024 |
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 |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|