Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
WLE Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

ISNAT Messages 1100-1199

1100	ERROR: -n option is required
	Description	The IIOP Server Listener process was invoked without the -n option. This parameter contains the well-known network address used by the IIOP Server Listener, and is required. The IIOP Server Listener 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 IIOP Server Listener process. The -n option must occur, must have an appropriate option argument, and must be located after the double dash (--) that separates WLE options from ISL specific options. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or while the system is shut down by reloading the configuration file through use of tmloadcf (1).
	See Also	The tmconfig (1) and tmloadcf (1) commands and the ISL command. For information about the tmconfig (1) and tmloadcf (1) commands, see the BEA TUXEDO Reference Manual. For information about the ISL command, see the Administration Guide.
1103	ERROR: Bad -m option
	Description	The IIOP Server Listener process was invoked with an -m option that specified an option argument outside the allowed range. The -m option specifies the minimum number of handlers that should be available at any given time in conjunction with this IIOP Server Listener. The legal range is between 0 and 255. The IIOP Server Listener process is exiting due to an error in its arguments.
	Action	Change the value for the ISL command -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 while the system is shut down by reloading the configuration file through use of tmloadcf (1).
	See Also	The tmconfig (1), tmloadcf (1), and ubbconfig (5) commands and the ISL command. For information about the tmconfig (1), tmloadcf (1), and ubbconfig (5) commands, see the BEA TUXEDO Reference Manual. For information about the ISL command, see the Administration Guide.
1104	ERROR: Bad -x option
	Description	The IIOP Server Listener process was invoked with an -x option that specified an option argument outside the allowed range. The -x option specifies the degree of multiplexing desired within each IIOP Server Handler. The legal range is between 1 and 32767. The IIOP Server Listener process is exiting due to an error in its arguments.
	Action	Change the value for the ISL command -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 while the system is shut down by reloading the configuration file through use of tmloadcf (1).
	See Also	The tmconfig (1), tmloadcf (1), and ubbconfig (5) commands and the ISL command. For information about the tmconfig (1), tmloadcf (1), and ubbconfig (5) commands, see the BEA TUXEDO Reference Manual. For information about the ISL command, see the Administration Guide.
1105	ERROR: Bad -M option
	Description	The IIOP Server Listener process was invoked with an ISL command -M option that specified an option argument outside the allowed range. The -M option specifies the maximum number of handlers that should be available at any given time in conjunction with this IIOP Server Listener. The legal range is between 1 and 32767. The IIOP Server Listener process is exiting due to an error in its arguments.
	Action	Change the value for the ISL command -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 while the system is shut down by reloading the configuration file through use of tmloadcf (1).
	See Also	The tmconfig (1), tmloadcf (1), and ubbconfig (5) commands and the command. For information about the tmconfig (1), tmloadcf (1), and ubbconfig (5) commands, see the BEA TUXEDO Reference Manual. For information about the ISL command, see the Administration Guide.
1106	ERROR: Error receiving unsolicited message, tperrno = tperrno_val
	Description	The IIOP Server Handler process experienced an error while receiving an unsolicited message. The numeric value of tperrno is also printed; this value can aid in determining the exact cause of the problem. You can convert a numeric value of tperrno to a symbolic value by looking in the <atmi.h> header file. In most cases, there is also a preceding message in the user log that gives further information as to the cause of the error.
	Action	Examine the user log for any immediately preceding messages giving further information as to the cause of the error. Also examine the user log on the site that sent the failed unsolicited message for further clues as to the cause of the error. Contact BEA Technical Support.
	See Also	The tperrno(5) command. For information about the tperrno(5) command, see the BEA TUXEDO Reference Manual.
