Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

ISNAT Messages 1200-1299

1200	INFO: .SysClientState: User usrname on LMID state change to state
	Description	This message indicates that the specified client application changed to a new state. A complete listing of the current attributes of the client application is sent in the posted buffer.
	Action	This is an informational message.
	See Also	The EVENT_MIB(5) and TM_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1201	WARN: .SysClientSecurity: User usrname on LMID authentication failure
	Description	This message indicates that the specified client application failed security validation when trying to join the application. A complete listing of the current attributes of the client application is sent in the posted buffer.
	Action	Make sure that a hacker is not trying to gain access to your application data.
	See Also	The EVENT_MIB(5) and TM_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1214	ERROR: Type switch uninitialization failure
	Description	While processing a client application buffer, the buffer uninitialization function, _tmuninitbuf(), returned an error.
	Action	Check the buffer type switch to see that it is correctly set up (that is, that the right uninitialization function is associated with the correct buffer type). If the buffer type is defined by the application, check the uninitialization function to see that it is coded correctly.
	See Also	The buffer(3c) and typesw(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.
1222	ERROR: Expected numeric argument to -z option
	Description	An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the ISL command -z 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 -z option is numeric.
	See Also	The ISL command. For information about the ISL command, see Administration in the WebLogic Enterprise online documentation.
1223	ERROR: Expected numeric argument to -Z option
	Description	An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the ISL command -Z 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 -Z option is numeric.
	See Also	The ISL command. For information about the ISL command, see Administration in the WebLogic Enterprise online documentation.
1237	ERROR: tpnotify(TPACK) failed to reply, tperrno = tperrno
	Description	The IIOP Server Handler sent an acknowledged unsolicited message to a client application. However, that client application never acknowledged the message.
	Action	The network may have experienced an error, or the client application waiting for the notification may have been killed. The tperrno process may provide clues as to the cause of this failure. If neither of these events has occurred, contact BEA Technical Support.
1240	ERROR: Failed to read server table entry, tperrno = tperrno
	Description	The IIOP Server Listener was rebooting after a failure and could not read the server table.
	Action	The Bulletin Board may be corrupted. The tperrno process may provide clues as to the cause of this failure. Contact BEA Technical Support.
1241	ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed
	Description	The IIOP Server Handler received an acknowledgment from a client application but was unable to forward the acknowledgment of the tpnotify to the sender.
	Action	The originator of the tpnotify may have been killed. If the originator of the notify has not been killed, contact BEA Technical Support.
1242	ERROR: Bad Internet type of listening address provided: address
	Description	The address is not a valid Internet address.
	Action	Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change address to comply with the known formats. If you believe that your address is in the proper format, contact BEA Technical Support.
1249	ERROR: -H and -n have different length of network address
	Description	If you are using an external address, that address must have the same format as the -n option.
	Action	Change the -H option to have the same format as the -n option.
1254	ERROR: Bad conversational sequence number
	Description	Conversations are sequenced to provide protection. One of the conversational messages arrived out of order. The conversation has been disconnected, and if a transaction was active, it has been set to the ABORTONLY state.
	Action	Look at the user log to determine whether the BRIDGE has given up sending any messages to the message queue for the IIOP Server Handler. If it has given up, the operating system may need to be tuned to handle a high volume of messages properly. This problem may also be alleviated by using compression. This error may also occur when the BRIDGE is failing over to a new network link or failing back to a high priority link.
1277	ERROR: Memory allocation failure
	Description	An attempt to allocate memory dynamically from the operating system using malloc() failed while the IIOP Server Listener or the IIOP Server Handler was being initialized.
	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.
1278	ERROR: Address conversion error
	Description	The IIOP Server Handler had a problem converting an address from a binary format to a text format.
	Action	If this error happens consistently, contact BEA Technical Support.
1279	ERROR: descriptor allocation error
	Description	The IIOP Server Handler was unable to allocate a network resource for the listening end point.
	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.
1280	ERROR: Could not initialize network (error)
	Description	The IIOP Server Handler or IIOP Server Listener could not initialize its network.
	Action	Ensure that the network is viable on the machine. If the network is viable, contact BEA Technical Support.
1281	ERROR: Could not initialize global information (error)
	Description	The IIOP Server Handler or IIOP Server Listener could not initialize its network.
	Action	Ensure that the network is viable on the machine. If the network is viable, contact BEA Technical Support.
1283	ERROR: Network error (error) servicing network event
	Description	The IIOP Server Listener encountered a severe error while handling network events.
	Action	Ensure that the network is viable on the machine. If the network is viable, contact BEA Technical Support.
1284	WARN: Failed to allocate a network resource (error)
	Description	The IIOP Server Handler or IIOP Server Listener could not allocate a network descriptor for a remote connection.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1286	ERROR: -K argument must be client, handler, both, or none
	Description	The -K option for the ISL command requires an argument of client application, handler, both, or none.
	Action	Ensure that the -K option of the ISL command is client application, handler, both, or none. Check your spelling.
1287	WARN: Forced shutdown of client; user name 'name'; client name 'name'; client address 'xxx.xxx.xxx.xxx'
	Description	This error may result from an IIOP Server Handler being shut down when client applications are connected, a client application connection has timed out, the IIOP Server Handler was unable to send a network message to the client application, or an incorrect APP_PW (application password) was rejected during tpinit().
	Action	If APP_PW is turned on, see your UBBCONFIG file and ubbconfig(5), and then check with your system administrator to verify that you are using the correct application password for your WLE application.
1288	WARN: setsockopt() for SO_KEEPALIVE failed
	Description	The KEEPALIVE handler-side networking option was configured for a IIOP Server Listener/Handler pair, but could not be enabled.
	Action	This error is ignored and IIOP Server Handler processing continues normally. However, network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client application timeout (ISL command -T option) to reclaim resources associated with dead network connections.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1289	WARN: KEEPALIVE option requested but not available on this platform
	Description	The KEEPALIVE handler-side networking option is configured for a IIOP Server Listener/Handler pair, but cannot be enabled because it is not available on this platform.
	Action	This error is ignored and IIOP Server Handler processing continues normally. However network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client application timeout (ISL command -T option) to reclaim resources associated with dead network connections.
	See Also	The ISL command. For information about the ISL command, see the Administration Guide.
1290	ERROR: Can't parse the address address
	Description	While the networking software was attempting to resolve address, an error occurred.
	Action	Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name and port number portion of address can be located by your server.
1291	ERROR: Can't resolve host name in address address
	Description	While the networking software was attempting to resolve the host name portion of address, an error occurred.
	Action	Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name portion of address can be located by your DNS server.
1292	ERROR: Unknown address type: address
	Description	The given address does not correspond to a type known by the system.
	Action	The WLE software understands several types of address format. Addresses that start with // must be Internet addresses. Other formats may or may not be understood by the WLE software.
1293	ERROR: Can't resolve port number in address address
	Description	While the networking software was attempting to resolve the port number portion of address, an error occurred.
	Action	Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the port number portion of address can be located by your server.
1294	ERROR: Can't convert the address address to binary format
	Description	While the WLE software was trying to convert an address to an internal binary representation, an error occurred.
	Action	Contact BEA Technical Support.
1295	ERROR: Illegal character in the address address
	Description	There is an illegal character in the port portion of address. Ports may only have alphanumeric characters.
	Action	Remove the illegal character from the port portion of the address.
1296	ERROR: Missing port number in the address address
	Description	The address must have a port number portion.
	Action	Supply a port number portion in the given address. Otherwise, the IIOP Server Listener or IIOP Server Handler cannot determine its listening end point properly.
1297	ERROR: Port number cant be bigger than value in the address address
	Description	The port number portion of address is larger than the largest allowable port number of value.
	Action	Change the port number to be within the specified range.