System Messages: LIBTUX Catalog 6200-6299


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 Oracle 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 parameters 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 Oracle 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 parameters 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	`tmunloadcf`
6203	ERROR: Unable to initialize registry
	Description	The system was unable to initialize the registry.
	Action	Contact Oracle Customer Support.
	See Also	`epifreg`, `epifregedt`
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 `epifregedt`. Ensure the implementation of the plug-in function did not return an error code.
	See Also	`epifregedt`, `_ec_sec_map_proof`, `_ec_sec_pki_init`
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 `tpsvrinit`(3c) either did not make a call to `tx_open`(3c) or `tpopen`(3c) to open the resource manager, or else this call failed. (Note that the default versions of `tpsvrinit`(3c) and `tpsvrthrinit`(3c) include a call to `tx_open`(3c) for all single-threaded servers.) As a result of this failure, this thread of control will not be able to participate in Oracle Tuxedo global transactions.
	Action	Include a call to `tx_open`(3c) or `tpopen`(3c) within your server initialization function if not already present, or investigate the reason why the existing call failed.
	See Also	`tpsvrinit`(3c), `tpopen`(3c), `tx_open`(3c)
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 `tpsvrthrinit`(3c) either did not make a call to `tx_open`(3c) or `tpopen`(3c) to open the resource manager, or else this call failed. (Note that the default version of `tpsvrthrinit`(3c) includes a call to `tx_open`(3c).) As a result of this failure, this thread of control will not be able to participate in Oracle Tuxedo global transactions.
	Action	Include a call to `tx_open`(3c) or `tpopen`(3c) within your server thread initialization function if not already present, or investigate the reason why the existing call failed.
	See Also	`tpsvrthrinit`(3c), `tpopen`(3c), `tx_open`(3c)
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 `audit_postop()` plugin security function during initialization failed. This call was being attempted after the failure of authentication security. No audit of the attempt was able to be performed/recorded.
	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	`epifregedt`, `epifreg`
6213	WARN: Unable to invoke audit postop on security failure
	Description	A call to the `audit_postop()` plugin security function on a service operation failed. This call was being attempted due to a deny or failure return from the `authorize_postop()` plugin security function call, performed prior to a call to `tpforward()`. No audit of the failure was able to be performed/recorded.
	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 `authorize_postop()` deny or failure, if the denial was not intended, check the registration, authorization configuration, and return from the `authorize_postop()` function.
	See Also	`epifregedt`, `epifreg`
6214	WARN: Unable to invoke audit postop on service completion
	Description	A call to the `audit_postop()` plugin security function on a service operation failed. This call was being attempted after the operation execution, prior to a call to `tpforward()`. No audit of the failure was able to be performed/recorded.
	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	`epifregedt`, `epifreg`
6215	WARN: Unable to invoke audit postop on security failure
	Description	A call to the `audit_postop()` plugin security function on a service operation failed. This call was being attempted due to a deny or failure return from the `authorize_preop()` plugin security function call. No audit of the failure was able to be performed/recorded.
	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 `authorize_preop()` deny or failure, if the denial was not intended, check the registration, authorization configuration, and return from the `authorize_preop()` function.
	See Also	`epifregedt`, `epifreg`
6216	WARN: Unable to invoke audit preop on service invocation
	Description	A call to the `audit_preop()` plugin security function on a service operation failed. This call was being attempted prior to the operation execution. No audit of the attempt was able to be performed/recorded.
	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	`epifregedt`, `epifreg`
6218	WARN: Unable to invoke audit postop on sevice completion
	Description	A call to the `audit_postop()` plugin security function on a service operation failed. This call was being attempted after the operation execution. No audit of the completion of the operation was able to be performed/recorded.
	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	`epifregedt`, `epifreg`
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	`epifregedt`, `epifreg`
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	`epifregedt`, `epifreg`
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	`epifregedt`, `epifreg`
6222	ERROR: JRW 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 Oracle Customer Support.

6223	ERROR: JRW Unable to generate decryption schedule
	Description	The system was unable to generate a decryption schedule.
	Action	Contact Oracle Customer Support.

6224	ERROR: JRW 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 Oracle Systems, Inc., then contact Oracle 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 Oracle Systems, Inc., then contact Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle Systems, Inc., then contact Oracle 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 Oracle 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	`servopts`
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 Oracle, contact Oracle 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 Oracle 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 Oracle, contact Oracle 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.

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 Oracle 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 Oracle, contact Oracle 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 Oracle 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 Oracle, contact Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle Customer Support and report val.

6256	ERROR: tpsvrthrinit() failed
	Description	A call to `tpsvrthrinit()` failed. As a result of this failure, the thread in which the failure occurred will exit. This failure may be caused by an application-defined `tpsvrthrinit()` function returning -1.
	Action	Check prior specific `tpsvrthrinit()` messages or verify the return code from an application-defined `tpsvrthrinit()` function.
	See Also	`tpsvrthrinit`(3c)
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 `tpsvrthrinit()` function. `tpsvrthrinit()` returned while still in transaction mode. Oracle Tuxedo will abort the outstanding transaction and the thread where the error occurred will exit.
	Action	Fix the coding of the application-define `tpsvrthrinit()` function so that it commits or aborts any transaction started in this function before returning.
	See Also	`tpsvrthrinit`(3c)
