NATIVE /WS MESSAGES 1100 & Above

1100 ERROR: -n option is required

DESCRIPTION

The workstation listener (WSL) process was invoked without the -n option. This parameter contains the well-known network address used by the workstation listener, and is required. The WSL process is exiting due to the absence of a required option.

ACTION

Examine the configuration file and determine the change that needs to be made to the CLOPT argument for the WSL process. The -n option must occur, must have an appropriate option argument, and must be located after the double dash, -- , that separates &T; options from WSL specific options. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or may be updated while the system is shut down by reloading the configuration file through use of tmloadcf (1).

SEE ALSO

tmconfig (1), tmloadcf (1), WSL(5)

1101 ERROR: Bad hex number provided for listening address: bad_hex_value

DESCRIPTION

The workstation listener (WSL) process was invoked with a -n option that specified a hexadecimal value as an option-argument. However, the value specified was not a valid hexadecimal constant.

ACTION

Change the network address specified for the WSL so that it contains an even number of hexadecimal digits, and make certain that each digit is '0' through '9', 'A' through 'F', or 'a' through 'f'. Also, remember that the WSNADDR environment variable in client processes associated with this WSL must be set to this same address. The WSL -n option and its associated network address are part of the CLOPT parameter specified for the WSL process in the configuration file. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or may be updated while the system is shut down by reloading the configuration file through use of tmloadcf (1).

SEE ALSO

tmconfig (1), tmloadcf (1), ubbconfig (5), WSL(5)

1103 ERROR: Bad -m option

DESCRIPTION

The workstation listener (WSL) process was invoked with a -m option that specified an option-argument outside of the allowed range. The -m option specifies the minimum number of handlers that should be available in conjunction with this WSL at any given time. The legal range is between 0 and 255. The WSL process is exiting due to an error in its arguments.

ACTION

Change the value for the WSL -m option so that it is within the legal range. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or may be updated while the system is shut down by reloading the configuration file through use of tmloadcf (1).

SEE ALSO

tmconfig (1), tmloadcf (1), ubbconfig (5), WSL(5)

1104 ERROR: Bad -x option

DESCRIPTION

The workstation listener (WSL) process was invoked with a -x option that specified an option-argument outside of the allowed range. The -x option specifies the degree of multiplexing desired within each workstation handler. The legal range is between 1 and 32767. The WSL process is exiting due to an error in its arguments.

ACTION

Change the value for the WSL -x option so that it is within the legal range. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or may be updated while the system is shut down by reloading the configuration file through use of tmloadcf (1).

SEE ALSO

tmconfig (1), tmloadcf (1), ubbconfig (5), WSL(5)

1105 ERROR: Bad -M option

DESCRIPTION

The workstation listener (WSL) process was invoked with a -M option that specified an option-argument outside of the allowed range. The -M option specifies the maximum number of handlers that should be available in conjunction with this WSL at any given time. The legal range is between 1 and 32767. The WSL process is exiting due to an error in its arguments.

ACTION

Change the value for the WSL -M option so that it is within the legal range. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or may be updated while the system is shut down by reloading the configuration file through use of tmloadcf (1).

SEE ALSO

tmconfig (1), tmloadcf (1), ubbconfig (5), WSL(5)

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 <atmi.h> header file. In most cases, there will also be a preceding message in the userlog giving further information as to the cause of the error.

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

tperrno (5)

1107 ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV

DESCRIPTION

The &N; System msgrcv system call returned an error to the workstation handler process. A prior message in the userlog will provide more information as to the cause of the error.

ACTION

Examine the prior message in the userlog to determine the specific &N; System error associated with this msgrcv failure. If the failure is not transient and the WSH is still active, the WSL may need to restart this particular WSH .

SEE ALSO

Uunix_err (3), tperrno (5)

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 your BEA TUXEDO Technical 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 your BEA TUXEDO Technical 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 WSH process is running and its associated workstation client. Also, examine the userlog to see if any immediately preceding entries give a more detailed explanation for the error.

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 your BEA TUXEDO Technical 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 your BEA TUXEDO Technical 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 WSH process is running and its associated workstation client. Also, examine the userlog to see if any immediately preceding entries give a more detailed explanation for the error.

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 <atmi.h> .

ACTION

Examine the userlog for a prior message indicating a more exact cause of the error.

SEE ALSO

tperrno (5)

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 $APPDIR/.adm/.keydb has not been accidentally removed and that the TUXCONFIG file has not been corrupted. If either of these two files has been corrupted, it will be necessary to reload the TUXCONFIG 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 WSL or WSH tried to restore the message to its original unencrypted state, but this operation failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1124 ERROR: Broadcast message received with unknown type 'type_name' subtype 'subtype_name'

DESCRIPTION

The workstation handler process received a notification or broadcast message from a workstation node with a type not known to it. This may occur if the system administrator adds a user-defined type to the &T; typeswitch but does not rebuild the workstation handler using the new typeswitch.

ACTION

