[Top] [Prev] [Next] [Bottom]

1. LIBTMIB Messages 1-99

1	INFO: Abortively terminating client process pid
	Description	An /AdminAPI request to change the state of a client to `DEAD` has caused the system to attempt termination of the process pid with the `SIGKILL` signal.
Action	Informational message only, no action required.
See Also	`MIB`(5), `TM_MIB`(5)
2	ERROR: Server group name does not match existing group
	Description	The server group name, `TA_SRVGRP`, specified on a `SET` request for the `T_SERVER` class, is not a recognized server group.
Action	Correct the server group name and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
3	ERROR: Invalid class name (class) presented to /Admin service svc
	Description	The class name class is not recognized by the administrative service svc.
Action	Correct the service name and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
4	ERROR: SYSTEM_ACCESS mismatch with NO_OVERRIDE set in T_DOMAIN class
	Description	A `SET` operation on a `T_SERVER` class object with the `TA_SYSTEM_ACCESS` attribute being updated specified a value different than that set in the `T_DOMAIN` class object and the `NO_OVERRIDE` modifier is also set in the `T_DOMAIN` class object.
Action	Remove the change to the `TA_SYSTEM_ACCESS` value from the `SET` request or remove the `NO_OVERRIDE` modifier from the `T_DOMAIN` class object.
See Also	`MIB`(5), `TM_MIB`(5)
5	*ERROR: TA_MAX(max) not set >= TA_MIN(min)*
	Description	The maximum number of server instances max specified on a `T_SERVER` class `SET` request was less than the specified minimum number of instance min.
Action	Lower min or raise max to be in accordance with the restriction and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
6	ERROR: SET operation violates restrictions on servers with same TA_RQADDR
	Description	The request queue address name for a `T_SERVER` class object is being `SET` to a value matching an existing server that is either a different server name or a different server group.
Action	Either set the request queue address name to something different than the matching servers name or change the server name and/or server group to match the desired existing servers attribute values and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
7	ERROR: Overlapping range for TA_SRVGRP, TA_SRVID and TA_MAX
	Description	A `SET` operation on a `T_SERVER` class object violated the restriction that within a particular server group, servers may not have overlapping server identifiers. This restriction takes into account the base server identifier as well as the setting for the maximum number of server instances.
Action	Lower the maximum number of server instances to eliminate the overlap or shift the base server identifier to avoid the overlap and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
8	ERROR: SET of TA_STATE to `NEW` matches existing class instance
	Description	An attempt was made to create a new object via the /AdminAPI, but the object keys specified in the request match an existing class object.
Action	Correct the keys used and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
9	*ERROR: Global /Admin update failed processing on LMID(lmid) with error code(num) and status(status)*
	Description	A `SET` operation that required global updates in a distribute application failed on one of the logical machines lmid with the /AdminAPI error code num and a status of status.
Action	The system will automatically refresh the remote site bulletin board and/or configuration file as necessary after detecting the failure. The status message should be examined for possible causes of the remote failure. This status message will contain a catalog name and message number that can be referenced in this manual for further information.
See Also	`MIB`(5), `TM_MIB`(5)
10	WARN: Could not find registry table entry for server svrgrp/svrid
	Description	A `SET` operation for the indicated server (svrgrp/svrid) attempted to update local attributes but could not locate the registry table entry on the servers logical machine.
Action	This message is indicative of other problems that may cause the registry table problem. The userlog on the servers logical machine should be examined for clues as to any problems that may have occurred leading up to this message. If the cause of the problem is still not clear, then contact your BEA TUXEDO system Technical Support.
See Also	`MIB`(5), `TM_MIB`(5)
11	ERROR: Cannot update T_SERVICE class with active T_SVCGRP instance
	Description	An /AdminAPI request to `SET` attribute values for a `T_SERVICE` class object could not be satisfied because a corresponding `T_SVCGRP` class object (matching `TA_SERVICENAME` values) is currently `ACTIVE`.
Action	Defer the update of the `T_SERVICE` class object until all of the corresponding `T_SVCGRP` objects are deactivated.
See Also	`MIB`(5), `TM_MIB`(5)
12	WARN: AUTOTRAN specified for SERVICE with TRANTIME=0
	Description	An /AdminAPI `SET` request resulted in an `TA_AUTOTRAN` attribute value for the service svc of `Y` and a `TA_TRANTIME` attribute value for the service svc of 0. This indicates an infinite timeout for transactions started in the server by virtue of the autotran characteristic and may result in "hung" servers if application failures result in transactions that do not complete. This setting should be made only with great care and the understanding of the administrator as to its possible side effects.
Action	Examine the object to be sure that the settings are what is intended and correct them if necessary.
See Also	`MIB`(5), `TM_MIB`(5)
13	ERROR: SET operation did not specify unique class instance
	Description	The indicated /AdminAPI `SET` request did not match a unique class object. The key fields provided match more than one object and are ambiguous as to which should be affected.
Action	Provide sufficient key fields to restrict the request to exactly one object and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
14	ERROR: Invalid class name (class) presented to /Admin service svc
	Description	The class name class is not recognized by the administrative service svc
Action	Correct the service name and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
15	*WARN: ROUTING criteria* (for SERVICE svc) is not defined in the ROUTING section**
	Description	The `TA_ROUTINGNAME` value criteria being set for a `T_SERVICE` class object with service name svc is not currently configured as a `T_ROUTING` class object.
