|
|
1001 |
ERROR: Unused arguments passed to buildwsh | |
|
Description |
The command line option passed to the |
Action |
Examine the command line that calls | |
See Also |
| |
1002 |
ERROR: Unable to execute the command command_string | |
|
Description |
While invoking the C compilation system to build a new Workstation Handler, an error was detected. This could happen for one of the following reasons:
|
Action |
Make sure the C compilation system is present on your machine. Make sure there is enough disk space available for the new Workstation Handler. This should be roughly the same as the existing | |
See Also |
| |
1004 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. Increase the space on the swap device. | |
See Also |
| |
1008 |
ERROR: Could not establish listening address on network string | |
|
Description |
This error occurs if the The format of the address supplied to the The address used in the The system has run out of network addresses for the A previously used address has not completed the close sequence. This occurs if the |
Action |
To correct the problem, match one of the following solutions with the problem descriptions above:
| |
See Also |
| |
1010 |
ERROR: Couldn't convert buffer to current release format | |
|
Description |
This error occurs if a Workstation client and the native UNIX system machine are of different TUXEDO System/T releases and the message is from an older release. The error can also occur if the message received by the |
Action |
Contact BEA Customer Support. | |
1011 |
ERROR: Couldn't convert buffer to native site format | |
|
Description |
The |
Action |
Check the userlog for a message indicating the nature of the failure (in particular, the type and subtype of the buffer that could not be converted). It may be necessary to rebuild the | |
See Also |
| |
1017 |
ERROR: Invalid data length, data not self describing | |
|
Description |
Pre-processing of the message being sent to the workstation client by the presend function for the buffer type failed. |
Action |
Check the userlog for additional messages indicating why the pre-processing failed. If the buffer type or the presend function is provided by the application, contact your system administrator. If this is one of the TUXEDO System/T-provided buffer types, contact BEA Customer Support. | |
See Also |
| |
1018 |
ERROR: Invalid data length of 0, data not self describing | |
|
Description |
Pre-processing of the message being sent to the workstation client by the presend function for the buffer type returned 0. This indicates that a message length of 0 was presented by the application and the buffer type is not self-describing, such that the presend function cannot infer the desired transfer length. |
Action |
The application must provide a length for sending messages of the particular buffer type. | |
See Also |
| |
1019 |
ERROR: Message conversion to workstation format failed | |
|
Description |
The |
Action |
This error should not occur. Contact BEA Customer Support. | |
1023 |
WARN: No client context space available in handler | |
|
Description |
While setting up a connection for a new workstation client, the |
Action |
This error should occur rarely since the | |
See Also |
| |
1024 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. Increase the space on the swap device. | |
See Also |
| |
1025 |
ERROR: Expected numeric argument to -x option | |
|
Description |
An invalid argument was passed to the Workstation Listener, |
Action |
Make sure the argument to the | |
See Also |
| |
1026 |
ERROR: Handler received unexpected message | |
|
Description |
The |
Action |
The message will be ignored. Contact BEA Customer Support. | |
1027 |
ERROR: Handler received unexpected opcode 0xcode | |
|
Description |
The |
Action |
The message will be ignored. Contact BEA Customer Support. | |
1028 |
WARN: Couldn't change to client context context_number, continuing | |
|
Description |
The Workstation Handler encountered an error switching to the context of a client when dropping all connections during shutdown. |
Action |
The connection is ignored. Contact BEA Customer Support. | |
1029 |
ERROR: Sending of reply message to client failed | |
|
Description |
While sending a reply message to a client, the operation failed. |
Action |
Check the userlog for messages indicating the nature of the failure. It may indicate that the client is no longer accessible (either the network or machine may have failed). Contact BEA Customer Support. | |
1030 |
INFO: Work Station Handler joining application | |
|
Description |
This message indicates that a |
Action |
No action required. | |
See Also |
| |
1031 |
ERROR: Invalid command line argument 'arg' ignored | |
|
Description |
An illegal command line option was found in the command line options for the |
Action |
This should be a rare event since the | |
See Also |
| |
1032 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. Increase the space on the swap device. | |
See Also |
| |
1033 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. Increase the space on the swap device. | |
See Also |
| |
1034 |
ERROR: Failed to attach to shared memory for listener table, errno = errno_val | |
|
Description |
The Workstation Handler, |
Action |
This is an operating system error. Check the value of errno_val for an indication of the problem. | |
1035 |
ERROR: Handler table entry already occupied by pid | |
|
Description |
The |
Action |
Contact BEA Customer Support. | |
See Also |
| |
1036 |
ERROR: Network provider returns a zero length network address, can't establish network address | |
|
Description |
The length of the network address that the |
Action |
Contact BEA Customer Support. | |
1037 |
ERROR: Can't synchronize with /WS listener ... continuing | |
|
Description |
The connection between the |
Action |
No action required, although the cause of | |
See Also |
| |
1038 |
WARN: Couldn't change to client context index, continuing | |
|
Description |
The Workstation Handler encountered an error switching to the context of a client when dropping all connections during shutdown. |
Action |
The connection is ignored. Contact BEA Customer Support. | |
1039 |
WARN: Can't use TPGETANY flag with tpcall() | |
|
Description |
The workstation client called |
Action |
No action required. | |
See Also |
| |
1040 |
WARN: tpsprio() call failed, tperrno = tperrno_val | |
|
Description |
A call to |
Action |
No action required. | |
See Also |
| |
1041 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. Increase the space on the swap device. | |
See Also |
| |
1042 |
ERROR: tpcall() call failed, tperrno = tperrno_val | |
|
Description |
A call to |
Action |
No action required. | |
See Also |
| |
1043 |
ERROR: tpacall() call failed, tperrno = tperrno_val | |
|
Description |
A call to |
Action |
No action required. | |
See Also |
| |
1044 |
ERROR: tpgprio() call failed, tperrno = tperrno_val | |
|
Description |
A call to |
Action |
No action required. | |
See Also |
| |
1045 |
ERROR: Sending of reply to tpacall() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1046 |
ERROR: Sending of reply to tpinit() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1047 |
ERROR: Sending of reply to tpterm() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1048 |
ERROR: Sending of error reply to call client failed | |
|
Description |
An attempt to send an acknowledgment message to the Workstation Client has failed. |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1049 |
ERROR: Couldn't create buffer for receiving messages | |
|
Description |
An attempt to create a buffer with |
Action |
This error indicates a resource problem. If there is not sufficient memory to allocate buffers, the Workstation Handler process can not operate. Please contact your System Administrator for help. If machine resources are sufficient, this would indicate an internal problem with the Workstation Handler. In this case, contact BEA Customer Support. | |
1050 |
ERROR: Error switching to the handler's context | |
|
Description |
The Workstation Handler was attempting to switch from a client context to the Workstation Handler context when it experienced an error. |
Action |
The error indicates an internal problem with the Workstation Handler. Contact BEA Customer Support. | |
1052 |
ERROR: Failed to process network event | |
|
Description |
The Workstation Handler was unable to process a network event using |
Action |
The error indicates an internal problem with the Workstation Handler or the | |
1053 |
ERROR: Error polling network connections | |
|
Description |
The Workstation Handler encountered an error polling a network connection using tmnwcpoll. |
Action |
The error indicates a network error. Check that the network connection to the Workstation Client has not gone down. If it has, the Workstation Client will have to rejoin the application. Contact BEA Customer Support. | |
1054 |
ERROR: Error generating network event list | |
|
Description |
The Workstation Handler encountered an error polling a network connection using tmnwcpoll. |
Action |
The error indicates a network error. Check that the network connection to the Workstation Client has not gone down. If it has, the Workstation Client will have to rejoin the application. Contact BEA Customer Support. | |
1055 |
ERROR: Connection to unassigned | |
|
Description |
The connection for the Workstation Client was timed out. |
Action |
This situation may happen if the system or the network is very busy, or if the network has gone down. The Workstation Client should try again to join the application. | |
1056 |
WARN: Couldn't change to client context index, continuing | |
|
Description |
The Workstation Handler encountered an error switching to the context of a client to do a |
Action |
This error indicates an internal problem. Contact BEA Customer Support. | |
1057 |
ERROR: Error processing message received from network | |
|
Description |
The Workstation Handler encountered an error receiving a message from the network. |
Action |
This error could indicate a network problem or an internal System/T problem. Contact BEA Customer Support. | |
1058 |
ERROR: Received message with opcode other than init for non-existant context | |
|
Description |
The Workstation Handler has received a message from a process that has not joined the application. |
Action |
This message indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support. | |
1059 |
ERROR: Received network message with unknown context | |
|
Description |
The Workstation Handler has received a message from a process that it does not know about. |
Action |
This message indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support. | |
1060 |
ERROR: Received message with context associated with a different connection | |
|
Description |
The Workstation Handler, working on behalf of one client context, has received a message intended for a different client context. |
Action |
This message indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support. | |
1061 |
ERROR: Received a reply message from a workstation | |
|
Description |
The Workstation Handler has received a message containing the reply protocol from a Workstation Client. |
Action |
A Workstation Client should never send a message with this protocol. This situation indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support. | |
1062 |
ERROR: Sending of reply to tpbegin() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1063 |
ERROR: No more workstation handlers available | |
|
Description |
An attempt to start a new Workstation Handler process has failed because the maximum limit of Workstation Handlers has already been started. |
Action |
The maximum number of Workstation Handlers specified in the configuration file have been started. In order to increase this number, the " | |
1064 |
ERROR: Error formatting command line options for handler | |
|
Description |
An error was encountered formatting the argument string needed for booting a Workstation Handler. |
Action |
This message would occur if there are more than 256 characters in the | |
See Also |
| |
1065 |
ERROR: Error retrieving machine table entry of the listener | |
|
Description |
An error was encountered trying to get internal machine information while booting a Workstation Handler. |
Action |
Contact BEA Customer Support. | |
1066 |
ERROR: Work Station Handler died, attempting restart | |
|
Description |
If a Workstation Handler process has died and the number of Workstation Handler processes booted is below the minimum specified in the configuration file, the BEA TUXEDO system attempts to boot a new Workstation Handler. This message is written to the userlog when this happens. |
Action |
Workstation Handlers should not die. If this happens, it could indicate an internal problem that requires attention. Additional Workstation Handlers may need to be booted, if the system is very busy. | |
1067 |
ERROR: Work Station Handler died, cleaning up | |
|
Description |
A Workstation Handler process has died and the number of Workstation Handler processes booted is below the minimum specified in the configuration file. An attempt to boot a new Workstation Handler has failed. |
Action |
This could either be an operating system error or an internal BEA TUXEDO system error. In the former case, please contact your system administrator. In the latter case, contact BEA Customer Support. | |
1068 |
ERROR: Invalid command line argument 'arg' ignored | |
|
Description |
An illegal command line option was found in the |
Action |
Check the BEA TUXEDO Reference Manual for correct options. | |
See Also |
| |
1069 |
ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
Contact BEA Customer Support. | |
1070 |
ERROR: Cannot boot | |
|
Description |
The Workstation Listener process has failed to boot because the |
Action |
The | |
1071 |
ERROR: Memory allocation failure | |
|
Description |
The Workstation Listener failed in an attempt to create a buffer for storing Workstation Handler information. |
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. Increase the space on the swap device. | |
See Also |
| |
1072 |
ERROR: Memory allocation failure | |
|
Description |
The Workstation Listener failed in an attempt to create a buffer for storing a device name. |
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. Increase the space on the swap device. | |
See Also |
| |
1073 |
ERROR: Memory allocation failure | |
|
Description |
The Workstation Listener failed in an attempt to create a buffer for storing a Workstation Handler's name. |
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. Increase the space on the swap device. | |
See Also |
| |
1074 |
ERROR: Memory allocation failure | |
|
Description |
The Workstation Listener failed in an attempt to create a buffer for storing a network address. |
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. Increase the space on the swap device. | |
See Also |
| |
1075 |
ERROR: Can't get machine entry for listener | |
|
Description |
The Workstation Listener encountered an error attempting to read the *MACHINES entry from the configuration file. |
Action |
Make sure the | |
1076 |
ERROR: Failed to create to shared memory for listener table, errno = errno_val | |
|
Description |
The Workstation Listener failed in an attempt to create a shared memory segment. |
Action |
This is an operating system error. Check the value of errno_val for an indication of the problem. | |
See Also |
| |
1077 |
ERROR: Failed to update server table entry, tperrno = tperrno_val | |
|
Description |
The Workstation Listener failed in an attempt to update the Bulletin Board. |
Action |
Check that the shared memory segment that contains the Bulletin Board has not been removed. If it has, then the application will need to be rebooted. Otherwise, this error would indicate an internal error. In this case, contact BEA Customer Support. | |
See Also |
| |
1078 |
ERROR: Failed to attach to shared memory for listener table, errno = errno_val | |
|
Description |
The Workstation Listener failed in an attempt to attach a shared memory segment. |
Action |
This is an operating system error. Check the value of errno_val for an indication of the problem. | |
See Also |
| |
1079 |
ERROR: Error starting minimum number of handlers | |
|
Description |
The Workstation Listener encountered an error attempting to boot the minimum number of Workstation Handlers. |
Action |
This could be an operating system error. Perhaps there are too many processes running. Or, this could be an internal error. Check the log file for other messages relating to this message. In this case, contact BEA Customer Support. | |
1080 |
ERROR: Error polling network connections | |
|
Description |
The Workstation Listener encountered an error polling a network connection. |
Action |
This error indicates a network error. Check with your system administrator to see if the network is down. | |
1082 |
ERROR: Error adding connection request to event list | |
|
Description |
The Workstation Listener was unable to allocate space on the event list. |
Action |
This error indicates a resource problem. If there is not sufficient memory to allocate buffers, the Workstation Listener process can not operate. Please contact BEA Customer Support for help. | |
1083 |
ERROR: Error assigning connection request, can't create any more handlers | |
|
Description |
The Workstation Listener was unable to start a new Handler. |
Action |
The most likely problem is that the maximum number of Workstation Handlers specified in the configuration file have been started. In order to increase this number, the Another possible source of the problem could be that the number of processes allowable by a user ( | |
1086 |
ERROR: Message conversion to release rel format failed | |
|
Description |
The Workstation Handler/Listener was unable to change the release structure to 4.2. |
Action |
Contact BEA Customer Support. | |
1088 |
ERROR: tpinit() failed, tperrno = tperrno_val | |
|
Description |
The |
Action |
Refer to the | |
See Also |
| |
1089 |
ERROR: tpscmt() failed, tperrno = tperrno_val | |
|
Description |
While attempting to commit a transaction on behalf of a workstation client, the workstation handler process was unable to set the transaction commit control characteristic for the transaction to |
Action |
Since the transaction cannot be committed, it will be necessary for the user to abort it. The value of | |
See Also |
| |
1090 |
ERROR: tpscmt() failed, tperrno = tperrno_val | |
|
Description |
While attempting to commit a transaction on behalf of a workstation client, the workstation handler process was unable to set the transaction commit control characteristic for the transaction to |
Action |
Since the transaction cannot be committed, it will be necessary for the user to abort it. The value of | |
See Also |
| |
1096 |
ERROR: Sending of reply to tpcommit() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1097 |
ERROR: Sending of reply to tpabort() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support. | |
1099 |
ERROR: Could not find correct number of active handlers, found num1, expected num2 | |
|
Description |
While being restarted after the death of a previous workstation listener process, the workstation listener found an inconsistency in the existing workstation specific shared memory regarding the number of workstation handler processes. The |
Action |
The administrator should check for any stray workstation handler ( |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|