If this application makes use of an application-defined typeswitch, rebuild the workstation handler with the buildwsh (1) command using the same application typeswitch as in other clients and servers. If the application typeswitch feature is not being used, contact your BEA TUXEDO Technical 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 (D)BBL administrative server. The message is to be sent to the DBBL administrative server in MP mode and to the BBL administrative server in SHM mode, which in turn takes care of broadcasting the unsolicited message to the target application clients.

ACTION

Check the error number, tperrno, and determine why the workstation handler was not able to send the message. Most likely the (D)BBL administrative server queue is full. In this case, change the operating system tunable parameters to increase the maximum queue size. If tperrno is set to TPESYSTEM or TPEOS , check the userlog for other error messages that may indicate the exact nature of the problem and the reason for this failure.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpbroadcast (3), tperrno (5), ubbconfig (5)

1132 ERROR: Received message of type 'type' to tpinit() call

DESCRIPTION

The workstation handler that performs the tpinit call on behalf of workstation clients received a request to join a workstation client to the application. However, the message it received in conjunction with the request was not a TPINIT buffer, but of type type. The workstation handler will therefore remove the workstation client context from the workstation handler and return an error.

ACTION

If the workstation clients trying to join an application pass a buffer to the workstation handler, make sure that it is a TPINIT buffer.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpinit (3)

1133 ERROR: TPINIT information must be passed to tpinit() call in secure application

DESCRIPTION

Prior to performing a tpinit on behalf of a workstation client, the workstation handler must make sure a TPINIT structure is passed if the application requires client authentication. In this case, the TPINIT information was not passed even though client authentication is required. 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. An error message, with tperrno set to TPEPERM , is sent back to the workstation client.

ACTION

Make sure the workstation clients trying to join the secure application are passing the TPINIT information to the workstation handler.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpinit (3)

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 TPINIT buffer. The value sysclient is reserved by the system for the cltname field.

ACTION

Make sure the workstation client does not use sysclient as a client name.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpinit (3)

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 TPINIT buffer flags field. For client notification, the possible values for flags are as follows: TPU_SIG , TPU_DIP , or TPU_IGN .

ACTION

Make sure the client notification value in the TPINIT buffer flags field is set correctly for the workstation client that failed to join the application.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpinit (3)

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 TPINIT buffer datalen field. The length must be greater than or equal to zero.

ACTION

Make sure the data length value in the TPINIT buffer datalen field is set correctly for the workstation client that failed to join the application.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpinit (3)

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" , tpinit (3)

1139 ERROR: Failed to send message to authentication server, tperrno = tperrno_val

DESCRIPTION

The workstation handler failed to send the TPINIT information to the authentication server. The call to tpacall failed with tperrno set to tperrno_val. This failure will cause the workstation handler to return an error to the workstation client with tperrno set to TPEPERM .

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 TPESYSTEM or TPEOS , check the userlog for other error messages that may indicate the exact nature of the problem and the reason for this failure.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpinit (3), tpacall (3), tperrno (5)

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 (D)BBL administrative server a request to forward unsolicited message on behalf of the workstation client. The request was not sent because of an existing blocking condition on the (D)BBL administrative server queue.

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" , tpbroadcast (3)

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-phase challenge/response protocol must be followed

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-phase challenge/response message. This is not the case. The two-phase challenge/response protocol must be followed in a secure application. An error message, with tperrno set to TPEPERM , is sent back to the workstation client.

ACTION

Contact your BEA TUXEDO Technical 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 _tpcryptinit . It is part of an internal interface that is designed to support various methods of data encryption.

ACTION

This probably indicates that a &T; 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. _tpcryptinit may also fail because an invalid argument was given. In this case, contact your BEA TUXEDO Technical Support.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , encryption (3i)

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 _tprandkey . It is part of an internal interface that is designed to support various methods of data encryption.

ACTION

Check the error number and determine why _tprandkey failed. This probably indicates that a &T; or operating system error occurred. Check the user log for other error messages that may indicate the exact nature of the problem and reason for this failure. _tprandkey may also fail because an invalid argument was given. In this case, contact your BEA TUXEDO Technical Support.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , encryption (3i)

1145 ERROR: tpalloc() failed, tperrno = tperrno_val

DESCRIPTION

An attempt dynamically to allocate a buffer in the workstation handler failed. The call to tpalloc failed with tperrno set to tperrno_val.

ACTION

Check the error number and determine why tpalloc failed. Most likely, a system limit has been reached. Change the operating system tunables to increase the amount of space a process is allowed dynamically to allocate.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , tpalloc (3), tperrno (5)

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 tpinit on behalf of a workstation client before performing the security protocol. 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" , tpinit (3)

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 TPINIT structure identifying the connecting client against an uninterpreted ticket structure identifying the security agent's opinion of the client to determine if the connecting client should be granted access to the application. The function used to perform the validation is _tpvalidate(3i). It is part of an internal interface that is designed to support various methods of application authentication.

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 &T; 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. _tpvalidate may also fail because an invalid argument was given. In this case, contact your BEA TUXEDO Technical Support.

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 malloc failed while validating the ticket information passed to the workstation handler by the workstation client.

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 _tpsessionkey . It is part of an internal interface that is designed to support various methods of authentication.

ACTION