Action	This situation will cause an error for types which have system support for routing such as FML and VIEWS. However, application types or types for which the application supplies their own customized routing function may function fine. These functions are passed the routing criteria name and process in their own way. The action to be taken depends on whether the application is relying on system support for routing. If they are, then a `T_ROUTING` object with a matching criteria name should be defined. Otherwise, no action is necessary.
See Also	`MIB`(5), `TM_MIB`(5)
16	ERROR: SET keys do not match existing class instance
	Description	An /AdminAPI request to `SET` attributes did not match an existing class instance. All requests other than a state change to `NEW` must match exactly one existing class object to be processed.
Action	Correct the request to address an existing class object and regenerate.
See Also	`MIB`(5), `TM_MIB`(5)
17	ERROR: TA_SVCRNAM may be set only when Activating service
	Description	A `SET` operation on a `T_SVCGRP` class object attempted to set the value for the `TA_SVCRNAM` attribute value without including a state change to the `ACTIVE` state. This is an invalid combination of attribute changes for this class.
Action	Include the setting of `TA_SVCRNAM` in an activation request for the object in question and remove it from other types of updates to this class.
See Also	`MIB`(5), `TM_MIB`(5)
18	WARN: AUTOTRAN specified for SERVICE svc with TRANTIME=0
	Description	An /AdminAPI `SET` request resulted in an `TA_AUTOTRAN` attribute value for the service svc of `Y` and a `TA_TRANTIME` attribute value for the service svc of 0. This indicates an infinite timeout for transactions started in the server by virtue of the autotran characteristic and may result in "hung" servers if application failures result in transactions that do not complete. This setting should be made only with great care and the understanding of the administrator as to its possible side effects.
Action	Examine the object to be sure that the settings are what is intended and correct them if necessary.
See Also	`MIB`(5), `TM_MIB`(5)
19	ERROR: TA_AUTHSVC specified without security turned on
	Description	A `SET` operation on the `T_DOMAIN` class object specified a value for the `TA_AUTHSVC` attribute without having security turned on via the `TA_SECURITY` attribute. This is an invalid combination of attribute values.
Action	Either turn on security before or with the request to set the `TA_AUTHSVC` attribute or remove the value for `TA_AUTHSVC` from the request.
See Also	`MIB`(5), `TM_MIB`(5)
20	ERROR: LAN or MIGRATE option specified without MP TA_MODEL value
	Description	A `SET` operation on the `T_DOMAIN` class object set either the LAN or `MIGRATE` option without setting the `TA_MODEL` attribute value to MP. This is an invalid combination of attribute values.
Action	Either set the `TA_MODEL` value to MP before or with the request to set the options as specified or eliminate the use of the offending options.
See Also	`MIB`(5), `TM_MIB`(5)
21	ERROR: Backup TA_MASTER allowed only for MP TA_MODEL
	Description	A backup master logical machine was specified in the `TA_MASTER` attribute value on a `SET` request for the `T_DOMAIN` class object without having the `TA_MODEL` set to `MP`. This is an invalid combination of attribute values.
Action	Either set the `TA_MODEL` value to `MP` before or with the change to the `TA_MASTER` attribute value or eliminate the setting of the backup master logical machine.
See Also	`MIB`(5), `TM_MIB`(5)
22	ERROR: Invalid master machine specified in TA_MASTER
	Description	The master logical machine identifier in the `TA_MASTER` attribute value for a `SET` operation on the `T_DOMAIN` class object is invalid. It either represents a logical machine other than the actual master machine or it represents an unconfigured logical machine identifier.
Action	Correct the logical machine identifiers used in the request.
See Also	`MIB`(5), `TM_MIB`(5)
23	ERROR: Invalid backup machine specified in TA_MASTER
	Description	The logical machine identifier specified in the `TA_MASTER` attribute value on a `SET` operation for the `T_DOMAIN` class object does not match any configured logical machines.
Action	Correct the logical machine identifier used for the backup machine.
See Also	`MIB`(5), `TM_MIB`(5)
24	ERROR: TA_SYSTEM_ACCESS value set with NO_OVERRIDE contradicts T_SERVER settings
	Description	An attempt was made to set the `NO_OVERRIDE` modifier on the `TA_SYSTEM_ACCESS` attribute value for the `T_DOMAIN` class object with a primary `TA_SYSTEM_ACCESS` attribute value that does not match all of the currently configured `T_SERVER` class objects.
Action	Either remove the `NO_OVERRIDE` modifier so that the primary attribute value may be set or reset the `TA_SYSTEM_ACCESS` values for all configured `T_SERVER` class objects prior to setting the `T_DOMAIN` `TA_SYSTEM_ACCESS` value with the `NO_OVERRIDE` modifier.
See Also	`MIB`(5), `TM_MIB`(5)
25	*ERROR: AUTOTRAN specified for SERVICE svc* SRVGRP group with no TMS**
	Description	A `SET` operation on a `T_SVCGRP` class object attempted to set the `TA_AUTOTRAN` attribute value to Y for service svc in server group group where the indicated server group does not have a TMS associated with it and can therefore not support transactions.