1107	ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
	Description	The UNIX system msgrcv system call returned an error to the IIOP Server Handler process. A prior message in the user log provides more information as to the cause of the error.
	Action	Examine the prior message in the user log to determine the specific UNIX system error associated with this msgrcv failure. If the failure is not transient and the IIOP Server Handler is still active, the IIOP Server Listener may need to restart this particular IIOP Server Handler. Contact BEA Technical Support.
	See Also	The tperrno (5) and Uunix_err (3c) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1108	ERROR: Handler received unexpected unsolicited opcode opcode_value
	Description	The IIOP Server 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 Technical Support.
1109	ERROR: Failed to process broadcast message
	Description	The IIOP Server Handler process received a broadcast message to be forwarded to the appropriate client application(s). However, it was unable to process this message for forwarding to the client application(s).
	Action	A previous message in the user log may indicate a more precise cause of the error and may indicate a corrective action. The client applications associated with this IIOP Server Handler did not receive the broadcast message sent to them. Depending on the particular situation, these client applications may need to be informed of the broadcast in another way. Contact BEA Technical Support.
1110	ERROR: Couldn't change to client context context_number, continuing
	Description	IIOP Server Handler encountered an error when switching to the context of a client application when dropping all connections during shutdown.
	Action	The connection is ignored. Contact BEA Technical Support.
1111	ERROR: Sending of broadcast message to client failed
	Description	The IIOP Server Handler process received a broadcast message to be forwarded to the appropriate client application(s). However, it was unable to process this message for forwarding to one of the client applications. Often, this error is due to a network error.
	Action	Use network management utilities to determine whether any networking problems exist between the machine on which the IIOP Server Handler process is running and its associated client application. Also, examine the user log to see whether any immediately preceding entries give a more detailed explanation for the error. Contact BEA Technical Support.
1112	ERROR: Failed to process notification message
	Description	The IIOP Server Handler process received a notification message to be forwarded to a client application. However, it was unable to process this message for forwarding to the client application.
	Action	If a prior message in the user log provides further explanation for the cause of the problem, follow the recommendations listed for that message. Otherwise, contact BEA Technical Support.
1113	ERROR: Couldn't change to client context context_number, continuing
	Description	The IIOP Server Handler encountered an error switching to the context of a client application when dropping all connections during shutdown.
	Action	The connection is ignored. Contact BEA Technical Support.
1114	ERROR: Sending of notification message to client failed
	Description	The IIOP Server Handler process received a notification message to be forwarded to a client application. However, it was unable to process this message for forwarding to the client application. Often, this error is due to a network error.
	Action	Use network management utilities to determine whether any networking problems exist between the machine on which the IIOP Server Handler process is running and its associated client application. Also, examine the user log to see whether any immediately preceding entries give a more detailed explanation for the error. Contact BEA Technical Support.
1120	ERROR: tpchkauth() failed, tperrno = tperrno_val
	Description	As part of its startup processing, the IIOP Server Handler process attempted to determine whether application authentication is required by this application configuration, but encountered an error while trying to obtain this information. A numeric value of tperrno is printed as part of the error message; you can convert this value to a symbolic value by examining <atmi.h>.
	Action	Examine the user log for a prior message indicating a more exact cause of the error. Contact BEA Technical Support.
	See Also	The tperrno (5) command. For information about this command, see the BEA TUXEDO Reference Manual.
1121	ERROR: Couldn't get administrative key for decrypting 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 IIOP Server Handler and client applications.
	Action	Verify that the process is running under the system administrator's ID. 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 is corrupted, you need to reload the TUXCONFIG file. Contact BEA Technical Support.
1122	ERROR: Restoring message to original condition after sending failed
	Description	Either the IIOP Server Listener or the IIOP Server Handler process sent an encrypted message to a client application. After the send, the IIOP Server Listener or IIOP Server Handler tried to restore the message to its original unencrypted state, but the operation failed.
	Action	Contact BEA Technical Support.
1124	ERROR: Broadcast message received with unknown type 'type_name' subtype 'subtype_name'
	Description	The IIOP Server Handler process received a notification or broadcast message from a node with an unknown type.
	Action	Contact BEA Technical Support.
