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

LIBWSC Messages 1400-1499

1417	ERROR: Cannot use the -d and -r options together
	Description	The -d and -r options to ud are mutually exclusive. The -d option specifies the maximum delay in receiving a reply before timeout. The -r option states that no reply is expected.
	Action	Change the arguments to the ud command so that the -d and -r options are not both specified, and re-execute the command.
	See Also	ud(1)
1420	ERROR: Unable to get user id
	Description	The ud command was unable to find the user name associated with the numeric user ID of the process invoking ud in the /etc/passwd file.
	Action	Have the UNIX System administrator correct any problems related to the entry of the user invoking ud in the /etc/passwd file.
	See Also	ud(1), getpwent(3C) in UNIX system reference manuals
1422	ERROR: Cannot determine authentication level
	Description	The tpchkauth() function returned an error when called by ud to determine the level of authentication required by the application configuration.
	Action	Attempt to determine why the tpchkauth() function call is failing. Often, this will be due to an incorrect setting of the TUXCONFIG shell variable.
	See Also	ud(1), tpinit(3c)
1424	ERROR: Unable to obtain application password
	Description	The ud command was unable to obtain a value for the application password. This value is entered at the terminal if ud is being invoked interactively, and is gotten from the APP_PW environment variable if the standard input to the ud process is not a terminal.
	Action	If the ud command is being invoked in the background, be sure to set and export the APP_PW environment variable. If ud is being invoked at a terminal, be sure that the user enters a value at the Enter Application Password: prompt.
	See Also	ud(1)
1425	ERROR: Handle entry not found
	Description	The handle in the tpgetrply() argument list is not a valid handle.
	Action	Check the application code to make sure that only handles obtained from the return of tpacall are used. If the handle is valid, then this would indicate an internal problem. In this case, contact BEA TUXEDO system Technical Support.
1426	ERROR: Memory allocation failure
	Description	An attempt to reallocate memory failed during a call to tprealloc().
	Action	Check that size requested is not inappropriately large. If that is not the problem, check that the application is freeing unneeded buffers before attempting to allocate new buffers.
	See Also	tprealloc(3c)
1427	ERROR: Cannot join application - permission denied
	Description	An ATMI function was called in a client before calling tpinit (), and an attempt to join the application failed. The client cannot join the application because it does not have permission to do so or because it did not supply the correct application password. Permission may be denied based on an invalid application password, failure to pass application specific authentication, or use of restricted names.
	Action	This is an application error. If the application has security turned on, then tpinit must be called explicitly with a TPINIT buffer supplying a valid password before calling any other ATMI functions.
	See Also	tpinit(3c)
1428	ERROR: Cannot join application - accesser limit exceeded
	Description	An ATMI function was called in a client before calling tpinit (), and an attempt to join the application failed. The client cannot join the application because of space limitations.
	Action	This is a application configuration problem. The number of accessers is too small and must be reconfigured to allow more clients.
	See Also	ubbconfig(5)
1429	ERROR: Could not access file filename
	Description	An attempt to get the status of a file failed. This file was created for temporary storage of a reply message. This is an operating system error that could be a result of an accidental deletion of the file, a change in file permissions, or a hardware problem.
	Action	Files created for this purpose have a prefix of W. Check for the existence of such files in the specified directory. If none are found, restart the client.
1430	ERROR: Unable to retrieve stored reply
	Description	An attempt to retrieve a stored conversation reply failed. This message was either stored in memory or in a temporary file.
	Action	If the message was stored in memory, then this indicates an internal BEA TUXEDO system problem. In this case the client should be shut down and restarted. Your BEA TUXEDO system Technical Support should be informed. If the message was stored in a temporary file, this could indicate a permissions problem or a hardware failure. Consult your UNIX system administrator in this case.
1431	ERROR: Received conversational message not stored
	Description	The application has asked for a conversational reply with a connection descriptor unknown to the system. This error should have been detected in tprecv. If the descriptor is valid, this indicates an internal BEA TUXEDO system error.
	Action	The application should be restarted. If the problem still occurs, contact your BEA TUXEDO system Technical Support.
1432	ERROR: Send of OWS_RECV message failed
	Description	An attempt to send a request to the Workstation Handler process failed. This could be a result of the network going down, the Workstation Handler process not running, or the site of the Workstation Handler going down.
	Action	Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support.
1433	ERROR: Unable to save a conversational message reply
	Description	An attempt to save a conversational message reply failed. There are two possible causes. The first is that the environment variable WSRPLYMAX was set too high and an attempt to allocate space for the message failed. The second is an attempt to write to a file opened for temporary storage of a reply message failed. This is an operating system error that could be a result of insufficient space in the file system.
	Action	In the first case, the value of WSRPLYMAX should be lowered. The client must be restarted to get the new value. In the second case, the amount of the space on the specified device should be checked.