This probably means that a &T; 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. _tpsessionkey may also fail because an invalid argument was given or the ticket could not be processed because the workstation client was denied permission for an implementation specific reason. In this case, contact your BEA TUXEDO Technical Support.

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 _tpcrypt . It is part of an internal interface that is designed to support various methods of encryption.

ACTION

This probably means that a &T; 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. _tpcrypt may also fail because an invalid argument was given. In this case, contact your BEA TUXEDO Technical Support.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , encryption(3i)

1155 ERROR: Couldn't process message for workstation client

DESCRIPTION

The workstation handler failed to receive a message from the workstation client. The failure occurred in a low level routine that performs all manipulations on a message after it has been received. This includes decoding and post receive work. The message received has an invalid data size field in the message header.

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"

1156 ERROR: Decryption of challenge request failed

DESCRIPTION

While a &ws; client was attempting to join the application, decrypting the challenge request message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1157 ERROR: Encryption of challenge request failed

DESCRIPTION

While a &ws; client was attempting to join the application, encrypting the challenge request message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1158 ERROR: Couldn't create encryption/decryption schedule

DESCRIPTION

While a &ws; client was attempting to join the application, the encryption or decryption schedule could not be created.

ACTION

Contact your BEA TUXEDO Technical Support.

1159 ERROR: Failed to encode/decode establish connection request message

DESCRIPTION

While a &ws; client was attempting to join the application, encoding or decoding of the establish connection request message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1160 ERROR: Decryption of challenge reply failed

DESCRIPTION

While a &ws; client was attempting to join the application, decrypting the challenge reply message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1161 ERROR: Encryption of challenge reply failed

DESCRIPTION

While a &ws; client was attempting to join the application, encrypting the challenge reply message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1162 ERROR: Encoding/decoding of ticket request failed

DESCRIPTION

While a &ws; client was attempting to join the application, encoding or decoding the ticket request message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1163 ERROR: Encoding/decoding of ticket request failed

DESCRIPTION

While a &ws; client was attempting to join the application, encoding or decoding the ticket request message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1164 ERROR: Decryption of TPINIT buffer failed

DESCRIPTION

While a &ws; client was attempting to join the application, decrypting the TPINIT message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1165 ERROR: Encoding/decoding of TPINIT buffer failed

DESCRIPTION

While a &ws; client was attempting to join the application, encoding or decoding the TPINIT message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1166 ERROR: Encryption of TPINIT buffer failed

DESCRIPTION

While a &ws; client was attempting to join the application, encrypting the TPINIT message failed.

ACTION

Contact your BEA TUXEDO Technical Support.

1167 ERROR: Unknown work station message to process

DESCRIPTION

While a &ws; client was attempting to join the application, an unknown message type was encountered for processing.

ACTION

Contact your BEA TUXEDO Technical Support.

1168 ERROR: Tried to process unexpected message opcode 0xcode

DESCRIPTION

While a &ws; client was attempting to join the application, an unknown message type was encountered for processing.

ACTION

Contact your BEA TUXEDO Technical 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 -D option needs to be numeric. This error will cause the workstation listener not to be booted.

ACTION

Make sure the argument to the -D option is numeric.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL (5)

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 -M option needs to be numeric. This error will cause the workstation listener not to be booted.

ACTION

Make sure the argument to the -M option is numeric.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL(5)

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 -m option needs to be numeric. This error will cause the workstation listener not to be booted.

ACTION

Make sure the argument to the -m option is numeric.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL(5)

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 -t option needs to be numeric. This error will cause the workstation listener not to be booted.

ACTION

Make sure the argument to the -t option is numeric.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL(5)

1173 ERROR: Bad -t option

DESCRIPTION

An invalid argument was passed to the workstation listener command line option. The argument to the -t option needs to be in the range 1 to 255 inclusive. This error will cause the workstation listener not to be booted.

ACTION

Make sure the argument to the -t option is in the allowable range.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL(5)

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 -t> command line option can be used to specify the amount of time that should be allowed for a workstation client to complete initialization processing through the workstation handler before being timed out by the workstation listener. This number may need to be increased to avoid frequent timeouts.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL(5)

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 -m, -M, and -x options should be used to that effect.

SEE ALSO

"BEA TUXEDO /Workstation Guide" , WSL(5)

1176 ERROR: Sending of reply to tpconnect() call to client failed

DESCRIPTION

An attempt to send an acknowledgment of a tpconnect 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 your BEA TUXEDO Technical Support.

1177 ERROR: Sending of reply to tpdiscon() call to client failed

DESCRIPTION

An attempt to send an acknowledgment of a tpdiscon 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 your BEA TUXEDO Technical 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 your BEA TUXEDO Technical 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 &ws; client software with an older Workstation Handler. Contact your BEA TUXEDO Technical Support.

1180 ERROR: Sending of reply to tpconnect() call to client failed

DESCRIPTION

An attempt to send an acknowledgment of a tpconnect 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 your BEA TUXEDO Technical Support.

1182 ERROR: Invalid -T option = num

DESCRIPTION

The -T command line option for the /WS listener WSL had an invalid argument. The value must be greater than or equal to 0 and less than 70409299.

