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

7. CMDGW Messages 2000-2099

2000	ERROR: Failed to decrypt password
	Description	If SECURITY is set to `APP_PW` in *RESOURCES section of the TUXCONFIG file, and `dmloadcf` is run on the `DMCONFIG` file, the user must enter the application password before the `BDMCONFIG` file is created or over-written. `dmloadcf` attempt to decrypt the application password failed.
Action	Contact BEA TUXEDO system Technical Support.
See Also	`dmconfig`(5)
2001	ERROR: Invalid application password
	Description	A failure occurred while processing the `dmconfig` file with the dmloadcf command. The application password given does not match the password established when the `ubbconfig` file was processed using the `tmloadcf` command.
Action	Retry the operation and enter the correct password. Alternatively, you may use `tmloadcf` to process the `ubbconfig` file again and establish a new password.
See Also	`dmconfig`(5)
2002	*ERROR: Duplicate NWADDR (string) occurs in DM_TDOMAIN section*
	Description	The value of `NWADDR` in `DM_TDOMAIN` section of the `DMCONFIG` file must be unique.
Action	Specify a valid value for `NWADDR` and re-load the configuration.
See Also	`dmconfig`(5)
2003	*ERROR: OSITP DOMAIN (ositp) has more than one address*
	Description	There can only be one address specified for an `OSITP` domain. `OSITP` domain, ositp, has multiple addresses.
Action	Delete one of the entries for ositp domain and re-load the configuration.
See Also	`dmconfig`(5)
2004	*ERROR: Can't specify string* addresses for domain string**
	Description	If a domain is defined as `TDOMAIN`, you cannot specify `OSITP` addresses for it. If a domain is defined as `OSITP`, you cannot specify `TDOMAIN` addresses for it.
Action	Correct the error and re-load the configuration.
See Also	`dmconfig`(5)
2005	*ERROR: Duplicate rsvc entries for string* for same LDOM should have the same ROUTING criterion if RDOM is different**
	Description	If entries in `DM_REMOTE_SERVICE` section of the `DMCONFIG` file have the same `LDOM` value, then they should also have the same `ROUTING` criterion if `RDOM` is different.
Action	Correct the error and re-load the configuration.
See Also	`dmconfig`(5)
2020	INFO: Statistics reset
	Description	The Gateway Administrative Server issues this message in response to the stats command which is used to toggle the statistics gathering functionality. This informational message indicates that statistics gathering has been reset.
Action	This is an informational message with no associated user action.
See Also	`dmadmin`(1)
2021	ERROR: Cannot access TUXCONFIG file to validate BLOCKTIME in DM_LOCAL_DOMAIN section
	Description	While executing `dmadmin`, the `TUXCONFIG` file cannot be accessed to validate `BLOCKTIME` in `DM_LOCAL_DOMAIN` section of the `DMCONFIG` file.
Action	Check to make sure that the file exists and the directory structure is accessible. If the `TUXCONFIG` file does not exist, create it first before running `dmloadcf`.
See Also	`dmconfig`(5)
2022	ERROR: All the remote domains in ACLIST of DM_ACCESS_CONTROL section must be of the same domain type
	Description	All remote domains listed in the `ACLIST` of `DM_ACCESS_CONTROL` section of the `DMCONFIG` file must be of the same type, that is, `TDOMAIN` or `OSITP`.
Action	Correct the error and re-load the configuration.
See Also	`dmconfig`(5)
2023	*ERROR: ACL (aclname) not defined in DM_ACCESS_CONTROL section*
	Description	An entry in `DM_LOCAL_SERVICES` section of the `DMCONFIG` file referenced an undefined entry, aclname, in `DM_ACCESS_CONTROL` section.
Action	Correct the error and re-load the configuration.
See Also	`dmconfig`(5)
2027	*ERROR: MTYPE parameter must be <= length* characters in length**
	Description	An error was detected while processing the `dmconfig` file using the `dmloadcf` command. The `MTYPE` parameter in the `DM_LOCAL_DOMAINS` section contains a value which is too long. The value for `MTYPE` must be less than or equal to length characters in length.