Action	Change the `TA_AUTOTRAN` attribute value to N or eliminate the setting of this attribute from the request.
See Also	`MIB`(5), `TM_MIB`(5)
26	*ERROR: TA_LMID value lmid* already exists**
	Description	An attempt to `SET` a new `T_MACHINE` class object was made with a logical machine identifier lmid that matches an existing class object.
Action	Change the logical machine identifier and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
27	*ERROR: TA_LMID value lmid* conflicts with existing T_GROUP class instance**
	Description	An attempt to `SET` a new `T_MACHINE` class object was made with a logical machine identifier lmid that matches an existing `T_GROUP` class object group name (`TA_SRVGRP`). This is an invalid combination.
Action	Change the logical machine identifier and regenerate the request or invalidate the server group and reuse the current logical machine identifier.
See Also	`MIB`(5), `TM_MIB`(5)
28	ERROR: TA_PMID value pmid already exists
	Description	An attempt to `SET` a new `T_MACHINE` class object was made with a physical machine identifier pmid that matches an existing class object.
Action	Change the physical machine identifier and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
29	ERROR: Cannot create new T_MACHINE class instances in SHM mode
	Description	A `SET` operation creating a `NEW` `T_MACHINE` class object was made in a `SHM` mode application as identified in the `T_DOMAIN` `TA_MODEL` attribute value. Only one machine is allowed in `SHM` mode and the creation of `NEW` machines is therefore disallowed.
Action	If an additional machine needs to be added to the application, then you must shut down the application, change the model to `MP`, set the `LAN TA_OPTIONS` value in the `T_DOMAIN` class object and only then can you add the additional machine.
See Also	`MIB`(5), `TM_MIB`(5)
30	ERROR: Cannot create new T_MACHINE class instances, full machine table
	Description	A `SET` operation to create a `NEW` `T_MACHINE` class object could not be satisfied because the machine tables have been filled. These tables are sized based on the `T_DOMAIN` `TA_MAXMACHINES` attribute value.
Action	Shut down the application, reconfigure the `T_DOMAIN` `TA_MAXMACHINES` attribute value and then the new machine may be added to the application.
See Also	`MIB`(5), `TM_MIB`(5)
31	ERROR: Insufficient networking information, TA_NADDR or TA_NLSADDR missing
	Description	A `SET` operation either creating a `NEW` `T_MACHINE` class object or adding networking information to an existing object did not supply sufficient networking information. The presence of either the `TA_BRIDGE` or `TA_NADDR` attribute on a `T_MACHINE` class object indicates that the machine is network enabled. A network enabled machine must have non-0 length string values specified for both `TA_NADDR` and `TA_NLSADDR`.
Action	Supply either or both of the missing `TA_NADDR` and `TA_NLSADDR` values.
See Also	`MIB`(5), `TM_MIB`(5)
32	ERROR: Networking information may not be specified without LAN option set
	Description	A `SET` operation creating a `NEW` `T_MACHINE` class object or modifying an existing object attempted to add one or more of the networking attributes in an application where the `T_DOMAIN` `TA_OPTIONS` value `LAN` is not set.
Action	Add the `LAN` option to the `T_DOMAIN` `TA_OPTIONS` value before adding the networking information for the machine.
See Also	`MIB`(5), `TM_MIB`(5)
33	ERROR: One of both of the LMIDs in TA_LMID do not match configured machines
	Description	A `SET` operation for a `T_GROUP` class object specified a `TA_LMID` value where either the primary or secondary logical machine identifier did not match a configured machine.
Action	Check both logical machine identifiers and change the invalid identifier to one for a configured machine.
See Also	`MIB`(5), `TM_MIB`(5)
34	ERROR: LMIDs not distinct in TA_LMID for T_GROUP
	Description	A `SET` operation for a `T_GROUP` class object specified identical logical machines for both the primary and secondary logical machine values in the `TA_LMID` attribute.
Action	Either change one of the logical machine identifiers to a different machine or set the server group to have only a primary machine.
See Also	`MIB`(5), `TM_MIB`(5)
35	ERROR: TA_SRVGRP matches defined logical machine name
	Description	A `SET` operation creating a `NEW` `T_GROUP` class object specified a `TA_SRVGRP` attribute value that conflicts with a configured `T_MACHINE` `TA_LMID` value. This is an invalid combination of attribute values.
Action	Change the `TA_SRVGRP` value for the group being created to a value distinct from configured logical machine identifiers.
See Also	`MIB`(5), `TM_MIB`(5)
36	ERROR: TA_SRVGRP or TA_GRPNO not unique
	Description	A `SET` operation creating a `NEW` `T_GROUP` class object specified a value for either the `TA_SRVGRP` or `TA_GRPNO` attribute that is not unique within the class.
Action	Change the server group name and/or the server group number to eliminate the conflict.
37	ERROR: T_GROUP class instance cannot be added, table full
	Description	A `SET` operation to create a `NEW` `T_GROUP` class object could not be satisfied because the group tables have been filled. These tables are sized based on the `T_DOMAIN` `TA_MAXGROUPS` attribute value.
