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

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 BEA 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 BEA 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 BEA Customer Support.
	See Also	WSL
1308	ERROR: Component not licensed
	Description	WSL was run, but the command read the BEA Tuxedo license and found that some of the necessary components, including transactions, /Q, /TDomain, TxRPC, Events, WebGUI, and /WS, were not enabled.
	Action	Install a valid BEA 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.
1310	ERROR: The -z (minimum) or -Z (maximum) must be 0, 40, 56 or 128
	Description	The -z and -Z options control the minimum level of link-level encryption required, and the maximum level allowed, respectively. Whenever possible, we recommend using the maximum level allowed. Valid arguments to these options are 0, 40, 56, and 128. The -z option must be followed by an argument that identifies the minimum value; the -Z option, by an argument that indicates the maximum value. The link-level encryption value of 40 bits is provided for backward compatibility.
	Action	Change the incorrect argument of the appropriate option to 0, 40, 56, or 128.
	See Also	WSL(5)
1311	ERROR: Only 56 bit encryption is allowed
	Description	The license installed allows only 56-bit encryption. However, the WSL attempted to set a minimum encryption level greater than 56.
	Action	Either change the -z option to be 56, 40, or 0 bits, or get a license for stronger link-level encryption. The link-level encryption value of 40 bits is provided for backward compatibility. If you believe you are licensed for stronger encryption, contact BEA Customer Support.
	See Also	WSL(5)
1312	ERROR: Could not add workstation information: error code errorcode
	Description	When transforming a buffer to workstation format, the WSH could not add workstation information. Save errorcode to give to BEA Customer Support.
	Action	Please contact BEA Customer Support.
	See Also	WSL
1313	ERROR: Could not add message information: error code val
	Description	When transforming a buffer to native format, the WSH could not add information. Save errorcode to give to BEA Customer Support.
	Action	Please contact BEA Customer Support.
	See Also	WSL
1314	ERROR: Could not add workstation information: error code code
	Description	The workstation handler or workstation listener could not add information necessary for the workstation client. The error code code may assist technical support determine the cause of the failure.
	Action	Please contact BEA Customer Support.
1318	ERROR: Unable to initialize public key subsystem
	Description	A WSH was unable to initialize its public key subsystem. The return value from the subsystem is errorcode.
	Action	Check to ensure the proper public key plug-ins are installed. This can be done with epifregedt. If you believe the proper plug-ins are installed, contact BEA Customer Support.
	See Also	_ec_sec_pki_init, epifregedt
1320	ERROR: Invalid unsolicited message format
	Description	The WSH has received an unsolicited message request in an invalid format. Routing information about intended recipients is missing.
	Action	Please contact BEA Customer Support.
	See Also	WSL, tpnotify, tpbroadcast
1321	ERROR: Invalid internal buffer
	Description	An internal buffer of the WSH used for unsolicited message notifications is corrupt.
	Action	Please contact BEA Customer Support.
	See Also	WSL, tpnotify, tpbroadcast
1322	ERROR: unable to decode or decrypt user data for routing
	Description	Some form of routing was necessary, but the WSH was unable to decrypt the buffer for routing.
	Action	Ensure that the WSH has a proper decryption key for messages requiring routing. Remove the routing from a service if the WSH cannot obtain the proper decryption key. Routing also includes buffer type constraints for a service. If you believe there are no routing criteria, or that the WSH has a decryption key, contact BEA Customer Support.
	See Also	WSL, _ec_sec_pki_init
1323	ERROR: A lockout has occurred because of license violation
	Description	DBBL/BBL lockout occurs because the system has determined that the total number of active users exceeded 110% of BEA Tuxedo system licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count drops below 110% on a subsequent DBBL/BBL scan cycle.
	Action	Upgrade your BEA Tuxedo system license with larger number of users to avoid future system lockouts. Please contact your BEA Tuxedo System Administrator.
1324	ERROR: tpalloc() failed, tperrno = val
	Description	An attempt to dynamically allocate a buffer in the workstation handler 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 tunable parameters to increase the amount of space a process is allowed to dynamically allocate.
	See Also	BEA TUXEDO Workstation Guide, tpalloc(3c), tperrno(5)
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. Using compression may also alleviate this problem. This error may also occur when the BRIDGE is failing over to a new network link or failing back to an high priority link.
1329	ERROR: Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc () failed while processing a tpacall message in the WSH. The message will fail.
	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.
