CMDGW Messages 3700-3799
|
|
3700
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)
3701
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 r
eboot it to clear any corrupted memory that may be present. Consider running the application temporarily with SYST
EM_ACCESS set to PROTECTED|NO_OVERRIDE in the RESOURCES section of the TUXCONFIG<
/code> file. This setting will slow performance, but will prevent the possibility of application corruption of shared me
mory. If the problem still persists when running with SYSTEM_ACCESS set to PROTECTED|NO_OVERRIDE, contact your BEA TUXEDO system Technical Support.
3702
ERROR: TCPKEEPALIVE value must be YES, NO, or LOCAL for remote TDOMAIN<name>
Description
The value specified for the TCPKEEPALIVE parameter for remote name in the DM_TDOMAIN section of the DMCONFIG file is invalid. YES, NO, and LOCAL are the acceptable TCPKEEPALIVE parameter values recognized by the GWTDOMAIN Domain Gateway.
Action
Specified a valid value and reload the configuration file.
See Also
dmconfig(5)
3703
ERROR: Unknown CONNECTION_POLICY <type>. Only ON_DEMAND, ON_STARTUP, INCOMING_ONLY, LOCAL are recognized values for remote TDOMAIN
Description
The value type specified for the CONNECTION_POLICY parameter for remote TDOMAIN is not valid. ON_DEMAND, ON_STARTUP, INCOMING_ONLY, and LOCAL are the acceptable CONNECTION_POLICY parameter values recognized by the remote GWTDOMAIN Domain Gateway.
Action
Specified a valid value and reload the configuration file.
See Also
dmconfig(5)
3704
ERROR: Unknown CONNECTION_POLICY <type>. Only ON_DEMAND, ON_STARTUP, INCOMING_ONLY are recognized values for local TDOMAIN
Description
The value type specified for the CONNECTION_POLICY parameter for local TDOMAIN is not valid. ON_DEMAND, ON_STARTUP, and INCOMING_ONLY are the acceptable CONNECTION_POLICY parameter values recognized by the local GWTDOMAIN Domain Gateway.
Action
Specified a valid value and reload the configuration file.
See Also
dmconfig(5)
3706
ERROR: RETRY_INTERVAL only allowed with CONNECTION_POLICY of ON_STARTUP
Description
The RETRY_INTERVAL parameter is not valid if the CONNECTION_POLICY is either ON_DEMAND, or INCOMING_ONLY.
Action
Remove the RETRY_INTERVAL or change the CONNECTION_POLICY to ON_STARTUP.
See Also
dmconfig(5)
3708
ERROR: MAXRETRY only allowed with CONNECTION_POLICY of ON_STARTUP
Description
The MAXRETRY parameter is not valid if the CONNECTION_POLICY is either ON_DEMAND, INCOMING_ONLY.
Action
Remove the MAXRETRY or change the CONNECTION_POLICY to ON_STARTUP.
See Also
dmconfig(5)
3712
ERROR: TCPKEEPALIVE value must be YES, or NO for local TDOMAIN<name>
Description
The specified value for TCPKEEPALIVE parameter is not valid for local TDOMAIN gateway. YES, or NO are the values accepted by local TDOMAIN gateway.
Action
Specified a valid value and reload the configuration file.
See Also
dmconfig(5)
3713
ERROR: Invalid license detected while processing name section of BDMCONFIG
Description
The Tuxedo license file is not valid, or it does not allow to do compression.
Action
Contact BEA Customer Support and get the valid Tuxedo license.
See Also
dmconfig(5)
3714
ERROR: name value must be >= lrange and <= hrange. (IC = code)
Description
The specified value for parameter name must be greater than or equal to lrange and less than or equal to hrange. The internal error code for identifying location of error is code.
Action
Correct the configuration with valid value, and reload the configuration file.
See Also
dmconfig(5)
3715
ERROR: Internal error while processing name section of BDMCONFIG
Description
Encountered operating system error while processing name section of BDMCONFIG.
Action
Contact BEA Customer Support.
See Also
dmconfig(5)
3716
ERROR: Valid values for name are <vals>.
Description
Incorrect value were specified while doing DM MIB update for the attribute name
. The correct choices are <vals$gt.Action
Give correct value for the attribute name for you DM MIB requests.
See Also
DM_MIB(5)
3717
ERROR: Invalid connection policy type for local domain name
Description
Incorrect connection policy type were specified for local domain name while doing dynamic update.
Action
Correct the value for connection policy and redo the dynamic update.
See Also
DM_MIB(5)
3718
ERROR: DM_RDOMAINS: TA_NEW: TA_RDOM is required
Description
The TA_RDOM attribute is required for TA_NEW operation for remote domain.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3719
ERROR: DM_RDOMAINS: TA_NEW: TA_TYPE is required
Description
The TA_TYPE attribute is required for TA_NEW operation for remote domain.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3720
ERROR: DM_RDOMAINS: TA_NEW: TA_DOMAINID is required
Description
The TA_DOMAINID attribute is required for TA_NEW operation for remote domain.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3721
ERROR: DM_RDOMAINS: TA_UPDATE: TA_RDOM is required
Description
The TA_RDOM attribute is required for TA_UPDATE operation for remote domain.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3722
ERROR: DM_TDOMAINS: TA_NEW: TA_TDOM is required
Description
The TA_TDOM attribute is required for TA_NEW operation for TDOMAIN type gateway.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3723
ERROR: DM_TDOMAINS: TA_NEW: TA_NWADDR is required
Description
The TA_NWADDR attribute is required for TA_NEW operation for TDOMAIN type gateway.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3724
ERROR: DM_TDOMAINS: TA_UPDATE: TA_TDOM is required
Description
The TA_TDOM attribute is required for TA_UPDATE operation for TDOMAIN type gateway.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3725
ERROR: DM_TDOMAINS: TA_UPDATE: TA_NWADDR is required
Description
The TA_NWADDR attribute is required for TA_UPDATE operation for TDOMAIN type gateway.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3726
ERROR: Can't find TDOM name entry
Description
Trying to dynamically update a none exist TDOMAIN type gateway.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3727
ERROR: DM_TDOMAINS: TA_UPDATE: TA_NWADDR does not match
Description
The targeted TDOMAIN gateway has a different NWADDR value than the TA_NWADDR specified in the dynamic update.
Action
Correct the error and redo the dynamic update.
See Also
DM_MIB(5)
3728
ERROR: Local Domain can not have -1 in DMKEEPALIVE field
Description
The value -1 is for remote TDOMAIN for indicating using whatever value specified for the local TDOMAIN when local TDOMAIN establishes a session with that remote TDOMAIN.
Action
Correct the DMKEEPALIVE value and reload the configureation file.
See Also
dmconfig(5)
3729
ERROR: Local Domain can not have -1 in ABORT_THRESHOLD field
Description
The value -1 is for remote TDOMAIN for indicating using whatever value specified for the local TDOMAIN when local TDOMAIN establishes a session with that remote TDOMAIN.
Action
Correct the DMKEEPALIVE value and reload the configureation file.
See Also
dmconfig(5)
3730
ERROR: Duplicated remote name (rname) occurs in *DM_EXPORT section
Description
The domain configuration file contains local services that has same remote name.
Action
Correct the domain configuration for local service in the DM_EXPORT section.
See Also
dmconfig(5)
3731
ERROR: _dmcf_open failed: Can't open DM_REMOTE_DOMAINS 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_REMOTE_DOMAINS 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)
3732
WARN: Unsupported DMADM CLOPT ignored!
Description
The DMADM in the SERVERS section of the UBBCONFIG is specified with an invalid CLOPT option.
Action
Check the CLOPT option value in the UBBCONFIG of DMADM and correct.
See Also
dmconfig(5)
3733
Invalid time format or value
Description
The dmadmin passwd command detected an error in either starting time or ending time. The time format must be yyyy/mm/dd:hh:mm and the ending time and starting time must have correct value. For instance, the month 13 is invalid.
Action
Reenter the command with correct value using the specified format for both ending time and starting time.
See Also
dmadmin(1)
3734
End time earlier than start time
Description
The dmadmin command passwd detected that the specified password pair expiration time, i.e. the end time, is earlier than the time when the password pair become effective.
Action
Reenter the command with correct value using the specified format for both ending time and starting time.
See Also
dmadmin(1)
3735
Current time later than end time
Description
The dmadmin passwd command detected that the specified password pair expiration time, i.e. the end time, is earlier than the current time.
Action
Reenter the command with correct value using the specified format for both ending time and starting time.
See Also
dmadmin(1)
3736
ERROR: Cannot create encryption key.
Description
The dmadmin failed to create encryption key for encrypting the password pair information.
Action
Check the health of DMADM server, and check whether the dmadmin and DMADM are from the same release and patch level. If this problem persists, please contact your BEA Customer Support.
See Also
dmadmin(1)
3737
ERROR: _dmcf_open failed: Can't open DM_RESOURCES section
Description
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section in the BDMCONFIG file (such as DM_RESOURCES) is stored as a separate table in the BDMCONFIG file. While trying to update password pair information in the BDMCONFIG file, DMADM encountered an error trying to open the DM_RESOURCES section.
Action
Check the BDMCONFIG environment variable value. If this value is correct, then the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
See Also
DMADM(1)
3738
ERROR: _dmcf_seek failed: Can't seek to DM_RESOURCES section
Description
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section in the BDMCONFIG file (such as DM_RESOURCES) is stored as a separate table in the BDMCONFIG file. While trying to update password pair information in the BDMCONFIG file, DMADM encountered an error trying to read the DM_RESOURCES section.
Action
Check the BDMCONFIG environment variable value. If this value is correct, then the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
See Also
DMADM(1)
3739
ERROR: _dmcf_open failed: Can't open DM_RESOURCES section
Description
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section in the BDMCONFIG file (such as DM_RESOURCES) is stored as a separate table in the BDMCONFIG file. While trying to re-encrypt password pair information in the BDMCONFIG file, DMADM encountered an error trying to open the DM_RESOURCES section.
Action
Check the BDMCONFIG environment variable value. If this value is correct, then the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
See Also
DMADM(1)
3740
ERROR: _dmcf_seek failed: Can't seek to DM_RESOURCES section
Description
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section in the BDMCONFIG file (such as DM_RESOURCES) is stored as a separate table in the BDMCONFIG file. While trying to re-encrypt password pair information in the BDMCONFIG file, DMADM encountered an error trying to read the DM_RESOURCES section.
Action
Check the BDMCONFIG environment variable value. If this value is correct, then the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
See Also
DMADM(1)
3741
ERROR: Cannot create encryption key
Description
The DMADM failed to create the new encryption key during the re-encryption operation.
Action
Shutdown DMADM server and reboot. Try the re-encrypt operation again. If the problem persists, contact your BEA Customer Support.
See Also
DMADM(1)
3742
ERROR: _dmcf_open failed: Can't open DM_PASSWORDS section
Description
The DMADM failed to open DM_PASSWORDS section during password pair re-encryption operation.
Action
Shutdown DMADM server and reboot.Try the re-encrypt operation again. If the problem persists, contact your BEA Customer Support.
See Also
DMADM(1)
3743
ERROR: _dmcf_write failed: Can't write entry in DM_PASSWORDS section
Description
The DMADM server encountered an error while writing the reencrypted password pair into the BDMCONFIG file.
Action
Check the BDMCONFIG environment variable value. If this value is correct,try shutting down DMADM server and reboot. Try the re-encrypt operation again. If this fails, try deleting the BDMCONFIG and regenerate it if possible. If the problem persists, contact your BEA Customer Support.
See Also
BDMCONFIG(5)
3744
ERROR: _dmcf_open failed: Can't open DM_TOPEND section
Description
The DMADM failed to open DM_TOPEND section during password pair re-encryption operation.
Action
Shutdown DMADM server and reboot. Try the re-encrypt operation again. If the problem persists, contact your BEA Customer Support.
See Also
DMADM(1)
3745
ERROR: _dmcf_write failed: Can't write entry in DM_TOPEND section
Description
The DMADM server encountered an error while writing the reencrypted password into the BDMCONFIG file.
Action
Check the BDMCONFIG environment variable value. If this value is correct, try to shutdown DMADM server and reboot. Try the reencrypt operation again. If this fails, try deleting the BDMCONFIG and regenerate it if possible. If the problem persists, contact your BEA Customer Support.
See Also
BDMCONFIG(5)
3746
ERROR: _dmcf_write failed: Can't write new DMKEY in DM_RESOURCES section
Description
The DMADM server encountered an error while writing DMKEY to the DM_RESOURCE section.
Action
Contact your BEA Customer Support.
See Also
DMADM(1)
3747
ERROR: field_name: Crypto operation failure at the named field.
Description
The Cryptographic operation failed at the named field, field_name. This includes encryption and decryption.
Action
Contact your BEA Customer Support.
See Also
DMADM(1)
3748
ERROR: Domain Gateway type does not match (ldom_name, ldom_type) vs (rdom_name, rdom_type).
Description
The configured local access point ldom_name and remote access point rdom_name are not of the same type. The requested adding new password pair operation failed.
Action
Check the type value for the local and remote access points to make sure they are correct. Redo the adding password operation for the local and remote access point only when both are of the same type.
See Also
DMIB(5)
3749
ERROR: Cannot create encryption key.
Description
The "dmadmin -c" for dynamic configuration failed to encrypt the password pair information.
Action
Contact your BEA Customer Support.
See Also
dmadmin(1)
3750
ERROR: Failed to encrypt password.
Description
The dmadmin in configuration mode failed to encrypt password pair before updating to the DMIB server.
Action
Contact your BEA Customer Support.
See Also
dmadmin(5)
3751
ERROR: Failed to encrypt password.
Description
The dmadmin failed to encrypt password pair before updating to the DMIB server.
Action
Contact your BEA Customer Support.
See Also
dmadmin(5)
3752
ERROR: PASSWORD entry for <ldom_name, rdom_name> already exists.
Description
The GWADM server failed to add new password pair because it already exists for local access point ldom_name and remote access point rdom_name.
Action
Use the update operation, or delete the old password pair and then add new password pair.
See Also
DMIB(5)
3753
ERROR: PASSWORD entry for <ldom_name, rdom_name> not found.
Description
The GWADM server failed the delete password pair operation for local access point ldom_name and remote access point rdom_name because password entry does not exist.
Action
Correct the ldom_name and rdom_name.
See Also
DMIB(5)
3754
ERROR: PASSWORD entry for <ldom_name, rdom_name> not found.
Description
The GWADM server failed the update password pair operation for local access point ldom_name and remote access point rdom_name because password entry does not exist.
Action
Correct the ldom_name and rdom_name.
See Also
DMIB(5)
3755
ERROR: PASSWORD entry for <ldom_name, rdom_name> does not have password pair <pair_number> defined.
Description
The GWADM server failed the update password pair operation for local access point ldom_name and remote access point rdom_name because the requested password pair pair_number does not exist.
Action
Correct the pair_number.
See Also
DMIB(5)
3756
ERROR: Domain Gateway type does not match (ldom_name, ldom_type) vs (rdom_name, rdom_type).
Description
The configured local access point ldom_name and remote access point rdom_name are not the same type. The requested adding new password pair operation is rejected by the DMIB server.
Action
Check the local and remote access point type values for errors. Redo your add password operation for local and remote access points only when both are of the same type.
See Also
DMIB(5)
3757
INFO: Triple-DES is enabled for DMADM.
Description
The Triple-DES enscription is enabled for /Domain password pair.
Action
Informational, no action required.
See Also
DMADM(1)
3758
ERROR: Invalid option argument cmd_line_arg.
Description
Unsupported CLOPT option specified in DMADM cmd_line_arg in the
Action
Remove the unsupported command line option from CLOPT attribute in the UBBCONFIG for DMADM.
See Also
DMADM(1)
3759
WARN: Admin password is required to show /Domain password pairs, however an incorrect password is specified.
Description
The BDMCONFIG file is created with password protection for the stored password pairs information. An incorrect password has been entered so dmunloadcf will not display the password pair information.
Action
Use the correct password when invoking the dmunloadcf utility in order to see the password information stored in BDMCONFIG.
See Also
dmunloadcf(1)
3760
WARN: Admin password is required to show /Domain password pairs.
Description
The BDMCONFIG file is created with password protection for the stored password pairs information. The user requested to dump the password pair information out without specifying the password.
Action
Give the password when invoking dmunloadcf utility.
See Also
dmunloadcf(1)
3761
INFO: Using version 2 BDMCONFIG, 3DES is enabled.
Description
The BDMCONFIG file is created with version 2 BDMCONFIG format. Version 2 BDMCONFIG formatting supports obfuscated DM Key, and by default it uses Triple-DES to encrypt password pairs.
Action
This is informational, no action required.
See Also
dmunloadcf(1)
3763
ERROR: LACCESSPOINT=<string> the regular expression does not mach any local domain names
Description
The value of LACCESSPOINT in the DM_TDOMAIN section is a regular expression, but it doesn't match any local domain name.
Action
Specify a regular expression with at least one matching local domain and re-load the configuration.
See Also
dmconfig(5)
3765
ERROR: LACCESSPOINT=<string> is not a valid regular expression
Description
The value of LACCESSPOINT in DM_TDOMAIN section is not a valid regular expression.
Action
Specify a valid regular expression and re-load the configuration.
See Also
dmconfig(5)
3766
INFO: .SysConnectionConfig: Configuration change for connection between LDOM and RDOM
Description
This event message is generated when the configuration between a local domain and a remote domain of TDomain session has been changed dynamically. The names of local domain and remote domain are printed.
Action
No action required. The configuration is changed and an event is generated.
See Also
dmconfig(5), DM_MIB(5)
3767
WARN: Entry domain_name was not defined in domain_type section.
Description
This event message is generated when local or remote domain is not in the related domain type section.
Action
No action required. The configuration is changed and an event is generated.
See Also
dmconfig(5)
3768
ERROR: MAC is MANDATORY but neither LLE nor SECURITY is supported for remote TDOMAIN <domain_name>
Description
If MAC is set to MANDATORY in local domain, but LLE or domain SECURITY is not supported for the connection between local domain and remote domain in a local configuration, the configuration is invalid.
Action
Adjust the configuration to eliminate the conflict.
3769
ERROR: Invalid argument
Description
GWTDOMAIN CLOPT option(s) configured incorrectly.
Action
Check the GWTDOMAIN CLOPT options to ensure they are configured correctly.
 |
 |
 |