Action	Correct the `MTYPE` parameter and retry the operation.
See Also	`dmconfig`(5)
2029	*ERROR: MTYPE parameter must be <= length* characters in length**
	Description	An error was detected while processing the `dmconfig` file using the `dmloadcf` command. The `MTYPE=` parameter in the `DM_REMOTE_DOMAINS` section contains a value which is too long. The value for `MTYPE` must be less than or equal to length characters in length.
Action	Correct the `MTYPE=` parameter and retry the operation.
See Also	`dmconfig`(5)
2030	ERROR: Memory allocation failure
	Description	An error was detected while processing the `dmconfig` file using the `dmloadcf` command. A memory allocation failure was detected.
Action	Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
See Also	`dmconfig`(5)
2031	ERROR: Can't open file file name
	Description	The Domain Administrative server detected an error while trying to open the temporary edit file file name. This error may indicate a problem with the file permission settings or a problem with the file system.
Action	Identify any problems with the file permission settings or file system.
See Also	`dmadmin`(1)
2032	ERROR: Can't put FIELDTBLS into environment
	Description	The Domain Administrative server detected an error while trying to create the configuration environment. The environment variable `FIELDTBLS` could not be added to the environment.
Action	This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO system Technical Support.
See Also	`dmadmin`(1)
2033	ERROR: Environment variable TUXDIR not defined
	Description	The Domain Administrative server detected an error while trying to create the configuration environment. The environment variable `TUXDIR` was not defined or the Domain Administrative server could not obtain the environment variable `TUXDIR`.
Action	Ensure that the environment variable `TUXDIR` is set in your environment to the absolute path for your BEA TUXEDO system software.
See Also	`dmadmin`(1)
2034	ERROR: Can't put FLDTBLDIR into environment
	Description	The Domain Administrative server detected an error while trying to create the configuration environment. The environment variable `FLDTBLDIR` could not be added to the environment.
Action	This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO system Technical Support.
See Also	dmadmin(1)
2035	ERROR: Fldid failed. Ferror: error code
	Description	The Domain Administrative server detected an error while trying to create the configuration environment. The field identifier could not be retrieved for field name `TA_SRVGRP`. The value of error code will give more details describing the cause of the error.
Action	Refer to the FML documentation for a description of error code. Correct the source of the error and retry the operation.
See Also	`dmadmin`(1)
2042	ERROR: Service TMS advertised in this group by server not on this queue
	Description	When the Domain gateway was booted, it found that another server on a different queue within the same group was already offering the same transaction coordination services that are offered by a Domain gateway. This is an error, and the gateway process will exit.
Action	Domain gateway groups should not have a TMS server associated with them, since the TMS functionality is performed by the gateway itself. Modify the `TUXCONFIG` file so that the `TMSNAME` parameter is not included in the `GROUPS` section of the configuration file for Domain gateway groups.
See Also	`ubbconfig`(5), `tmloadcf`(1), `tmconfig`(1)
2043	ERROR: Multiple Domain gateways not allowed within the same group
	Description	The current release of the Domain software does not allow multiple domain gateways within the same group. Additional gateways beyond the first gateway will fail to boot.
Action	No immediate action is required, but the `TUXCONFIG` file should be updated so that this error does not reoccur when the application is next booted. Only one Domain gateway should be specified per group in the `TUXCONFIG` file. If a very high throughput application requires the use of more than one Domain gateway, the gateways can be placed in separate server groups.
See Also	`ubbconfig`(5), `tmloadcf`(1)
2044	ERROR: Invalid class specified
	Description	A request of an invalid class has been routed to the `DMADM` server.
