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

CMDTUX Messages 4000-4099

4002	ERROR: Syntax Error in the -g argument.
	Description	Each group specified by the -g argument of tpacladd(1) or tpaclmod(1) must be greater than 0 characters and less than 31 characters.
	Action	Modify the -g argument so that the group identification falls within acceptable limits.
4003	ERROR: Syntax Error in the -g argument.
	Description	Each group specified by the -g argument of tpacladd(1) or tpaclmod(1) must be greater than 0 characters and less than 31 characters.
	Action	Modify the -g argument so that the group identification falls within acceptable limits.
4004	ERROR: Could not retrieve group information.
	Description	When tpacladd(1) or tpaclmod(1) was attempting to retrieve information about one of the groups specified by the -g argument, an error occurred.
	Action	Try the command again. If it fails consistently, contact your BEA Customer Support.
4005	ERROR: Group number does not exist.
	Description	tpacladd(1) or tpaclmod(1) encountered a group number given via the -g parameter which does not exist.
	Action	Add the desired group to the T_ACLGROUP class by using the tpgrpadd(1) command, and then re-run this command.
4006	ERROR: Group groupname does not exist.
	Description	tpacladd(1) or tpaclmod(1) encountered a group name given via the -g parameter which does not exist.
	Action	Add the desired group to the T_ACLGROUP class by using the tpgrpadd(1) command, and then re-run this command.
4008	ERROR: type field is not valid.
	Description	The type field given via the -t option to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. The only recognized types are SERVICE, ENQ, DEQ, or POSTEVENT.
	Action	Change the -t option of the command being run to SERVICE, ENQ, DEQ, or POSTEVENT.
4010	ERROR: name field is not valid.
	Description	The name given to tpacladd(1), tpaclmod(1), or tpacldel(1) was invalid. An ACL name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
	Action	Change the name given to the command in order to comply with the specifications.
4011	ERROR: FML32 error error.
	Description	When adding or deleting a field from an FML buffer, the given error occurred. This error occurs when running tpacladd(1), tpaclmod(1), or tpacldel(1).
	Action	Try running the command again. If it fails consistently, contact your BEA Customer Support.
4012	ERROR: Memory allocation error.
	Description	When using the command tpacladd(1), tpaclmod(1), or tpacldel(1), the system ran out of memory.
	Action	Check the memory on the system where the command was run. If it seems that there should be enough memory for this operation, contact your BEA Customer Support.
4014	ERROR: TUXCONFIG is not set.
	Description	tpacladd(1), tpaclmod(1), and tpacldel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
	Action	Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4018	ERROR: Unknown executable name.
	Description	The given executable name is not known. This error can happen if the tpgrpadd(1), tpgrpdel(1), or tpgrpmod(1) commands have been renamed.
	Action	Do not rename the tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) commands. Use the original names with which the BEA TUXEDO system binary was packaged.
4019	ERROR: MIB error number.
	Description	When running the tpacladd(1), tpaclmod(1), or tpacldel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
	Action	Consult the MIB(5) reference pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
4020	ERROR: grpname field is not valid.
	Description	The group name given to tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
	Action	Change the group name given to the command in order to comply with the specifications.
4021	ERROR: MIB error number.
	Description	When running the tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
	Action	Consult the MIB(5) reference pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
4022	ERROR: FML32 error error.
	Description	When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1).
	Action	Try running the command again. If it continues to fail, contact your BEA Customer Support.
4023	ERROR: Memory allocation error.
	Description	When using the commands tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1), the system ran out of memory.
	Action	Make sure 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.
4024	ERROR: MIB error number.
	Description	When running the tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
	Action	Consult the MIB(5) reference pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
4025	ERROR: TUXCONFIG is not set.
	Description	tpgrpadd(1), tpgrpmod(1), and tpgrpdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
	Action	Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4026	ERROR: new group name is not valid.
	Description	The new group name given to tpgrpmod(1) was invalid. A group name must not contain the characters '#', ',', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
	Action	Change the new group name given to the command in order to comply with the specifications.
4027	ERROR: Could not retrieve group information.
	Description	When tpgrpadd(1) or tpgrpmod(1) was attempting to retrieve information about groups specified on the command line, an error occurred.
	Action	Try the command again. If the command fails consistently, contact your BEA Customer Support.
4028	ERROR: groupname group already exists.
	Description	In the T_ACLGROUP class, no two groups can have the same name. tpgrpmod(1) attempted to add two groups with the same name.
	Action	Do not attempt to have two groups with the same name. Change the group name and re-run the command.
4029	ERROR: Group groupname does not exist.
	Description	tpgrpmod(1) attempted to modify a group that does not exist.
	Action	Use tpgrpadd(1) to add new groups to the T_ACLGROUP class. Use the BEA TUXEDO GUI to get a complete list of the currently defined groups.
