CMDGW Messages 1900-1999
|
|
1900
ERROR: NWADDR - must contain an even number of hex digits
Description
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The NWADDR parameter specified was found to contain an odd number of hex digits. The NWADDR parameter must contain and even number of hex digits.
Action
Correct the value of the NWADDR parameter and retry the operation.
See Also
dmconfig(5)
1901
ERROR: AET - must contain an even number of hex digits
Description
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The AET parameter specified was found to contain an odd number of hex digits. The AET parameter must contain and even number of hex digits.
Action
Correct the value of the AET parameter and retry the operation.
See Also
dmconfig(5)
1902
ERROR: AET=<string> is in an invalid format (IC = number)
Description
The value of AET in DM_OSITP section is in invalid format.
Action
Specify a valid value and re-load the configuration.
See Also
dmconfig(5)
1903
ERROR: TUXCONFIG environment variable not set.
Description
While executing dmadmin, the TUXCONFIG environment variable has not been set and exported.
Action
Set and export the TUXCONFIG environment variable and re-execute the command.
See Also
dmconfig(5)
1904
ERROR: TUXCONFIG environment variable must be an absolute pathname.
Description
The value of the TUXCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Action
Correct the value for the TUXCONFIG environment variable to be an absolute pathname.
See Also
dmconfig(5)
1905
ERROR: Error in reading TUXCONFIG file.
Description
While performing dynamic re-configuration, DMADM administrative server cannot read TUXCONFIG file. Since the application must be booted for dynamic reconfiguration to occur and booting requires reading the configuration file, this error should not normally occur. It may indicate that the configuration file has been destroyed or that a disk problem has occurred.
Action
Shut down the application and re-generate the TUXCONFIG file.
See Also
dmconfig(5)
1906
ERROR: Duplicate type/subtype(string) occurs in BUFTYPE of DM_ROUTING section.
Description
The BUFTYPE parameter in DM_ROUTING section in the DMCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)
Action
Modify the entry so that the same type/subtype pair is not specified more than once. Reload the configuration file.
See Also
dmconfig(5)
1907
ERROR: Duplicate (routname type:subtype) (string) occurs in DM_ROUTING section.
Description
While executing dmadmin, duplicate entries were found in the DM_ROUTING. ROUTINGNAME and type/subtype together constitute the key.
Action
Modify the entries so that no /type/subtype pair is specified for a particular ROUTINGNAME more than once. Re-execute the command.
See Also
dmconfig(5)
1909
WARN: Cannot update own queue table entry
Description
When the Domain gateway was booted, it was unable to update its own BEA TUXEDO system queue table entry with the proper flags. This failure will prevent the gateway from receiving either conversational or RPC type requests.
Action
Look to see whether an earlier userlog message gives further information on the failure. Shut down the application and reboot it to clear any corrupted memory that may be present. Consider running the application temporarily with SYSTEM_ACCESS set to PROTECTED|NO_OVERRIDE in the RESOURCES section of the TUXCONFIG file. This setting will slow performance, but will prevent the possibility of application corruption of shared memory. If the problem still persists when running with SYSTEM_ACCESS set to PROTECTED|NO_OVERRIDE, contact your BEA TUXEDO system Technical Support.
1911
ERROR: GWADM corresponding to local domain string is not running
Description
An attempt was made to dynamically re-configure a local domain that is non-existent, or the GWADM server corresponding to that local domain is not running.
Action
If the specified local domain name is invalid, enter a valid value and re-submit the command. If the GWADM server for the local domain is not running, startup the server and then re-issue the command.
See Also
dmconfig(5)
1915
ERROR: _dmcf_open failed: Cannot open DM_PASSWORDS section
Description
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (DM_RESOURCES, DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the DM_PASSWORDS section.
Action
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
See Also
dmconfig(5)
1917
ERROR: The passwd command must be run from the terminal
Description
The passwd command must be run from a terminal as opposed to, say, a shell script, since dmadmin prompts for new passwords on the terminal.
Action
Remove the use of the passwd command from any non-terminal invocations of dmadmin.
See Also
dmconfig(5)
1919
ERROR: Error obtaining Local Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1921
ERROR: Error obtaining Local Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1923
ERROR: Too many failed attempts
Description
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Action
Retry the passwd command.
See Also
dmconfig(5)
1925
ERROR: Error obtaining Remote Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1927
ERROR: Error obtaining Remote Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1929
ERROR: Too many failed attempts
Description
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Action
Retry the passwd command.
See Also
dmconfig(5)
1931
ERROR: Write to gateway log failed
Description
The Domain gateway was unable to write a record to the Domain transaction log.
Action
Check if a hardware failure or administrator action has accidentally damaged the device specified as the DMTLOGDEV in the DM_LOCAL_DOMAINS section of the BDMCONFIG file. If possible, repair any corruption. If the DMTLOGDEV must be recreated, shut down the Domain gateway group. Then use the dmadmin(1) subcommand crdmlog to create the domain, or just reboot the Domain gateway group, which will automatically create the log if it does not already exist.
See Also
dmadmin(1)
1937
ERROR: The passwd command must be run from the terminal
Description
Entries to DM_PASSWORDS section of BDMCONFIG file can only be added by running the command from a terminal as opposed to, say, a shell script, since dmadmin prompts for new passwords on the terminal.
Action
Remove the usage of the command from any non-terminal invocations of dmadmin.
See Also
dmconfig(5)
1938
ERROR: When updating LPWD, TA_LPWD should be set to U
Description
When updating LPWD parameter for a DM_PASSWORDS entry in the BDMCONFIG file using dmadmin configuration mode, TA_LPWD must be set to U.
Action
Specify a valid value for TA_LPWD and re-execute the command.
See Also
dmconfig(5)
1939
ERROR: When Adding a DM_PASSWORD entry, TA_LPWD should be set to Y
Description
When adding a DM_PASSWORDS entry to the BDMCONFIG file using dmadmin configuration mode, TA_LPWD must be set to Y.
Action
Specify a valid value for TA_LPWD and re-execute the command.
See Also
dmconfig(5)
1940
ERROR: When Adding a DM_PASSWORD entry, TA_LPWD should be set to Y
Description
When adding a DM_PASSWORDS entry to the BDMCONFIG file using dmadmin configuration mode, TA_LPWD must be set to Y.
Action
Specify a valid value for TA_LPWD and re-execute the command.
See Also
dmconfig(5)
1941
ERROR: When updating RPWD, TA_RPWD should be set to U
Description
When updating RPWD parameter for a DM_PASSWORDS entry in the DMCONFIG file using dmadmin configuration mode, TA_RPWD must be set to U.
Action
Specify a valid value for TA_RPWD and re-execute the command.
See Also
dmconfig(5)
1942
ERROR: When Adding a DM_PASSWORD entry, TA_RPWD should be set to Y
Description
When adding a DM_PASSWORDS entry to the DMCONFIG file using dmadmin configuration mode, TA_RPWD must be set to Y.
Action
Specify a valid value for TA_RPWD and re-execute the command.
See Also
dmconfig(5)
1943
ERROR: When Adding a DM_PASSWORD entry, TA_RPWD should be set to Y
Description
When adding a DM_PASSWORDS entry to the DMCONFIG file using dmadmin configuration mode, TA_RPWD must be set to Y.
Action
Specify a valid value for TA_RPWD and re-execute the command.
See Also
dmconfig(5)
1945
ERROR: Error obtaining Local Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1947
ERROR: Error obtaining Local Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1949
ERROR: Too many failed attempts
Description
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Action
Retry the passwd command.
See Also
dmconfig(5)
1951
ERROR: Error obtaining Remote Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1953
ERROR: Error obtaining Remote Domain Password
Description
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1955
ERROR: Too many failed attempts
Description
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Action
Retry the passwd command.
See Also
dmconfig(5)
1956
ERROR: Cannot create encryption key
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1957
ERROR: Cannot create encryption key
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1958
ERROR: Cannot create encryption schedule
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1959
ERROR: Failed to crypt password
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1961
ERROR: Cannot create encryption key
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1962
ERROR: Cannot create encryption schedule
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1963
ERROR: Failed to crypt password
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1964
ERROR: _dmcf_open failed: Can't open DM_RESOURCES section
Description
While re-encrypting passwords in DM_PASSWORDS section of BDMCONFIG file, the DM_RESOURCES section of BDMCONFIG file cannot be opened for reading.
Action
Make sure that the BDMCONFIG file still exists.
See Also
dmconfig(5)
1965
ERROR: _dmcf_seek failed: Can't seek to DM_RESOURCES section
Description
While re-encrypting passwords in DM_PASSWORDS section of BDMCONFIG file, the DM_RESOURCES section of BDMCONFIG file cannot be accesses for reading.
Action
Make sure that the BDMCONFIG file still exists.
See Also
dmconfig(5)
1966
ERROR: _dmcf_open failed: Can't open DM_PASSWORDS section
Description
While re-encrypting passwords in DM_PASSWORDS section of BDMCONFIG file, the DM_PASSWORDS section of BDMCONFIG file cannot be opened for reading.
Action
Make sure that the BDMCONFIG file still exists.
See Also
dmconfig(5)
1968
ERROR: _dmcf_write failed: Can't write new DMKEY in DM_RESOURCES section
Description
While re-encrypting passwords in DM_PASSWORDS section of BDMCONFIG file, the DM_PASSWORDS section of BDMCONFIG file cannot be accessed for writing the new DMKEY.
Action
Make sure that the BDMCONFIG file still exists.
See Also
dmconfig(5)
1969
ERROR: Cannot create encryption key
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1970
ERROR: TUXCONFIG environment variable not set
Description
While executing dmloadcf, the TUXCONFIG environment variable has not been set and exported.
Action
Set and export the TUXCONFIG environment variable and re-execute the command.
See Also
dmconfig(5)
1971
ERROR: TUXCONFIG environment variable must be an absolute pathname.
Description
The value of the TUXCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Action
Correct the value for the TUXCONFIG environment variable to be an absolute pathname.
See Also
dmconfig(5)
1972
ERROR: Error in reading TUXCONFIG file
Description
While executing dmloadcf, the TUXCONFIG configuration file cannot be read to validate information in the DMCONFIG file.
Action
Check for the existence of the TUXCONFIG file. If the file exists, make sure that the file and the directory can be accessed. If it does not exist, generate the TUXCONFIG file before running dmloadcf.
See Also
dmconfig(5)
1973
ERROR: Failed to crypt password
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1974
ERROR: Cannot create encryption schedule
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc.
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.
See Also
dmconfig(5)
1975
ERROR: Failed to crypt password
Description
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
1976
ERROR: Cannot access $TUXCONFIG to validate BLOCKTIME in LDOM
Description
While executing dmloadcf, 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)
1981
ERROR: NWDEVICE file string must be an absolute pathname
Description
The value of NWDEVICE in DM_TDOMAIN section of the DMCONFIG file must be an absolute pathname. Relative paths and environment variables are not allowed.
Action
Correct the value for the NWDEVICE to be an absolute pathname.
See Also
dmconfig(5)
1982
ERROR: NWDEVICE must be an absolute pathname
Description
The value of NWDEVICE in DM_OSITP section of the DMCONFIG file must be an absolute pathname. Relative paths and environment variables are not allowed.
Action
Correct the value for the NWDEVICE to be an absolute pathname.
See Also
dmconfig(5)
1984
ERROR: If APT is an Object Identifier, then AEQ must be an integer
Description
If APT in DM_OSITP section of the DMCONFIG file is an object identifier, then AEQ for that entry must be an integer value.
Action
Specify a valid value for AEQ and re-load the configuration.
See Also
dmconfig(5)
1985
ERROR: If APT is an Object Identifier, then AEQ must be an integer
Description
If APT in DM_OSITP section of the DMCONFIG file is an object identifier, then AEQ for that entry must be an integer value.
Action
Specify a valid value for AEQ and re-load the configuration.
See Also
dmconfig(5)
1995
ERROR: If standard input is not a terminal, APP_PW environment variable must be set to application password
Description
When doing dmloadcf, if SECURITY is set to APP_PW in RESOURCES section of UBBCONFIG file, then the administrator should enter the password before the BDMCONFIG file is over-written or created. This message indicates that if the standard input is not a terminal, then APP_PW environment variable should be set to the application password before running dmloadcf.
Action
Correct the error and re-execute the batch command.
See Also
dmconfig(5)
1997
ERROR: Error obtaining Application Password
Description
If an application password is required, dmloadcf either prompts for it (if the invoker is attached to a terminal), or it reads from the environment variable, APP_PW, if standard input is not a terminal. This message is issued when the password cannot be obtained. The most common cause for this is that APP_PW is not set and standard input is not a terminal.
Action
If dmloadcf is not attached to a terminal when invoked, then check that the environment variable, APP_PW, is set correctly.
See Also
dmconfig(5)
1998
ERROR: Cannot read encryption key
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 attempted to read the key used for 2-way encryption from the protected file, $APPDIR/.adm/.keydb. This message is issued when an error is encountered reading this key from the key database file.
Action
If APPDIR has been changed or $APPDIR/.adm/.keydb has been removed, re-load the TUXCONFIG file using tmloadcf which will create $APPDIR/.adm/.keydb. Then, run dmloadcf to create the BDMCONFIG file.
See Also
dmconfig(5)
1999
ERROR: Cannot create encryption schedule
Description
An unexpected error occurred while trying to encrypt the application security password.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
 |
 |
 |