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

LIBWSC Messages 1300-1399

1310	ERROR: Option -d argument 'arg_value' is not numeric
	Description	The -d option to the ud command specifies the maximum delay time in seconds before timeout. The -d option requires an argument, which must be numeric. The option argument supplied was not numeric.
	Action	Correct the argument to the ud command so that the -d option is numeric, and re-execute the command.
	See Also	ud(1)
1311	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)
1312	ERROR: Argument 'arg_value' to option -e is not numeric
	Description	The -e option to ud specifies the maximum number of allowable errors before the process exits. This option requires a numeric argument. The argument specified was not numeric.
	Action	Correct the arguments to the ud command so that the -e option is numeric, and re-execute the command.
	See Also	ud(1)
1313	ERROR: Argument 'arg_value' to -s is not numeric
	Description	The -s option to ud specifies a sleep time between requests. This option requires an option argument, which must be numeric. The option argument specified by the user was not numeric.
	Action	Correct the arguments to the ud command so that the -s option is numeric, and re-execute the command.
	See Also	ud(1)
1314	ERROR: Argument 'arg_value' to -t is not numeric
	Description	The -t option to ud specifies a transaction timeout value in seconds. This option requires an option argument, which must be numeric. The option argument specified by the user was not numeric.
	Action	Correct the arguments to the ud command so that the -t option is numeric, and re-execute the command.
	See Also	ud(1)
1315	ERROR: Cannot use the -t and -r options together
	Description	The user specified options to ud that combined the transaction mode option, -t, with the no reply option, -r. This is not allowed.
	Action	Change the arguments to the ud command so that the -r and -t options are not both specified, and re-execute the command.
	See Also	ud(1)
1316	ERROR: Cannot use the -t and -d options together
	Description	The user specified options to ud that combined the transaction mode option, -t, with the message delay option, -d. This is not allowed.
	Action	Change the arguments to the ud command so that the -d and -t options are not both specified, and re-execute the command.
	See Also	ud(1)
1319	ERROR: ud detected syntax error in fielded buffer # number
	Description	One of the fielded buffers passed as input to the ud program has invalid syntax.
	Action	Inspect the input data to ud and correct any errors in the input format.
	See Also	ud(1)
1320	ERROR: No service in FBFR
	Description	One of the input buffers to ud did not contain a service name.
	Action	Be sure to include a line with fieldname SRVCNM, a tab character, and the name of a service in every fielded buffer input to ud.
	See Also	ud(1)
1322	ERROR: Cannot send buffer buf
	Description	ud was unable to send a buffer to the requested service. It is also possible that the transaction or service timed out. A description of the particular error encountered is included in the latter half of the message.
	Action	To deal with the most common causes of this error, verify that the service specified in the ud input buffer exists, is not a conversational service, and is available, that the service accepts FML input buffers, and that the server supports transactions if the -t option of ud was specified. The tpcall(3c) manual page contains information on these and other conditions that could cause an error return from tpacall.
	See Also	ud(1), tpcall(3c)
1324	ERROR: Return packet time out
	Description	A service call request made by ud has timed out. This can occur either due to a transaction timeout or a blocking timeout.
	Action	Determine whether it is necessary to allocate a longer time for this transaction or service call to complete. If so, increase the time specified with the -t option if using transaction mode, or use the -d option if not running in transaction mode. Reexecute the failed request.
	See Also	ud(1), tpcall(3c)
1325	ERROR: Reply failure - tperrno_message
	Description	The tpgetrply function was called from within ud to receive the response from a service request, and returned an error. A description of the particular error encountered is included in the latter part of the message.
	Action	Refer to the tpcall(3c) manual page for information on the particular errors returned.
	See Also	ud(1), tpcall(3c)
1329	ERROR: Too many errors encountered, exiting!
	Description	The ud command has encountered too many errors, and is exiting. The maximum number of allowable errors defaults to 25, and may be specified explicitly using the -e option.
	Action	Investigate the earlier errors reported by ud, and try to eliminate as many as possible. If it is an expected condition for a large number of service calls to return errors, invoke with the -e option to specify an explicit error limit.
	See Also	ud(1)
1331	ERROR: Invalid option - argument to -u not n, u, or j
	Description	The command option -u was specified for wud but the argument was not n, u, or j. This option specifies how the request buffer is modified before reading each new packet. The n argument indicates that the buffer should be re-initialized (treated as new). The u argument indicates that the buffer should be updated with the reply buffer using Fupdate(3fml). The j argument indicates that the reply buffer should be joined with the request buffer using Fojoin(3fml).
	Action	Re-execute the command using a valid -u argument.
	See Also	wud(1)
1332	ERROR: Unable to set mode to NONBLOCK
	Description	An attempt to set the mode of reading from the network to nonblocking has failed. This indicates a network problem.
	Action	Check that the network is not down. If this is not the problem, contact your BEA TUXEDO system Technical Support.
