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

WSNAT Messages 1300-1399

1304	ERROR: Failed to encode/decode establish connection request message
	Description	The WSH was unable to encode or decode the initial message that establishes a connection to a workstation client.
	Action	Please contact your BEA TUXEDO System Customer Support.
	See Also	WSL
1305	ERROR: Encoding/decoding of ticket request failed
	Description	The WSH was unable to encode or decode part of the challenge response protocol between itself and a workstation client.
	Action	Please contact your BEA TUXEDO System Customer Support.
	See Also	WSL
1306	ERROR: Encoding/decoding of ticket request failed
	Description	The WSH was unable to encode or decode part of the challenge response protocol between itself and a workstation client.
	Action	Please contact your BEA TUXEDO System Customer Support.
	See Also	WSL
1308	ERROR: Component not licensed
	Description	WSL was run but the command read the TUXEDO license and found that some of the necessary components, including transaction, /Q, /TDomain, TxRPC, Events, WebGUI, and /WS, were not enabled.
	Action	Install a valid TUXEDO license file, that allows for all components support, in $TUXDIR/udataobj before running the command.
1309	ERROR: Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed in the WSH while processing an unsolicited message that requires an acknowledgement.
	Action	Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
1328	ERROR: Bad conversational sequence number
	Description	Conversations are sequenced in order to provide protection. One of the conversational messages arrived out of order. The conversation has been disconnected, and if a transaction was active, it has been set to the ABORTONLY state.
	Action	Look at the userlog to determine whether or not the BRIDGE has given up sending any messages to the message queue for the workstation handler. If it has, the operating system may need to be tuned to properly handle a high volume of messages. This problem may also be alleviated by using compression. This error may also occur when the BRIDGE is failing over to a new network link or failing back to an high priority link.