CMDTUX MESSAGES 1700-1799

1700 ERROR: Could not execute, executable file not found

DESCRIPTION

While activating a server, the new program could not be started (forked or spawned) because either the program does not exist or it is not correctly in the execution path.

ACTION

Check the existence of the desired server, the configured environment (TUXDIR and APPDIR) and that the server is executable. Re-try the operation.

SEE ALSO

TM_MIB(5), ubbconfig(5)

1701 WARN: Status uncertain, Timeout period expired on /Admin blocking request

DESCRIPTION

While trying to activate a server on a remote machine, the operation timed out. The status of the activation is not certain.

ACTION

Retrieve the status of active servers to determine the status of the server; it may still boot after a delay. Check the event log for the remote machine to see if there are administrative messages regarding the status of the server.

SEE ALSO

TM_MIB(5)

1702 ERROR: Could not execute, network send error

DESCRIPTION

While trying to activate a server on a remote machine, a network error occurred while sending the request.

ACTION

Check the event log for related messages. The remote machine or the network may not be available.

SEE ALSO

TM_MIB(5)

1703 WARN: Status uncertain, Timeout period expired on /Admin blocking request

DESCRIPTION

While trying to activate a server on a remote machine, the operation timed out. The status of the activation is not certain.

ACTION

Retrieve the status of active servers to determine the status of the server; it may still boot after a delay. Check the event log for the remote machine to see if there are administrative messages regarding the status of the server.

SEE ALSO

TM_MIB(5)

1704 WARN: Status uncertain, network receive error

DESCRIPTION

While trying to activate a server on a remote machine, a network error occurred while receiving information about the request.

ACTION

Check the event log for related messages. The remote machine or the network may not be available.

SEE ALSO

TM_MIB(5)

1705 WARN: Status uncertain, pipe synchronization error

DESCRIPTION

While trying to activate a server, the indication from the server that it is booted did not occur. Usually this indicates that the server did not activate correctly (e.g., it exited or aborted execution).

ACTION

Check the event log for related messages. If the server is not running and no messages appear, check to see if the program is running using operating system services. Also check for a core dump in $APPDIR.

SEE ALSO

TM_MIB(5)

1706 ERROR: No BBL available, cannot boot

DESCRIPTION

An activation request for a server was received but the administrative servers for that machine have not yet been activated.

ACTION

Activate the administrative servers for a machine before any application servers.

SEE ALSO

TM_MIB(5)

1707 ERROR: No DBBL available, cannot boot

DESCRIPTION

An activation request for a server was received but the administrative servers for that machine have not yet been activated.

ACTION

Activate the administrative servers for a machine before any application servers.

SEE ALSO

TM_MIB(5)

1708 ERROR: Invalid or unspecified administrative password

DESCRIPTION

While activating a server on a remote site, an invalid administrative password was sent to or received from the remote machine.

ACTION

There are two possible ways to correct this problem. One is to set up the user invoking tmboot to include the appropriate password setting via the TUXADMPWFILE environment variable. The second is to modify the password file indicated on the tlisten command line to include the administrative password for this application.

SEE ALSO

tmboot(1), tlisten(1)

1709 ERROR: Failed with System/T error message

DESCRIPTION

While activating a server, a TUXEDO error occurred. The message will indicate the specific problem Typically, it involves the configurations (e.g., there might not be enough service or accessor entries).

ACTION

Correct the error and re-try the operation.

SEE ALSO

TM_MIB(5)

1710 ERROR: Failed with code code

DESCRIPTION

While activating a server, a TUXEDO error occurred. The message will indicate the specific problem Typically, it involves the configurations (e.g., there might not be enough service or accessor entries).

ACTION

Correct the error and re-try the operation.

SEE ALSO

TM_MIB(5)

1711 ERROR: Could not boot any servers

DESCRIPTION

A TMIB request to activate one or more servers failed (no servers were booted).

ACTION

Check the event log for earlier related messages.

SEE ALSO

TM_MIB(5)

1712 ERROR: Could not tmunloadcf config file for propagation to remote site

DESCRIPTION

As part of booting a non-master machine, the configuration file is unloaded and propagated to the remote machine. This operation failed.

ACTION

Check that $TUXDIR/bin/tmunloadcf exists and is executable. Check for operating system errors that might prevent its execution (lack of system resources such as process table entries, free space in the file system, etc.). Correct the problem and re-try the operation.

SEE ALSO

TM_MIB(5)

1713 ERROR: Could not access unloaded configuration file for propagation

