1300

ERROR: Unlicensed System Binary

Description

A valid license file has not been installed in $TUXDIR/udataobj/lic.txt. This license file must have a section for SALT with the specific version number..

Action

Buy a license and install the provided file in udataobj/lic.txt.

1301

ERROR: Expired System Binary

Description

Your copy of the BEA SALT software is an evaluation copy, and the expiration date has passed.

Action

If you wish to continue using the BEA SALT, contact the company from which you received the product.

1302

ERROR: Invalid option: option

Description

wsadmin(1) has been invoked with an invalid option. The offending option is printed with this error message.

Action

Verify options to wsadmin and re-execute the command.

See Also

wsadmin(1)

1303

ERROR: Invalid argument: argument

Description

wsadmin(1) has been invoked with an invalid argument. The offending option and argument are printed with this error message.

Action

Verify options to wsadmin and re-execute the command.

See Also

wsadmin(1)

1304

ERROR: TUXCONFIG environment variable not set.

Description

The TUXCONFIG environment variable was not set. wsadmin command failed.

Action

Set the TUXCONFIG environment variable to the pathname of the TUXCONFIG file.

See Also

wsadmin(1)

1305

ERROR: TUXCONFIG must be an absolute pathname.

Description

When executing wsadmin, the TUXCONFIG environment variable is not a rooted (full) pathname.

Action

Re-set the TUXCONFIG value to a rooted path for the ubb configuration file.

See Also

wsadmin(1)

1306

Usage: wsadmin [-r] [-v]

Description

Invalid use of wsadmin.

Action

Follow the "Usage:" hint.

See Also

wsadmin(1)

1307

ERROR: Error while obtaining the Bulletin Board parameters

Description

An error was produced in wsadmin while retrieving the Bulletin Board parameters. A more specific error explaining the situation should already exist in the user log.

Action

Check the user log for a more specific error message. Check that the TUXCONFIG is readable, and re-execute the wsadmin command.

See Also

wsadmin(1)

1308

ERROR: Could not determine level of authentication required.

Description

When wsadmin starts up, it calls tpchkauth(3c) to see what level of authentication is required by the application. This message is issued when tpchkauth(3c) fails. tpchkauth(3c) can fail if wsadmin cannot find the TUXCONFIG file.

Action

Make sure the TUXCONFIG environment variable is set correctly.

See Also

wsadmin(1)

1309

ERROR: Could not allocate internal TPINIT typed buffer.

Description

Executing the wsadmin command error. An error was encountered while trying to obtain virtual memory for the TPINIT buffer.

Action

Attempt to identify and stop any extraneous processes to free up virtual memory on your system, and then retry the command.

See Also

wsadmin(1)

1310

ERROR: Could not find entry for user UID.

Description

When wsadmin is invoked, the invoker's login ID is used as the "User Name" when wsadmin joins the application. If there is an error retrieving the invoker's login ID from the system password file, this message is printed.

Action

Contact your system administrator to ensure that your password entry contains your user ID (UID) and your login.

See Also

wsadmin(1)

1312

ERROR: Unable to obtain application password.

Description

If an application password is required, wsadmin either prompts for it (if the invoker is attached to a terminal), or it reads it from the environment variable, APP_PW, if standard input is not a terminal. This message is issued when the password cannot be obtained. The most common cause for this is that APP_PW is not set and standard input is not a terminal.

Action

If wsadmin is not attached to a terminal when invoked, then check that the environment variable, APP_PW, is set correctly.

See Also

wsadmin(1)

1313

ERROR: can't become a client - tpinit() failed - string

Description

Execution of wsadmin failed because the user could not join the application. The printed string indicates the reason for the failure. This message can be printed either because no more clients can join the application or because the user failed security permissions.

Action

If the reason is that no more clients can join the application, re-try the operation a later time. The system should be configured to allow for more clients.

See Also

wsadmin(1)

1316

WARN: Cannot become administrator.

Description

The wsadmin program was not able to enter the administrative mode. A limited set of commands is available (that is, the set of commands available when wsadmin is run with the -r option).

Action

No action required.

See Also

wsadmin(1)

1319

ERROR: Error executing string.

Description

A command was given to wsadmin that was to be executed by the shell. An error was encountered by the shell in executing the command.

Action

Retry the command. If it continues to fail, refer to the system(3S) manual page for reasons why the command may have failed.

See Also

system(3S) in UNIX reference manuals

1320

ERROR: -char option: argument must be numeric.

Description

When the -char option is used as an argument to the wsadmin sub-command, its argument must be a numeric value.

Action

Try the command again with the numeric value for the char option.

See Also

wsadmin(1)

1326

ERROR: Can't allocate memory. (IC=code)

Description

wsadmin detected an error while trying to process the operation specified by the value code. The process was unable to obtain enough virtual memory. The value code is an internal error code for use in diagnosis.

Action

Attempt to identify and stop any extraneous processes to free up virtual memory on your system.

See Also

wsadmin(1)

1327

ERROR: Can't perform the operation. Please check the ULOG for more descriptive message. (IC=code)

Description

wsadmin detected an error while trying to process the operation specified by the value code. The process was unable to perform the operation. The value code is an internal error code for use in diagnosis. The ULOG will contain more specific information.

Action

Check the ULOG for more specific information on the cause of the error. Correct the cause of the error and retry the operation.

See Also

wsadmin(1)

1328

ERROR: gwws_instance_id value is not valid

Description

Action

Please refer to SALTCONFIG for the syntax of GWWS instance id value.

See Also

wsadmin(1), BEA SALT Administration Guide

1329

ERROR: gwws instance is not present

Description

wsadmin detected the specified GWWS instance is not available. Either the GWWS process is not configured in the UBBCONFIG, or the process is not booted.

Action

Check if the specified GWWS instance is configured in the SALTCONFIG as well as in the UBBCONFIG. If not, please refer to BEA SALT administration Guide to configure the desired GWWS instance properly. If your configuration is correct, please check if the specified GWWS process is down. Start it using Tuxedo administrative command if necessary.

See Also

1330

ERROR: call gwws service error(tperrno=code)

Description

wsadmin detected an error while trying to invoke the specified GWWS process. The value code indicates the tperrno of the invocation.

Action

Check if the specified GWWS process is started and the status is healthy. Check the meaning of the tperrno value to help diagnose the process' status.

See Also

wsadmin(1), GWWS(1)