Action	Contact BEA TUXEDO system Technical Support with the exact error message.
2045	ERROR: Memory allocation failure
	Description	Failed to allocate dynamic memory necessary for processing the administrative request.
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.
2046	ERROR: Failed to perform dynamic reconfiguration of the application
	Description	While performing dynamic re-configuration for a local domain, the `DMADM` administrative server encountered an error. Check surrounding messages for specifics.
Action	Correct the error and re-issue the request.
See Also	`dmconfig`(5)
2047	*ERROR: Invalid operation (string) specified for /Admin request*
	Description	An invalid operation was specified in the administrative request. The valid operations are `GET`, `SET`, and `GETNEXT`.
Action	Specify the correct operation in the administrative request.
2048	*ERROR: Invalid class name (string) presented to /Admin service*
	Description	A request of an invalid class has been routed to the `DMADM` server.
Action	If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO system Technical Support with the exact error message.
2049	ERROR: Can't send dynamic re-configuration changes to GWADM server(s)
	Description	The `DMADM` administrative server received a request for dynamic re-configuration of the application. It successfully made the changes to the `BDMCONFIG` file but failed to propagate the changes to `GWADM` server(s).
Action	Check if any `GWADM` server terminated abnormally. Restart any `GWADM` servers that died. The changes will be picked up by the restarting `GWADM`s.
See Also	`dmconfig`(5)
2050	ERROR: tpalloc failed
	Description	Failed to allocate memory necessary for processing the administrative request.
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. If message persists, contact BEA TUXEDO system Technical Support with the exact error message.
2051	ERROR: Invalid class specified
	Description	A request of an invalid class has been routed to the `DMADM` server.
Action	If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO system Technical Support with the exact error message.
2052	ERROR: Failed to map request
	Description	An invalid request buffer was passed to the Domain Admin server (`DMADM`).
Action	Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO system Technical Support.
2053	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core `MIB` modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2054	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core `MIB` modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2055	ERROR: tpalloc failed
	Description	Failed to allocate memory necessary for processing the administrative request.
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. If message persists, contact BEA TUXEDO system Technical Support with the exact error message.
2056	ERROR: Invalid class specified
	Description	A request of an invalid class has been routed to the `DMADM` server.
Action	If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO system Technical Support with the exact error message.
2057	ERROR: Failed to map request
	Description	An invalid request buffer was passed to the Domain Admin server (`DMADM`).
Action	Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO system Technical Support.
2058	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core `MIB` modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2059	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core MIB modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2060	ERROR: Transaction state unknown
	Description	The transaction state corresponding to the (one of the) transaction(s) is invalid.
Action	Contact BEA TUXEDO system Technical Support with exact message and events leading up to the message.
2061	ERROR: tpalloc failed
	Description	Failed to allocate memory necessary for processing the administrative request.
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. If message persists, contact BEA TUXEDO system Technical Support with the exact error message.
2062	ERROR: Invalid class specified
	Description	A request of an invalid class has been routed to the `DMADM` server.
Action	If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO system Technical Support with the exact error message.
2063	ERROR: Failed to map request
	Description	An invalid request buffer was passed to the Domain Admin server (`DMADM`).
Action	Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO system Technical Support.
2064	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core `MIB` modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2065	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core MIB modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2066	ERROR: Failed to get generic request parameters
	Description	The generic `MIB` attributes specified in the request buffer are invalid.
Action	Correct the generic `MIB` attributes in the request buffer and re-issue the request.
2067	ERROR: tpalloc failed
	Description	Failed to allocate memory necessary for processing the administrative request.
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. If message persists, contact BEA TUXEDO system Technical Support with the exact error message.
2068	ERROR: Invalid TA_STATE specification
	Description	The `TA_STATE` attribute specified in the request buffer is invalid. Refer to the `MIB`(5) manual page for the class in question and check the allowable values for `TA_STATE`.
Action	Correct the request buffer and re-issue the request.
2069	ERROR: Failed Encryption
	Description	Failed to encrypt the password specified. This may be due to a number of problems with the configuration files and other system files.