1333	ERROR: Unable to reset mode to BLOCK
	Description	An attempt to change the mode of reading from the network to blocking has failed. This indicates a network problem.
	Action	Check that the network is not down. If this is not the problem, contact your BEA TUXEDO system Technical Support.
1334	ERROR: Unable to allocate connection buffer
	Description	An attempt to allocate memory to store a message has failed. A message must be sent to the Workstation Listener process in order to get the network address of the Workstation Handler. The system has failed in an attempt to allocate space for this message. This error would indicate the workstation does not have sufficient memory to join an application successfully.
	Action	Consult your system administrator.
1336	ERROR: Invalid handle returned
	Description	A handle with a negative value has been returned by the Workstation Handler. This message indicates a system problem with the Workstation Handler.
	Action	Contact your BEA TUXEDO system Technical Support for advice.
1337	ERROR: Handle must be 0 for TPNOREPLY
	Description	A handle with a value other than zero has been returned by the Workstation Handler. When tpacall is invoked with a flag value of TPNOREPLY, the handle returned should be zero. This message indicates that the Workstation Handler has returned a handle other than zero. This is a system problem.
	Action	Contact your BEA TUXEDO system Technical Support for advice.
1338	ERROR: Unable to send ticket to WSH
	Description	An attempt to send a message containing the security ticket to the Workstation Handler process has failed. This message indicates that the network may have gone down, the Workstation Handler process may not be running, or the host machine may have gone down.
	Action	Check with your system administrator for any of these problems. If there is still a problem, contact your BEA TUXEDO system Technical Support.
1342	ERROR: Unable to establish signal handler, switching to DIP-IN
	Description	An attempt to set a signal handler function has failed. This function is called when LIBNET receives a signal. With this failure, the system has changed the method for receiving unsolicited messages to DIP-IN. This is an internal problem.
	Action	Contact your BEA TUXEDO system Technical Support. It should be noted that the client will not receive unsolicited messages by DIP-IN notification if it has not called tpsetunsol to set the appropriate function. If there is a problem with signal based notification, some changes must be made to the client code to use DIP-IN.
1344	ERROR: Decryption of challenge request failed
	Description	While a Workstation client was attempting to join the application, decrypting the challenge request message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1345	ERROR: Encryption of challenge request failed
	Description	While a Workstation client was attempting to join the application, encrypting the challenge request message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1346	ERROR: Couldn't create encryption/decryption schedule
	Description	While a Workstation client was attempting to join the application, the encryption or decryption schedule could not be created.
	Action	Contact your BEA TUXEDO system Technical Support.
1347	ERROR: Failed to encode/decode establish connection request message
	Description	While a Workstation client was attempting to join the application, encoding or decoding of the establish connection request message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1348	ERROR: Decryption of challenge reply failed
	Description	While a Workstation client was attempting to join the application, decrypting the challenge reply message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1349	ERROR: Encryption of challenge reply failed
	Description	While a Workstation client was attempting to join the application, encrypting the challenge reply message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1350	ERROR: Encoding/decoding of ticket request failed
	Description	While a Workstation client was attempting to join the application, encoding or decoding the ticket request message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1351	ERROR: Encoding/decoding of ticket request failed
	Description	While a Workstation client was attempting to join the application, encoding or decoding the ticket request message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1352	ERROR: Decryption of TPINIT buffer failed
	Description	While a Workstation client was attempting to join the application, decrypting the TPINIT message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1353	ERROR: Encoding/decoding of TPINIT buffer failed
	Description	While a Workstation client was attempting to join the application, encoding or decoding the TPINIT message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1354	ERROR: Encryption of TPINIT buffer failed
	Description	While a Workstation client was attempting to join the application, encrypting the TPINIT message failed.
	Action	Contact your BEA TUXEDO system Technical Support.
1355	ERROR: Unknown work station message to process
	Description	While a Workstation client was attempting to join the application, an unknown message type was encountered for processing.
	Action	Contact your BEA TUXEDO system Technical Support.
1356	ERROR: Tried to process unexpected message opcode 0xcode
	Description	While a Workstation client was attempting to join the application, an unknown message type was encountered for processing.
	Action	Contact your BEA TUXEDO system Technical Support.
1357	ERROR: Received message not intended for this client
	Description	The Workstation Handler has returned the wrong identifier to this client. This is an internal error. The Workstation Handler process may need to be restarted.
	Action	Contact your BEA TUXEDO system Technical Support.
1364	ERROR: Unable to get TPINIT buffer
	Description	An attempt to send a message to the Security server failed because the buffer used was not obtained by a call to tpalloc with a buffer type of TPINIT.
	Action	When attempting to join an application with authentication, the client application must pass a buffer of type TPINIT to the tpinit call.
