IIOP Server Listener/Handler Messages

IIOP Server Listener/Handler Messages 1000-1099

Note: When IIOP Listener/Handler messages are listed in the user log (ULOG), the messages have the prefix ISNAT_CAT. For example, message 1101 is listed as ISNAT_CAT:1101.

1001	ERROR: Unused arguments passed to buildish.
	Description	The command-line option passed to the buildish command is not recognized as a valid option. An extra hyphen (-) in the command line also might cause this error.
	Action	Examine the command line that calls buildish and remove the extra option.

1002	ERROR: Unable to execute the command command_string.
	Description	While the C compilation system was being invoked to build a new IIOP Server Handler, an error was detected. This error could happen for one of the following reasons: The C compilation system command was not found. The CC command returned an error while linking the new IIOP Server Handler. The $CC environmental variable was not set correctly. The $CFLAGS environmental variable has invalid options.
	Action	Make sure the C compilation system is present on your machine. Make sure there is enough disk space available for the new IIOP Server Handler. The amount of disk space should be roughly the same as the existing IIOP Server Handler and the added object files. Examine the $CC and $CFLAGS variables and, if these variables are set, make sure the options are correct for your C compilation environment.

1003	ERROR: Could not find buffer type type_val: subtype subtype_val information.
	Description	This error occurs when the IIOP Server Handler receives a message from either a server application or a client application, and it cannot find the buffer type information for the buffer type of the message.
	Action	The error indicates an internal problem with the IIOP Server Handler. Contact BEA Customer Support.

1004	ERROR: Memory allocation failure.
	Description	An attempt to allocate memory dynamically 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 by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1008	ERROR: Could not establish listening address on network string.
	Description	This error occurs if the IIOP Server Listener cannot advertise its listening address on the network. This error could happen for one of the following reasons: The format of the address supplied to the IIOP Server Listener is incorrect. If the address format is incorrect, the network provider will be unable to advertise the address and the request fails. The address used in the -n command-line option to the IIOP Server Listener is already in use by another process. For TCP/IP, this condition can be verified by using the netstat command. A previously used address has not completed the close sequence. This condition occurs if either the IIOP Server Listener or the IIOP Server Handler were killed in an abortive manner, such as kill-9. Some transports (among them, TCP/IP) keep the connection open for an implementation-dependent amount of time to flush the existing data on the buffered network connection.
	Action	To correct the problem, match one of the following solutions with the previous problem descriptions: Check the address format. For TCP/IP, the address must be specified in either of the following two formats: //hostname:port_number" "//#.#.#.#:port_number" The #.#.#.# is in dotted decimal format. In dotted decimal format, each # should be a number from 0 to 255. See whether other processes are using the requested network address. For TCP/IP, use the netstat command and, if the address is already in use, select a different address. If the system is out of network addresses, ask the system administrator to increase the number of addresses. If the connection is not closed yet, wait a few minutes and try again.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1009	ERROR: Cannot decode header of the received message.
	Description	Either the IIOP Server Handler or the IIOP Server Listener read the data from the network. Each message has a header at the top of the message. If the message is corrupted or is smaller that the expected header, this error occurs.
	Action	Contact BEA Technical Support.

1010	ERROR: Couldn't convert buffer to current release format.
	Description	This error occurs if an WLE remote client application and the native UNIX system machine have different WLE releases and the message is from an older release. The error can also occur if the message received by either the IIOP Server Handler or the IIOP Server Listener is corrupted.
	Action	Contact BEA Technical Support.

1011	ERROR: Couldn't convert buffer to native site format.
	Description	The IIOP Server Handler cannot convert a message from a client application format to the native format. This indicates that the buffer type is unknown to the IIOP Server Handler .
	Action	Check the user log for a message indicating the nature of the failure (in particular, the type and subtype of the buffer that could not be converted).

1012	ERROR: Received message with an unknown internal type index indexval.
	Description	While processing a message from the client application, the system indicates that the internal buffer type is unknown.
	Action	Because the buffer type is set during the conversion to the native format, this error should not occur. Contact BEA Technical Support.