1434	ERROR: Memory allocation failure
	Description	An attempt to allocate memory to save a conversational message reply failed.
	Action	The value of WSRPLYMAX should be lowered so that messages are stored in temporary files rather than memory. The client must be restarted to get the new value.
1435	ERROR: Unable to store conversational message in temporary file
	Description	An attempt to save a conversational reply message in a temporary file has failed. If the application has the necessary permissions, then the device must be full.
	Action	Check the setting of the environment variable TMPDIR. This may be set to a file system with restrictive permissions, or it may be full. Resetting this variable to a file system with sufficient space may solve the problem.
1436	ERROR: Invalid connection descriptor
	Description	An attempt was made to retrieve a message with an invalid connection descriptor.
	Action	Check for an application error that would cause this situation. If no errors are found, contact your BEA TUXEDO system Technical Support.
1437	ERROR: Unable to read conversational message from temporary file
	Description	An attempt to process a conversational reply failed. Earlier messages indicate the exact nature of the problem.
	Action	Look for earlier messages in the log file (e.g., 1429, 1016, 1077, or 1017).
1438	ERROR: Invalid connection descriptor
	Description	An attempt was made to retrieve a message with an invalid connection descriptor.
	Action	Check for an application error that would cause this situation. If no errors are found, contact your BEA TUXEDO system Technical Support.
1439	ERROR: tpconnect() message send failure
	Description	An attempt to send a request to the Workstation Handler process failed during a tpconnect (). This could be a result of the network going down, the Workstation Handler process not running, or the site of the Workstation Handler going down.
	Action	Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support.
1440	ERROR: tpconnect() get reply failed
	Description	An attempt to receive an acknowledgment to a tpconnect request failed. This could be the result of the network going down, the Workstation Handler process not running, or the site of the Workstation Handler going down.
	Action	Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support.
1441	ERROR: Unable to send message
	Description	An attempt to send a request to the Workstation Handler process failed during a tpsend. This could be a result of the network going down, the Workstation Handler process not running, or the site of the Workstation Handler going down.
	Action	Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support.
1442	ERROR: Unable to get reply
	Description	An attempt to receive an acknowledgment to a tpsend request failed. This could be the result of the network going down, the Workstation Handler process not running, or the site of the Workstation Handler going down.
	Action	Shut the client down and attempt to reconnect. If this fails, contact your BEA TUXEDO system Technical Support.
1443	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc failed while allocating space to hold the compilation parameters in buldclient or buildclt.
	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.
1444	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc failed while allocating space to hold the compilation parameters in buldclient or buildclt.
	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.
1445	ERROR: tpchkauth failed - Uunixerr = errno
	Description	An operating system error occurred while attempting to determine the level of authentication required by the application configuration. A code is printed indicating the specific UNIX System call that failed. These codes may be referenced in the header file <Uunix.h>.
	Action	Attempt to determine why the UNIX System call is failing. Often, this error will occur if the TUXCONFIG shell variable is not set consistently in this process and in the rest of the application.
	See Also	ud(1), tpinit(3c)
1446	ERROR: Cannot create buffer - tpalloc() failed - errmsg
	Description	While executing wud, tpalloc failed to allocate a typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	wud(1), tpalloc(3c)
1447	ERROR: Cannot become a client - tpinit() failed - errmsg
	Description	The wud program was unable to attach to the TUXEDO System/T bulletin board as a client. Further information is contained in the errmsg message associated with tperrno printed as part of the error message.
	Action	The tpinit(3c) manual page contains a description of each error value returned.
	See Also	wud(1), tpinit(3c)
1448	ERROR: tpalloc for TPINIT failed - errmsg
	Description	While executing wud, tpalloc failed to allocate a TPINIT typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	wud(1), tpalloc(3c)
1449	ERROR: Cannot start a transaction - tpbegin() failed - errmsg
	Description	ud attempted to start a transaction and was unsuccessful. Further information is indicated by the errmsg.
	Action	The tpbegin(3c) manual page contains a description of each error value returned.
	See Also	ud(1), tpbegin(3c)
1450	ERROR: Cannot commit transaction - tpcommit() failed - errmsg
	Description	wud encountered an error while attempting to commit a transaction. Quite often, the failure of the transaction commit is due to the failure of one or more of the service participants, or due to transaction timeout. Further information is indicated by the value of errmsg.
	Action	The tpbegin(3c) manual page lists the specific reasons why tpcommit may fail.
	See Also	wud(1), tpbegin(3c)
1451	ERROR: tpalloc for TPINIT failed - errmsg
	Description	While executing wtmconfig, tpalloc failed to allocate a TPINIT typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	tmconfig(1), tpalloc(3c)