DESCRIPTION

As part of booting a non-master machine, the configuration file is unloaded and propagated to the remote machine. This operation failed because the temporary file created to hold the configuration could not be opened.

ACTION

Check for operating system errors that might prevent its execution (free space in the file system, etc.). Correct the problem and re-try the operation. Contact your TUXEDO System Technical Support.

SEE ALSO

TM_MIB(5)

1714 ERROR: Send failure on TUXCONFIG propagation to lmid

DESCRIPTION

As part of booting a remote machine, an error occurred in propagating the configuration file. Check the event log, both on the master and remote machines for related messages.

ACTION

Check the event log, both on the master and remote machines for related messages. Correct the problem and re-try the operation.

SEE ALSO

TM_MIB(5)

1715 ERROR: Receive failure on TUXCONFIG propagation to lmid

DESCRIPTION

As part of booting a remote machine, an error occurred in propagating the configuration file. Check the event log, both on the master and remote machines for related messages.

ACTION

Check the event log, both on the master and remote machines for related messages. Correct the problem and re-try the operation.

SEE ALSO

TM_MIB(5)

1716 ERROR: Could not create remote tmp file on lmid for file creation

DESCRIPTION

As part of booting a non-master machine, lmid, an error occurred in propagating the configuration file. Check the event log, both on the master and remote machines for related messages.

ACTION

Check the event log, both on the master and remote machines for related messages.

SEE ALSO

TM_MIB(5)

1717 ERROR: tmloadcf error on lmid for file creation, tmloadcf output:

DESCRIPTION

While processing a TMIB request to boot a non-master machine, an error failed in loading the configuration file. The message will contain the output of the failed load command.

ACTION

Check the message to determine the problem. Correct the problem and re-try the operation.

SEE ALSO

tmloadcf(1), TM_MIB(5)

1719 ERROR: Unknown error propagating TUXCONFIG file to lmid

DESCRIPTION

While activating a non-master machine, an error occurred in propagating the configuration file to the remote machine, lmid.

ACTION

Check the event log for related messages. Correct the problem and re-try the operation.

SEE ALSO

tmloadcf(1), TM_MIB(5)

1729 WARN: Status uncertain, Timeout period expired on /Admin blocking request

DESCRIPTION

While trying to activate a server on a remote machine, the operation timed out. The status of the activation is not certain.

ACTION

Retrieve the status of active servers to determine the status of the server; it may still boot after a delay. Check the event log for the remote machine to see if there are administrative messages regarding the status of the server.

SEE ALSO

TM_MIB(5)

1730 INFO: About to activate server

DESCRIPTION

This message indicates that a server is about to be activated in response to a TMIB request.

ACTION

No action required.

SEE ALSO

TM_MIB(5)

1731 INFO: About to deactivate server

DESCRIPTION

This message indicates that a server is about to be deactivated in response to a TMIB request.

ACTION

No action required.

SEE ALSO

TM_MIB(5)

1732 ERROR: Application initialization failure

DESCRIPTION

A server activation failed because the server initialization function returned an error.

ACTION

Administrative servers normally write a message to the event log. If this is an application server, then check whatever feedback mechanism is used in the application.

SEE ALSO

tpsvrinit(3)

1733 INFO: Duplicate server

DESCRIPTION

A server activation failed because a server with the same TA_SRVGRP and TA_SRVID is already active.

ACTION

No action required.

SEE ALSO

TM_MIB(5)

1734 ERROR: Identifier for DOMAINID must be <= number characters in length

DESCRIPTION

The value specified for the DOMAINID parameter in the *RESOURCES section of the ubbconfig(5) file is longer than number characters in length.

ACTION

Shorten the value specified for this attribute and rerun tmloadcf(1).

SEE ALSO

"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)

1735 WARN: Timeout period expired on /Admin request

DESCRIPTION

While processing a TMIB request for tlisten information, the operation timed out. Normally this indicates that the remote machine or the network is unavailable or slow.

ACTION

Check the event log for the remote machine to see if there are administrative messages regarding the status of the machine.

SEE ALSO

TM_MIB(5)

1736 ERROR: Services names beginning with '.' are reserved for system servers

DESCRIPTION

buildserver(1) was invoked with a -s option that attempted to build a reserved service name beginning with '.' into an application server.

ACTION

Modify the options to the buildserver(1) command to eliminate the reserved service name.

SEE ALSO

"TUXEDO Programmer's Guide" , buildserver (1)

1737 ERROR: Could not process internal *MIBPERMS section

