CMDTUX Messages 7000-7099
|
|
7000
ERROR: Minimum encryption (strength is larger than 56, but only the 56-bit SSL package is installed
Description
The configured minimum encryption strength is greater than 56 bits, but the installed TUXEDO system is licensed to do at maximum 56 bits encryption.
Action
Change the configuration to the allowable encryption strength value, or contact BEA Customer Support for purchasing the TUXEDO SSL license.
7001
WARN: SSL encryption is configured for this configuration, but the SSL package is not installed
Description
The BRIDGE configuration requires SSL but the installed TUXEDO is not licensed to use SSL.
Action
Change configuration to use LLE if it is license, or contact BEA Customer Support to purchase the TUXEDO SSL license.
7002
WARN: Minimum encryption (strength) is larger than 56, but only the 56-bit SSL package is installed
Description
The configured minimum encryption strength) is greater than 56 bits, but the installed TUXEDO system is licensed to do at most 56 bits encryption.
Action
Change the configuration to the allowalbe encryption strngth value, or contact BEA Customer Support for purchasing the TUXEDO SSL license.
7003
ERROR: NO SSL encryption package installed, but this configuration speifies SSL
Description
The 'tlisten' process is configured with SSL but the installed TUXEDO System is not licensed to use SSL.
Action
Modified your configuration, or call BEA Customer Support for purchasing TUXEDO SSL license.
7004
ERROR: 56-bit SSL package installed. num bits minimum encryption is configured
Description
A 56-bit TUXEDO SSL package is installed, bu the configured minimum SSL encryption strength requrement is greater than 56 bits.
Action
Modify configuration, or call BEA Customer Support.
7005
ERROR: -s is specified, but the SSL package is not installed
Description
The SSL secure port option is specified for tlisten process but the installed TUXEDO System does not have SSL package.
Action
Change command line option, or contact BEA Customer Support for purchasing TUXEDO SSL package.
7006
ERROR: -z (number-of-bits) is larger than 56, but only 56-bit SSL package is installed
Description
The SSL minimum encryption strength option is specified with value 'number-of-bits' for tlisten process but the installed TUXEDO SSL package only support maximum 56 bit encryption strength.
Action
Change command line option, or contact BEA Customer Support for purchasing TUXEDO SSL package.
7007
ERROR: Cannot initialize SSL subsystem
Description
The tlisten or slisten process failed while during SSL subsystem initialization.
Action
Look for prior error message in the ULOG to find the true nature of the failure. The most common problems are due to the incorrect PKI configuration. Check your SSL configuration especially the certificate and private key to see whether they match the PKI plug-in configuration. You may also need to check whether your LDAP filter rules.
7008
ERROR: Connection closed by peer
Description
BRIDGE SSL network connection is closed by its peer.
Action
Check ULOG of its peer for reason of closing the network connection.
7009
ERROR: Connection closed by peer
Description
BRIDGE SSL network connection is closed by its peer.
Action
Check ULOG of its peer for reason of closing the network connection.
7010
ERROR: Connection closed by peer
Description
BRIDGE SSL network connection is closed by its peer gracefully.
Action
Check ULOG of its peer for reason of closing the network connection.
7011
ERROR: Memory allocation failure for nbytes bytes
Description
An attempt by BRIDGE to allocate memory dynamically for nbytes bytes failed while receiving network message.
Action
Make sure the operation 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device.
7012
ERROR: Missing security principal name in registry
Description
The slisten is configured to use SSL but the required security principal name is not found in Windows registry.
Action
Run 'TUXEDO Administration' from control panel and correct Windows registrys information. Or reinstall TUXEDO and configure it correctly.
7013
ERROR: Missing security principal location in registry
Description
The slisten is configured to use SSL but the required security principal private key location is not found in Windows registry.
Action
Run 'TUXEDO Administration' from control panel and correct Windows registrys information. Or reinstall TUXEDO and configure it correctly.
7014
ERROR: Missing security principal password in registry
Description
The slisten is configured to use SSL but the required security principal password for private key is not found in Windows registry. This password is in encrypted and represented in BASE64 format.
Action
Run 'convertp2e.exe password' from command line, copy the output. Then run 'TUXEDO Administration' from control panel and paste the data. Or reinstall TUXEDO and configure the private key password.
7015
INFO: Missing maximum encryption strength in registry, use default 128-bit!
Description
The maximum encryption strength for 'slisten' process is not configured in the Windows registry. Use 128 bits as maximum encryption strength.
Action
No action required; however, if 128-bits is not desired then either use 'TUXEDO Administrator' to modify registry or reinstall TUXEDO and configure it correctly.
7016
ERROR: Invalid maximum encryption strength(n) in registry!
Description
The maximum encryption strength is incorrectly configured in the Windows registry with a value of 'n'.
Action
Correct the configured value either through reinstall TUXEDO or modify the registry using 'TUXEDO Administrator'.
7017
INFO: Missing minimum encryption strength in registry, use default 0-bit!
Description
The minimum encryption strength for 'slisten' process is not configured in the Windows registry. Use 0 bits as minimum encryption strength.
Action
No action required; however, if 0-bits is not desired then either use 'TUXEDO Administrator' to modify registry or reinstall TUXEDO and configure it correctly.
7018
ERROR: Invalid minimum encryption strength(n) in registry!
Description
The minimum encryption strength is incorrectly configured in the Windows registry with a value of 'n'.
Action
Correct the configured value either through reinstall TUXEDO or modify the registry using 'TUXEDO Administrator'.
7019
ERROR: Minimum encryption strength(min) greater than maximum encryption strength(max)!
Description
The configured minimum encryption strength 'min' is greater than maximum encryption value 'max'.
Action
Correct the configured value either through reinstall TUXEDO or modify the registry using 'TUXEDO Administrator'.
7020
ERROR: Could not encrypt principal password, errno=ecode
Description
The encryption of user private key password failed with error return code 'ecode'.
Action
Contact BEA Customer Support.
7021
ERROR: Could not initialize encryption of principal password, errno=ecode
Description
Failed to initialize the encyrption process for user private key password.
Action
Check ULOG for actual cause of the failure and contact BEA Customer Support.
7022
ERROR: TSAM Manager reported error: error message
Description
TSAM Manager reported error message to the request from LMS.
Action
Check ULOG for actual cause of the failure and contact BEA Customer Support
7023
"\nWARN: MAXSPDATA parameter should be >= %d and <= 2147483640\n"
Description
The MAXSPDATA is out of range. TUXCONFIG is still generated using MAXSPDATA = 0. The default value is used when TUXCONFIG is reading memory at boot time.
Action
If MAXSPDATA related features are not used (for example, TSAM), ignore this message. Otherwise, set the MAXSPDATA with the indication.
7024
"\nWARN: According to the specified MAXQUEUES (or MAXSERVERS, if MAXQUEUES not set), the MAXSPDATA parameter should be >= %d and <= 2147483640\n"
Description
MAXSPDATA is out of range. This range is decided by MAXQUEUES (or MAXSERVERS, if MAXQUEUES not set). TUXCONFIG is still generated using MAXSPDATA = 0. The default value is used when TUXCONFIG is reading memory at boot time.
Action
If MAXSPDATA related features are not used (for example, TSAM), ignore this message. Otherwise, set the MAXSPDATA with the indication.
7025
ERROR: tms_abort xa_rollback returned error for group groupname
Description
BEA TUXEDO was rolling back a transaction. The resource manager returned an error when xa_rollback was called. The XA return code was not XA_OK, XA_HEURRB, or XAER_NOTA.
Action
Check the error reporting mechanism for the associated resource manager.
7026
ERROR: tms_habort xa_rollback returned error for group groupname
Description
BEA TUXEDO was heuristically rolling back a transaction. The xa_rollback() function returned an error that was not one of the expected values.
Action
Check the error reporting mechanism for the associated resource manager.
7027
ERROR: tms_timeout xa_rollback returned error for group groupname
Description
BEA TUXEDO was processing a timeout request for a transaction. The resource manager returned an error from xa_rollback.
Action
Check the error reporting mechanism for the associated resource manager.
7028
ERROR: Only one LMS instance is allowed on one machine
Description
Only one LMS instance is allowed on one machine.
Action
Make sure only deploy one LMS on one machine in a Tuxedo domain.
7029
ERROR: TSAM Manager rejected message: request message
Description
TSAM Manager refused to accept a request message from LMS.
Action
Check ULOG for actual cause of the failure and contact BEA Customer Support
7031
ERROR: TUXCONFIG environment variable not set
Description
While executing tpkill, 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
tpkill(1)
7032
ERROR: Unable to read RESOURCES section of TUXCONFIG file
Description
tpkill was unable to get information on the RESOURCES section from the TUXCONFIG file. Additional information from the userlog might indicate why the system was unable to do so. For example, the TUXCONFIG environment variable may not have been set.
Action
Please examine the userlog for further information. If necessary, please contact your BEA TUXEDO System Administrator.
7033
ERROR: Execute permission denied, not application administrator
Description
tpkill must be run by the TUXEDO system administrator, as defined in the RESOURCES section of the TUXCONFIG file.
Action
Re-run the command as the proper user.
7034
ERROR: Unable to initialize public key subsystem
Description
tpkill was unable to initialize its public key subsystem. There may be a problem with the registry, or with the configured plug-in.
Action
Ensure the registry is in a consistent state with the epifregedt command. If you believe the registry is in a consistent state, please contact BEA Customer Support.
See Also
epifregedt(1)
7035
ERROR: Cannot become a client - tperrno tperrno_value errno errno_value Uunixerr Uunixerr_value
Description
The administrative client tpkill could not join the application. tperrno_value provides further information about the cause of the problem. If tperrno_value is TPEOS (7), then errno_value contains the operating system error number and Uunixerr_value contains a code representing the failed system call.
Action
There may be more than one instance of tpkill running at the same time. Ensure that at most one instance of tpkill is running at any one time.
7036
ERROR: memory allocation failure
Description
tpkill memory allocation failed.
Action
Memory resources may be depleted. Use system administrative tools to free memory before tpkill is run.
7039
ERROR: Can not lock the bulletin board
Description
A bulletin board lock could not be obtained when tpkill attempt to kill a Tuxedo process.
Action
Try again after a few seconds, giving the bulletin board lock recovery algorithm time to run. If this error continues, contact your BEA TUXEDO system Technical Support.
7042
ERROR: NADDR parameter does not support wildcard([::]) in MP mode when IPv6 enabled.
Description
In UBB configuration file, configure NADDR parameter as wildcard([::]) is not allowed.
Action
Change NADDR to specific IP address and try again.
7043
ERROR: NLSADDR parameter does not support wildcard([::]) in MP mode when IPv6 enabled.
Description
In UBB configuration file, configure NLSADDR parameter as wildcard([::]) is not allowed.
Action
Change NLSADDR to specific IP address or hostname and try again.
7044
ERROR: tlisten does not support wildcard([::]).
Description
When booting tlisten with -l //[::], tlisten configured to bind on wildcard([::]) IP address is not allowed.
Action
Configure tlisten with -l on specific IP address or hostname and try again .
7045
ERROR: Cannot boot, error reading *ROUTING section
Description
During the tmboot process, the ROUTING section of the configuration file could not be read.
Action
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf), or TUXCONFIG was propagated to all machines in the configuration.
See Also
tmboot(1), tmunloadcf(1)
7046
ERROR: Cannot boot old release site (site_name) when CLOPT is greater than 256
Description
For pre-Tuxedo 10gR3 releases, the CLOPT is limited to 256. When Tuxedo is running in a mixed releases MP mode environment on any slave node that runs a release earlier than Tuxedo 10gR3, then CLOPT is limited to 256 for the entire Tuxedo Application domain.
Action
Either upgrade the older release node to Tuxedo 10gR3 and above, or change the CLOPT to value smaller than or equal to 256.
7047
ERROR: Cannot boot old release site (site_name) when ROUTING section FIELD is greater than 30
Description
For pre-Tuxedo 10gR3 releases, the FIELD of ROUTING section is limited to 30. When Tuxedo is running in a mixed releases MP mode environment on any slave node that runs a release earlier than Tuxedo 10gR3, then FIELD of ROUTING section is limited to 30 for the entire Tuxedo Application domain.
Action
Either upgrade the older release node to Tuxedo 10gR3 and above, or change the FIELD of ROUTING section to value smaller than or equal to 30.
7048
ERROR: Cannot boot, error reading *SERVICES section
Description
During the tmboot process, the SERVICES section of the configuration file could not be read.
Action
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf), or TUXCONFIG was propagated to all machines in the configuration.
See Also
tmboot(1), tmunloadcf(1)
7049
ERROR: Cannot boot older Oracle Tuxedo release site (site_name) when SERVICES section service name is greater than 15
Description
For Oracle Tuxedo release older than 11gR1, the UBBCONFIG SERVICES section service name is limited to 15. From Oracle TUXEDO 11gR1 and later the service name length is increased to 127. When Oracle Tuxedo is running in a mixed-release-MP-mode environment on slave nodes that run a release earlier than 11gR1, then service names in the UBBCONFIG SERVICES section is limited to 15 for the entire Oracle Tuxedo Application domain.
Action
Upgrade the older release node to Oracle Tuxedo 11gR1 and above, or change the UBBCONFIG SERVICES section service name to value smaller than or equal to 15.
7050
ERROR: Cannot boot old release site (site_name) when RESOURCE section AUTHSVC name is greater than 15.
Description
For Oracle Tuxedo release older than 11gR1, the service name length for AUTHSVC in the UBBCONFIG RESOURCES section is limited to 15. From Oracle TUXEDO 11gR1 and above, the service name length is increased to 127. When Oracle Tuxedo is running in a mixed-release MP-mode environment on slave nodes that run a release earlier than 11gR1, then AUTHSVC is limited to 15 for the entire Oracle Tuxedo Application domain.
Action
Either upgrade the older release node to Oracle Tuxedo 11gR1 and above, or change AUTHSVC in the RESOURCES section to a value smaller than or equal to 15.
See Also
tmboot(1), UBBCONFIG(5)
7052
ERROR: SESSIONROLE parameter must be BEGIN, END or NONE
Description
UBBCONFIG services section SESSIONROLE parameter must be set to BEGIN, END or NONE
Action
Set UBBCONFIG services section SESSIONROLE parameter to BEGIN, END or NONE
See Also
UBBCONFIG(5)
7054
ERROR: AFFINITYSCOPE parameter must be MACHINE, GROUP or SERVER
Description
UBBCONFIG services section AFFINITYSCOPE parameter must be set to MACHINE, GROUP or SERVER
Action
Set UBBCONFIG services section AFFINITYSCOPE parameter to MACHINE, GROUP or SERVER
See Also
UBBCONFIG(5)
7056
ERROR: AFFINITYSTRICT parameter must be MANDATORY or PRECEDENT
Description
UBBCONFIG services section AFFINITYSTRICT parameter must be set to MANDATORY or PRECEDENT
Action
Set UBBCONFIG services section AFFINITYSTRICT parameter to MANDATORY or PRECEDENT
See Also
UBBCONFIG(5)
7057
ERROR: Cannot advertise services with long names when an older Oracle Tuxedo release joins an application
Description
For Oracle Tuxedo release older than 11gR1, the service name is limited to 15. From TUXEDO 11gR1 and above, the service name has increased to 127. When Tuxedo is running in a mixed-release MP mode environment on slave nodes that run a release earlier than 11gR1, the service name is limited to 15 for the entire Oracle Tuxedo Application domain.
Action
Either upgrade the older release node to Oracle Tuxedo 11gR1 and above, or change the service name to value smaller than or equal to 15.
7061
ERROR: Duplicate *RMS section
Description
More than one RMS section has been specified in the configuration file.
Action
Modify the configuration file so that only one RMS section is specified.
See Also
ubbconfig(5)
7062
ERROR: *GROUPS section must appear before *RMS section
Description
The RMS section has been defined before the GROUPS section in the configuration file.
Action
Edit the configuration file such that the RESOURCES, MACHINES, and GROUPS sections are the first three sections in that order.
See Also
ubbconfig(5)
7063
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc failed while setting up a table to keep track of the information kept in the RMS section of the UBBCONFIG file.
Action
Please refer to Message 157 above.
7065
ERROR: RMID parameter must be >= 1 and <= 31
Description
The value for RMID (permissions) as specified in the RMS section of the UBBCONFIG file is less than 1 or greater than 31. RMID must be greater than or equal to 1 and less than or equal to 31.
Action
Correct the value for RMID as specified in theRMS section of the UBBCONFIG file to be greater than or equal to 1 and less than or equal to 31.
See Also
ubbconfig(5)
7067
ERROR: Group name must be <= len characters in length
Description
The SRVGRP value indicated by the arrow is greater than 30 characters in length.
Action
Edit the configuration file such that all SRVGRP values are less than or equal to 30 characters in length.
See Also
ubbconfig(5)
7069
ERROR: Group name grpname not defined in *GROUPS section
Description
The specified server group name grpname has not been defined in the GROUPS section of the configuration file.
Action
Edit the configuration file such that the server group name is defined in the GROUPS section.
See Also
ubbconfig(5)
7071
ERROR: TMSNAME parameter must be <= len characters in length
Description
The value for TMSNAME indicated by the arrow is greater than 256 characters.
Action
Specify a value for TMSNAME that is less than or equal to 256 characters in length.
See Also
ubbconfig(5)
7073
ERROR: TMSNAME cannot be configured if the NO_XA option is set
Description
The identifier for TMSNAME as specified in the RMS section of the UBBCONFIG cannot be set if the OPTIONS in the RESOURCE section has the NO_XA option set.
Action
Correct the incompatible value of the UBBCONFIG file and re-run tmloadcf(1).
See Also
ubbconfig(5) and tmloadcf (1)
7075
ERROR: TMSCOUNT parameter must be > 1 and <= 256
Description
The TMSCOUNT parameter in the RMS section of the configuration file must be within the proper range of values.
Action
Specify a value that is between 2 and 256, inclusive.
See Also
tmloadcf(1), ubbconfig(5)
7077
ERROR: OPENINFO parameter must be <= len characters in length
Description
The value for the OPENINFO string indicated by the arrow is greater than 256 characters in length.
Action
Specify a value for the OPENINFO string that is less than or equal to 256 characters in length.
See Also
ubbconfig(5)
7079
ERROR: OPENINFO cannot be configured if the NO_XA option is set
Description
The identifier for OPENINFO as specified in the RMS section of the UBBCONFIG cannot be set if the OPTIONS in the RESOURCE section has the NO_XA option set.
Action
Correct the incompatible value of the UBBCONFIG file and re-run tmloadcf(1).
See Also
ubbconfig(5) and tmloadcf (1)
7080
ERROR:Non encrypted part of OPENINFO attribute must be <= val characters in length
Description
The non-encrypted part of the OPENINFO value of the RMS section of the configuration file must be <= 200 characters.
Action
Specify a value that is less than or equal to 200 characters.
See Also
tmloadcf(1), ubbconfig(5)
7082
ERROR: CLOSEINFO parameter must be <= len characters in length
Description
The value for the CLOSEINFO string indicated by the arrow is greater than 256 characters.
Action
Specify a value for the CLOSEINFO string that is less than or equal to 256 characters in length.
See Also
ubbconfig(5)
7084
ERROR: CLOSEINFO cannot be configured if the NO_XA option is set
Description
The identifier for CLOSEINFO as specified in the RMS section of the UBBCONFIG can not be set if the OPTIONS in the RESOURCE section has the NO_XA option set.
Action
Correct the incompatible value of the UBBCONFIG file and re-run tmloadcf(1).
See Also
ubbconfig(5) and tmloadcf (1)
7086
ERROR: RMS identifier entry name must be <= number characters in length
Description
The value specified for the RMS identifier entry name in the RMS section of the ubbconfig(5) file is longer than number characters in length.
Action
Shorten the value specified for this attribute and rerun tmloadcf(1).
See Also
TUXEDO Administrator's Guide, tmloadcf(1), <
code>ubbconfig
7088
ERROR: RMS entry name rmsname must not contain *, comma, or colon
Description
A RMS entry name specified starting in the first column of a line in the RMS section of the UBBCONFIG file contained an asterisk, comma, or colon. This is not allowed. It is also possible for this error to occur if the tmloadcf program interprets some other parameter as a group name due to earlier errors in the configuration file.
Action
Verify that the configuration file has the proper syntax. If necessary, choose a new name for the RMS entry name which meets the syntax restrictions.
See Also
ubbconfig(5)
7090
ERROR: Duplicate *RMS entry rmsname
Description
The value for the rmsname indicated by the arrow is invalid due to being specified previously in the RMS section of the configuration file.
Action
Specify a value for rmsname that has not already been specified in the RMS section of the configuration file.
See Also
ubbconfig(5)
7091
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc failed while setting up a table to keep track of the information kept in the RMS section of the UBBCONFIG file.
Action
Please refer to Message 157 above.
7092
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc failed while setting up a table to keep track of the information kept in the RMS section of the UBBCONFIG file.
Action
Please refer to Message 157 above.
7093
ERROR: More than 32766 RMS entries in configuration file
Description
The application was configured to handle up to 32766 configured RMS entries and has excess RMS entries defined in the ubbconfig(5) file.
Action
Decrease the number of RMS entries in the *RMS section of the
tmloadcf(1).
See Also
TUXEDO Administrator's Guide, tmloadcf(1), <
code>ubbconfig
7094
ERROR: SRVGRP parameter missing in *RMS entry AOUT
Description
Each entry in the RMS section of the configuration file must have a SRVGRP parameter.
Action
Specify a SRVGRP value that specifies the group name for the group which the RMS entry belong to.
See Also
ubbconfig(5)
7095
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc failed while setting up a table to keep track of the information kept in the RMS section of the UBBCONFIG file.
Action
Please refer to Message 157 above.
7096
ERROR: RMID parameter missing in *RMS entry
Description
Each entry in the RMS section of the configuration file must have a RMID parameter.
Action
Specify a RMID value that specifies an integer that uniquely identifies a RMS entry within a RMS.
See Also
ubbconfig(5)
7097
ERROR: The parameter RMID of *RMS entry is duplicated for group grpname
Description
The value for the RMID is invalid due to being specified previously in the RMS section of the configuration file.
Action
Verify that the configuration file has the proper syntax. If necessary, choose a new value for the RMID which meets the syntax restrictions.
See Also
ubbconfig(5)
7098
ERROR: The total number of RMS entries for one group cannot be more than number
Description
The total number of RMS entries which belong to the same group cannot be more than number.
Action
Decrease the total number of RMS entries to not more than number.
See Also
ubbconfig(5)
7099
ERROR: The total number of TMSCOUNT for one group must be > 1 and <= 256
Description
The total number of TMSCOUNT parameter in the RMS section for one server group must be within the proper range of values.
Action
Make the total number of TMSCOUNT for one server group between 2 and 256 inclusive.
See Also
tmloadcf(1), ubbconfig(5)
 |
 |
 |