1330	ERROR: Unable to get server group information for WSL
	Description	While booting, a workstation handler must be able to retrieve information about its parent workstation listener process.
	Action	Please contact BEA Customer Support.
1331	ERROR: Unable to get machine information for WSL
	Description	While booting, a workstation handler must be able to retrieve information about its parent workstation listener process.
	Action	Please contact BEA Customer Support.
1332	ERROR: Unable to get server information for WSL
	Description	While booting, a workstation handler must be able to retrieve information about its parent workstation listener process.
	Action	Please contact BEA Customer Support.
1333	ERROR: Sending of reply to security token call to client failed
	Description	An attempt to send a reply to the workstation client with security tokens during the authentication exchange failed.
	Action	Ensure that the client process still exists and that there are no network problems with the connection to the client.
1334	ERROR: Attempt to send encrypted buffer to interoperating site
	Description	An attempt has been made to send a buffer which would have been encrypted to a site older than BEA Tuxedo Release 7.1.
	Action	No buffer is marked for encryption can be sent to a site older than BEA Tuxedo Release 7.1. Upgrade the software on the remote system to handle encrypted buffers, or remove encryption from this buffer.
	See Also	tpseal, tpkey_open
1335	ERROR: Could not decode buffer for interoperating client
	Description	The workstation handler must decode all messages from interoperating clients. However, the postrecv operation failed in the WSH.
	Action	Contact BEA Customer Support
	See Also	buffer
1336	ERROR: Handler received message of unknown format
	Description	A message arrived at the WSH with an unknown format.
	Action	Contact BEA Customer Support.
1337	WARN: WSH has policy SIGNATURE_REQUIRED=signature-required and ENCRYPTION_REQRUIRED=encryption-required but the message from the client was neither signed nor sealed
	Description	If the WSL is in a group that has a SIGNATURE_REQUIRED value of signature-required or an ENCRYPTION_REQUIRED value of encryption-required, then every message originating from a workstation client must be signed or sealed, as determined by the policy. A message came in to the WSH which did not meet the requirement.
	Action	Ensure all messages arriving at a WSH/WSL with the given policy is appropriately signed or sealed.
	See Also	tpsign, tpseal, tpkey_open, ubbconfig
1338	WARN: WSH required encryption but the message from the client was not encrypted
	Description	If the WSL is in a group that has a policy of ENCRYPTION_REQUIRED, then every message originating from a workstation client must be sealed. A message came in to the WSH which did not meet the requirement.
	Action	Ensure all messages arriving at a WSH/WSL with the given policy is sealed.
	See Also	tpseal, tpkey_open, ubbconfig
1339	ERROR: WSH unable to decrypt message in order to enforce SIGNATURE_REQUIRED policy
	Description	If the WSL is in a group that has a policy of SIGNATURE_REQUIRED, then every message originating from a workstation client must be signed. In order to determine if a particular message is signed, the WSH must be able to decrypt the message. However, no decryption key was available to the WSH to decrypt a message from the workstation client.
	Action	Open an appropriate decryption key in the WSH using the public key initialization infrastructure.
	See Also	tpseal, tpkey_open, _e_sec_pki_init ubbconfig
1340	ERROR: Invalid security context
	Description	An internal error occurred in the handler while attempting to enforce signature or encryption policy.
	Action	Contact BEA Customer Support.
1341	WARN: WSH requires encryption but the message from the client is not encrypted
	Description	If the WSL is in a group that has a policy of ENCRYPTION_REQUIRED, then every message originating from a workstation client must be sealed. A message came in to the WSH which did not meet the requirement.
	Action	Ensure all messages arriving at a WSH/WSL with the given policy is sealed.
	See Also	tpseal, tpkey_open, ubbconfig
1342	WARN: WSH requires digital signature but the message from the client is not signed
	Description	If the WSL is in a group that has a policy of SIGNATURE_REQUIRED, then every message originating from a workstation client must be signed. A message came in to the WSH which did not meet the requirement.
	Action	Ensure all messages arriving at a WSH/WSL with the given policy is signed.
	See Also	tpsign, tpkey_open, ubbconfig