1452	ERROR: Cannot become a client - tpinit() failed - errmsg
	Description	While executing wtmconfig, tpinit failed in trying to join the application. The nature of the failure is indicated by errmsg.
	Action	The tpinit(3c) manual page lists the specific reasons why tpinit may fail.
	See Also	tmconfig(1), tpinit(3c)
1453	ERROR: Cannot create buffer - tpalloc() failed - errmsg
	Description	While executing wtmconfig, tpalloc failed to allocate an FML typed buffer. The nature of the failure is indicated by errmsg.
	Action	The tpalloc(3c) manual page lists the specific reasons why tpalloc may fail.
	See Also	tmconfig(1), tpalloc(3c)
1458	ERROR: Invalid installation - can't find file
	Description	This is an unauthorized BEA TUXEDO system installation.
	Action	For a valid installation, contact your BEA TUXEDO system Technical Support.
1460	ERROR: SJIS conversion failed
	Description	Converting an unsolicited message from SJIS to EUC format failed. This indicates that the input data was invalid.
	Action	Check that the application is generating valid SJIS format.
1461	ERROR: EUC conversion failed
	Description	Restoring an unsolicited message from EUC to SJIS format failed. This indicates that the input data was invalid.
	Action	Since this is undoing the earlier action, this error should not occur. Call BEA TUXEDO system Technical Support.
1462	ERROR: EUC conversion failed
	Description	Converting a received message from EUC to SJIS format failed. This indicates that the input data was invalid.
	Action	Check that the application server is generating valid EUC format.
1463	ERROR: SJIS conversion failed
	Description	Converting an unsolicited message to be transmitted from SJIS to EUC format failed. This indicates that the input data was invalid.
	Action	Check that the application is generating valid SJIS format.
1464	ERROR: SJIS conversion failed
	Description	Converting a message to be transmitted from SJIS to EUC format failed. This indicates that the input data was invalid.
	Action	Check that the application is generating valid SJIS format.
1465	ERROR: EUC conversion failed
	Description	Restoring a converted message from EUC to SJIS format failed. This indicates that the input data was invalid.
	Action	Since this is undoing the earlier action, this error should not occur. Call BEA TUXEDO system Technical Support.
1467	ERROR: Unable to initialize type switch
	Description	Initialization of the Workstation client type switch failed.
	Action	Look for earlier messages in the event log for more details (e.g., memory allocation failure).
	See Also	tpinit(3c)
1468	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system failed while processing an AEWaddtypesw call. Additional information about the problem is printed as part of the message.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1470	ERROR: tpcall() failed, tperrmsg
	Description	The command tmconfig(1) received a failure return from tpcall(3c) while processing the requested dynamic configuration request. The specific cause of the failure is indicated in tperrmsg.
	Action	Determine from the specific cause of the error if the problem can be corrected administratively or is a transient problem (for example, a timeout). Contact your BEA TUXEDO system Technical Support for assistance if unsure of how to resolve the situation.
	See Also	Administering the BEA TUXEDO System, tmconfig(1)
1472	ERROR: Cannot map XID to string, invalid mchidshift setting
	Description	An error occurred when mapping an XID to string.
	Action	This error should not normally occur. Call BEA TUXEDO system Technical support.
	See Also	tpcvt(3c)
1473	ERROR: Cannot map XID string to structure on /WS platforms
	Description	A Workstation client called tpcvt() to convert an XID to a structure. This feature is not supported of Workstation clients.
	Action	Re-write the client so that it no longer does this operation. If needed, write a service that does this operation on behalf of the client.
	See Also	tpcvt(3c)
1474	WARN: Trace specification contains pattern; ignored
	Description	A trace specification includes a regular expression pattern. This feature is not supported on MAC workstations.
	Action	Re-write the client to not use regular expressions in the trace specification.
	See Also	trace(3c)
1475	ERROR: Cannot convert message with unknown protocol num
	Description	A Workstation client received a message from a Workstation Handler (WSH) with an unknown protocol number, num.
	Action	Check that the WSTYPE environment variable is correctly set so that encoding is done if necessary. Validate that the correct Workstation software is being used with the associated WSH. You may need to contact your BEA TUXEDO system Technical Support.
1476	ERROR: Cannot convert message from protocol num1 to num2
	Description	The Workstation client received a message to or from a Workstation Handler (WSH) with a protocol version that cannot be converted.
	Action	Contact your BEA TUXEDO system Technical Support.
1477	INFO: WS Handler has been shutdown
	Description	A Workstation client received a shutdown message from the Workstation Handler. Further operations will fail until the client re-joins the application.
	Action	No action required.
	See Also	tpinit(3c)