1013	ERROR: Received message of unknown type 'typeval' subtype `subtypeval'.
	Description	While processing a message from the client application, the system indicates that the application buffer type and subtype are unknown.
	Action	Because the buffer type is set during conversion to the native format, this error should not occur. Contact BEA Technical Support.

1014	ERROR: Received message of unknown type `type'.
	Description	While processing a message from the client application, the system indicates that the application buffer type is unknown.
	Action	Because the buffer type is set during conversion to the native format, this error should rarely occur. Contact BEA Technical Support.

1015	ERROR: Message decode failure.
	Description	Decoding of the message received from the client application by the encdec function for the buffer type failed.
	Action	Check the user log for additional messages that indicate why the decoding failed. Contact BEA Technical Support.
	See Also	The typesw(5) command. For information about the typesw(5) command, see the BEA TUXEDO Reference Manual.

1016	ERROR: Post receive operation on message failed.
	Description	Postprocessing of the message received from the client application by the postsend function for the buffer type failed.
	Action	Check the user log for additional messages that indicate why the postprocessing failed. Contact BEA Technical Support.
	See Also	The typesw(5) command. For information about the typesw(5) command, see the BEA TUXEDO Reference Manual.

1017	ERROR: Message presend routine failed.
	Description	Preprocessing of the message being sent to the client application by the presend function for the buffer type failed.
	Action	Check the user log for additional messages that indicate why the preprocessing failed. Contact BEA Technical Support.
	See Also	The typesw(5) command. For information about the typesw(5) command, see the BEA TUXEDO Reference Manual.

1018	ERROR: Invalid data length of 0, data not self describing.
	Description	Preprocessing of the message being sent to the client application by the presend function for the buffer type returned 0. This error indicates that a message length of 0 was presented by the application and that the buffer type is not self-describing, such that the presend function cannot infer the desired transfer length.
	Action	The application must provide a length for sending messages of the particular buffer type.
	See Also	The TUXEDO typesw(5) command. For information about the typesw(5) command, see the BEA TUXEDO Reference Manual.

1019	ERROR: Message conversion to client format failed.
	Description	The IIOP Server Handler cannot convert a message from native format to client application format.
	Action	This error should not occur. Contact BEA Technical Support.

1023	WARN: No client context space available in handler.
	Description	While setting up a connection for a new client application, the IIOP Server Handler ran out of space to keep context for client applications.
	Action	This error should occur rarely because the IIOP Server Listener transfers control of client application connections to IIOP Server Handler programs based on their current degree of multiplexing. Contact BEA Technical Support.
	See Also	For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1024	ERROR: Memory allocation failure.
	Description	An attempt to allocate memory dynamically 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 by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1025	ERROR: Expected numeric argument to -x option.
	Description	An invalid argument was passed to the ISL command-line option. The argument to the -x option, the degree of multiplexing, needs to be numeric. This error causes the IIOP Server Listener not to be booted.
	Action	Make sure the argument to the -x option is numeric.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.

1026	ERROR: Handler received unexpected message.
	Description	The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler) that is not in the correct format. It is not a WLE message.
	Action	The message is ignored. Contact BEA Technical Support.

1027	ERROR: Handler received unexpected opcode 0xcode.
	Description	The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler) that has an unrecognized operation code. This message is normally a shutdown message from the IIOP Server Listener.
	Action	The message is ignored. Contact BEA Technical Support.

1028	WARN: Couldn't change to client context context_number, continuing.
	Description	The IIOP Server Handler encountered an error while it was switching to the context of a client application when the IIOP Server Handler was dropping all connections during shutdown.
	Action	The connection is ignored. Contact BEA Technical Support.

1029	ERROR: Sending of reply message to client failed.
	Description	While a reply message was being sent to a client application, the operation failed.
	Action	Check the user log for messages that indicate the nature of the failure. This warning may indicate that the client application is no longer accessible (that is, either the network or the machine has failed). Contact BEA Technical Support.