DESCRIPTION

While loading an application configuration, multiple *MIBPERMS sections exist or the value of a string is greater than 30 characters in length.

ACTION

Normally, this section is not generated by te administrator, but is generated only during activation of a remote machine. Contact your TUXEDO System Technical Support.

SEE ALSO

TM_MIB(5), ubbconfig(5)

1738 ERROR: Invalid command name cmdname

DESCRIPTION

The executable file tpaddusr(1) was invoked with a name, cmdname, other than the permissible names of tpaddusr, tpdelusr, and tpmodusr. This is caused by an application copying or linking the delivered executable to a differently named executable file.

ACTION

Modify the command line to use the supported command names.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1739 ERROR: usage: cmdname <usrname> <file> [<cltname>]

DESCRIPTION

Either the tpdelusr or tpmodusr command (indicated by cmdname) was invoked improperly.

ACTION

Correct the command line and retry the command.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1740 ERROR: usage: cmdname <usrname> <file> [<cltname> [<uid>]]

DESCRIPTION

The tpaddusr command (indicated by cmdname) was invoked improperly.

ACTION

Correct the command line and retry the command.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1741 ERROR: User name (usr) is too long, maximum num characters

DESCRIPTION

The username usr specified on the tpaddusr, tpdelusr, or tpmodusr command line is too long (greater than num characters).

ACTION

Correct the command line and retry the command.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1742 ERROR: Non-numeric value for user id

DESCRIPTION

The user id specified on the tpaddusr, tpdelusr, or tpmodusr command line is non-numeric.

ACTION

Correct the command line and retry the command.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1743 ERROR: Client name (clt) is too long, maximum num characters

DESCRIPTION

The client name clt specified on the tpaddusr, tpdelusr, or tpmodusr command line is too long (greater than num characters).

ACTION

Correct the command line and retry the command.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1744 ERROR: Could not access file file, error

DESCRIPTION

The password file file could not be accessed due to a UNIX error indicated by the message error.

ACTION

Correct the problem using the appropriate UNIX tools as indicated by the UNIX error message displayed.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1745 ERROR: Could not open file file for read/write

DESCRIPTION

The password file file could not be accessed for update due to a UNIX permissions restriction.

ACTION

Correct the permissions on the relevant files and/or directories and retry the command.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1746 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed while processing one of the following commands; tpaddusr, tpdelusr, or tpmodusr.

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.

SEE ALSO

malloc (3) in UNIX System reference manuals, tpaddusr (1)

1748 ERROR: User already exists

DESCRIPTION

The user being added using the tpaddusr command already exists in the password file.

ACTION

Use the command tpmodusr to modify an existing user's entry in the password file.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1749 ERROR: Failed to add user

DESCRIPTION

The user could not be added to the password file because of errors that occurred while prompting or attempting to prompt for a password value for the user.

ACTION

Be sure to run tpaddusr with stdin from the terminal, and be sure not to interrupt the command with the break key or any other interrupts.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1750 ERROR: Invalid user specified for deletion

DESCRIPTION

The user was not found in the password file and therefore could not be deleted.

ACTION

Check that the correct user name is being used and rerun the tpdelusr command if necessary.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1751 ERROR: Invalid user specified for modification

DESCRIPTION

The user was not found in the password file and therefore could not be modified.

ACTION

Check that the correct user name is being used and rerun the tpmodusr command if necessary.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1752 ERROR: Failed to modify user

DESCRIPTION

The user could not be modified in the password file because of errors that occurred while prompting or attempting to prompt for a new password value for the user.

ACTION

Be sure to run tpmodusr with stdin from the terminal, and be sure not to interrupt the command with the break key or any other interrupts.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1753 ERROR: Could not open file file for writing

DESCRIPTION

The password file could not be opened for writing.

ACTION

Be sure the directories and permissions allow the password file to be created and written as necessary.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1754 ERROR: System error writing file file, error

DESCRIPTION

The password file file could not be written due to a UNIX error indicated by the message error.

ACTION

Correct the problem using the appropriate UNIX tools as indicated by the UNIX error message displayed.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1755 ERROR: tpsvrinit: can't retrieve own table entry

DESCRIPTION

A migrating DBBL could not retrieve its own server table entry from the bulletin board. This indicates a corrupt bulletin board on the backup master site.

ACTION

Contact your TUXEDO System Technical Support for assistance in recovering the application. Consideration may need to be given to using protected mode access to avoid bulletin board corruption by the application.

SEE ALSO