1343	WARN: Unable to format orderly release message - error-code
	Description	An internal error of error-code occurred while attempting to format an orderly release message for a workstation client.
	Action	Contact BEA Customer Support.
	See Also	tpterm
1344	WARN: Unable to encode orderly release message
	Description	An internal error occurred while attempting to encode an orderly release message for a workstation client.
	Action	Contact BEA Customer Support.
	See Also	tpterm
1345	ERROR: unable to decode or decrypt user data for routing
	Description	While doing a tpconnect on behalf of a workstation client, the WSH was forced to examine the data in order to route the message properly. However, the WSH could not decrypt the message, and so could not route the message.
	Action	Either open an appropriate decryption key in the WSH using the public key initialization infrastructure, or do not use routing on the conversational service.
	See Also	tpconnect, ubbconfig
1346	ERROR: Invalid network address specified for -n option, val
	Description	The argument passed with the -n option is not a valid network address. See the description of the -n option on the WSL(5) page.
	Action	Correct the CLOPT for the WSL and re-boot the server.
	See Also	WSL
1347	WARN: Unable to invoke audit postop on security failure
	Description	A call to the audit_postop() plugin security function on authentication failure. This call was being attempted due to a failure return from the authentication plugin security function acquire_cred(). No audit of the failure was able to be performed/recorded.
	Action	Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code. In addition, because of the authentication failure, if the failure was not intended, check the registration, authentication configuration, and return from the acquire_cred() plugin security function.
	See Also	epifregedt, epifreg
1348	WARN: Unable to invoke audit postop on security failure
	Description	A call to the audit_postop() plugin security function on a failure to send a message to the client failed. No audit of the failure was able to be performed/recorded.
	Action	Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code.
	See Also	epifregedt, epifreg
1349	WARN: Unable to invoke audit postop on security failure
	Description	A call to the audit_postop() plugin security function during authentication failed. This call was being attempted due to a failure return from the authentication plugin security function accept_sec_context(). No audit of the failure was able to be performed/recorded.
	Action	Check the registration of the auditing plugin. If the plugin used is the default supplied plugin, check the userlog file and filesystem space. If the plugin used is not the default supplied plugin, contact the supplier of the plugin code. In addition, because of the authentication failure, if the failure was not intended, check the registration, authentication configuration, and return from the accept_sec_context() plugin security function.
	See Also	epifregedt, epifreg
1350	ERROR: Pre 7.1 client not allowed. Use -t option on WSL
	Description	A request from a workstation client older than BEA Tuxedo Release 7.1 arrived at the WSH. However, the -t servopts option was not specified on the WSL CLOPT line in the UBBCONFIG. In order to close a possible security hole, the administrator must explicitly tell the WSL that it is allowed to accept requests from older workstation clients.
	Action	If you wish to allow the server to interoperate with sites older than BEA Tuxedo Release 7.1, then the CLOPT for the WSL must contain -t before the -- option.
	See Also	servopts
1351	ERROR: Pre 7.1 client not allowed. Use -t option on WSL
	Description	A request from a workstation client older than BEA Tuxedo Release 7.1 arrived at the WSH. However, the -t servopts option was not specified on the WSL CLOPT line in the UBBCONFIG. In order to close a possible security hole, the administrator must explicitly tell the WSL that it is allowed to accept requests from older workstation clients.
	Action	If you wish to allow the server to interoperate with sites older than BEA Tuxedo Release 7.1, then the CLOPT for the server must contain -t before the -- option.
	See Also	servopts
1352	ERROR: Cannot get security tokens for client
	Description	Tokens are not available for the workstation client. This client's network connection will be dropped.
	Action	Contact your AAA security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support.
1353	ERROR: Failure during security token exchange val
	Description	A fatal error occurred during the GSSAPI exchange of tokens between the workstation client and the workstation handler. The error code was val.
	Action	Contact your AAA security provider. If you are using the default AAA security provider provided by BEA Systems, Inc., then contact BEA Customer Support.