Action	Contact BEA TUXEDO system Technical Support with the exact message, after sanity checks on the BEA TUXEDO Configuration files and Domain Configuration files.
2070	ERROR: Invalid class specified
	Description	A request of an invalid class has been routed to the `DMADM` server.
Action	If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO system Technical Support with the exact error message.
2071	ERROR: Failed to map request
	Description	An invalid request buffer was passed to the Domain Admin server (`DMADM`).
Action	Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO system Technical Support.
2072	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core `MIB` modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2073	ERROR: Failed to map reply
	Description	An invalid reply buffer was returned by core `MIB` modules, in response to the current request.
Action	Contact BEA TUXEDO system Technical Support.
2074	ERROR: BDMCONFIG file (string) does not exist
	Description	When `DMADM` administrative server is booted, it manages a `BDMCONFIG` file. The `BDMCONFIG` file, however, does not exist or is not accessible.
Action	Set a valid value for `BDMCONFIG` environment variable and restart the `DMADM` server.
See Also	`dmconfig`(5)
2075	ERROR: Unable to access TUXCONFIG file
	Description	The BEA TUXEDO Configuration file indicated by the environment variable TUXCONFIG is not accessible.
Action	Check for the presence of the `$TUXCONFIG` file and also check the permissions of the file along with permissions of directories in its pathname. Correct the problem and reboot the `DMADM` server.
2076	ERROR: Incompatible GWADM server -- group = string
	Description	The Gateway Administrative server (`GWADM`) for the indicated gateway group is of a different compatibility level than the Domain Admin server (`DMADM`).
	Action	Check that the `GWADM` server being executed is of the correct release/version number. Also check that for the `DMADM` server. If the `GWADM` server belongs to an incorrect version, reboot only the Gateway group with the correct `GWADM` server. If `DMADM` server belongs to an incorrect version, reboot the entire set of Domain servers (`DMADM`, all `GWADM`(s), all Gateways) using the correct DMADM server.
2077	*ERROR: Specified Local domain domain name* not active or not configured**
	Description	The Domain Administrative server detected an error. The domain domain name is not active. The domain must be active for the operation to complete.
Action	Activate the domain domain name and retry the operation.
See Also	`dmadmin`(1)
2078	*WARN: Service service name* offered by more than one server in this domain**
	Description	The Gateway Administrative server detected an error during server initialization. The service service name is offered by more than one server in this domain. A service can be offered by no more than one server in a given domain.
Action	Correct the domain configuration such that no service is offered by more than one server in the domain.
See Also	`GWADM`(5)
2079	*ERROR: Domain administrative service service name* not advertised: Can't get configuration: Exiting**
	Description	The Gateway Administrative server detected an error during server initialization. The Domain Administrative service service name is not advertised. The `DMADM` process must be booted before `GWADM` can be initialized.
Action	Boot the Domain Administrative server `DMADM` and retry.
See Also	`GWADM`(5)
2080	ERROR: Memory allocation failure
	Description	The Domain Administrative server detected an error while trying to create the configuration environment. An error occurred while trying to allocate virtual memory.
Action	Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
See Also	`dmadmin`(1)
2081	*ERROR: The password for user name* is unchanged, must be done from a tty**
	Description	The Domain Administrative server detected an error while trying to process the `modusr` command. The `modusr` command must be processed under control of a terminal.
Action	Retry the `modusr` command from a terminal.
See Also	`dmadmin`(1)
2082	ERROR: Cannot set both remote usr and local usr to *
	Description	The Domain Administrative server detected an error while trying to process the `addumap` command. The `addumap` command cannot set both the remote user and the local user to *.
Action	Retry the `addumap` command with a valid argument.
See Also	`dmadmin`(1)
2083	ERROR: Cannot set both remote usr and local usr to *
	Description	The Domain Administrative server detected an error while trying to process the `delumap` command. The `delumap` command cannot set both the remote user and the local user to *.
Action	Retry the `delumap` command with a valid argument.
See Also	`dmadmin`(1)

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