![]() |
![]() |
|
|
1001 |
ERROR: The MAXCONV parameter must be > 0 and < 32768. | |
|
Description |
The |
Action |
Correct the value for | |
See Also |
| |
1002 |
ERROR: The MIN parameter must be >=1 and <= 1000 | |
|
Description |
The |
Action |
Correct the value for | |
See Also |
| |
1003 |
ERROR: The MAX parameter must be >=1 and <= 1000 | |
|
Description |
The |
Action |
Correct the value for | |
See Also |
| |
1021 |
ERROR: The Primary and Backup LMIDs for a Group can't be the same. | |
|
Description |
In the GROUPS section of the |
Action |
Correct the value for | |
See Also |
| |
1022 |
WARN: The MIGRATE option was given without any Backup LMIDs present. | |
|
Description |
The Note that some versions of BEA TUXEDO system R4.2 have a bug where this warning will appear even though a backup Master machine was specified. |
Action |
Make sure that either the Master machine was made migratable (using the If only the Master is migratable, and the configuration looks ok, then this warning is probably due to the bug mentioned in the description. The message can be ignored in this case. | |
See Also |
| |
1036 |
ERROR: The AUTHSVC parameter is NULL or longer than len characters. | |
|
Description |
The |
Action |
Change the | |
See Also |
| |
1037 |
ERROR: MAXWSCLIENTS must be >= 0 and < 32768. | |
|
Description |
The |
Action |
Change the | |
See Also |
| |
1056 |
ERROR: Can't get Application Password | |
|
Description |
When the This error happens if |
Action |
If running | |
See Also |
| |
1057 |
WARN: Passwords do not match. Try again. | |
|
Description |
|
Action |
Re-enter the password correctly. | |
See Also |
| |
1058 |
ERROR: Too many failures to obtain application password. | |
|
Description |
After three failed attempts to read the application password, the |
Action |
Re-load the configuration again, entering matching password values. | |
See Also |
| |
1070 |
ERROR: Unable to forward message, sending it back | |
|
Description |
A server cleanup was underway. While draining the request queue, a function executed to (possibly) convert from one BEA TUXEDO system release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release. |
Action |
Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator. | |
1071 |
ERROR: Unable to forward message, sending it back | |
|
Description |
A server cleanup was underway. While attempting to forward messages, a function executed to (possibly) convert from one BEA TUXEDO system release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release. |
Action |
Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator. | |
1073 |
WARN: Client process pid - dropped message because server died, SERVICE=service_name | |
|
Description |
A server cleanup was underway. The BEA TUXEDO system logs a message to the userlog file indicating that the server had been cleaned up. |
Action |
Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator. | |
1074 |
WARN: Client process pid - dropped message because server and client died, SERVICE=service_name | |
|
Description |
A server cleanup was underway. The BEA TUXEDO system logs a message to the userlog file indicating that the server and client had died. |
Action |
Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator. | |
1081 |
ERROR: Unable to read RESOURCES section of TUXCONFIG file | |
|
Description |
A server cleanup was underway. The BEA TUXEDO system was unable to get information on the RESOURCES section from the |
Action |
Please examine the userlog for further information. If necessary, please contact the BEA TUXEDO system Administrator. | |
1082 |
ERROR: Execute permission denied, not application administrator | |
|
Description |
A server cleanup had been attempted, but the executor of this command did not have the proper permissions to execute the |
Action |
Please contact the BEA TUXEDO system Administrator. | |
1089 |
ERROR: Unable to read the *RESOURCES section of the TUXCONFIG file | |
|
Description |
The |
Action |
The shared memory might be corrupted. Check the permissions on all IPC or contact your BEA TUXEDO system Technical Support. See LIBTUX_CAT Message 607 for further explanation. | |
1090 |
ERROR: Execute permission denied, not application administrator | |
|
Description |
Execute permission was denied when a non-administrator was executing the |
Action |
Only the BEA TUXEDO system application administrator can execute the command. | |
1091 |
ERROR: Invalid option, duplicate option option | |
|
Description |
The |
Action |
Invoke the | |
See Also |
| |
1092 |
ERROR: tlisten could not set group id to group_id | |
|
Description |
The |
Action |
Verify that the user name or user id passed as an argument to the | |
See Also |
| |
1096 |
ERROR: Could not send broadcast to BBL (machine) | |
|
Description |
A A likely cause is UNIX system message queue blocking on the |
Action |
| |
See Also |
BEA TUXEDO Installation Guide, | |
1097 |
WARN: DBBL should not be receiving notifications | |
|
Description |
A |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
1098 |
ERROR: Can't create queue | |
|
Description |
Queues used for communication with the (D)BBL could not be created. |
Action |
Examine the userlog for further details. Contact your BEA TUXEDO system Technical Support. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|