---

18. 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 BEA TUXEDO system 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 BEA TUXEDO system 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 BEA 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(3c)
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	BEA 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	BEA 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 the administrator, but is generated only during activation of a remote machine. Contact your BEA 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, ortpmodusr 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 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 BEA 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 BEA 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(3c) 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 BEA TUXEDO system Technical Support for assistance if unsure of how to resolve the situation.
	See Also	BEA 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	BEA 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	BEA 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	BEA 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 BEA 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 BEA TUXEDO system.
1784	ERROR: Can't register machine machine - will exceed TUXEDO System Binary Licensed User Count (number)
	Description	Your license for the BEA 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	The files in your BEA TUXEDO system installation do not contain the expected software license information, such as the maximum number of licensed users. The installation program prompted the installer for this information at installation time.
	Action	Reinstall the BEA TUXEDO system software, using the license token and serial number supplied with the distribution media. Make sure not to terminate the installation program prematurely, because the license information is processed at the end.
1787	ERROR: Expired TUXEDO System Binary
	Description	Your copy of the BEA TUXEDO system software is an evaluation copy, and the expiration date has passed.
	Action	If you wish to continue using the BEA TUXEDO system, contact the company from which you received the product.
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.

---

---