1365	ERROR: System buffer already in use
	Description	A system buffer was passed to tpinit. This is an internal error.
	Action	Contact your BEA TUXEDO system Technical Support.
1366	ERROR: Unable to get reply to challenge request
	Description	An attempt to receive a reply to a challenge request has failed. This is an error that 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	Contact your BEA TUXEDO system Technical Support.
1367	ERROR: Received message not intended for this client
	Description	An attempt to receive a reply to a challenge request has resulted in an invalid client id being returned to the client. This is an internal error that indicates a problem between the Workstation Client and the Workstation Handler.
	Action	Contact your BEA TUXEDO system Technical Support.
1368	ERROR: Challenge reply returned an error
	Description	The return value in the challenge reply message indicates an error.
	Action	Check the value of tperrno for an indication of the nature of the error.
1369	ERROR: Memory allocation failure
	Description	An attempt to allocate memory to store a security ticket has failed. The system has failed in an attempt to allocate space for this structure. This error would indicate the workstation does not have sufficient memory to successfully join an application.
	Action	Consult your system administrator.
1370	ERROR: Unable to send ticket message
	Description	An attempt to send a security ticket has failed. This error occurred on a network send. This would indicate either a network problem, a problem with the host machine, or that the Workstation Handler process is no longer running.
	Action	For these situations, consult the BEA TUXEDO system administrator.
1371	ERROR: Unable to get reply to OWS_TICKET request
	Description	An attempt to receive the confirmation reply to the security ticket request has failed. This error occurred on a network receive. This would indicate either a network problem, a problem with the host machine, or that the Workstation Handler process is no longer running.
	Action	For these situations, consult the BEA TUXEDO system administrator.
1372	ERROR: Received message not intended for this client
	Description	The reply to the message that sent the ticket request contains an invalid client id. This is an internal error that indicates a problem between the Workstation Client and the Workstation Handler.
	Action	Contact your BEA TUXEDO system Technical Support.
1373	ERROR: System returned error to OWS_TICKET request
	Description	The return value in the ticket reply message indicates an error.
	Action	Check the value of tperrno for an indication of the nature of the error.
1374	ERROR: Failed to create decryption schedule
	Description	An error was detected during a call to _tpcryptinit. This is an internal error.
	Action	Contact your BEA TUXEDO system Technical Support.
1375	ERROR: Unable to send challenge request
	Description	An attempt to send a message containing the challenge request to the Workstation Handler process has failed. This message would indicate that the network may have gone down, the Workstation Handler process may not be running, or the host machine may have gone down.
	Action	Check with your system administrator for any of these problems. If there is still a problem, contact your BEA TUXEDO system Technical Support.
1377	ERROR: Signal based notification not allowed for DOS client, changing to DIP-IN
	Description	The client has chosen to be notified of unsolicited messages by signals. However, DOS and MAC do not support signals, so the BEA TUXEDO system has changed the method to DIP-IN.
	Action	This change means that the client will only receive these messages when it is receiving a reply to an ATMI call. The application developer may wish to use tpchkunsol for this purpose.
1379	ERROR: Unable to get user id
	Description	While executing wtmconfig, the program was unable to get the password entry based on the current user identifier.
	Action	Make sure that a password entry exists for the administrator who is running the wtmconfig command. Contact your BEA TUXEDO system Technical Support.
	See Also	wtmconfig(1)
1380	ERROR: tpchkauth failed - Uunixerr = code
	Description	While executing wtmconfig, 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	wtmconfig(1), tpchkauth(3c)
1381	ERROR: Cannot determine authentication level
	Description	The tpchkauth function returned an error when called by wtmconfig 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	wtmconfig(1), tpinit(3c)
1383	ERROR: Unable to obtain application password
	Description	The wtmconfig command was unable to obtain a value for the application password. This value is entered at the terminal if wtmconfig is being invoked interactively, and is gotten from the APP_PW environment variable if the standard input to the wtmconfig process is not a terminal.
	Action	If the wtmconfig command is being invoked in the background, be sure to set and export the APP_PW environment variable. If wtmconfig is being invoked at a terminal, be sure that the user enters a value at the Enter Application Password: prompt.
	See Also	wtmconfig(1)
1386	ERROR: Cannot open filename
	Description	When writing out the current buffer values, wtmconfig was unable to create and open a temporary file for writing (in the current directory for DOS, or /tmp for UNIX).
	Action	Check that the directory has write and execute permissions set correctly, and that the file system has the proper resources for creating and writing a file.
	See Also	wtmconfig(1)
1389	ERROR: Cannot find the tpadmin field table in dir
	Description	While executing wtmconfig, the program was unable to get the field identifier for TA_SECTION from the field table $TUXDIR/udataobj/tpadmin.
	Action	Make sure that the tpadmin field table exists and is readable. Contact your BEA TUXEDO system Technical Support.
	See Also	wtmconfig(1)