1030	INFO: IIOP Handler joining application.
	Description	The IIOP Server Listener started an IIOP Server Handler process based on the command-line options for the listener and the current demand by clients.
	Action	None.
	See Also	For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1031	ERROR: Invalid command line argument `arg' ignored.
	Description	An illegal command-line option was found in the command-line options for the IIOP Server Handler. This error is rare because the IIOP Server Listener, not the system administrator, starts the IIOP Server Handler.
	Action	Contact BEA Technical Support.
	See Also	For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1032	ERROR: Memory allocation failure.
	Description	An attempt to allocate memory dynamically 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 by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1033	ERROR: Memory allocation failure.
	Description	An attempt to allocate memory dynamically 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 by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1034	ERROR: Failed to attach to shared memory for listener table, errno = errno_val.
	Description	The IIOP Server Handler failed to attach a shared memory segment.
	Action	This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Technical Support.

1035	ERROR: Handler table entry already occupied by pid.
	Description	The IIOP Server Listener started an IIOP Server Handler and assigned it a slot that is already occupied by another IIOP Server Handler process that has the process identifier pid.
	Action	Contact BEA Technical Support.
	See Also	For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1036	ERROR: Network provider returns a zero length network address, can't establish network address.
	Description	The length of the network address that the IIOP Server Handler is using to establish a connection is 0. This is invalid (and should not occur).
	Action	Contact BEA Technical Support.

1037	ERROR: Can't synchronize with IIOP listener... continuing.
	Description	The forked IIOP Server Handler process lost the connection between the IIOP Server Listener and the IIOP Server Handler that it is executing. The pipe with IIOP Server Listener may have been lost because the IIOP Server Listener process is being stopped.
	Action	No action is required. However, the cause of the IIOP Server Listener disconnection should be investigated if the cause is not known.
	See Also	For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1038	WARN: Couldn't change to client context index, continuing.
	Description	The IIOP Server Handler encountered an error while it was switching to the context of a client application when the IIOP Server Handler was dropping all connections during shutdown.
	Action	The connection is ignored. Contact BEA Technical Support.

1039	WARN: Can't use TPGETANY flag with tpcall().
	Description	The client application called tpcall() with the TPGETANY option. This option is not valid, and TPEINVAL is returned to the application.
	Action	This error should not occur. Contact BEA Technical Support.

1040	WARN: tpsprio() call failed, tperrno = tperrno_val.
	Description	A call to tpsprio in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.
	Action	None.
	See Also	The tpsprio(3c) command. For information about the tpsprio(3c) command, see the BEA TUXEDO Reference Manual.

1041	ERROR: Memory allocation failure.
	Description	An attempt to allocate memory dynamically 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 by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1042	ERROR: tpcall() call failed, tperrno = tperrno_val.
	Description	A call to tpcall in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.
	Action	None.
	See Also	The tpcall(3c) command. For information about the tpcall(3c) command, see the BEA TUXEDO Reference Manual.

1043	ERROR: tpacall() call failed, tperrno = tperrno_val.
	Description	A call to tpacall in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.
	Action	None.
	See Also	The tpacall(3c) command. For information about the tpacall(3c) command, see the BEA TUXEDO Reference Manual.

1044	ERROR: tpgprio() call failed, tperrno = tperrno_val.
	Description	A call to tpgprio in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.
	Action	None.
	See Also	The buildish(1) command. For information about the buildish(1) command, see the BEA TUXEDO Reference Manual.

1045	ERROR: Sending of reply to tpacall() call to client failed.
	Description	An attempt to send an acknowledgment of a tpacall request to the WLE remote client application failed. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.
	Action	Contact BEA Technical Support.

1046	ERROR: Sending of reply to tpinit() call to client failed.
	Description	An attempt to send an acknowledgment of a tpinit request to the WLE remote client application failed. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.
	Action	Contact BEA Technical Support.

1047	ERROR: Sending of reply to tpterm() call to client failed.
	Description	An attempt to send an acknowledgment of a tpterm request to the WLE remote client application failed. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.
	Action	Contact BEA Technical Support.

1048	ERROR: Sending of error reply to call client failed.
	Description	An attempt to send an acknowledgment message to the WLE remote client application has failed. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.
	Action	Contact BEA Technical Support.

1049	ERROR: Couldn't create buffer for receiving messages.
	Description	An attempt to create a buffer with tpalloc failed. This buffer is used to receive messages. This error indicates either a resource problem or an internal problem with the IIOP Server Handler.
	Action	If there is insufficient memory to allocate buffers, the IIOP Server Handler process cannot operate. Contact BEA Technical Support. If machine resources are sufficient, there is an internal problem with the IIOP Server Handler. In this case, contact BEA Technical Support.

1050	ERROR: Error switching to the handler's context.
	Description	The IIOP Server Handler was attempting to switch from a client application context to the IIOP Server Handler context when it experienced an error.
	Action	The error indicates an internal problem with the IIOP Server Handler. Contact BEA Technical Support.

1052	ERROR: Failed to process network event.
	Description	The IIOP Server Handler was unable to process a network event using tmnwevent.
	Action	The error indicates an internal problem with the IIOP Server Handler software. Contact BEA Technical Support.

1053	ERROR: Error polling network connections.
	Description	The IIOP Server Handler encountered an error polling a network connection using tmnwcpoll.
	Action	The error indicates a network error. Check that the network connection to the WLE remote client application has not gone down. If the network connection has gone down, the WLE remote client application has to rejoin the application. Contact BEA Technical Support.

1054	ERROR: Error generating network event list.
	Description	The IIOP Server Handler encountered an error when polling a network connection using tmnwcpoll.
	Action	The error indicates a network error. Check that the network connection to the WLE remote client application has not gone down. If the network connection has gone down, the WLE remote client application has to rejoin the application. Contact BEA Technical Support.

1055	ERROR: Connection to unassigned ISH rejected.
	Description	The connection for the client application was timed out.
	Action	This situation may occur if the system or the network is very busy, or if the network has gone down. The client application should try again to join the application.

1056	WARN: Couldn't change to client context index, continuing.
	Description	The IIOP Server Handler encountered an error when switching to the context of a client application to do a tpterm.
	Action	This error indicates an internal problem. Contact BEA Technical Support.

1057	ERROR: Error processing message received from network.
	Description	The IIOP Server Handler encountered an error when receiving a message from the network.
	Action	This error could indicate a network problem or an internal BEA problem. Contact BEA Technical Support.

1058	ERROR: Received message with opcode other than init for non-existent context.
	Description	The IIOP Server Handler has received a message from a process that has not joined the application.
	Action	This message indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Technical Support.

1059	ERROR: Received network message with unknown context.
	Description	The IIOP Server Handler has received a message from an unknown process.
	Action	This message indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Technical Support.

1060	ERROR: Received message with context associated with a different connection.
	Description	The IIOP Server Handler, working on behalf of one client application context, has received a message intended for a different client application context.
	Action	This message indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Technical Support.

1061	ERROR: Received a reply message from a client.
	Description	The IIOP Server Handler has received from an WLE remote client application a message that contains the reply protocol.
	Action	A WLE remote client application should never send a message with this protocol. This situation indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Technical Support.

1062	ERROR: Sending of reply to tpbegin() call to client failed.
	Description	An attempt to send an acknowledgment of a tpbegin request to the WLE remote client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process. Contact BEA Technical Support.

1063	ERROR: No more IIOP handlers available.
	Description	An attempt to start a new IIOP Server Handler process has failed because the maximum limit of IIOP Server Handlers has already been reached.
	Action	The maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in one of two ways: Shut down the application, change the configuration file, and reboot the application. Change the value dynamically with tmconfig (1), and shut down and reboot only the IIOP Server Listener.

1064	ERROR: Error formatting command line options for handler.
	Description	An error was encountered while the argument string needed for booting an IIOP Server Handler was being formatted.
	Action	This message occurs if there are more than 256 characters in the CLOPT string in the configuration file.
	See Also	ISL command and servopts(5). For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter. For information about servopts(5), see the BEA TUXEDO Reference Manual.

1065	ERROR: Error retrieving machine table entry of the listener.
	Description	An error was encountered while an IIOP Server Handler was trying to get internal machine information during an IIOP Server Handler boot process.
	Action	Contact BEA Technical Support.

1066	ERROR: IIOP Handler died, attempting restart.
	Description	If an IIOP Server Handler process has died and the number of IIOP Server Handler processes booted is below the minimum number specified in the configuration file, the BEA WLE system attempts to boot a new IIOP Server Handler.
	Action	IIOP Server Handlers should not die. If IIOP Server Handlers do die, it could indicate an internal problem that requires attention. Additional IIOP Server Handlers may need to be booted, if the system is very busy.

1067	ERROR: IIOP Handler died, cleaning up.
	Description	An IIOP Server Handler process has died and the number of IIOP Server Handler processes booted is below the minimum number specified in the configuration file. An attempt to boot a new IIOP Server Handler has failed.
	Action	This could either be an operating system error or an internal WLE error. In the former case, contact your system administrator. In the latter case, contact BEA Technical Support.

1068	ERROR: Invalid command line argument `arg' ignored.
	Description	An illegal command-line option was found in the CLOPT string.
	Action	Examine the command line and remove the invalid option.
	See Also	ISL command and servopts(5). For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter. For information about servopts(5), see the BEA TUXEDO Reference Manual.