4030	ERROR: FML32 error error.
	Description	When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running tpusradd(1), tpusrmod(1), or tpusrdel(1).
	Action	Try running the command again. If it fails again, contact your BEA Customer Support.
4031	ERROR: Memory allocation error.
	Description	When using the commands tpusradd(1), tpusrmod(1), or tpusrdel(1), the system ran out of memory.
	Action	Make sure 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.
4032	ERROR: Could not retrieve group information.
	Description	When tpusradd(1) or tpusrmod(1) was attempting to retrieve information about a group specified on the command line, an error occurred.
	Action	Try the command again. If it fails consistently, contact your BEA Customer Support.
4033	ERROR: Group number does not exist.
	Description	tpusradd(1) or tpusrmod(1) encountered a group number given via the -g parameter which does not exist.
	Action	Add the desired group to the T_ACLGROUP class by using the tpgrpadd(1) command, and then re-run this command.
4034	ERROR: Group groupname does not exist.
	Description	tpusradd(1) or tpusrmod(1) encountered a group name given via the -g parameter which does not exist.
	Action	Add the desired group to the T_ACLGROUP class by using the tpgrpadd(1) command, and then re-run this command.
4038	ERROR: Unknown executable name.
	Description	The given executable name is not known. This error can happen if the tpusradd(1), tpusrdel(1), or tpusrmod(1) commands have been renamed.
	Action	Do not rename the tpusradd(1), tpusrmod(1), or tpusrdel(1) commands. Use the original names with which the BEA TUXEDO binary was packaged.
4039	ERROR: TUXCONFIG is not set.
	Description	tpusradd(1), tpusrmod(1), and tpusrdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
	Action	Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4040	ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL.
	Description	In order to run tpacladd(1), tpaclmod(1), or tpacldel(1), the security level of the BEA TUXEDO application must be USER_AUTH, ACL, or MANDATORY_ACL.
	Action	Change the security level in the ubbconfig(5) file to USER_AUTH, ACL, or MANDATORY_ACL. Run tmloadcf(1) on the new ubbconfig(5) file. Then re-run the command that caused this failure.
4043	ERROR: username user already exists.
	Description	In the T_ACLPRINCIPAL class, no two users can have the same numeric identification. tpusrmod(1) attempted to add two users with the same identification.
	Action	Do not attempt to have two users with the same numeric identification. Change the user name and re-run the command.
4044	ERROR: User username does not exist.
	Description	tpusrmod(1) attempted to modify a user which does not exist.
	Action	Use tpusradd(1) to add new users to the T_ACLPRINCIPAL class. Use the BEA TUXEDO GUI to get a complete list of the currently defined users.
4045	ERROR: usrname field is not valid.
	Description	The user name given to tpusradd(1), tpusrmod(1), or tpusrdel(1) was invalid. A user name must not contain the characters '#', ':' or newline. Furthermore, the name must be less than or equal to 30 characters in length.
	Action	Change the name given to the command in order to comply with the specifications.
4046	ERROR: Invalid group specified.
	Description	The group name given to tpusradd(1) or tpusrmod(1) was invalid. Either the group did not exist or there was a syntax error in the group name.
	Action	Use tpgrpadd(1) to add new groups. Change the group name given to the command to correspond to an existing group. Change the group name to conform to the specifications for group names.
4047	ERROR: User numbers must be between 1 and max
	Description	User numbers in the T_ACLPRINCIPAL class must be between 1 and 131071. A user number presented to tpusradd(1) or tpusrmod(1) was not within that range.
	Action	Change the user number to be within the allowable range and re-run the command.
4048	ERROR: MIB error number.
	Description	When running the tpusradd(1), tpusrmod(1), or tpusrdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
	Action	Consult the MIB(5) reference pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
4049	ERROR: A group with id number already exists.
	Description	In the T_ACLGROUP class, no two groups can have the same numeric identification. tpgrpadd(1) or tpgrpmod(1) attempted to add two groups with the same identification.
	Action	Do not attempt to have two groups with the same numeric identification. Change the identification number and re-run the command.
4050	ERROR: A user with id number already exists.
	Description	In the T_ACLPRINCIPAL class, no two users can have the same numeric identification. tpusradd(1) or tpusrmod(1) attempted to add two users with the same identification.
	Action	Do not attempt to have two users with the same numeric identification. Change the identification number and re-run the command.
4053	ERROR: User username not added.
	Description	Due to an error processing the user password, this user has not been added to the system. This can happen when using tpusradd(1) or tpusrmod(1).
	Action	Re-run the command that caused the error. If this error occurs consistently, call BEA Customer Support.
4054	ERROR: Passwords do not match.
	Description	The user passwords entered to tpusradd(1) or tpusrmod(1) do not match.
	Action	Re-run the command and make sure that you enter the passwords correctly each time you are prompted.