ACTION

Reconfigure the CLOPT for the WSL and reboot the process.

1183 ERROR: Expected numeric argument to -T option

DESCRIPTION

The -T command line option for the /WS listener WSL had a non-numeric argument.

ACTION

Reconfigure the CLOPT for the WSL and reboot the process.

1185 INFO: Userid: [user], Clientid: [client] timed out due to inactivity

DESCRIPTION

A /WS client attached to the application has been invalid for longer than the configured timeout value, specified via the -T command line option. The associated user name and client name are printed.

ACTION

No action required.

1186 ERROR: Cannot convert message with unknown protocol num

DESCRIPTION

The /WS Handler, WSH, received a message from a /WS client with an unknown protocol number, num.

ACTION

Check that the WSTYPE environment variable is correctly set so that encoding is done if necessary. Validate that the correct /WS software is being used with the associated WSH. You may need to contact your BEA TUXEDO Technical Support.

1187 ERROR: Cannot convert message from protocol num1 to num2

DESCRIPTION

The /WS Handler, WSH, received a message to or from a /WS client with a protocol version that cannot be converted.

ACTION

Contact your BEA TUXEDO Technical Support.

1188 ERROR: Unrecognized message format, release num

DESCRIPTION

The /WS Listener, WSL, received a connection message from a /WS client with an unknown protocol number, num.

ACTION

Check that the WSTYPE environment variable is correctly set so that encoding is done if necessary. Validate that the correct /WS software is being used with the associated WSL. You may need to contact your BEA TUXEDO Technical Support.

1189 ERROR: Received message of unknown type 'type' subtype 'subtype'

DESCRIPTION

The /WS Handler, WSH, received a typed buffer from a /WS client with an unknown type and/or subtype, indicated in the message.

ACTION

The /WS client must have a type switch that contains types and/or subtypes that are unknown to the WSH. These buffer types must be added to the type switch associated with the WSH.

ACTION

"BEA TUXEDO Administrator's Guide"

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

"BEA TUXEDO Administrator's Guide" , MIB (5), WS_MIB (5)

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

"BEA TUXEDO Administrator's Guide" , MIB (5), WS_MIB (5)

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

ACTION

Informational message, no action required.

1193 WARN: Obsolete option used, -t

DESCRIPTION

An obsolete option, -t, was specified in the command line options for a workstation listener server. This option is being replaced by the -I option, which takes a client initialization timeout value in seconds instead of the SCANUNIT multiple expected for the -t option.

ACTION

The -t option may be removed in future releases; therefore, the administrator should plan to transition workstation listener specifications to use the -I option. Since the administrator may not know at configuration time if the site where the listener may be run supports the -I option yet, the current implementation allows both on the command line and will use the last option found on the command line. Therefore, the recommended action is to add a corresponding -I option at the end of the command line options for the workstation listener. In environments where there are no pre-release 6.0 &T; sites, the -t option may be discarded entirely.

SEE ALSO

"BEA TUXEDO Administrator's Guide" , MIB (5), WSL(5), WS_MIB (5)

1194 ERROR: Invalid or non-numeric value specified for -I option, <val>

DESCRIPTION

The workstation listener command line options contained an invalid value for the -I option. This option requires a numeric value between 1 and 32,767 inclusive.

ACTION

Correct the value in the command line options and reboot the server.

SEE ALSO

"BEA TUXEDO Administrator's Guide" , MIB (5), WSL(5), WS_MIB (5)

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

"BEA TUXEDO Administrator's Guide" , netstat (1), MIB (5), WS_MIB (5)

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

"BEA TUXEDO Administrator's Guide" , tmshutdown (1), MIB (5), WS_MIB (5)

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

"BEA TUXEDO Administrator's Guide" , WSL(5)

1199 WARN: .SysClientDied: User usrname on LMID client died

DESCRIPTION

This message indicates that the client specified above exited the application without doing a tpterm(). A complete listing of the current attributes of the client are sent in the posted buffer. In the normal way, the clients should do a tpterm() before exiting the application.

ACTION

This is an informational message.

SEE ALSO

EVENT_MIB (5), TM_MIB (5)

NATIVE /WS MESSAGES 1200-1299

1200 INFO: .SysClientState: User usrname on LMID state change to state

DESCRIPTION

This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer.

ACTION

This is an informational message.

SEE ALSO

EVENT_MIB (5), TM_MIB (5)

1201 WARN: .SysClientSecurity: User usrname on LMID authentication failure

DESCRIPTION

This message indicates that the client specified above failed security validation when trying to join the application. A complete listing of the current attributes of the client are sent in the posted buffer.

ACTION

Check to make sure that this is not some hacker trying to gain access to your application data.

SEE ALSO

EVENT_MIB (5), TM_MIB (5)

1204 ERROR: Memory allocation failure error_info

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while decoding a /WS client message. Additional information about the problem is printed as part of the message.

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.

1205 ERROR: Memory allocation failure error_info

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while decompressing a /WS client message. Additional information about the problem is printed as part of the message.

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.

1206 ERROR: Memory allocation failure error_info

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while trying to compress a message. Additional information about the problem is printed as part of the message.

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.