6258	ERROR: tpsvrthrinit() failed with outstanding message handles
	Description	A call to `tpsvrthrinit()`, although returning success, failed to receive all outstanding reply messages and therefore has outstanding handles. As a result of this error, the thread in which the error occurred will exit. This error should only happen when an application-defined `tpsvrthrinit()` function is used.
	Action	Fix the coding of the application-defined `tpsvrthrinit()` function so that it does not return with outstanding handles.
	See Also	`tpsvrthrinit`(3c)
6259	ERROR: tpsvrthrinit() failed with open conversations
	Description	A call to `tpsvrthrinit()`, although returning success, had one or more conversations open at the time of return. As a result of this error, the thread in which the error occurred will exit. This error should only happen when an application-defined `tpsvrthrinit()` function is used.
	Action	Fix the coding of the application-defined `tpsvrthrinit()` function so that it does not return with open conversations.
	See Also	`tpsvrthrinit`(3c)
6260	ERROR: tpsvrinit() failed with open conversations
	Description	A call to `tpsvrinit()`, although returning success, had one or more conversations open at the time of return. As a result of this error, the server will exit. This error should only happen when an application-defined `tpsvrinit()` function is used.
	Action	Fix the coding of the application-defined `tpsvrinit()` function so that it does not return with open conversations.
	See Also	`tpsvrinit`(3c)
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 Oracle Tuxedo context issued concurrent `tpgetrply()` calls. The first `tpgetrply()` call tried to retrieve a reply for a specific call descriptor. While this call was still outstanding, a second `tpgetrply()` call tried to retrieve a reply for any outstanding call descriptor. This is not allowed by the system. As a result, the second `tpgetrply()` wrote this userlog message and returned -1 with `tperrno` set to `TPEPROTO`.
	Action	Change the coding of the application so that this case does not occur. One possibility is to specify a specific handle on all `tpgetrply()` calls, which is allowed even if the calls are performed concurrently. Another possibility is to dedicate one thread in each context to retrieve all replies for that context. Other valid possibilities also exist.
	See Also	`tpgetrply`(3c)
6262	ERROR: An application association may not issue multiple concurrent tpgetrply(TPGETANY) calls
	Description	In a multithreaded application, two threads associated with the same Oracle Tuxedo context issued concurrent `tpgetrply()` calls with the TPGETANY flag. This is not allowed by the system. As a result, the second `tpgetrply()` call wrote this userlog message and returned -1 with `tperrno` set to `TPEPROTO`.
	Action	Change the coding of the application so that this case does not occur. One possibility is to specify a specific handle on all `tpgetrply()` calls, which is allowed even if the calls are performed concurrently. Another possibility is to dedicate one thread in each context to retrieve all replies for that context. Other valid possibilities also exist.
	See Also	`tpgetrply`(3c)
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 Oracle Tuxedo context issued concurrent `tpgetrply()` calls. The first `tpgetrply()` call tried to retrieve a reply for any outstanding call descriptor. While this call was still outstanding, a second `tpgetrply()` call tried to retrieve a reply for a specific call descriptor. This is not allowed by the system. As a result, the second `tpgetrply()` call wrote this userlog message and returned -1 with `tperrno` set to `TPEPROTO`. The call descriptor specified by the second `tpgetrply()` call is still valid until retrieved by either the first `tpgetrply()` call or some `tpgetrply()` call issued in the future.
	Action	Change the coding of the application so that this case does not occur. One possibility is to specify a specific handle on all `tpgetrply()` calls, which is allowed even if the calls are performed concurrently. Another possibility is to dedicate one thread in each context to retrieve all replies for that context. Other valid possibilities also exist.
	See Also	`tpgetrply`(3c)
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 Oracle, contact Oracle 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 `_tmpresend2` function in the buffer type switch can ask the system for more space if necessary. However, it must always ask for more space than it was given. However, in this case required is less than given.
	Action	Fix the implementation of _tmpresend2 to ensure more data is asked for than given.
	See Also	`buffer(3i)`
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 Oracle Customer Support.
	See Also	`Fchg32`, `Fadd32`
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 `Finit32` failed. The error was string-val.
	Action	Contact Oracle Customer Support.
	See Also	`Finit32`
6269	ERROR: Token container error string-val
	Description	An attempt to initialize the AAA container buffer with `Finit32` failed. The error was string-val.
	Action	Contact Oracle Customer Support.
	See Also	`Finit32`
6270	ERROR: Memory allocation failure.
	Description	An attempt dynamically to allocate memory from the operating system failed.
	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 on the machine.

6271	ERROR: Memory allocation failure.
	Description	An attempt dynamically to allocate memory from the operating system failed.
	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 on the machine.

6272	ERROR: Unable to get bulletin board parameters
	Description	A failure to retrieve bulletin board parameters occurred while attempting to shut down the audit and authorization subsystems.
	Action	Contact Oracle Customer Support.

6274	ERROR: TMNOTHREADS set to yes but multiple threads detected: string-val/string-val
	Description	The setting of the TMNOTHREADS environment variable specifies the application to be single-threaded, but Oracle Tuxedo has detected that the application is multi-threaded.
	Action	Set the TMNOTHREADS environment variable to match the application.

6275	*ERROR: Unable to initialize public key subsystem (numeric-val)*
	Description	An error occurred when initializing the public key subsystem. The specific error is indicated by the decimal number in the error message.
	Action	Make sure that your public key proof material is specified correctly. Resolve previous errors, if any occurred. Contact Oracle Customer Support if you are unable to resolve this problem.

6276	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 Oracle Customer Support.

6277	ERROR: Unable to generate decryption schedule
	Description	The system was unable to generate a decryption schedule.
	Action	Contact Oracle Customer Support.

6278	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.