Action	Shut down the application, reconfigure the `T_DOMAIN` `TA_MAXGROUPS` attribute value and then the new server group may be added to the application.
See Also	`MIB`(5), `TM_MIB`(5)
38	*WARN: TA_OPENINFO/TA_CLOSEINFO ignored for group(group) with no TMS*
	Description	A `SET` operation on a `T_GROUP` class object specified non-0 length values for either or both of `TA_OPENINFO` and `TA_CLOSEINFO` for a server group with no associated `TA_TMSNAME` value. The values specified for `TA_OPENINFO` and `TA_CLOSEINFO` are ignored in this case when configuring the group.
Action	If the server group is intended to be associated with a resource manager, then the groups attributes should be modified to include the appropriate `TA_TMSNAME` value and the values for `TA_OPENINFO` and `TA_CLOSEINFO` may be configured at that time.
See Also	`MIB`(5), `TM_MIB`(5)
39	ERROR: Machine associated with server group does not have a TLOG device
	Description	A `SET` operation for a `T_GROUP` class object specified either a primary or secondary logical machine for the group without an associated `TA_TLOGDEVICE` even though the group is being configured with a non-NULL `TA_TMSNAME` value. A non-NULL value is one which is non-0 length and is not "TMS".
Action	Either associate `TA_TLOGDEVICE` values with the selected machines or change the group so that `TA_TMSNAME` is a non-NULL.
See Also	`MIB`(5), `TM_MIB`(5)
40	ERROR: Multiple LMIDs disallowed, MIGRATE option not set
	Description	A `SET` operation on a `T_GROUP` class object specified both primary and secondary logical machine identifiers and the `T_DOMAIN` `MIGRATE` `TA_OPTIONS` value is not set. This is an invalid combination of attribute values.
Action	Add the `MIGRATE` option to the `T_DOMAIN` `TA_OPTIONS` attribute value and reconfigure the group with the primary and secondary logical machine identifiers.
41	ERROR: TA_GSTATE without TA_GRPNO on T_TRANSACTION group state change
	Description	A `SET` operation on a `T_TRANSACTION` class object specified a `TA_GSTATE` attribute value change without a corresponding `TA_GRPNO` value.
Action	Correct the request to include the appropriate `TA_GRPNO` value.
See Also	`MIB`(5), `TM_MIB`(5)
42	ERROR: TA_GSTATE and TA_STATE specified on T_TRANSACTION group state change
	Description	A `SET` operation on a `T_TRANSACTION` class object specified changes to both the `TA_STATE` and `TA_GSTATE` attribute values. Only one of these attribute values may be changed on any one request.
Action	Remove one of the attribute updates from the request buffer and regenerate.
See Also	`MIB`(5), `TM_MIB`(5)
43	ERROR: Permissions violation on SET request
	Description	A `SET` request contained an update to an attribute value that is not allowed for the initiating user in the current object state. The particular attribute violating the permissions is indicated in the field `TA_BADFLD`.
Action	Remove the update to the offending attribute from the request.
44	ERROR: Invalid GTRID for T_TRANSACTION state change
	Description	A `SET` operation on a `T_TRANSACTION` class object specified a `TA_GTRID` value that does not match any outstanding transactions.
Action	Check to be sure that the correct `TA_GTRID` value was used and correct if necessary. This situation may occur if the transaction is resolved before the request for the state change is generated in which case no action is necessary.
See Also	`MIB`(5), `TM_MIB`(5)
45	ERROR: TA_GRPNO not found for T_TRANSACTION class instance
	Description	A `SET` operation on a `T_TRANSACTION` class object specifying a `TA_GSTATE` change has specified a corresponding `TA_GRPNO` value that is not currently part of the indicated transaction.
Action	Correct the `TA_GRPNO` value and regenerate the request.
See Also	`MIB`(5), `TM_MIB`(5)
46	ERROR: Cannot destroy device entry specified
	Description	A `SET` operation to invalidate a `T_DEVICE` class object could not be processed because of an internal failure to delete the device.
Action	Contact your BEA TUXEDO system Technical Support.
See Also	`MIB`(5), `TM_MIB`(5)
47	ERROR: TA_TLOGCOUNT required to write new log records
	Description	A `SET` operation to add transaction log records failed to specify a value for `TA_TLOGCOUNT`. This attribute is used to determine how many records from the corresponding request should be added to the log.
Action	Add the appropriate value for `TA_TLOGCOUNT` to the request.
See Also	`MIB`(5), `TM_MIB`(5)
48	ERROR: TA_CFGDEVICE required on T_DEVICE GET operation
	Description	A `GET` operation on the `T_DEVICE` class failed to provide a value for the attribute key field `TA_CFGDEVICE` as required.
Action	Provide a value for `TA_CFGDEVICE` that points to a configured BEA TUXEDO system device file name.
See Also	`MIB`(5), `TM_MIB`(5)
49	ERROR: Invalid input to T_DEVICE SET request
	Description	A `SET` operation on a `T_DEVICE` class object did not specify the required change in `TA_STATE` value to either `NEW` or `INV`.
Action	Correct the request to include the appropriate state change.
See Also	`MIB`(5), `TM_MIB`(5)
50	ERROR: Could not create device entry specified
	Description	A `SET` operation to create a `T_DEVICE` class object could not be processed because of an internal failure. Possible causes are a non-zero offset (`TA_DEVOFFSET`) was specified for the first device list entry (`TA_DEVICE`) in the BEA TUXEDO system device file (`TA_CFGDEVICE`); control information in the BEA TUXEDO system device file is corrupted; the specified offset and size overlap with the storage already allocated to another device list entry (`TA_DEVICE`); the maximum number of devices allowed in a BEA TUXEDO system device file (`TA_CFGDEVICE`) was exceeded; the BEA TUXEDO system device file could not be locked; an operating system error occurred.