4055	ERROR: Unable to get host user id.
	Description	tpusradd(1), tpusrmod(1), or tpusrdel(1) was unable to retrieve the user identification from the host system.
	Action	Make sure that the user id of the BEA TUXEDO administrator is known to the system. If the user id is known to the system, contact your BEA Customer Support.
4056	ERROR: Unable to get host user id.
	Description	tpacladd(1), tpaclmod(1), or tpacldel(1) was unable to retrieve the user identification from the host system.
	Action	Make sure that the user id of the BEA TUXEDO administrator is known to the system. If the user id is known to the system, contact your BEA Customer Support.
4057	ERROR: Unable to get host user id.
	Description	tpgrpadd(1), tpgrpmod(1), or tpgrpdel(1) was unable to retrieve the user identification from the host system.
	Action	Make sure that the user id of the BEA TUXEDO administrator is known to the system. If the user id is known to the system, contact your BEA Customer Support.
4058	INFO: .SysMachineState: val state change to ACTIVE
	Description	This message states that the specified machine changed to ACTIVE. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4059	ERROR: SRVID parameter must be >= 1 and <= 30000
	Description	The SRVID parameter in the JDBCCONNPOOLS section of the configuration file must be within the proper range of values.
	Action	Specify a value that is between 1 and 30,000, inclusive.
	See Also	tmloadcf(1), ubbconfig(5)
4060	ERROR: Unknown executable name.
	Description	The given executable name is not known. This error can happen if the tpacladd(1), tpacldel(1), or tpaclmod(1) commands have been renamed.
	Action	Do not rename the tpacladd(1), tpaclmod(1), or tpacldel(1) commands. Use the original names with which the BEA TUXEDO system binary was packaged.
4062	ERROR: MIB error number.
	Description	When running the tpusradd(1), tpusrmod(1), or tpusrdel(1) command, an error occurred in the MIB(5). The returned error number was retrieved from the TA_ERROR field of the returned FML32 buffer.
	Action	Consult the MIB(5) reference pages to determine exactly which error was returned. Further action may be suggested by the nature of the error returned by the MIB.
4063	INFO: .SysNetworkState: LMID1->LMID2 state change to INACTIVE
	Description	This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to an INACTIVE state. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4064	INFO: .SysMachineState: LMID state change to PARTITIONED
	Description	This message states that the specified machine changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4065	INFO: .SysNetworkState: LMID1->LMID2 state change to ACTIVE
	Description	This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4066	INFO: .SysNetworkState: LMID1->LMID2 state change to SUSPENDED
	Description	This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to a SUSPENDED state. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4068	INFO: .SysServerState: servername, group srvgrp, id srvid state change to state
	Description	This message indicates that the server specified above changed to a new state. A complete listing of the server attributes are sent in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4069	INFO: .SysClientState: User usrname on LMID state change to state
	Description	This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4070	ERROR: Application must be configured.
	Description	tpacladd(1), tpaclmod(1), and tpacldel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
	Action	Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4071	ERROR: Application must be configured.
	Description	tpgrpadd(1), tpgrpmod(1), and tpgrpdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
	Action	Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4072	ERROR: Application must be configured.
	Description	tpusradd(1), tpusrmod(1), and tpusrdel(1) must be run on configured systems. Furthermore, the TUXCONFIG variable must point to the BEA TUXEDO configuration file.
	Action	Configure the application (see ubbconfig(5) and tmloadcf(1)). Set your TUXCONFIG variable appropriately. Run tmloadcf(1). Then re-run the command that caused this error.
4073	INFO: .SysNetworkConfig: LMID1->LMID2 configuration change
	Description	This message indicates that the network link between the two machines specified changed to a new state. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4075	INFO: .SysMachineState: LMID state change to INACTIVE
	Description	This message states that the specified machine changed to an INACTIVE state. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
4076	ERROR: .SysEventDelivery: System Event Monitor delivery failure on LMID
	Description	This message indicates that the event server failed to perform at least one notification for a posted event.
	Action	Check to make sure that the notifications specified in the subscriptions that match the posted events can be done.
	See Also	EVENT_MIB(5), TM_MIB(5)
4077	ERROR: .SysEventFailure: System Event Monitor subsystem failure on LMID
	Description	The system event server periodically sends a message to itself to detect blocking conditions on the message queues. This event is generated if the server can't put a message on the queue in no-block node. It can also be generated if the received message doesn't match what was sent out earlier. The second case will probably never happen.
	Action	Configure larger message queues or distribute the load in the application equally among all the machines.
	See Also	EVENT_MIB(5), TM_MIB(5)
4078	ERROR: Memory allocation failure
	Description	Memory allocation failed in the event server.
	Action	Make sure 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.