tmadmin (1), ubbconfig (5)

1757 ERROR: Invalid class specified

DESCRIPTION

An error occurred in handling a TMIB request for the T_BRIDGE class.

ACTION

Check the event log for additional information.

SEE ALSO

TM_MIB(5)

1758 WARN: Could not update master site information completely

DESCRIPTION

System tables identifying master site information could not be updated due to failed configuration file access and/or table lookup.

ACTION

Shut down the site on which the message appeared as soon as possible and reboot it to force repropagation of up to date information.

SEE ALSO

tmadmin (1), tmboot (1), tmshutdown (1)

1759 WARN: Could not update master site information

DESCRIPTION

System tables identifying master site information could not be updated due to failed configuration file access and/or table lookup.

ACTION

Shut down the site on which the message appeared as soon as possible and reboot it to force repropagation of up to date information.

SEE ALSO

tmadmin (1), tmboot (1), tmshutdown (1)

1760 WARN: BB out of date, machine=lmid

DESCRIPTION

The logical machine lmid has an out of date bulletin board, most likely due to communications failures or delays.

ACTION

None. The system reacts to this situation automatically by propagating a new copy of the bulletin board to the affected site.

1761 WARN: TUXCONFIG file out of date, machine=lmid

DESCRIPTION

The logical machine lmid has an out of date configuration file, most likely due to communications failures or delays.

ACTION

None. The system reacts to this situation automatically by propagating a new copy of the configuration file to the affected site.

1762 INFO: Sending new TUXCONFIG file to machine lmid

DESCRIPTION

The system has determined that the logical machine lmid has an out of date configuration file and is sending a new copy to that site.

ACTION

None.

1763 ERROR: Failed to find configuration information on machine lmid

DESCRIPTION

The system could not find configuration information about the logical machine lmid that it needs to propagate a new configuration file to that machine.

ACTION

Contact your TUXEDO System Technical Support.

1764 ERROR: Failed to propagate updated configuration information to machine lmid

DESCRIPTION

The system could not propagate a new configuration file to the logical machine lmid.

ACTION

Check to make sure the tlisten(1) process is still running on the indicated machine and that the permissions for directories and files are correct for that machine's configuration file.

SEE ALSO

tlisten (1)

1766 ERROR: tpcall() failed, tperrmsg

DESCRIPTION

The command tmconfig(1) received a failure return from tpcall(3) 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 TUXEDO System Technical Support for assistance if unsure of how to resolve the situation.

SEE ALSO

"TUXEDO Administrator's Guide" , tmconfig (1)

1768 ERROR: Passwords do not match

DESCRIPTION

The passwords entered for the original and confirming password prompts when executing the command tpaddusr(1) do not match.

ACTION

Retry the command being careful to enter identical password entries for the two prompts.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1769 ERROR: Passwords do not match

DESCRIPTION

The passwords entered for the original and confirming password prompts when executing the command tpmodusr do not match.

ACTION

Retry the command being careful to enter identical password entries for the two prompts.

SEE ALSO

tpaddusr (1), AUTHSVR (5)

1771 WARN: MAXDRT increased from num1 to num2 to meet configured routing criteria

DESCRIPTION

The configured value num1 for the MAXDRT parameter in the *RESOURCES section of the ubbconfig(5) file was automatically increased to a value num2 large enough to accommodate the configured *ROUTING section entries.

ACTION

The ASCII version of the configuration file should be updated to reflect the change either manually or using tmunloadcf.

SEE ALSO

tmloadcf (1), tmunloadcf (1), ubbconfig (5)

1772 WARN: MAXRFT increased from num1 to num2 to meet configured routing criteria

DESCRIPTION

The configured value num1 for the MAXRFT parameter in the *RESOURCES section of the ubbconfig(5) file was automatically increased to a value num2 large enough to accommodate the configured *ROUTING section entries.

ACTION

The ASCII version of the configuration file should be updated to reflect the change either manually or using tmunloadcf.

SEE ALSO

tmloadcf (1), tmunloadcf (1), ubbconfig (5)

1773 WARN: MAXRTDATA increased from num1 to num2 to meet configured routing criteria

DESCRIPTION

The configured value num1 for the MAXRTDATA parameter in the *RESOURCES section of the ubbconfig(5) file was automatically increased to a value num2 large enough to accommodate the configured *ROUTING section entries.

ACTION

The ASCII version of the configuration file should be updated to reflect the change either manually or using tmunloadcf.

SEE ALSO