Action	Correct the request.
See Also	`MIB`(5), `TM_MIB`(5)
51	ERROR: Cannot destroy device entry 0 while other entries are in UDL
	Description	A `SET` operation to delete a `T_DEVICE` class object attempted to delete device index 0 without it being the last configured device for this BEA TUXEDO system file system.
Action	Delete the non-0 index devices from the file system before deleting device index 0.
52	ERROR: Invalid TA_OPTIONS modification in active system
	Description	A `SET` operation on the `T_DOMAIN` class object in an active application changed the existing settings for the `TA_OPTIONS` value with respect to the `LAN` and/or `MIGRATE` options. These options may only be changed in an inactive system.
Action	Shut down the application before attempting to change these options values.
See Also	`MIB`(5), `TM_MIB`(5)
53	ERROR: ACCSTATS may not be set in MP model application
	Description	A `SET` operation on the `T_DOMAIN` class object attempted to set the `TA_OPTIONS` attribute value `ACCSTATS`. This attribute value may only be set in `SHM` mode application.
Action	Convert the application to `SHM` mode before setting this option value.
See Also	`MIB`(5), `TM_MIB`(5)
54	ERROR: Missing or invalid LMID for SET operation
	Description	A `SET` operation modifying information local to only one site did not have the necessary information to route the request to the appropriate logical machine for processing.
Action	Add the correct `TA_LMID` attribute or other site identifying attribute to the originating request so that the request can be routed correctly.
See Also	`MIB`(5), `TM_MIB`(5)
55	ERROR: TA_MASTER migration combined with other T_DOMAIN changes
	Description	A `SET` operation on the `T_DOMAIN` class specified both a master machine migration and other attribute changes. These activities may not be combined in a single request.
Action	Split the request into a master machine migration and the other changes being requested and make 2 requests instead of the one original request.
See Also	`MIB`(5), `TM_MIB`(5)
56	ERROR: Could not perform TA_MASTER migration
	Description	A `SET` operation requested master machine migration. This operation could not be satisfied due to an internal system error.
Action	ACTION Contact your BEA TUXEDO system Technical Support.
See Also	`MIB`(5), `TM_MIB`(5)
57	*ERROR: Backup machine minor release (b_minor) differs from current master (m_minor)*
	Description	A `SET` operation on the `T_DOMAIN` class object resetting the backup logical machine identifier in the `TA_MASTER` attribute specified a logical machine with a minor release number b_minor that is different from the master machine minor release number m_minor. The backup and master logical machines must be the same major and minor BEA TUXEDO system release numbers.
Action	Either upgrade the new backup logical machine to the same minor release or select a different logical machine as your backup machine.
See Also	`MIB`(5), `TM_MIB`(5)
58	ERROR: T_SVCGRP state change INA to ACT without corresponding active server
	Description	A `SET` operation on a `T_SVCGRP` class object to set the state from `IN`ACTIVE to `ACTIVE` did not specify sufficient additional key fields to map the request to a active server or queue within the application.
Action	Provide either the `TA_RQADDR` or the `TA_SRVGRP` and `TA_SRVID` attribute values to map the request to an active server for processing.
See Also	`MIB`(5), `TM_MIB`(5)
59	ERROR: Alternate LMID not specified for group
	Description	A `SET` operation changing the state of a `T_GROUP` class object from `ACTIVE` to `MIGRATING` was applied to a server group without a configured backup logical machine configured.
Action	Configure a backup logical machine for the server group before requesting migration.
See Also	`MIB`(5), `TM_MIB`(5)
60	ERROR: Group does not have an alternate location defined
	Description	A `SET` operation changing the state of a `T_GROUP` class object from `MIGRATING` to `ACTIVE` or `REACTIVATE` was applied to a server group without a configured backup logical machine configured.
Action	Configure a backup logical machine for the server group before requesting activation.
See Also	`MIB`(5), `TM_MIB`(5)
61	*ERROR: Alternate location for group (lmid) is not active*
	Description	A `SET` operation on a `T_GROUP` class object requesting a state change from `MIGRATING` to `ACTIVE` or `REACTIVATE` could not be satisfied because the secondary logical machine identifier lmid is not currently active.
Action	Activate the secondary logical machine and then retry the server group state change.
See Also	`MIB`(5), `TM_MIB`(5)
62	*ERROR: Server group group* cannot migrate, server id svrid in an improper state**
	Description	A `SET` operation changing the state of a `T_GROUP` class object from `MIGRATING` to `ACTIVE` or `REACTIVATE` could not be satisfied because the server indicated by group and svrid is not in the `MIGRATING` state.
Action	Either the migration can be canceled (state change from `MIGRATING` to `IN`ACTIVE) or the offending server can be deactivated prior to retrying the migration.
See Also	`MIB`(5), `TM_MIB`(5)
63	ERROR: Could not update group location information
	Description	A `SET` operation on a `T_GROUP` class object requesting a state change from `MIGRATING` to `ACTIVE` or `REACTIVATE` could not be completed because of an internal system error updating the current group location in the bulletin board.
