|
|
1100 |
ERROR: -n option is required | |
|
Description |
The workstation listener ( |
Action |
Examine the configuration file and determine the change that needs to be made to the | |
See Also |
| |
1101 |
ERROR: Bad hex number provided for listening address: bad_hex_value | |
|
Description |
The workstation listener ( |
Action |
Change the network address specified for the | |
See Also |
| |
1103 |
ERROR: Bad -m option | |
|
Description |
The workstation listener ( |
Action |
Change the value for the | |
See Also |
| |
1104 |
ERROR: Bad -x option | |
|
Description |
The workstation listener ( |
Action |
Change the value for the | |
See Also |
| |
1105 |
ERROR: Bad -M option | |
|
Description |
The workstation listener ( |
Action |
Change the value for the | |
See Also |
| |
1106 |
ERROR: Error receiving unsolicited message, tperrno = tperrno_val | |
|
Description |
The workstation handler process experienced an error while receiving an unsolicited message. The numeric value of tperrno is also printed; this can aid in determination of a more exact cause for the problem. A numeric value of tperrno can be converted to a symbolic value by looking in the |
Action |
Examine the userlog for any immediately preceding messages giving further information as to the cause of the error. Also examine the userlog on the site that sent the failed unsolicited message for further clues as to the cause of the error. | |
See Also |
| |
1107 |
ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV | |
|
Description |
The UNIX System |
Action |
Examine the prior message in the userlog to determine the specific UNIX System error associated with this | |
See Also |
| |
1108 |
ERROR: Handler received unexpected unsolicited opcode opcode_value | |
|
Description |
The workstation handler process received an unsolicited message that contained an unexpected internal opcode. The opcode value is printed as part of the error message. |
Action |
Contact BEA Customer Support. | |
1109 |
ERROR: Failed to process broadcast message | |
|
Description |
The workstation handler process received a broadcast message to be forwarded to the appropriate workstation client(s). However, it was unable to process this message for forwarding to the workstation client(s). |
Action |
A previous message in the userlog may indicate a more precise cause of the error and indicate a corrective action to take. The workstations associated with this workstation handler did not receive the broadcast message sent to them. Depending on the particular situation, these workstations may need to be informed of the broadcast in another way. | |
1110 |
ERROR: 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. | |
1111 |
ERROR: Sending of broadcast message to client failed | |
|
Description |
The workstation handler process received a broadcast message to be forwarded to the appropriate workstation client(s). However, it was unable to process this message for forwarding to one of the workstation clients. Often, this is due to a network error. |
Action |
Make use of network management utilities to determine if any networking problems exist between the machine on which the | |
1112 |
ERROR: Failed to process notification message | |
|
Description |
The workstation handler process received a notification message to be forwarded to a workstation client. However, it was unable to process this message for forwarding to the workstation client. |
Action |
If a prior message in the userlog provides further explanation for the cause of the problem, follow the recommendations listed for that message. Otherwise, contact BEA Customer Support. | |
1113 |
ERROR: 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. | |
1114 |
ERROR: Sending of notification message to client failed | |
|
Description |
The workstation handler process received a notification message to be forwarded to a workstation client. However, it was unable to process this message for forwarding to the workstation client. Often, this is due to a network error. |
Action |
Make use of network management utilities to determine if any networking problems exist between the machine on which the | |
1120 |
ERROR: tpchkauth() failed, tperrno = tperrno_val | |
|
Description |
As part of its startup processing, the workstation handler process attempted to determine whether application authentication is required by this application configuration, but encountered an error trying to obtain this information. The numeric value of tperrno is printed as part of the error message; this may be converted to a symbolic value by examining |
Action |
Examine the userlog for a prior message indicating a more exact cause of the error. | |
See Also |
| |
1121 |
ERROR: Couldn't get administrative key for decrypting workstation client messages | |
|
Description |
The process was unable to access the encoded form of the password used to create the encryption/decryption schedule employed between the workstation handler and workstation clients. |
Action |
Verify that the process is running under the ID of the application administrator. Also, verify that the file | |
1122 |
ERROR: Restoring message to original condition after sending failed | |
|
Description |
The workstation listener or workstation handler process sent an encrypted message to a workstation client. After the send, the |
Action |
Contact BEA Customer Support. | |
1131 |
ERROR: tpbroadcast() or tpnotify() failed on send, tperrno = tperrno | |
|
Description |
The workstation handler that performs the tpbroadcast or tpbroadcast call on behalf of the workstation clients failed to forward the broadcast message to the |
Action |
Check the error number, tperrno, and determine why the workstation handler was not able to send the message. Most likely the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1132 |
ERROR: Received message of type 'type' to tpinit() call | |
|
Description |
The workstation handler that performs the |
Action |
If the workstation clients trying to join an application pass a buffer to the workstation handler, make sure that it is a | |
See Also |
BEA TUXEDO Workstation Guide, | |
1133 |
ERROR: TPINIT information must be passed to tpinit() call in secure application | |
|
Description |
Prior to performing a |
Action |
Make sure the workstation clients trying to join the secure application are passing the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1134 |
ERROR: Sending of reply to ticket protocol failed | |
|
Description |
The workstation handler failed to send the ticket reply back to the workstation client. The workstation handler will therefore unregister the workstation client from the Bulletin Board, remove the workstation client context from the workstation handler, and return an error. |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide | |
1135 |
ERROR: Invalid client name given 'cltname'. | |
|
Description |
While processing a workstation client's request to join the application, an invalid client name, cltname, was found in the |
Action |
Make sure the workstation client does not use | |
See Also |
BEA TUXEDO Workstation Guide, | |
1136 |
WARN: Invalid notification option given 0xoption, reset to TPU_IGN. | |
|
Description |
While processing a workstation client's request to join the application, an invalid notification option, option, was found in the |
Action |
Make sure the client notification value in the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1137 |
ERROR: Invalid length for TPINIT structure given | |
|
Description |
While processing a workstation client's request to join the application, an invalid data length was found in the |
Action |
Make sure the data length value in the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1138 |
ERROR: Failed to update registry table information | |
|
Description |
The workstation handler failed to update the workstation client information in the Bulletin Board's registry table. The workstation handler will therefore unregister the workstation client from the Bulletin Board, remove the workstation client context from the workstation handler, and return an error. |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide, | |
1139 |
ERROR: Failed to send message to authentication server, tperrno = tperrno_val | |
|
Description |
The workstation handler failed to send the |
Action |
Check the error number, tperrno_val, and determine why the call to the authentication server failed. Most likely, the authentication server is not booted. In this case, boot the authentication server. If tperrno_val is set to | |
See Also |
BEA TUXEDO Workstation Guide, | |
1140 |
WARN: tpbroadcast() or tpnotify() encountered blocking condition | |
|
Description |
The workstation handler failed to send an unsolicited message due to a blocking condition. The workstation handler is responsible for sending to the |
Action |
Most likely a system limit has been reached. You may wish to change the operating system tunable parameters related to the maximum size of a queue. | |
See Also |
BEA TUXEDO Workstation Guide, | |
1141 |
ERROR: Unable to assign connection request, can't create any more handlers | |
|
Description |
The workstation listener failed to start a new workstation handler. This may be due to no more workstation handlers being available, an error in the formatting of the command line for the workstation handler, an error in retrieving the machine table entry for the workstation listener in the Bulletin Board, or an error executing the workstation handler. |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide | |
1142 |
ERROR: For a secure application, the two | |
|
Description |
The workstation handler received a message over the network from a workstation client. No context exists for this client. When running in a secure application, the only message that can be accepted by the workstation handler from a workstation client with no context is a two |
Action |
Contact BEA Customer Support. | |
See Also |
BEA TUXEDO Workstation Guide | |
1143 |
ERROR: Failed to create encryption/decryption schedule | |
|
Description |
The workstation handler failed to create an encryption/decryption schedule. The function used to create the encryption/decryption schedule is called |
Action |
This probably indicates that a BEA TUXEDO system or operating system error occurred. Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide, | |
1144 |
ERROR: _tprandkey() failed tperrno = tperrno_val, could not generate random encryption key | |
|
Description |
The workstation handler failed to create a random key conforming to the restrictions of the encryption subsystem in use. The function used to create the random key is |
Action |
Check the error number and determine why | |
See Also |
BEA TUXEDO Workstation Guide, | |
1145 |
ERROR: tpalloc() failed, tperrno = tperrno_val | |
|
Description |
An attempt dynamically to allocate a buffer in the workstation handler failed. The call to |
Action |
Check the error number and determine why | |
See Also |
BEA TUXEDO Workstation Guide, | |
1146 |
ERROR: Sending of reply to challenge call to client failed | |
|
Description |
The workstation handler failed to send the challenge reply back to the workstation client. The workstation handler will therefore unregister the workstation client from the Bulletin Board, remove the workstation client context from the workstation handler, and return an error. |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide | |
1147 |
ERROR: Protocol error, can't process tpinit() request before performing security protocol | |
|
Description |
The workstation handler in a secure application received a request to perform a |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide, | |
1148 |
ERROR: Processing of message to be sent to client failed | |
|
Description |
The workstation handler failed to send a message to the workstation client. The failure occurred in a low level routine that performs all manipulations for the message send. This includes pre-send, encoding, and post-send work. The message being sent from the workstation handler to the workstation client had to do with the workstation client trying to join the application. During this phase, all messages are encrypted when they are sent across the network. The messages may also be encoded if the machines are not of the same type. The workstation handler failed to encrypt the message. |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide | |
1149 |
ERROR: Validation of TPINIT information failed | |
|
Description |
The workstation handler failed to validate the |
Action |
This probably indicates that the security ticket and tpinit information do not match, and the user should not be allowed to join the application. It can also mean that a BEA TUXEDO system or operating system error occurred. Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide, security(3i) | |
1150 |
ERROR: Incorrect timestamp value sent by workstation client | |
|
Description |
The workstation handler failed to validate the ticket information passed to it by a workstation client. The ticket information passed from the workstation client to the workstation handler does not match the timestamp information stored in the workstation handler. |
Action |
Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide | |
1152 |
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 be a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
See Also |
BEA TUXEDO Workstation Guide | |
1153 |
ERROR: Could not obtain session key from ticket | |
|
Description |
The workstation handler failed to retrieve a session key from a ticket in a secure application while trying to validate the ticket information passed to it by a workstation client. The function used to retrieve the session key is |
Action |
This probably means that a BEA TUXEDO system or operating system error occurred. Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide, security(3i) | |
1154 |
ERROR: Failed to encrypt ticket information | |
|
Description |
The workstation handler failed to encrypt data according to a schedule while accepting a challenge and timestamp value that is to be used to verify that the request is valid. The function used to encrypt data is |
Action |
This probably means that a BEA TUXEDO system or operating system error occurred. Check the userlog for other error messages that may indicate the exact nature of the problem and reason for this failure. | |
See Also |
BEA TUXEDO Workstation Guide, encryption(3i) | |
1156 |
ERROR: Decryption of challenge request failed | |
|
Description |
While a workstation client was attempting to join the application, decrypting the challenge request message failed. |
Action |
Contact BEA Customer Support. | |
1157 |
ERROR: Encryption of challenge request failed | |
|
Description |
While a workstation client was attempting to join the application, encrypting the challenge request message failed. |
Action |
Contact BEA Customer Support. | |
1158 |
ERROR: Couldn't create encryption/decryption schedule | |
|
Description |
While a workstation client was attempting to join the application, the encryption or decryption schedule could not be created. |
Action |
Contact BEA Customer Support. | |
1159 |
ERROR: Failed to encode/decode establish connection request message | |
|
Description |
While a workstation client was attempting to join the application, encoding or decoding of the establish connection request message failed. |
Action |
Contact BEA Customer Support. | |
1160 |
ERROR: Decryption of challenge reply failed | |
|
Description |
While a workstation client was attempting to join the application, decrypting the challenge reply message failed. |
Action |
Contact BEA Customer Support. | |
1161 |
ERROR: Encryption of challenge reply failed | |
|
Description |
While a workstation client was attempting to join the application, encrypting the challenge reply message failed. |
Action |
Contact BEA Customer Support. | |
1162 |
ERROR: Encoding/decoding of ticket request failed | |
|
Description |
While a workstation client was attempting to join the application, encoding or decoding the ticket request message failed. |
Action |
Contact BEA Customer Support. | |
1163 |
ERROR: Encoding/decoding of ticket request failed | |
|
Description |
While a workstation client was attempting to join the application, encoding or decoding the ticket request message failed. |
Action |
Contact BEA Customer Support. | |
1164 |
ERROR: Decryption of TPINIT buffer failed | |
|
Description |
While a workstation client was attempting to join the application, decrypting the |
Action |
Contact BEA Customer Support. | |
1165 |
ERROR: Encoding/decoding of TPINIT buffer failed | |
|
Description |
While a workstation client was attempting to join the application, encoding or decoding the |
Action |
Contact BEA Customer Support. | |
1166 |
ERROR: Encryption of TPINIT buffer failed | |
|
Description |
While a workstation client was attempting to join the application, encrypting the |
Action |
Contact BEA Customer Support. | |
1167 |
ERROR: Unknown work station message to process | |
|
Description |
While a workstation client was attempting to join the application, an unknown message type was encountered for processing. |
Action |
Contact BEA Customer Support. | |
1168 |
ERROR: Tried to process unexpected message opcode 0xcode | |
|
Description |
While a workstation client was attempting to join the application, an unknown message type was encountered for processing. |
Action |
Contact BEA Customer Support. | |
1169 |
ERROR: Expected numeric argument to -D option | |
|
Description |
An invalid argument was passed to the workstation listener command line option. The argument to the |
Action |
Make sure the argument to the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1170 |
ERROR: Expected numeric argument to -M option | |
|
Description |
An invalid argument was passed to the workstation listener command line option. The argument to the |
Action |
Make sure the argument to the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1171 |
ERROR: Expected numeric argument to -m option | |
|
Description |
An invalid argument was passed to the workstation listener command line option. The argument to the |
Action |
Make sure the argument to the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1172 |
ERROR: Expected numeric argument to -t option | |
|
Description |
An invalid argument was passed to the workstation listener command line option. The argument to the |
Action |
Make sure the argument to the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1173 |
ERROR: Bad -t option | |
|
Description |
An invalid argument was passed to the workstation listener command line option. The argument to the |
Action |
Make sure the argument to the | |
See Also |
BEA TUXEDO Workstation Guide, | |
1174 |
WARN: Disconnecting listener connection to workstation, connection timed out | |
|
Description |
The workstation listener will scan its handler table and time out any connections that are overdue, restart any dead handlers, and allocate any blocked connection requests to a handler that is available. When scanning this table, the workstation listener found a handler that was waiting for a connection that had timed out. The workstation listener went ahead and forced the connection closed. |
Action |
The workstation listener | |
See Also |
BEA TUXEDO Workstation Guide, | |
1175 |
WARN: Disconnecting listener connection to workstation, request timed out | |
|
Description |
The workstation listener will scan its handler table and time out any connections that are overdue, restart any dead handlers, and allocate any blocked connection requests to a handler that is available. When scanning this table, the workstation listener found a blocked connection request that had not been passed to an available handler. Since the time to assign a handler expired, the workstation listener went ahead and forced the connection closed. |
Action |
This probably indicates that the number of workstation clients that need to join the application can not be supported by the existing configuration. The workstation listener command line options should be reset to support a larger number of workstation clients. The workstation listener | |
See Also |
BEA TUXEDO Workstation Guide, | |
1176 |
ERROR: Sending of reply to tpconnect() 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. | |
1177 |
ERROR: Sending of reply to tpdiscon() 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. | |
1178 |
ERROR: Sending of reply to tpsend() call to client failed | |
|
Description |
An attempt to send an acknowledgment of a tpbroadcast request 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. | |
1179 |
ERROR: Unrecognized opcode: opcode | |
|
Description |
A message was received in the Workstation Handler requesting an operation that is not known. |
Action |
This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. It could indicate the use of newer workstation client software with an older Workstation Handler. Contact BEA Customer Support. | |
1180 |
ERROR: Sending of reply to tpconnect() 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. | |
1182 |
ERROR: Invalid -T option = num | |
|
Description |
The |
Action |
Reconfigure the | |
1183 |
ERROR: Expected numeric argument to -T option | |
|
Description |
The |
Action |
Reconfigure the | |
1185 |
INFO: Userid: [user], Clientid: [client] timed out due to inactivity | |
|
Description |
A workstation client attached to the application has been invalid for longer than the configured timeout value, specified via the |
Action |
No action required. | |
1186 |
ERROR: Cannot convert message with unknown protocol num | |
|
Description |
The workstation Handler, |
Action |
Check that the | |
1187 |
ERROR: Cannot convert message from protocol num1 to num2 | |
|
Description |
The workstation Handler, |
Action |
Contact BEA Customer Support. | |
1188 |
ERROR: Unrecognized message format, release num | |
|
Description |
The workstation Listener, |
Action |
Check that the | |
1190 |
INFO: Reestablished network address string | |
|
Description |
A previously suspended workstation listener process has been unsuspended and has reestablished its network address. |
Action |
Informational message, no action required. | |
See Also |
Administering the BEA TUXEDO System, | |
1191 |
INFO: Network address disabled | |
|
Description |
A workstation listener process has been suspended and has disabled its listening network address to disallow further incoming connections. |
Action |
Informational message, no action required. | |
See Also |
Administering the BEA TUXEDO System, | |
1192 |
INFO: Abortively disconnecting workstation client user[usr], client[clt] | |
|
Description |
A workstation handler is disconnecting the virtual circuit associated with a particular workstation client (usr>/clt) because of an administrative request to set the client state to |
Action |
Informational message, no action required. | |
1193 |
WARN: Obsolete option used, -t | |
|
Description |
An obsolete option, |
Action |
The | |
See Also |
Administering the BEA TUXEDO System, | |
1194 |
ERROR: Invalid or non-numeric value specified for | |
|
Description |
The workstation listener command line options contained an invalid value for the |
Action |
Correct the value in the command line options and reboot the server. | |
See Also |
Administering the BEA TUXEDO System, | |
1195 |
WARN: Failed to reestablish network address string | |
|
Description |
A previously suspended workstation listener server was administratively unsuspended but could not reestablish its network address. |
Action |
Failure to reestablish the network address is usually caused either by a failure of the network drivers on the machine to clear the previously held network address or by another process claiming the network address while the listener was suspended. In the former case, the network address will eventually be released by the system and the workstation listener will reestablish its network address through its periodic retry mechanism; therefore, no action is required in this case. In the latter case, local commands may be used to determine what process and user are occupying the network address, and they should be asked to relinquish the address. | |
See Also |
Administering the BEA TUXEDO System, | |
1196 |
INFO: Terminating handlers in preparation for shutdown | |
|
Description |
The workstation listener is shutting down and is about to terminate its associated workstation handler processes in preparation. |
Action |
Informational message, no action required. | |
See Also |
Administering the BEA TUXEDO System, | |
1197 |
INFO: Exiting system | |
|
Description |
The workstation listener has completed its shutdown and is exiting the system. |
Action |
Informational message, no action required. | |
See Also |
Administering the BEA TUXEDO System, | |
1199 |
WARN: .SysClientDied: User usrname on LMID client died | |
|
Description |
This message indicates that the client specified above exited the application without doing a |
Action |
This is an informational message. | |
See Also |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|