![]() |
![]() |
|
|
1 |
INFO: Abortively terminating client process pid | |
|
Description |
An /AdminAPI request to change the state of a client to |
Action |
Informational message only, no action required. | |
See Also |
| |
2 |
ERROR: Server group name does not match existing group | |
|
Description |
The server group name, |
Action |
Correct the server group name and regenerate the request. | |
See Also |
| |
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 |
| |
4 |
ERROR: SYSTEM_ACCESS mismatch with NO_OVERRIDE set in T_DOMAIN class | |
|
Description |
A |
Action |
Remove the change to the | |
See Also |
| |
5 |
ERROR: TA_MAX(max) not set >= TA_MIN(min) | |
|
Description |
The maximum number of server instances max specified on a |
Action |
Lower min or raise max to be in accordance with the restriction and regenerate the request. | |
See Also |
| |
6 |
ERROR: SET operation violates restrictions on servers with same TA_RQADDR | |
|
Description |
The request queue address name for a |
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 |
| |
7 |
ERROR: Overlapping range for TA_SRVGRP, TA_SRVID and TA_MAX | |
|
Description |
A |
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 |
| |
8 |
ERROR: SET of TA_STATE to | |
|
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 |
| |
9 |
ERROR: Global /Admin update failed processing on LMID(lmid) with error code(num) and status(status) | |
|
Description |
A |
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 |
| |
10 |
WARN: Could not find registry table entry for server svrgrp/svrid | |
|
Description |
A |
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 |
| |
11 |
ERROR: Cannot update T_SERVICE class with active T_SVCGRP instance | |
|
Description |
An /AdminAPI request to |
Action |
Defer the update of the | |
See Also |
| |
12 |
WARN: AUTOTRAN specified for SERVICE service with TRANTIME=0 | |
|
Description |
An /AdminAPI |
Action |
Examine the object to be sure that the settings are what is intended and correct them if necessary. | |
See Also |
| |
13 |
ERROR: SET operation did not specify unique class instance | |
|
Description |
The indicated /AdminAPI |
Action |
Provide sufficient key fields to restrict the request to exactly one object and regenerate the request. | |
See Also |
| |
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 |
| |
15 |
WARN: ROUTING criteria (for SERVICE svc) is not defined in the ROUTING section | |
|
Description |
The |
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 | |
See Also |
| |
16 |
ERROR: SET keys do not match existing class instance | |
|
Description |
An /AdminAPI request to |
Action |
Correct the request to address an existing class object and regenerate. | |
See Also |
| |
17 |
ERROR: TA_SVCRNAM may be set only when Activating service | |
|
Description |
A |
Action |
Include the setting of | |
See Also |
| |
18 |
WARN: AUTOTRAN specified for SERVICE svc with TRANTIME=0 | |
|
Description |
An /AdminAPI |
Action |
Examine the object to be sure that the settings are what is intended and correct them if necessary. | |
See Also |
| |
19 |
ERROR: TA_AUTHSVC specified without security turned on | |
|
Description |
A |
Action |
Either turn on security before or with the request to set the | |
See Also |
| |
20 |
ERROR: LAN or MIGRATE option specified without MP TA_MODEL value | |
|
Description |
A |
Action |
Either set the | |
See Also |
| |
21 |
ERROR: Backup TA_MASTER allowed only for MP TA_MODEL | |
|
Description |
A backup master logical machine was specified in the |
Action |
Either set the | |
See Also |
| |
22 |
ERROR: Invalid master machine specified in TA_MASTER | |
|
Description |
The master logical machine identifier in the |
Action |
Correct the logical machine identifiers used in the request. | |
See Also |
| |
23 |
ERROR: Invalid backup machine specified in TA_MASTER | |
|
Description |
The logical machine identifier specified in the |
Action |
Correct the logical machine identifier used for the backup machine. | |
See Also |
| |
24 |
ERROR: TA_SYSTEM_ACCESS value set with NO_OVERRIDE contradicts T_SERVER settings | |
|
Description |
An attempt was made to set the |
Action |
Either remove the | |
See Also |
| |
25 |
ERROR: AUTOTRAN specified for SERVICE svc SRVGRP group with no TMS | |
|
Description |
A |
Action |
Change the | |
See Also |
| |
26 |
ERROR: TA_LMID value lmid already exists | |
|
Description |
An attempt to |
Action |
Change the logical machine identifier and regenerate the request. | |
See Also |
| |
27 |
ERROR: TA_LMID value lmid conflicts with existing T_GROUP class instance | |
|
Description |
An attempt to |
Action |
Change the logical machine identifier and regenerate the request or invalidate the server group and reuse the current logical machine identifier. | |
See Also |
| |
28 |
ERROR: TA_PMID value pmid already exists | |
|
Description |
An attempt to |
Action |
Change the physical machine identifier and regenerate the request. | |
See Also |
| |
29 |
ERROR: Cannot create new T_MACHINE class instances in SHM mode | |
|
Description |
A |
Action |
If an additional machine needs to be added to the application, then you must shut down the application, change the model to | |
See Also |
| |
30 |
ERROR: Cannot create new T_MACHINE class instances, full machine table | |
|
Description |
A |
Action |
Shut down the application, reconfigure the | |
See Also |
| |
31 |
ERROR: Insufficient networking information, TA_NADDR or TA_NLSADDR missing | |
|
Description |
A |
Action |
Supply either or both of the missing | |
See Also |
| |
32 |
ERROR: Networking information may not be specified without LAN option set | |
|
Description |
A |
Action |
Add the | |
See Also |
| |
33 |
ERROR: One of both of the LMIDs in TA_LMID do not match configured machines | |
|
Description |
A |
Action |
Check both logical machine identifiers and change the invalid identifier to one for a configured machine. | |
See Also |
| |
34 |
ERROR: LMIDs not distinct in TA_LMID for T_GROUP | |
|
Description |
A |
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 |
| |
35 |
ERROR: TA_SRVGRP matches defined logical machine name | |
|
Description |
A |
Action |
Change the | |
See Also |
| |
36 |
ERROR: TA_SRVGRP or TA_GRPNO not unique | |
|
Description |
A |
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 |
Action |
Shut down the application, reconfigure the | |
See Also |
| |
38 |
WARN: TA_OPENINFO/TA_CLOSEINFO ignored for group(group) with no TMS | |
|
Description |
A |
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 | |
See Also |
| |
39 |
ERROR: Machine associated with server group does not have a TLOG device | |
|
Description |
A |
Action |
Either associate | |
See Also |
| |
40 |
ERROR: Multiple LMIDs disallowed, MIGRATE option not set | |
|
Description |
A |
Action |
Add the | |
41 |
ERROR: TA_GSTATE without TA_GRPNO on T_TRANSACTION group state change | |
|
Description |
A |
Action |
Correct the request to include the appropriate | |
See Also |
| |
42 |
ERROR: TA_GSTATE and TA_STATE specified on T_TRANSACTION group state change | |
|
Description |
A |
Action |
Remove one of the attribute updates from the request buffer and regenerate. | |
See Also |
| |
43 |
ERROR: Permissions violation on SET request | |
|
Description |
A |
Action |
Remove the update to the offending attribute from the request. | |
44 |
ERROR: Invalid GTRID for T_TRANSACTION state change | |
|
Description |
A |
Action |
Check to be sure that the correct | |
See Also |
| |
45 |
ERROR: TA_GRPNO not found for T_TRANSACTION class instance | |
|
Description |
A |
Action |
Correct the | |
See Also |
| |
46 |
ERROR: Cannot destroy device entry specified | |
|
Description |
A |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
47 |
ERROR: TA_TLOGCOUNT required to write new log records | |
|
Description |
A |
Action |
Add the appropriate value for | |
See Also |
| |
48 |
ERROR: TA_CFGDEVICE required on T_DEVICE GET operation | |
|
Description |
A |
Action |
Provide a value for | |
See Also |
| |
49 |
ERROR: Invalid input to T_DEVICE SET request | |
|
Description |
A |
Action |
Correct the request to include the appropriate state change. | |
See Also |
| |
50 |
ERROR: Could not create device entry specified | |
|
Description |
A
|
Action |
Correct the request. | |
See Also |
| |
51 |
ERROR: Cannot destroy device entry 0 while other entries are in UDL | |
|
Description |
A |
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 |
Action |
Shut down the application before attempting to change these options values. | |
See Also |
| |
53 |
ERROR: ACCSTATS may not be set in MP model application | |
|
Description |
A |
Action |
Convert the application to | |
See Also |
| |
54 |
ERROR: Missing or invalid LMID for SET operation | |
|
Description |
A |
Action |
Add the correct | |
See Also |
| |
55 |
ERROR: TA_MASTER migration combined with other T_DOMAIN changes | |
|
Description |
A |
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 |
| |
56 |
ERROR: Could not perform TA_MASTER migration | |
|
Description |
A |
Action |
ACTION Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
57 |
ERROR: Backup machine minor release (b_minor) differs from current master (m_minor) | |
|
Description |
A |
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 |
| |
58 |
ERROR: T_SVCGRP state change INA to ACT without corresponding active server | |
|
Description |
A |
Action |
Provide either the | |
See Also |
| |
59 |
ERROR: Alternate LMID not specified for group | |
|
Description |
A |
Action |
Configure a backup logical machine for the server group before requesting migration. | |
See Also |
| |
60 |
ERROR: Group does not have an alternate location defined | |
|
Description |
A |
Action |
Configure a backup logical machine for the server group before requesting activation. | |
See Also |
| |
61 |
ERROR: Alternate location for group (lmid) is not active | |
|
Description |
A |
Action |
Activate the secondary logical machine and then retry the server group state change. | |
See Also |
| |
62 |
ERROR: Server group group cannot migrate, server id svrid in an improper state | |
|
Description |
A |
Action |
Either the migration can be canceled (state change from | |
See Also |
| |
63 |
ERROR: Could not update group location information | |
|
Description |
A |
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 |
| |
64 |
WARN: Server could not be migrated and was removed from BB | |
|
Description |
|
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 |
| |
65 |
WARN: Terminating process pid via SIGTERM | |
|
Description |
An /AdminAPI request to change the state of a |
Action |
Informational message only, no action required. | |
See Also |
| |
66 |
WARN: Terminating process pid via SIGKILL | |
|
Description |
An /AdminAPI request to change the state of a |
Action |
Informational message only, no action required | |
See Also |
| |
67 |
ERROR: Cannot change primary LMID for an active T_GROUP class instance | |
|
Description |
A |
Action |
Server group migration is achieved by setting the | |
See Also |
| |
68 |
ERROR: Cannot delete a T_MACHINE class instance with a pre-5.0 release site active | |
|
Description |
A operation to delete a |
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 |
| |
69 |
ERROR: Cannot invalidate T_MACHINE class instance specified in T_DOMAIN TA_MASTER attribute | |
|
Description |
A |
Action |
Change the | |
See Also |
| |
70 |
ERROR: Cannot invalidate T_MACHINE class instance specified in T_GROUP TA_LMID attribute | |
|
Description |
A |
Action |
Change the | |
See Also |
| |
71 |
ERROR: Cannot invalidate T_GROUPS class instance with servers configured in group | |
|
Description |
A |
Action |
Invalidate the individual | |
See Also |
| |
72 |
ERROR: Cannot invalidate T_GROUPS class instance with services configured in group | |
|
Description |
A |
Action |
Invalidate the individual | |
See Also |
| |
73 |
ERROR: Cannot invalidate T_SERVICE class instance with a corresponding configured T_SVCGRP class instance | |
|
Description |
A |
Action |
Invalidate all | |
See Also |
| |
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: |
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 | |
See Also |
| |
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 |
| |
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 |
Action |
Correct the request message to include a TA_CLASS value. | |
See Also |
| |
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 |
| |
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 |
Action |
Correct the input buffer to include an appropriate value for the TA_OPERATION attribute. | |
See Also |
| |
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 |
Action |
The required TA_CURSOR value should be extracted from a previous | |
See Also |
| |
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 | |
See Also |
| |
82 |
ERROR: SET operation on readonly class class | |
|
Description |
A |
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 | |
See Also |
| |
83 |
ERROR: Conflicting key values in SET request | |
|
Description |
A |
Action |
Correct the key values on the request to be consistent. | |
See Also |
| |
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 |
Action |
Correct the input buffer to include an appropriate value for the TA_OPERATION attribute. | |
See Also |
| |
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 |
| |
86 |
ERROR: Invalid TA_MASTER (string) specified on SET operation | |
|
Description |
An invalid string value for the |
Action |
Correct the | |
See Also |
| |
87 |
ERROR: Invalid TA_MASTER (new_mast,new_back) specified on SET operation | |
|
Description |
The |
Action |
Correct the request to contain a valid change to the | |
See Also |
| |
88 |
ERROR: Invalid logical machine identifier (lmid) specified for master | |
|
Description |
The backup logical machine identifier lmid specified for the |
Action |
Correct the request to include a valid logical machine on the request. | |
See Also |
| |
89 |
ERROR: Missing /Admin API key field(s) on SET | |
|
Description |
An /AdminAPI |
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 |
| |
90 |
ERROR: Class class is not readable to this user | |
|
Description |
A |
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 | |
See Also |
| |
91 |
ERROR: Missing required key field keyfield on T_DEVICE GET request | |
|
Description |
The key field keyfield is missing on a |
Action |
Add the necessary key field value to the request. | |
See Also |
| |
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 |
| |
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 |
| |
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 |
| |
95 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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 |
| |
97 |
ERROR: Invalid logical machine specification and/or conflict in search criteria | |
|
Description |
A |
Action |
Correct the key values on the request to be consistent. | |
See Also |
| |
98 |
WARN: Stray reply during fanout processing, ignored | |
|
Description |
A GET or |
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 | |
See Also |
| |
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, |
Action |
Correct the input buffer to include an appropriate value for the TA_OPERATION attribute. | |
See Also |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|