1131	ERROR: tpbroadcast() or tpnotify() failed on send, tperrno = tperrno
	Description	The IIOP Server Handler that performs the tpbroadcast or tpnotify call on behalf of the client applications 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 client applications.
	Action	Check the error number, tperrno, and determine why the IIOP Server 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 user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
	See Also	The tpbroadcast (3c), tperrno (5), and ubbconfig (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1132	ERROR: Received message of type 'type' to tpinit() call
	Description	The IIOP Server Handler that performs the tpinit call on behalf of client applications received a request to join a client application to the WLE server application. However, the message it received in conjunction with the request was not a TPINIT buffer, but of type type. The IIOP Server Handler, therefore, removes the client application context from the IIOP Server Handler and returns an error.
	Action	Contact BEA Technical Support.
1133	ERROR: TPINIT information must be passed to tpinit() call in secure application
	Description	Prior to performing a tpinit on behalf of a client application, the IIOP Server Handler must make sure a TPINIT structure is passed if the application requires client application authentication. This error indicates that the TPINIT information was not passed, even though client application authentication is required. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error. An error message, with tperrno set to TPEPERM, is sent back to the client application.
	Action	Contact BEA Technical Support.
1134	ERROR: Sending of reply to ticket protocol failed
	Description	The IIOP Server Handler failed to send the ticket reply back to the client application. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
1135	ERROR: Invalid client name given 'cltname'.
	Description	While a client application's request to join the application was being processed, an invalid client application name, cltname, was found in the TPINIT buffer. The value sysclient is reserved by the system for the cltname field.
	Action	Contact BEA Technical Support.
1136	WARN: Invalid notification option given 0xoption, reset to TPU_IGN.
	Description	While a client application's request to join the application was being processed, an invalid notification option option was found in the TPINIT buffer flags field. For client application notification, the possible values for flags are as follows: TPU_SIG, TPU_DIP, or TPU_IGN.
	Action	Contact BEA Technical Support.
1137	ERROR: Invalid length for TPINIT structure given
	Description	While a client's request to join the application was being processed, an invalid data length was found in the TPINIT buffer datalen field. The length must be greater than or equal to zero.
	Action	Contact BEA Technical Support.
1138	ERROR: Failed to update registry table information
	Description	The IIOP Server Handler failed to update the client application information in the Bulletin Board's registry table. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
1139	ERROR: Failed to send message to authentication server, tperrno = tperrno_val
	Description	The IIOP Server Handler failed to send the TPINIT information to the authentication server. The call to tpacall failed with tperrno set to tperrno_val. This failure causes the IIOP Server Handler to return an error to the client application 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 user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
	See Also	The tpinit (3c), tpacall, and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1140	WARN: tpbroadcast() or tpnotify() encountered blocking condition
	Description	The IIOP Server Handler failed to send an unsolicited message due to a blocking condition. The IIOP Server Handler is responsible for sending to the (D)BBL administrative server a request to forward unsolicited messages on behalf of the client application. 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 want to change the operating system tunable parameters related to the maximum size of a queue.
	See Also	The tpbroadcast (3c) command. For information about this command, see the BEA TUXEDO Reference Manual.
1141	ERROR: Unable to assign connection request, can't create any more handlers
	Description	The IIOP Server Listener failed to start a new IIOP Server Handler. This error may be due to no more IIOP Server Handlers being available, an error in the formatting of the command line for the IIOP Server Handler, an error in retrieving the machine table entry for the IIOP Server Listener in the Bulletin Board, or an error executing the IIOP Server Handler.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
1142	ERROR: For a secure application, the two-phase challenge/response protocol must be followed
	Description	The IIOP Server Handler received a message over the network from a client application. No context exists for this client application. When a secure application is running, the only message that can be accepted by the IIOP Server Handler from a client application with no context is a two-phase challenge/response message. This error indicates that this requirement has not been adhered to. 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 client application.
	Action	Contact BEA Technical Support.
1143	ERROR: Failed to create encryption/decryption schedule
	Description	The IIOP Server Handler failed to create an encryption/decryption schedule. The function used to create the encryption/decryption schedule is called _tpcryptinit. This function is part of an internal interface that is designed to support various methods of data encryption.
	Action	This error probably indicates a WLE system or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpcryptinit function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.
	See Also	The encryption(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.
1144	ERROR: _tprandkey() failed tperrno = tperrno_val, could not generate random encryption key
	Description	The IIOP Server 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. This function 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 error probably indicates a WLE software or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tprandkey function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.
	See Also	The encryption(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.
1145	ERROR: tpalloc() failed, tperrno = tperrno_val
	Description	An attempt to allocate a buffer in the IIOP Server Handler dynamically 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 to allocate dynamically.
	See Also	The tpalloc and tperrno(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1146	ERROR: Sending of reply to challenge call to client failed
	Description	The IIOP Server Handler failed to send the challenge reply back to the client application. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure.
1147	ERROR: Protocol error, can't process tpinit() request before performing security protocol
	Description	The IIOP Server Handler in a secure application received a request to perform a tpinit on behalf of a client application before performing the security protocol. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
	See Also	The tpinit(3c) command. For information about tpinit(3c), see the BEA TUXEDO Reference Manual.
1148	ERROR: Processing of message to be sent to client failed
	Description	The IIOP Server Handler failed to send a message to the client application. The failure occurred in a low-level routine that performs all manipulations for the message send. This includes presend, encoding, and postsend work. The message being sent from the IIOP Server Handler to the client application had to do with the client application 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 IIOP Server Handler failed to encrypt the message.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.
1149	ERROR: Validation of TPINIT information failed
	Description	The IIOP Server Handler failed to validate the TPINIT structure identifying the connecting client application against an uninterpreted ticket structure identifying the security agent's opinion of the client application. This validation determines whether the connecting client application should be granted access to the application. The function used to perform the validation is _tpvalidate(3i). This function is part of an internal interface that is designed to support various methods of application authentication.
	Action	This error probably indicates that the security ticket and tpinit information do not match, and the user should not be allowed to join the application. This error may also indicate a WLE software or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpvalidate function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.
	See Also	The security(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.
1150	ERROR: Incorrect timestamp value sent by client
	Description	The IIOP Server Handler failed to validate the ticket information passed to it by a client application. The ticket information passed from the client application to the IIOP Server Handler does not match the time-stamping information stored in the IIOP Server Handler.
	Action	Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure.
1152	ERROR: Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc failed while the ticket information passed to the IIOP Server Handler by the client application was being validated.
	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.
1153	ERROR: Could not obtain session key from ticket
	Description	The IIOP Server 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 client application. The function used to retrieve the session key is _tpsessionkey. This function is part of an internal interface that is designed to support various methods of authentication.
	Action	This probably means a WLE or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpsessionkey function may also fail because an invalid argument was given or the ticket could not be processed because the client application was denied permission for an implementation-specific reason. In this case, contact BEA Technical Support.
	See Also	The security(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.
1154	ERROR: Failed to encrypt ticket information
	Description	The IIOP Server Handler failed to encrypt data according to a schedule while accepting a challenge and time-stamping value that is to be used to verify that the request is valid. The function used to encrypt data is _tpcrypt. This function is part of an internal interface that is designed to support various methods of encryption.
	Action	This error probably means a WLE software or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpcrypt function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.
	See Also	The encryption(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.
1156	ERROR: Decryption of challenge request failed
	Description	While a client application was attempting to join the application, the challenge request message could not be decrypted.
	Action	Contact BEA Technical Support.
1157	ERROR: Encryption of challenge request failed
	Description	While a client application was attempting to join the application, the challenge request message could not be decrypted.
	Action	Contact BEA Technical Support.
1158	ERROR: Couldn't create encryption/decryption schedule
	Description	While a client application was attempting to join the application, the encryption or decryption schedule could not be created.
	Action	Contact BEA Technical Support.
1159	ERROR: Failed to encode/decode establish connection request message
	Description	While a client application was attempting to join the application, the establish connection request message could not be encoded or decoded.
	Action	Contact BEA Technical Support.
1160	ERROR: Decryption of challenge reply failed
	Description	While a client application was attempting to join the application, the challenge reply message could not be decrypted.
	Action	Contact BEA Technical Support.
1161	ERROR: Encryption of challenge reply failed
	Description	While a client application was attempting to join the application, the challenge reply message could not be decrypted.
	Action	Contact BEA Technical Support.
1162	ERROR: Encoding/decoding of ticket request failed
	Description	While a client application was attempting to join the application, the ticket request message could not be encoded or decoded.
	Action	Contact BEA Technical Support.
1163	ERROR: Encoding/decoding of ticket request failed
	Description	While a client application was attempting to join the application, the ticket request message could not be encoded or decoded.
	Action	Contact BEA Technical Support.
1164	ERROR: Decryption of TPINIT buffer failed
	Description	While a client application was attempting to join the application, the TPINIT message could not be decrypted.
	Action	Contact BEA Technical Support.
1165	ERROR: Encoding/decoding of TPINIT buffer failed
	Description	While a client application was attempting to join the application, the TPINIT message could not be encoded or decoded.
	Action	Contact BEA Technical Support.
1166	ERROR: Encryption of TPINIT buffer failed
	Description	While a client application was attempting to join the application, the TPINIT message could not be encrypted.
	Action	Contact BEA Technical Support.
1167	ERROR: Unknown client message to process
	Description	While a client application was attempting to join the application, an unknown message type was encountered for processing.
	Action	Contact BEA Technical Support.
1168	ERROR: Tried to process unexpected message opcode 0xcode
	Description	While a client application was attempting to join the application, an unknown message type was encountered for processing.
	Action	Contact BEA Technical Support.
1169	ERROR: Expected numeric argument to -D option
	Description	An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the ISL command -D option needs to be numeric. This error causes the IIOP Server Listener not to be booted.
	Action	Make sure the argument to the ISL command -D option is numeric.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1170	ERROR: Expected numeric argument to -M option
	Description	An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the ISL command -M option needs to be numeric. This error causes the IIOP Server Listener not to be booted.
	Action	Make sure the argument to the ISL command -M option is numeric.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1171	ERROR: Expected numeric argument to -m option
	Description	An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the -m option needs to be numeric. This error causes the IIOP Server Listener not to be booted.
	Action	Make sure the argument to the -m option is numeric.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1174	WARN: Disconnecting listener connection to client, connection timed out
	Description	The IIOP Server Listener scans its handler table and times out any connections that are overdue, restarts any dead handlers, and allocates any blocked connection requests to a handler that is available. When scanning this table, the IIOP Server Listener found a handler that was waiting for a connection that had timed out. The IIOP Server Listener proceeded and forced the connection closed.
	Action	Contact BEA Technical Support.
1175	WARN: Disconnecting listener connection to client, request timed out
	Description	The IIOP Server Listener scans its handler table and times out any connections that are overdue, restarts any dead handlers, and allocates any blocked connection requests to a handler that is available. When scanning this table, the IIOP Server Listener found a blocked connection request that had not been passed to an available handler. Because the time to assign a handler expired, the IIOP Server Listener proceeded and forced the connection to close.
	Action	This error probably indicates that the number of client applications that need to join the application cannot be supported by the existing configuration. The command-line options for the ISL command should be modified to support a larger number of client applications. The ISL command -m, -M, and -x options should be used to that effect.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1176	ERROR: Sending of reply to tpconnect() call to client failed
	Description	An attempt to send an acknowledgment of a tpconnect request to the client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network or with the client application process. Contact BEA 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 client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network or with the client application process. Contact BEA 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 client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network or with the client application process. Contact BEA Technical Support.
1179	ERROR: Unrecognized opcode: opcode
	Description	A message was received in the IIOP Server Handler requesting an unknown operation.
	Action	This is an internal message. This failure indicates a problem with the network or with the client application process. This failure could indicate the use of newer client application software with an older IIOP Server Handler. Contact BEA 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 client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network or with the client application process. Contact BEA Technical Support.
1182	ERROR: Invalid -T option = num
	Description	The -T command-line option for the ISL command had an invalid argument. The value must be greater than or equal to 0 and less than 70409299.
	Action	Reconfigure the CLOPT parameter for the ISL command and reboot the process. For information about the ISL command , see the Administration Guide.
1183	ERROR: Expected numeric argument to -T option
	Description	The -T command-line option for the ISL command had a nonnumeric argument.
	Action	Reconfigure the CLOPT parameter for the ISL command and reboot the process. For information about the ISL command, see the Administration Guide.
1185	INFO: Userid: [user], Clientid: [client] timed out due to inactivity
	Description	A client application attached to the application has been invalid for longer than the configured timeout value, specified via the -T command-line option of the ISL command. The associated user name and client application name are printed.
	Action	None.
1186	ERROR: Cannot convert message with unknown protocol num
	Description	The IIOP Server Handler received a message from a client application with an unknown protocol number, num.
	Action	Contact BEA Technical Support.
1187	ERROR: Cannot convert message from protocol num1 to num2
	Description	The IIOP Server Handler received a message to or from a client application with a protocol version that cannot be converted.
	Action	Contact BEA Technical Support.
1188	ERROR: Unrecognized message format, release num
	Description	The IIOP Server Listener received a connection message from a client application with an unknown protocol number, num.
	Action	Contact BEA Technical Support.
1190	INFO: Reestablished network address string
	Description	A previously suspended IIOP Server Listener process has been unsuspended and has reestablished its network address.
	Action	Informational message, no action required.
	See Also	The MIB(5) and WS_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1191	INFO: Network address disabled
	Description	An IIOP Server 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	The MIB(5) and WS_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1192	INFO: Abortively disconnecting client user[usr], client[clt]
	Description	An IIOP Server Handler is disconnecting the virtual circuit associated with a particular client application (<usr>/<clt>) because of an administrative request to set the client application state to DEAD.
	Action	Informational message, no action required.
1195	WARN: Failed to reestablish network address string
	Description	A previously suspended IIOP Server 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 eventually is released by the system and the IIOP Server Listener reestablishes 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 processes and users are occupying the network address; these processes and users should be asked to relinquish the address.
	See Also	The UNIX netstat command, the Microsoft Windows NT NetStatisticsGet command, and the MIB(5) and WS_MIB(5) commands. For information about the netstat command, see the UNIX manual page. For information about the NetStatisticsGet command, see Microsoft Visual C++ online help. For information about the MIB(5) and WS_MIB(5) commands, see the BEA TUXEDO Reference Manual.
1196	INFO: Terminating handlers in preparation for shutdown
	Description	The IIOP Server Listener is shutting down and in preparation is about to terminate its associated IIOP Server Handler processes.
	Action	Informational message, no action required.
	See Also	The MIB(5), tmshutdown(1), and WS_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1197	INFO: Exiting system
	Description	The IIOP Server Listener has completed its shutdown and is exiting the system.
	Action	Informational message, no action required.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1199	WARN: .SysClientDied: User usrname on clientname client died
	Description	This message indicates that the specified client application exited the application without ending the session. The client applications should call either the PrincipalAuthenticator::logoff() function or the Tobj_Bootstrap::destroy_current() function before exiting the application.
	Action	This is an informational message. No action is required.
	See Also	The PrincipalAuthenticator::logoff() and the Tobj_Bootstrap::destroy_current() functions. For information about these functions, see the BEA WLE C++ Programming Reference.