Action	Consult the userlog on the master site for any indication of the cause of the problem and contact your BEA TUXEDO system Technical Support.
See Also	`MIB`(5), `TM_MIB`(5)
64	WARN: Server could not be migrated and was removed from BB
	Description	`TA_STATUS` message indicating that the associated server could not be migrated as requested and has been deactivated.
Action	Consult the userlog on the server groups new site for information on why the server failed to migrate. If the problem can be resolved, the server can be brought back up by activating it normally.
See Also	`MIB`(5), `TM_MIB`(5)
65	*WARN: Terminating process pid* via SIGTERM**
	Description	An /AdminAPI request to change the state of a `T_SERVER` class object from `ACTIVE` or `SUSPENDED` to `DEAD` has caused the system to send a `SIGTERM` signal to the process in an attempt to allow the server to gracefully exit. If the server fails to shut down gracefully within the timeout period for the /AdminAPI request (`TA_MIBTIMEOUT`), then the server will be abortively terminated with a `SIGKILL` signal.
Action	Informational message only, no action required.
See Also	`Usignal`(3c), `MIB`(5), `TM_MIB`(5)
66	WARN: Terminating process pid via SIGKILL
	Description	An /AdminAPI request to change the state of a `T_SERVER` class object from `ACTIVE` or `SUSPENDED` to `DEAD` has caused the system to send a `SIGKILL` signal to the process to abortively terminate the server.
Action	Informational message only, no action required
See Also	`Usignal`(3c), `MIB`(5), `TM_MIB`(5)
67	ERROR: Cannot change primary LMID for an active T_GROUP class instance
	Description	A `SET` operation for a `T_GROUP` class object attempted to change the primary logical machine identifier for an active server group.
Action	Server group migration is achieved by setting the `TA_STATE` of the group to `MIGRATING` followed by completing any group specific migration activities and finally by setting the `TA_STATE` of the group to `ACTIVE`. Once this sequence is completed, the primary and backup logical machines for the group will be reversed.
See Also	`MIB`(5), `TM_MIB`(5)
68	ERROR: Cannot delete a T_MACHINE class instance with a pre-5.0 release site active
	Description	A operation to delete a `T_MACHINE` class instance could not be satisfied because one or more machines in the configuration is running a release prior to 5.0.
Action	BEA TUXEDO system sites running releases prior to 5.0 do not have the /AdminAPI service and the requested global update cannot be done while those systems are active within the application. Otherwise, the indicated machines userlog file should be examined for possible causes of the missing service. The indicated machine can be deactivated and reactivated in an attempt to make the required service available.
See Also	`MIB`(5), `TM_MIB`(5)
69	ERROR: Cannot invalidate T_MACHINE class instance specified in T_DOMAIN TA_MASTER attribute
	Description	A `SET` operation on a `T_MACHINE` class object to set the `TA_STATE` from `IN`ACTIVE to `INVALID` could not be satisfied because the logical machine identifier is referenced in the `T_DOMAIN` `TA_MASTER` attribute value.
Action	Change the `T_DOMAIN` `TA_MASTER` value to reference other machines before attempting to invalidate this machine.
See Also	`MIB`(5), `TM_MIB`(5)
70	ERROR: Cannot invalidate T_MACHINE class instance specified in T_GROUP TA_LMID attribute
	Description	A `SET` operation on a `T_MACHINE` class object to set the `TA_STATE` from `IN`ACTIVE to `INVALID` could not be satisfied because the logical machine identifier is referenced in a `T_GROUP` `TA_LMID` attribute value
Action	Change the `T_GROUP` `TA_LMID` values to reference other machines before attempting to invalidate this machine.
See Also	`MIB`(5), `TM_MIB`(5)
71	ERROR: Cannot invalidate T_GROUPS class instance with servers configured in group
	Description	A `SET` operation on a `T_GROUP` class object to set the `TA_STATE` from `IN`ACTIVE to `INVALID` could not be satisfied because their are currently configured `T_SERVER` class objects associated with the server group.
Action	Invalidate the individual `T_SERVER` class objects in the group before attempting to invalidate the server group itself.
See Also	`MIB`(5), `TM_MIB`(5)
72	ERROR: Cannot invalidate T_GROUPS class instance with services configured in group
	Description	A `SET` operation on a `T_GROUP` class object to set the `TA_STATE` from `IN`ACTIVE to INVALID could not be satisfied because their are currently configured `T_SVCGRP` class objects associated with the server group.
Action	Invalidate the individual `T_SVCGRP` class objects associated with the group before attempting to invalidate the server group itself.
See Also	`MIB`(5), `TM_MIB`(5)
73	ERROR: Cannot invalidate T_SERVICE class instance with a corresponding configured T_SVCGRP class instance
	Description	A `SET` operation on a `T_SERVICE` class object to set the `TA_STATE` from INACTIVE to INVALID could not be satisfied because their are currently configured `T_SVCGRP` class objects associated with the same TA_SERVICENAME attribute value.