1069	ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed.
	Description	An attempt to send an acknowledgment of a tpbroadcast or tpnotify request to the WLE remote client application has failed.
	Action	Contact BEA Technical Support.

1070	ERROR: Cannot boot ISL with MAXWSCLIENTS for machine set to 0.
	Description	The IIOP Server Listener process has failed to boot because the MAXWSCLIENTS parameter was not specified in the configuration file.
	Action	The MAXWSCLIENTS parameter must be specified either in the RESOURCES section or in the MACHINES section of the configuration file.

1071	ERROR: Memory allocation failure.
	Description	The IIOP Server Listener failed to create a buffer for storing IIOP Server Handler information.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1072	ERROR: Memory allocation failure.
	Description	The IIOP Server Listener failed to create a buffer for storing a device name.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1073	ERROR: Memory allocation failure.
	Description	The IIOP Server Listener failed to create a buffer for storing an IIOP Server Handler's name.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1074	ERROR: Memory allocation failure.
	Description	The IIOP Server Listener failed to create a buffer for storing a network address.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.
	See Also	See the malloc function. For UNIX systems, see the malloc(3) manual page. For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1075	ERROR: Can't get machine entry for listener.
	Description	The IIOP Server Listener encountered an error when attempting to read the MACHINES entry from the configuration file.
	Action	Make sure the TUXCONFIG file has not been removed or corrupted. If the TUXCONFIG file is all right, contact BEA Technical Support.