1207 ERROR: Expected numeric argument to -c option

DESCRIPTION

A non-numeric argument was passed to the WSL -c option.

ACTION

Change the configuration of the WSL to have a numeric compression limit.

SEE ALSO

WSL(5)

1208 ERROR: Memory allocation failure error_info

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while trying to process a /WS client message for _tmpostrecv(). Additional information about the problem is printed as part of the message.

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.

1213 ERROR: Type switch uninitialization failure

DESCRIPTION

While processing a /WS client buffer, the buffer unintialization function, _tmuninitbuf(), returned an error.

ACTION

Check the buffer type switch to see that it is correctly set up (that the right uninitialization function is associated with the correct buffer type). If an application-defined buffer type, check the uninitialization function to see that it is coded correctly.

SEE ALSO

buffer(3), typesw(5)

1215 ERROR: Expected numeric argument to -k option

DESCRIPTION

A non-numeric argument was passed to the WSL -k option.

ACTION

Change the configuration of the WSL to have a numeric compression limit.

SEE ALSO

WSL(5)

1216 ERROR: Expected numeric argument to -p option

DESCRIPTION

The -p option to the workstation listener controls the minimum TCP port number which a workstation handler will attempt to listen. This port number must be numeric.

ACTION

Change the -p option to be numeric.

1217 ERROR: Expected numeric argument to -P option

DESCRIPTION

The -P option to the workstation listener controls the maximum TCP port number which a workstation handler will attempt to listen. This port number must be numeric.

ACTION

Change the -P option to be numeric.

1218 ERROR: The -p (minport) or -P (maxport) option is out of range

DESCRIPTION

minport must be less than or equal to maxport, and both must be less than or equal to 65535.

ACTION

Change the -p or -P option to comply with the restrictions.

1219 ERROR: Memory allocation failure

DESCRIPTION

While creating a data structure to keep track of TCP port numbers, the system ran out of memory.

ACTION

Make sure 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.

1220 ERROR: Exhausted all available ports

DESCRIPTION

The workstation listener has tried all TCP ports within the range specified by the -p and -P options. It could not bind to any of the TCP ports in the range.

ACTION

If there are more workstation handlers than ports available in the range specified by -p and -P , then a new handler will not be able to bind to any of the TCP ports in the allowable range. Do not forget about the TCP port which is used by the workstation listener as well. Increase the range specified by the -p and -P options.

1221 ERROR: Could not establish listening address address

DESCRIPTION

The workstation listener has tried all TCP ports within the range specified by the -p and -P options. It could not bind to any of the TCP ports in the range. The workstation listener could not bind to the given address.

ACTION

If there are more workstation handlers than ports available in the range specified by -p and -P , then a new handler will not be able to bind to any of the TCP ports in the allowable range. Do not forget about the TCP port which is used by the workstation listener as well. Increase the range specified by the -p and -P options. Make sure that address is correct.

1222 ERROR: Expected numeric argument to -z option

DESCRIPTION

The -z option to the workstation listener controls the minimum allowable encryption strength. This number must be numeric.

ACTION

Change the -z option to be numeric.

1223 ERROR: Expected numeric argument to -Z option

DESCRIPTION

The -z option to the workstation listener controls the maximum allowable encryption strength. This number must be numeric.

ACTION

Change the -Z option to be numeric.

1224 ERROR: Link Level Encryption add-on package is not installed

DESCRIPTION

The minimum number of encryption bits was greater than zero, but there is no link level encryption add-on package installed on this machine.

ACTION

Install the link level encryption package or change the minimum encryption bits (the -z option) to be zero.

1225 ERROR: Only 40 bit encryption is allowed

DESCRIPTION

The minimum number of encryption bits was greater than forty, but only the 40-bit link level encryption add-on package is installed on this machine.

ACTION

Install the 128-bit link level encryption package or change the minimum encryption bits (the -z option) to be zero or forty.

1226 ERROR: The -z (min) or -Z (max) must be 0, 40 or 128

DESCRIPTION

The only levels of encryption understood by the system are 0, 40 or 128.

ACTION

Ensure that both min and max are set only to 0, 40 or 128.

1229 WARN: A client failed encryption negotiation

DESCRIPTION

A workstation client attempted to log in to the system, but could not negotiate an acceptable encryption level.

ACTION

When workstation clients log into the system, they negotiate an encryption strength with the workstation listener. If the client and listener cannot agree on the level of encryption (for example, if the workstation listener demands 128-bit encryption and the client can only speak 40-bits encryption) then this message will appear. The administrator can either change the encryption policy of the workstation listener or workstation client.

1230 ERROR: Invalid security protocol

DESCRIPTION

An invalid opcode was attempted while the workstation listener was insecure.

ACTION

Monitor your network for malicious use. Contact your BEA TUXEDO Technical Support.

1231 ERROR: Memory allocation error

DESCRIPTION

While negotiating the Diffie-Hellman parameters, the workstation listener ran out of memory.

ACTION

Make sure 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.

1232 ERROR: Encryption negotiation protocol error

DESCRIPTION