4080	ERROR: Message received did not match sent message
	Description	The event server periodically tests the message queue subsystem for blocking conditions by sending a message to itself in NOWAIT mode and receiving the message right after. This message indicates that the received message didn't match the sent message.
	Action	Contact your BEA Customer Support.
	See Also	TMSYSEVT(5), TMUSREVT(5)
4081	ERROR: FML32 error error.
	Description	When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running tpaclcvt(1).
	Action	Try running the command again. If it fails consistently, contact your BEA Customer Support.
4082	ERROR: Memory allocation error.
	Description	When using the command tpaclcvt(1), the system ran out of memory.
	Action	Make sure 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.
4083	INFO: Line number not added because it is a comment.
	Description	The given line number in the user file was ignored by tpaclcvt(1). The line was not formatted correctly, and hence was ignored.
	Action	Be sure that the file which is being converting has the correct format.
4084	INFO: User ID field field is not numeric. Line number not added.
	Description	If tpaclcvt(1) encounters a user identification number which is not numeric, then it does not attempt to add the user. This can occur when converting the user file.
	Action	Be sure that the file which is being converted has the correct format.
4085	INFO: User ID number is invalid. Line number not added.
	Description	User identification numbers are only valid within the range 1 to 131,071. If tpaclcvt(1) encounters a user identification number which is not in the given range, then it does not attempt to add the user.
	Action	Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
4086	INFO: Group ID field number is not numeric. Line number not added.
	Description	If tpaclcvt(1) encounters a group identification number which is not numeric, then it does not attempt to add the user. This can occur when converting the user file.
	Action	Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
4087	INFO: Line number not added. # is an illegal character.
	Description	The given line in the user file was not converted by tpaclcvt(1). This is because a # character was encountered in the username, which is illegal.
	Action	Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
4088	INFO: Line number not added. error_string.
	Description	tpaclcvt(1) encountered an error when attempting to get information concerning the user on the given line.
	Action	Examine the error code returned. This error can be used to determine the actual BEA TUXEDO system error that occurred.
4089	INFO: Line number user name not added. Error retrieving number of occurrences.
	Description	When tpaclcvt(1) is converting a user file, it attempts to look for duplicate users. If an error occurs while extracting the number of users, this message occurs.
	Action	Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
4090	INFO: Line number user username not added. User username already exists.
	Description	When tpaclcvt(1) is converting a user file, it attempts to look for duplicate users. If an error occurs while extracting the number of users, this message occurs.
	Action	You can add any user which tpaclcvt(1) did not add with tpusradd(1).
4091	INFO: Line number not added. error_string.
	Description	tpaclcvt(1) encountered an error when attempting to get information concerning user identifiers.
	Action	Examine the error code returned. This error can be used to determine the actual BEA TUXEDO system error that occurred.
4092	INFO: Line number user name not added. Error retrieving number of occurrences.
	Description	When tpaclcvt(1) is converting a user file, it attempts to look for duplicate users identification numbers. If an error occurs while extracting the number of user identifiers, this message occurs.
	Action	Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
4093	INFO: Line number user usernumber not added. User usernumber already exists.
	Description	tpaclcvt(1) did not add the given user because that user identification number already exists.
	Action	Any users which tpaclcvt(1) could not add can be added with tpusradd(1).
4094	INFO: Line number user username not added. Error writing file.
	Description	tpaclcvt(1) was attempting to modify the user file to add the given user.
	Action	Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, contact BEA Customer Support.
4095	INFO: Line number not added because it is a comment.
	Description	The given line number in the group file was ignored by tpaclcvt(1). The line was not formatted correctly, and hence was ignored.
	Action	Be sure that the file which is being converted has the correct format.
4096	INFO: Group ID field string is not numeric. Line number not added.
	Description	If tpaclcvt(1) encounters a group identification number that is not numeric, then it does not attempt to add the user. This can occur when converting the group file.
	Action	Any groups which tpaclcvt(1) could not add can be added with tpgrpadd(1).
4097	INFO: Line number not added. error_string.
	Description	tpaclcvt(1) encountered an error when attempting to add a group. The error_string can help to determine exactly what error occurred.
	Action	Examine the error code returned. This error can be used to determine the actual BEA TUXEDO system error that occurred.
4098	INFO: Line number Group groupname not added. Error retrieving error.
	Description	tpaclcvt(1) encountered an error when adding a group to the T_ACLGROUP class. When attempting to retrieve the error from the returned FML32 buffer, an error occurred.
	Action	If this error occurs consistently, contact BEA Customer Support.
4099	INFO: Line number Group groupname:error_string
	Description	tpaclcvt(1) received the given error_string from the MIB when adding the group on the given line.
	Action	Use the error_string returned from the MIB to determine exactly what error occurred.