1076	ERROR: Failed to create to shared memory for listener table, errno = errno_val.
	Description	The IIOP Server Listener failed to create a shared memory segment.
	Action	This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Technical Support.
	See Also	The Uunix_err(3c) command. For information about the Uunix_err(3c) command, see the BEA TUXEDO Reference Manual.

1077	ERROR: Failed to update server table entry, tperrno = tperrno_val.
	Description	The IIOP Server Listener failed to update the Bulletin Board.
	Action	Check that the shared memory segment that contains the Bulletin Board has not been removed. If this segment has been removed, the application needs to be rebooted. Otherwise, this error indicates an internal error and you should contact BEA Technical Support.
	See Also	The tperrno(5) command. For information about the tperrno(5) command, see the BEA TUXEDO Reference Manual.

1078	ERROR: Failed to attach to shared memory for listener table, errno = errno_val.
	Description	The IIOP Server Listener failed to attach a shared memory segment.
	Action	This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Technical Support.
	See Also	The tperrno(5) command. For information about the tperrno(5) command, see the BEA TUXEDO Reference Manual.

1079	ERROR: Error starting minimum number of handlers.
	Description	The IIOP Server Listener encountered an error when attempting to boot the minimum number of IIOP Server Handlers.
	Action	This could be an operating system error. Perhaps there are too many processes running. This could also be an internal error. Check the log file for other messages relating to this message. Contact BEA Technical Support.

1080	ERROR: Error polling network connections.
	Description	The IIOP Server Listener encountered an error when polling a network connection.
	Action	This error indicates a network error. Check with your system administrator to see whether the network is down. If the network is all right, contact BEA Technical Support.