An invalid opcode was attempted while the workstation listener was insecure.

ACTION

Monitor your network for malicious use. Contact your BEA TUXEDO Technical Support.

1233 ERROR: Unable to get encryption handle

DESCRIPTION

While negotiating the Diffie-Hellman parameters, the workstation listener had an error while attempting to get an encryption handle.

ACTION

Make sure 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.

1234 ERROR: Unable to establish negotiation parameters

DESCRIPTION

An invalid opcode was attempted while the workstation listener was insecure.

ACTION

Monitor your network for malicious use. Contact your BEA TUXEDO Technical Support.

1235 ERROR: Unable to send negotiation parameters

DESCRIPTION

While attempting to send the Diffie-Hellman parameters to the client, an error occurred.

ACTION

The network may have experienced an error, or the client waiting for the security packet may have been killed. If neither of these events has occurred, contact your BEA TUXEDO Technical Support.

1236 ERROR: Unable to begin encryption

DESCRIPTION

After establishing the shared key, an error occurred while starting encryption.

ACTION

Monitor your network for malicious use. Contact your BEA TUXEDO Technical Support.

1237 ERROR: tpnotify(TPACK) failed to reply, tperrno = tperrno

DESCRIPTION

The workstation handler sent an acknowledged unsolicited message to a client. However, that client never sent its acknowledgment.

ACTION

The network may have experienced an error, or the client waiting for the notification may have been killed. tperrno may provide clues as to the cause of this failure. If neither of these events has occurred, contact your BEA TUXEDO Technical Support.

1238 ERROR: Invalid security parameters

DESCRIPTION

The encryption level of the workstation listener is greater than zero bits, but the link level encryption package is not installed on this machine.

ACTION

The MIB may have changed the minimum encryption bits for this workstation handler. If the new value of the minimum encryption bits is greater than zero and the link level encryption package is not installed, then no clients will be able to log into the workstation handler. Change the minimum encryption value via the -z option to the workstation listener, or through the MIB with the TA_MINENCRYPTBITS member of the T_WSL class.

1239 ERROR: Invalid security parameters

DESCRIPTION

The encryption level of the workstation listener is greater than forty bits, but only the 40-bit link level encryption package is installed on this machine.

ACTION

The MIB may have changed the minimum encryption bits for this workstation handler. If the new value of the minimum encryption bits is greater than forty, then no clients will be able to log into the workstation handler. Change the minimum encryption value via the -z option to the workstation listener, or through the MIB with the TA_MINENCRYPTBITS member of the T_WSL class.

1240 ERROR: Failed to read server table entry, tperrno = tperrno

DESCRIPTION

The workstation listener was rebooting after a failure and could not read the server table.

ACTION

The bulletin board may be corrupted. tperrno may provide clues as to the cause of this failure. Contact your BEA TUXEDO Technical Support.

1241 ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed

DESCRIPTION

The workstation handler received an acknowledgment from a workstation client but was unable to forward the acknowledgment to the sender of the tpnotify.

ACTION

The originator of the tpnotify may have been killed. If the originator of the notify has not been killed, contact your BEA TUXEDO Technical Support.

1242 ERROR: Bad Internet type of listening address provided: address

DESCRIPTION

address is not a valid internet address.

ACTION

Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number . Other formats may be recognized. Change address to comply with the known formats. If you believe that your address is in the proper format, contact your BEA TUXEDO Technical Support.

1243 ERROR: -H hexadecimal value has to have an even length

DESCRIPTION

If an address starts with 0x, then that address must be an even length of characters.

ACTION

A hexidecimal character represents a nibble (4 bits). A byte is 8 bits. To fully specify a byte, two characters are needed. Change the address to have an even number of characters.

1244 ERROR: Memory allocation failure

DESCRIPTION

While creating a data structure for an address specified via the -H option, the system ran out of memory.

ACTION

Make sure 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.

1245 ERROR: Bad hexadecimal number provided for external address: address

DESCRIPTION

The hexadecimal address address from the -H option is in an improper format.

ACTION

Any address which starts with 0x must be a valid hexadecimal address. Valid hexadecimal characters are 0 - 9, a-f and A-F. Change address to comply with the known formats.

1246 ERROR: Bad Internet type of external address provided: address

DESCRIPTION

The internet address address from the -H option is in an improper format.

ACTION

Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number . Other formats may be recognized. Change address to comply with the known formats.

1247 ERROR: Memory allocation failure

DESCRIPTION

While allocating space for the binary representation of the -H option address, the system ran out of memory.

ACTION

Make sure 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.

1248 ERROR: Memory allocation failure

DESCRIPTION

While allocating space for the binary representation of the -H option address, the system ran out of memory.

ACTION

Make sure 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.

1249 ERROR: -H and -n have different length of network address

DESCRIPTION

If you are using an external address, then that address must have the same format as the -n option.

ACTION

Change the -H option to have the same format as the -n option.

1250 ERROR: External address can not be resolved val

DESCRIPTION

The Domain Name Service could not resolve the address given by the -H option.

ACTION

Make sure that the Domain Name Service knows the server represented by the address given in the -H option. If the name service does not know the server, reconfigure the name service properly. Change the address in the -H option to a name which is well known by the name service.