tmloadcf (1), tmunloadcf (1), ubbconfig (5)

1775 ERROR: MAXDRT parameter must be >= 0 and < 32768

DESCRIPTION

The MAXDRT parameter in the *RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of 1 to 32767.

ACTION

Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).

SEE ALSO

"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)

1777 ERROR: MAXRFT parameter must be >= 0 and < 32768

DESCRIPTION

The MAXRFT parameter in the *RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of 1 to 32767.

ACTION

Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).

SEE ALSO

"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)

1779 ERROR: MAXRFT parameter must be >= 0 and < 32761

DESCRIPTION

The MAXRTDATA parameter in the *RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of 1 to 32760.

ACTION

Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).

SEE ALSO

"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)

1780 INFO: Server activated successfully

DESCRIPTION

A TMIB request to activate a server completed successfully.

ACTION

No action required.

SEE ALSO

TM_MIB(5)

1781 INFO: Server deactivated successfully

DESCRIPTION

A TMIB request to deactivate a server completed successfully.

ACTION

No action required.

SEE ALSO

TM_MIB(5)

1783 ERROR: Can't register machine machine - duplicate serial number

DESCRIPTION

The license for your copy of the TUXEDO System specifies that the software may be installed and executed on only one machine at a time. However, the serial number of the copy running on machine machine is identical to the serial number of the copy running on another machine named in the TUXCONFIG file.

ACTION

Contact the company from which you purchased the product to license additional copies of the TUXEDO System.

1784 ERROR: Can't register machine machine - will exceed TUXEDO System Binary Licensed User Count (number)

DESCRIPTION

Your license for the TUXEDO System specifies that the maximum number of users, application-wide, that can be supported is number. However, the number of users for machine machine, as indicated by the value of MAXACCESSERS in the TUXCONFIG file, will cause the maximum to be exceeded if that machine is booted.

ACTION

Reduce the values of MAXACCESSERS for the machines participating in your application, so that their sum does exceed the maximum number of licensed users. This number is reported by tmboot (1) at startup. If you wish to increase the maximum number of licensed users, contact the company from which you purchased the product.

1786 ERROR: Unlicensed TUXEDO System Binary

DESCRIPTION

See Message No. 1606 above.

ACTION

See Message No. 1606 above.

1787 ERROR: Expired TUXEDO System Binary

DESCRIPTION

See Message No. 1609 above.

ACTION

See Message No. 1609 above.

1788 WARN: Could not advertise administrative service

DESCRIPTION

The BRIDGE could not offer the administrative service necessary to support access to the T_BRIDGE class via the /AdminAPI. The BRIDGE will still start and handle application network communication.

ACTION

Check the system sizing parameters, specifically the TA_MAXSERVICES attribute of the T-DOMAIN class to make sure it is set sufficiently high to allow for system services. Also check the userlog for additional information. The system may need to be brought down and reconfigured to resolve this problem.

SEE ALSO

MIB (5), TM_MIB (5), ubbconfig (5)

1789 ERROR: String for PREFERENCES must be <= num characters in length

DESCRIPTION

The string value for the PREFERENCES parameter in the *RESOURCES section of the UBBCONFIG file is too large, that is, greater than num characters.

ACTION

Shorten the value for the parameter and rerun tmloadcf.

SEE ALSO

tmloadcf (1), ubbconfig (5)

1791 ERROR: SANITYSCAN parameter must be > 0 and < 32768

DESCRIPTION

The SANITYSCAN parameter is not within acceptable limits.

ACTION

Set SANITYSCAN to the proper value in the UBBCONFIG file.

1793 ERROR: DBBLWAIT parameter must be > 0 and < 32768

DESCRIPTION

The DBBLWAIT parameter is not within acceptable limits.

ACTION

Set DBBLWAIT to the proper value in the UBBCONFIG file.

1795 ERROR: BBLQUERY parameter must be > 0 and < 32768

DESCRIPTION

The BBLQUERY parameter is not within acceptable limits.

ACTION

Set BBLQUERY to the proper value in the UBBCONFIG file.

1797 ERROR: BLOCKTIME parameter must be > 0 and < 32768

DESCRIPTION

The BLOCKTIME parameter is not within acceptable limits.

ACTION

Set BLOCKTIME to the proper value in the UBBCONFIG file.

1799 ERROR: SCANUNIT parameter must be > 0 and <= 60

DESCRIPTION

The SCANUNIT parameter is not within acceptable limits.

ACTION

Set SCANUNIT to the proper value in the UBBCONFIG file.