1354	ERROR: Protocol error, second tpinit or security exchange incomplete
	Description	The workstation handler received an initialization request before the security protocol was finished. There may be an attack under way.
	Action	Ensure the security of your network. If the network is secure and operating properly, contact BEA Customer Support.
1355	ERROR: Unable to switch client contexts
	Description	While processing an initialization request, the workstation handler was unable to switch contexts to the context of the workstation client.
	Action	Contact BEA Customer Support.
1356	ERROR: A lockout has occurred because of license violation
	Description	There are too many clients logged in for the current license.
	Action	Upgrade your BEA Tuxedo system license to avoid future system lockouts. Please contact your BEA Tuxedo System Administrator.
1357	ERROR: Invalid tpinit buffer
	Description	The buffer that points to the tpinit buffer in the workstation handler is corrupt.
	Action	Contact BEA Customer Support.
1358	ERROR: Invalid client name given val.
	Description	The client name val is invalid. This name is reserved for special workstation clients provided by BEA Systems.
	Action	Change the client name in the TPINIT buffer of the workstation client. Ensure the security of your network. If the network is secure and operating properly, contact BEA Customer Support.
1359	WARN: Invalid notification option given 0xval, reset to TPU_IGN.
	Description	The notification option val is invalid.
	Action	Remove the option val in the TPINIT buffer of the workstation client. If you believe that the option val is not set in the TPINIT buffer of the workstation client, then contact BEA Customer Support.
1360	ERROR: Failed to update registry table information
	Description	The workstation client was unable to update registry information about a workstation client that tried to log in.
	Action	Contact BEA Customer Support.
1361	ERROR: Memory allocation error
	Description	While attempting to allocate memory for the reply to an initialization request, the workstation hander ran out of memory.
	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.
1362	WARN: setsockopt() for SO_KEEPALIVE failed
	Description	An attempt was made to set the SO_KEEPALIVE socket option on a workstation client link inside the workstation handler. The attempt failed.
	Action	Ensure your TCP/IP stack supports the SO_KEEPALIVE option. If it does, and you believe your network to be operating properly, contact BEA Customer Support.
1363	WARN: KEEPALIVE option requested but not available on this platform
	Description	The keepalive option was requested from the WSH to the WSC, but this platform does not support the KEEPALIVE option.
	Action	Set the -K option on the WSL command line to 'none' or 'client'.
	See Also	WSL(5)
1364	ERROR: Unable to format reply buffer for tpinit
	Description	An internal buffer in the workstation handler was corrupted.
	Action	Contact BEA Customer Support.
1365	ERROR: Unable to send client initialization parameters
	Description	An attempt was made to send client initialization parameters to the workstation client. However, the attempt to send failed.
	Action	Check the network connection. This error could occur if the workstation client was suddenly disconnected from the network. If you believe the workstation client is still connected and that the network is operating properly, contact BEA Customer Support.
1366	ERROR: Pre 7.1 client not allowed. Use -t option on WSL
	Description	A request from a workstation client older than BEA Tuxedo Release 7.1 arrived at the WSH. However, the -t servopts option was not specified on the WSL CLOPT line in the UBBCONFIG. In order to close a possible security hole, the administrator must explicitly tell the WSL that it is allowed to accept requests from older workstation client.
	Action	If you wish to allow the server to interoperate with sites older than BEA Tuxedo Release 7.1 then the CLOPT for the WSL must contain -t before the -- option.
	See Also	servopts
1367	ERROR: Invalid attempt to use older initialization opcode
	Description	A BEA Tuxedo Release 7.1 or later workstation client attempted to use an older initialization opcode. A security attack may be under way.
	Action	Ensure the security of your network. If the network is secure and operating properly, contact BEA Customer Support.
1368	ERROR: Too many client requests are blocked on WSH context(id), request dropped!
	Description	The workstation handler was unable to send the request due to a blocking condition. The message buffered because of the blocking condition exceeded the limitation. A TPESYSTEM error code is returned to WS client.
	Action	Perform one or more of the following actions to relieve the blocking condition. Modify the client application so that there will not be too many requests outstanding for the same context at the same time. You can also configure more application servers in the BEA Tuxedo system configuration file so that request can be handled faster. You may also need to tune the kernel to have a larger message queue.