1082	ERROR: Error adding connection request to event list.
	Description	The IIOP Server Listener was unable to allocate space on the event list.
	Action	This error indicates a resource problem. If there is insufficient memory to allocate buffers, the IIOP Server Listener process cannot operate. Contact BEA Technical Support.

1083	ERROR: Error assigning connection request, can't create any more handlers.
	Description	The IIOP Server Listener was unable to start a new Handler.
	Action	The most likely problem is that the maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in one of two ways: Shut down the application, change the configuration file, and reboot the application. Change the value dynamically with tmconfig(1), and shut down and reboot only the IIOP Server Listener. Another source of the problem could be that the number of processes allowable by a user (ulimit) has been reached. If the ulimit has been reached, consult with your system administrator to increase this limit.

1086	ERROR: Message conversion to release rel format failed.
	Description	The IIOP Server Listener/Handler was unable to change the release structure to 4.2.
	Action	Contact BEA Technical Support.

1088	ERROR: tpinit() failed, tperrno = tperrno_val.
	Description	The tpinit(3c) function call used to connect a client application to a WLE server application has failed. Further information about the cause of the failure is provided by the value of tperrno. By examining the <atmi.h> header file, this numeric tperrno value may be converted to a symbolic value. Potential causes of each such symbolic value are listed for the tpinit(3c) command.
	Action	For causes of the specific tperrno value that was reported to the application, see the tpinit(3c) command in the BEA TUXEDO Reference Manual. Eliminate the potential causes of such an error and retry the failed operation. Contact BEA Technical Support.
	See Also	The tpinit(3c) and tperrno(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1089	ERROR: tpscmt() failed, tperrno = tperrno_val.
	Description	While attempting to commit a transaction on behalf of a client application, the IIOP Server Handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_LOGGED. For this reason, the attempt to commit the transaction failed. For further information about the transaction commit control characteristic, refer to the tpscmt (3c) command in the BEA TUXEDO Reference Manual.
	Action	Because the transaction cannot be committed, the user must abort the transaction. The value of tperrno and immediately preceding messages in the user log may provide further information as to the cause of the error.
	See Also	The tpabort (3c), tpcommit (3c), tpscmt (3c), and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1090	ERROR: tpscmt() failed, tperrno = tperrno_val.
	Description	While attempting to commit a transaction on behalf of a client application, the IIOP Server Handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_COMPLETE. For this reason, the attempt to commit the transaction failed. For further information about the transaction commit control characteristic, refer to the tpscmt(3c) command in the BEA TUXEDO Reference Manual.
	Action	Because the transaction cannot be committed, the user must abort the transaction. The value of tperrno and immediately preceding messages in the user log may provide further information as to the cause of the error.
	See Also	The tpabort (3c), tpcommit (3c), tpscmt (3c), and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1096	ERROR: Sending of reply to tpcommit() call to client failed.
	Description	An attempt to send an acknowledgment of a tpcommit request to the WLE remote client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process. Contact BEA Technical Support.

1097	ERROR: Sending of reply to tpabort() call to client failed.
	Description	An attempt to send an acknowledgment of a tpabort request to the WLE remote client application has failed.
	Action	This is an internal message. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process. Contact BEA Technical Support.

1099	ERROR: Could not find correct number of active handlers, found num1, expected num2.
	Description	While being restarted after the death of a previous IIOP Server Listener process, the IIOP Server Listener found an inconsistency in the existing specific shared memory regarding the number of IIOP Server Handler processes. The IIOP Server Listener attempts to shut down any associated IIOP Server Handler processes that it knows about, removes the inconsistent shared memory, and exits.
	Action	The system administrator should check for any stray IIOP Server Handler processes associated with this particular IIOP Server Listener, and see that they are manually terminated. The system administrator may then reboot the IIOP Server Listener process.

IIOP Server Listener/Handler Messages 1100-1199

Note: When IIOP Server Listener/Handler messages are listed in the user log (ULOG), the messages have the prefix ISNAT_CAT. For example, message 1100 is listed as ISNAT_CAT:1100

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	The 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 tpbroadcast 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.