1251 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc 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 be a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1252 ERROR: Unable to determine license level

DESCRIPTION

While validating the value of the -c argument of the workstation listener, an error occurred while retrieving the current license attributes.

ACTION

Contact your BEA TUXEDO Technical Support.

1253 ERROR: Workstation compression configured, but no license for workstation compression was found

DESCRIPTION

You do not have a license to use workstation compression.

ACTION

Purchase a license for workstation compression. If you believe that you own and have installed the license for workstation compression, contact your BEA TUXEDO Technical Support.

1254 ERROR: Bad conversational sequence number

DESCRIPTION

Conversations are sequenced in order to provide protection. One of the conversational messages arrived out of order. The conversation has been disconnected, and if a transaction was active, it has been set to the ABORTONLY state.

ACTION

Look at the userlog to determine whether or not the BRIDGE has given up sending any messages to the message queue for the workstation handler. If it has, the operating system may need to be tuned to properly handle a high volume of messages. This problem may also be alleviated by using compression. This error may also occur when the BRIDGE is failing over to a new network link or failing back to an high priority link.

1255 WARN: Couldn't change to client context num, continuing

DESCRIPTION

An internal error was encountered while attempting to switch client contexts.

ACTION

Contact your BEA TUXEDO System Technical Support.

1256 WARN: .SysClientSecurity: User user on machine authentication failure

DESCRIPTION

This is the system event message which is posted when a user fails authentication.

ACTION

The action depends on the security policy of the user.

1257 ERROR: Couldn't create buffer for receiving messages

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed in the generic handler.

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.

1258 WARN: No client context space available in handler

DESCRIPTION

The maximum number of clients has been used up in the generic handler.

ACTION

Either increase the total number of clients allowable into the system, or do not attempt to connect to a loaded system.

1259 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed in the generic handler.

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.

1260 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed in the generic handler.

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.

1261 ERROR: tpinit() failed, tperrno = tperrno

DESCRIPTION

A client was unable to enter the system from the generic handler. The tperrno may give clues as to the cause of this failure.

ACTION

Contact your BEA TUXEDO System Technical Support.

1262 ERROR: tpchkauth() failed, tperrno = tperrno

DESCRIPTION

tpchkauth failed from the generic handler. The tperrno may give clues as to the cause of this failure.

ACTION

Contact your BEA TUXEDO System Technical Support.

1263 WARN: Forced shutdown of client; user name 'name'; client name 'client'

DESCRIPTION

A forced shutdown of the given user name and client name has been performed by the generic handler.

ACTION

None.

1264 WARN: .SysClientDied: User user on machine client died

DESCRIPTION

This is the event posted when a forced shutdown of the given user name on machine has been performed by the generic handler.

ACTION

None.

1265 ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV

DESCRIPTION

An operating system error occured in the generic handler while reading a message queue.

ACTION

Ensure the sanity of the sytem. Contact your BEA TUXEDO System Technical Support.

1266 ERROR: Received message of type 'type' to tpinit() call

DESCRIPTION

The only message type which tpinit takes is TPINIT. The generic handler found a type of type was given to tpinit.

ACTION

Ensure all clients of the generic handler provide the proper buffer type during tpinit.

1267 ERROR: TPINIT information must be passed to tpinit() call in secure application

DESCRIPTION

Secure applications must provide the TPINIT buffer to tpinit. A client of the generic handler in a secure application did not provide the TPINIT buffer.

ACTION

Ensure all clients of the generic handler provide a TPINIT buffer during tpinit in a secure application.

1268 ERROR: Invalid client name given 'client'.

DESCRIPTION

The given client is invalid in the application.

ACTION

Ensure that the TPINIT buffer passed to tpinit does not have the invalid client name.

1269 ERROR: Invalid length for TPINIT structure given

DESCRIPTION

An invalid TPINIT buffer has been processed by the generic handler.

ACTION

There may be a negative length in the TPINIT datalen field. Ensure no client passes a TPINIT buffer with a negative datalen field to the generic handler.

1270 ERROR: Failed to update registry table information

DESCRIPTION

The generic handler was not able to update the BEA TUXEDO registry information.

ACTION

Contact your BEA TUXEDO System Technical Support.

1271 ERROR: Failed to send message to authentication server, tperrno = tperrno

DESCRIPTION

The generic handler was not able to send the TPINIT buffer to the server offering AUTHSVC.

ACTION

Ensure that the authentication server is up and running, and that the AUTHSVC is currently advertised. Contact your BEA TUXEDO System Technical Support.

1272 WARN: Invalid notification option given, reset to TPU_IGN.

DESCRIPTION

The generic handler does not handle the notification option from the client.

ACTION

Ensure that all clients change the notification options to one which the generic handler is able to accept.

1273 INFO: .SysClientState: User user on machine state change to state

DESCRIPTION

This event is posted by the generic handler whenever the user on machine changes state. The new state is given in state.

ACTION

None.

1274 INFO: Abortively disconnecting workstation client user[user], client[client]

DESCRIPTION