Action	Invalidate all `T_SVCGRP` class objects for a particular TA_SERVICENAME value before attempting to invalidate the `T_SERVICE` class object for that TA_SERVICENAME.
See Also	`MIB`(5), `TM_MIB`(5)
74	ERROR: Failed to advertise dynamic /Admin service svc
	Description	The administrative service svc could not be offered by the administrative server generating the userlog message during server initialization. This message is generated by one of the following administrative servers: `DBBL`, `BBL` or `BRIDGE`. In the case of a `BRIDGE` server, the error is non-fatal and the server will boot and continue to function. For the other servers, the error causes server initialization to fail and the server fails to boot.
Action	In most cases, this problem is encountered when the configured size of the services table in the bulletin board is too small. In this case, shut down the application and increase the value for the `T_DOMAIN` TA_MAXSERVICES attribute before attempting to reboot the application. If this does not solve the problem, then consult the userlog messages immediately preceding and following this message for more information on the failure.
See Also	`MIB`(5), `TM_MIB`(5)
75	ERROR: /Admin service input buffer not FML32
	Description	An /AdminAPI request was received that was not an FML32 typed buffer. /AdminAPI services process only FML32 typed buffers.
Action	Change the administrative program to generate FML32 requests only.
See Also	`Fintro`(3fml), `MIB`(5), `TM_MIB`(5)
76	ERROR: /Admin service input buffer does not include class
	Description	An administrative request received by an /AdminAPI service did not contain a TA_CLASS value. A TA_CLASS value is required as defined in `MIB`(5).
Action	Correct the request message to include a TA_CLASS value.
See Also	`Fintro`(3fml), `MIB`(5), `TM_MIB`(5)
78	ERROR: Invalid class specified
	Description	The TA_CLASS value for an /AdminAPI request is either invalid (does not match any classes known by the system) or is missing.
Action	Examine the original input buffer (also contained with the reply buffer) to see if the TA_CLASS value is missing or invalid. If it is missing, then add the appropriate class value to the buffer. If it is invalid, then check reference pages and spelling and correct the class name in the request.
See Also	`MIB`(5), `TM_MIB`(5)
79	ERROR: Invalid operation specified
	Description	Missing or invalid value for TA_OPERATION included in /AdminAPI request buffer. This is a required input parameter on all /AdminAPI requests and must have a value of `GET`, `SET` or `GETNEXT`.
Action	Correct the input buffer to include an appropriate value for the TA_OPERATION attribute.
See Also	`MIB`(5), `TM_MIB`(5)
80	ERROR: Missing cursor on GETNEXT operation
	Description	A TA_CURSOR was not included in a GETNEXT request. GETNEXT operations require a TA_CURSOR value be included with the request. TA_CURSOR values are returned from both `GET` and GETNEXT operations when there are additional objects matching the request criteria that have not yet been returned.
Action	The required TA_CURSOR value should be extracted from a previous `GET` or GETNEXT reply message and included in the GETNEXT request.
See Also	`MIB`(5), `TM_MIB`(5)
81	ERROR: Invalid cursor (cursor) specified on GETNEXT operation
	Description	The TA_CURSOR value provided with a GETNEXT request is invalid. Cursor values have a specific internally defined format and the provided cursor does not match that format.
Action	Insure that cursor values are extracted from previous `GET` or GETNEXT reply messages and that they are not modified in any way before using them on subsequent GETNEXT requests.
See Also	`MIB`(5), `TM_MIB`(5)
82	ERROR: SET operation on readonly class class
	Description	A `SET` request on the class class failed because the indicated class has no writable attributes.
Action	Consult the appropriate reference page for the class in question to see if any attributes are defined as writable in any instance. If not, then the administrative tool being used should be changed to keep from generating `SET` requests for this class. Otherwise, the permissions for attributes in the class have been changed dynamically (see `T_CLASSATT` class definition in `MIB`(5)) to make it a read only class. In this case, the application administrator should be consulted to see if the appropriate action is to change the class permissions or to change the administrative tool to eliminate the request.
See Also	`MIB`(5), `TM_MIB`(5)
83	ERROR: Conflicting key values in SET request
	Description	A `SET` request on a class with local information only contained conflicting key values with respect to mapping the request to a particular logical machine. The key values in question may be any of the following depending on the class in question; `TA_LMID`, `TA_PMID`, `TA_SRVGRP`, `TA_CLIENTID`, `TA_SOURCE` or `TA_GTRID`.
Action	Correct the key values on the request to be consistent.
See Also	`MIB`(5), `TM_MIB`(5)
84	ERROR: Invalid operation specified
	Description	Missing or invalid value for TA_OPERATION included in /AdminAPI request buffer. This is a required input parameter on all /AdminAPI requests and must have a value of `GET`, `SET` or GETNEXT.
Action	Correct the input buffer to include an appropriate value for the TA_OPERATION attribute.
See Also	`MIB`(5), `TM_MIB`(5)
85	*ERROR: Internal System/T failure (tperrno)*
	Description	Internal BEA TUXEDO system error tperrno encountered while attempting to process master migration.
Action	Contact your BEA TUXEDO system Technical Support.
See Also	`MIB`(5), `TM_MIB`(5)
86	ERROR: Invalid TA_MASTER (string) specified on SET operation
	Description	An invalid string value for the `TA_MASTER` attribute was specified on a `SET` request for the `T_DOMAIN` class object.