The generic handler is disconnecting a client which is believed to be dead.

ACTION

None.

1275 INFO: Userid: [userid], Clientid: [clientid] timed out due to inactivity

DESCRIPTION

The generic handler timed out the given userid and clientid.

ACTION

None.

1276 ERROR: Received message with unknown release number value

DESCRIPTION

The WSH received a packet with an unknown release number value. The network may be having difficulty. If link level encryption is in use, this error may be an indication that an attack is in progress.

ACTION

If this error happens consistently, then contact the BEA TUXEDO System Technical Support.

1277 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed while initializing the WSL or WSH.

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.

1278 ERROR: Address conversion error

DESCRIPTION

The WSH had a problem converting an address from a binary format to a text format.

ACTION

If this error happens consistently, then contact the BEA TUXEDO System Technical Support.

1279 ERROR: descriptor allocation error

DESCRIPTION

The WSH was unable to allocate a network resource for the listening endpoint.

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.

1280 ERROR: Could not initialize network (error)

DESCRIPTION

The WSH or WSL could not initialize its network.

ACTION

Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO System Technical Support.

1281 ERROR: Could not initialize global information (error)

DESCRIPTION

The WSH or WSL could not initialize its network.

ACTION

Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO System Technical Support.

1282 ERROR: Failed to initialize network protocol information (error)

DESCRIPTION

The WSH or WSL could not initialize its network.

ACTION

Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO System Technical Support.

1283 ERROR: Network error (error) servicing network event

DESCRIPTION

The WSL encountered a severe error while handling network events.

ACTION

Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO System Technical Support.

1284 WARN: Failed to allocate a network resource (error)

DESCRIPTION

The WSH or WSL could not allocate a network descriptor for a remote connection.

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.

1285 ERROR: Expected numeric argument to -N option

DESCRIPTION

The -N option to the WSL requires a numeric argument greater than or equal to zero.

ACTION

Modify the -N option of the WSL to have a numeric argument in the proper range.

1286 ERROR: -K argument must be client, handler, both, or none

DESCRIPTION

The -K option for the WSL requires an argument of client, handler, both or none.

ACTION

Ensure that the -K option of the WSL is client, handler, both or none. Check your spelling.

1290 ERROR: Can't parse the address address

DESCRIPTION

While attempting to resolve address, an error occured.

ACTION

Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name and port number portion of address can be located by your server.

1291 ERROR: Can't resolve host name in address address

DESCRIPTION

While attempting to resolve the host name portion of address, an error occured.

ACTION

Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name portion of address can be located by your DNS server.

1292 ERROR: Unknown address type: address

DESCRIPTION

The given address does not correspond to a type known by the system.

ACTION

The BEA TUXEDO understands several types of address format. Addresses which start with // must be internet addresses. Addresses which start with 0x are hexadecimal representations of the address. Other formats may or may not be understood by the BEA TUXEDO.

1293 ERROR: Can't resolve port number in address address

DESCRIPTION

While attempting to resolve the port number portion of address, an error occured.

ACTION

Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the port number portion of address can be located by your server.

1294 ERROR: Can't convert the address address to binary format

DESCRIPTION

An error occured while converting address to an internal binary representation.

ACTION

Contact your BEA TUXEDO Technical Support.

1295 ERROR: Illegal character in the address address

DESCRIPTION

There is an illegal character in the port portion of address. Ports may only have alphanumeric characters.

ACTION

Remove the illegal character from the port portion of the address.

1296 ERROR: Missing port number in the address address

DESCRIPTION

address must have a port number portion.

ACTION

Supply a port number portion in the given address. Otherwise, the WSL or WSH cannot determine its listening endpoint properly.

1297 ERROR: Port number cant be bigger than value in the address address

DESCRIPTION

The port number portion of address is larger than the largest allowable port number of value.

ACTION

Change the port number to be within the specified range.

1287 WARN: Forced shutdown of client; user name 'name'; client name 'name'; workstation address 'xxx.xxx.xxx.xxx'

DESCRIPTION

This may result from shutting down a WSH when clients are connected, a client connection has timed out, the WSH was unable to send a network message to the client or an incorrect APP_PW (application password) was rejected during tpinit().

ACTION

If APP_PW is turned on (refer to your ubbconfig file and ubbconfig(5) ), then check with your system administrator to verify that you are using the correct application password for your BEA TUXEDO application.

1288 WARN: setsockopt() for SO_KEEPALIVE failed

The KEEPALIVE handler-side networking option was configured for a WSL/WSH pair, but could not be enabled.

/ACTION/

This error is ignored and WSH processing continues normally. However network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client timeout (WSL -T option) to reclaim resources associated with dead network connections.

SEE ALSO

WSL(5)

1289 WARN: KEEPALIVE option requested but not available on this platform

The KEEPALIVE handler-side networking option was configured for a WSL/WSH= pair, but could not be enabled because it is not available on this platform.

ACTION

This error is ignored and WSH processing continues normally. =20 However network errors may not be reported, or may be reported less= promptly. Consider enabling the inactive client timeout (WSL -T option) to reclaim resources associated with dead network connections.

SEE ALSO

WSL(5)