Action	Correct the `TA_MASTER` value in the request
See Also	`MIB`(5), `TM_MIB`(5)
87	*ERROR: Invalid TA_MASTER (new_mast,new_back) specified on SET operation*
	Description	The `TA_MASTER` value provided on a `SET` request for the `T_DOMAIN` class was invalid. The problem is caused either by the new master logical machine new_mast not matching the previous backup logical machine value or by the new backup logical machine new_back not matching the previous master logical machine value.
Action	Correct the request to contain a valid change to the `TA_MASTER` attribute value as defined in the `TM_MIB`(5) reference page.
See Also	`MIB`(5), `TM_MIB`(5)
88	*ERROR: Invalid logical machine identifier (lmid) specified for master*
	Description	The backup logical machine identifier lmid specified for the `TA_MASTER` attribute on a `SET` request for the `T_DOMAIN` class does not match a configured logical machine.
Action	Correct the request to include a valid logical machine on the request.
See Also	`MIB`(5), `TM_MIB`(5)
89	ERROR: Missing /Admin API key field(s) on SET
	Description	An /AdminAPI `SET` request on a class with local attributes only did not specify sufficient key fields to route the request to the logical machine where the object is resident.
Action	Consult the reference page to determine what key fields are available for the class in question and provide sufficient key fields for logical machine mapping.
See Also	`MIB`(5), `TM_MIB`(5)
90	ERROR: Class class is not readable to this user
	Description	A `GET` request for class could not be satisfied because the class contains no readable attributes for the invoking user.
Action	In cases where the information is not intended to be available to the invoking user, this message is informational only and there is no action to be taken. If the administrator intended the user to have access to the indicated class, then the permissions on the class need to be relaxed by setting appropriate permissions values via the `T_CLASSATT` class or by resetting the `T_DOMAIN` `TA_MIBMASK` attribute value.
See Also	`MIB`(5), `TM_MIB`(5)
91	*ERROR: Missing required key field keyfield* on T_DEVICE GET request**
	Description	The key field keyfield is missing on a `GET` request for the `T_DEVICE` class. The key field keyfield is required for `GET` access to the `T_DEVICE` class as defined in the `TM_MIB`(5) reference page.
Action	Add the necessary key field value to the request.
See Also	`MIB`(5), `TM_MIB`(5)
92	*ERROR: Invalid service name (svc) presented to /Admin service*
	Description	An invalid service name svc has been presented to the /AdminAPI service processing routine.
Action	Correct the requested service on the request.
See Also	`MIB`(5), `TM_MIB`(5)
93	*ERROR: Invalid service name (svc) presented to /Admin service*
	Description	An invalid service name svc has been presented to the /AdminAPI service processing routine.
Action	Correct the requested service on the request.
See Also	`MIB`(5), `TM_MIB`(5)
94	ERROR: Failed to update FML and VIEW environment variables
	Description	/AdminAPI service initialization for the administrative process logging the message failed because the indicated environment variables could not be dynamically updated to include references to directories and files necessary for /AdminAPI processing. This error is caused by a failure to allocate sufficient memory from the system.
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, `MIB`(5), `TM_MIB`(5)
95	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc` failed while adding FML and VIEW environment variables to the process memory.
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, `MIB`(5), `TM_MIB`(5)
97	ERROR: Invalid logical machine specification and/or conflict in search criteria
	Description	A `GET` request contained conflicting key values with respect to mapping the request to a particular logical machine. The key values in question may be any of the following depending on the class in question; `TA_LMID`, `TA_PMID`, `TA_SRVGRP`, `TA_CLIENTID`, `TA_SOURCE` or `TA_GTRID`.
Action	Correct the key values on the request to be consistent.
See Also	`MIB`(5), `TM_MIB`(5)
98	WARN: Stray reply during fanout processing, ignored
	Description	A GET or `SET` that required the `DBBL` to fanout the processing received a stray reply from a previous such request. The stray reply is ignored and processing continues.
Action	This condition may be caused by a number of different conditions. A temporary disruption of network service may cause replies to be delayed past the timeout period. Timeout periods that are too small may cause fanout processing to abandon polling for replies before a reasonable amount of time has passed. Excessive administrative traffic may be clogging the network causing undue delays. If the condition occurs infrequently and is not attributable to a particular request, then no action is indicated. If the condition occurs consistently after a particular request, then examine requests made just previously to see if their timeout values are too small. If the condition occurs frequently, then the `T_DOMAIN` timer attribute values (`TA_SCANUNIT`, `TA_BBLQUERY`, `TA_BLOCKTIME`, `TA_DBBLWAIT` and `TA_SANITYSCAN`) may need to be raised to reduce administrative traffic on the network. Additionally, the administrative tools being used to monitor the system may need to be examined to identify excessive traffic they may be injecting into the system.
See Also	`MIB`(5), `TM_MIB`(5)
99	ERROR: Invalid operation (op) specified for /Admin request
	Description	Missing or invalid value for TA_OPERATION included in /AdminAPI request buffer. This is a required input parameter on all /AdminAPI requests and must have a value of GET, `SET` or GETNEXT.
Action	Correct the input buffer to include an appropriate value for the TA_OPERATION attribute.
See Also	`MIB`(5), `TM_MIB`(5)

[Top] [Prev] [Next] [Bottom]