CMDGW Messages 3000-3099
|
|
|
3014
ERROR: Error obtaining Remote User's Password
Description
The Domain Administrative server detected an internal error while trying to obtain a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3015
ERROR: Application security not enabled
Description
The Domain Administrative server detected an error while trying to check a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The SECURITY parameter in the RESOURCES section of the ubbconfig(5) file is set to NONE. In order for this operation to complete the application security must be other than NONE.
Action
Set the SECURITY parameter in the RESOURCES section of the ubbconfig(5) file to a valid value other than NONE and retry the operation.
See Also
ubbconfig(5), dmadmin(1)
3016
ERROR: Adding remote users and passwords must be run from a terminal
Description
The Domain Administrative server detected an error while trying to add a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server detected that it was not being run from a terminal.
Action
Attempt the operation again by running dmadmin(1) from a terminal.
See Also
dmadmin(1)
3017
ERROR: When updating a DM_REMOTE_USER entry, TA_RPRINPASSWD should be set to U
Description
The Domain Administrative server detected an error while trying to update a remote user entry. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server found an invalid value for the TA_RPRINPASSWD tag in the edit buffer. In order to update a remote user entry the value should be set to U.
Action
Retry the operation specifying the value U for TA_RPRINPASSWD.
See Also
dmadmin(1)
3018
ERROR: When adding a DM_REMOTE_USER entry, TA_RPRINPASSWD should be set to Y
Description
The Domain Administrative server detected an error while trying to add a remote user entry. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server found an invalid value for the TA_RPRINPASSWD tag in the edit buffer. In order to add a remote user entry the value should be set to Y.
Action
Retry the operation specifying the value Y for TA_RPRINPASSWD.
See Also
dmadmin(1)
3019
ERROR: When adding a DM_REMOTE_USER entry, TA_RPRINPASSWD should be set to Y
Description
The Domain Administrative server detected an error while trying to add a remote user entry. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server found an invalid value for the TA_RPRINPASSWD tag in the edit buffer. In order to add a remote user entry the value should be set to Y.
Action
Retry the operation specifying the value Y for TA_RPRINPASSWD.
See Also
dmadmin(1)
3023
ERROR: BUFTYPE="buffer type" needs subtype specification
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type requires a subtype specification.
Action
Correct the parameter specification in error and reload the configuration.
See Also
dmconfig(5)
3024
ERROR: BUFTYPE="buffer type" needs subtype specification
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type requires a subtype specification.
Action
Correct the parameter specification in error and reload the configuration.
See Also
dmconfig(5)
3026
ERROR: _dmcf_open failed: Can't open DM_SNADOM 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_SNADOM 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)
3027
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)
3030
ERROR: Size of remote password is too large, maximum is 8
Description
An invalid password value was given (greater than 8 characters in length).
Action
Retry the passwd command.
See Also
dmconfig(5)
3031
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)
3032
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)
3033
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)
3034
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)
3035
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)
3036
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)
3037
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)
3039
ERROR: Error obtaining Remote User's Password
Description
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing either an addusr or modusr command.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3040
ERROR: Unable to obtain the remote password for this remote user
Description
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing an addusr command.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3041
ERROR: Unable to obtain the remote password for this remote user
Description
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing a modusr command.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3043
ERROR: Error obtaining Remote User's Password
Description
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing either an addusr or a modusr command.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3044
ERROR: _dmcf_OLD_open failed: Can't open DM_SNADOM section
Description
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The DM_SNADOM section of the bdmconfig file could not be opened.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3046
ERROR: _dmcf_OLD_open failed: Can't open DM_RDOMSEC section
Description
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The DM_RDOMSEC section of the bdmconfig file could not be opened.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3048
ERROR: Error obtaining Remote User's Password
Description
The Domain Administrative server detected an internal error while trying to obtain a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3050
ERROR: Can't list vtoc
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The VTOC could not be listed. A more specific error message will follow.
Action
Check the surrounding messages for more detailed information. Correct the source of the error and reload the configuration.
See Also
dmconfig(5)
3051
ERROR: VTOC Can't read
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The VTOC could not be read. A more specific error message will follow.
Action
Check the surrounding messages for more detailed information. Correct the source of the error and reload the configuration.
See Also
dmconfig(5)
3052
ERROR: Can't write
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The configuration could not be written. A more specific error message will follow.
Action
Check the surrounding messages for more detailed information. Correct the source of the error and reload the configuration.
See Also
dmconfig(5)
3053
ERROR: Invalid Internet type of address.
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. An invalid internet address was found.
Action
Correct the parameter specification in error and reload the configuration.
See Also
dmconfig(5)
3055
INFO: The password for principal name is set to -1
Description
The Domain Administrative server issues this informational message to indicate that the password for principal principal name has been set to a default value of -1 as a result of an addusr command.
Action
This is an informational message with no associated user action.
See Also
dmadmin(1)
3057
ERROR: _dmcf_OLD_open failed: Can't open DM_OSITPX section
Description
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The DM_OSITP section of the bdmconfig file could not be opened.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3058
ERROR: SNADOM DOMAIN (domain) has more than one address
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The SNA domain domain has more than one address.
Action
Correct the parameter specification in error and reload the configuration.
See Also
dmconfig(5)
3059
ERROR: _dmcf_OLD_open failed: Can't open DM_RDOMUSR section
Description
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The DM_RDOMUSR section of the bdmconfig file could not be opened.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3060
ERROR: _dmcf_OLD_open failed: Can't open DM_OSITP section
Description
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The DM_OSITP section of the bdmconfig file could not be opened.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
dmadmin(1)
3061
ERROR: _dmcf_OLD_open failed: Can't open DM_LOCAL_DOMAINS section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3062
ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_DOMAINS section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3063
ERROR: _dmcf_OLD_open failed: Can't open DM_TDOMAIN section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3064
ERROR: _dmcf_OLD_open failed: Can't open DM_LOCAL_SERVICES section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3065
ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_SERVICES section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3066
ERROR: _dmcf_OLD_open failed: Can't open DM_ACCESS_CONTROL section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3067
ERROR: _dmcf_OLD_open failed: Can't open DM_ROUTING section
Description
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
Action
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
See Also
dmconfig(5)
3068
ERROR: Can't read SERVERS section of TUXCONFIG file
Description
When the GWADM administrative server is booted, it reads the TUXCONFIG file to determine the number of gateway processes in its group so that it can figure out the size of PROC table in shared memory. This message indicates that GWADM could not read the TUXCONFIG file. Make sure that the file still exists and is accessible.
Action
If the file still exists, check the permissions. If it does not exist, restart the application.
See Also
dmconfig(5)
3069
ERROR: Cannot allocate shared memory to create hash table
Description
The GWADM administrative server could not create shared memory segment(s) to create hash tables for various sections in the DMCONFIG file. The GWADM creates a large segment and doles out portions of it for hash tables in the very beginning of the initialization procedure. This error should not occur normally.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3070
ERROR: Cannot allocate shared memory to create table
Description
The GWADM administrative server first estimates the size of shared memory required for the domain, creates the shared memory, and then doles out pieces of it for various sections. This message indicates that the GWADM could not create one of the tables in shared memory because there was no space left in shared memory, and it could not create additional segments to hold the new table.
Action
Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.
See Also
dmconfig(5)
3071
ERROR: Can't setup links from LOCAL DOMAIN entry to tdomain/ositp/snadom
Description
The GWADM administrative server first loads the addresses for the local domain and then sets up links from the local domain information to its listening addresses. This message indicates that it could not set up the link. This message should only happen if the shared memory is corrupted for some reason.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3072
ERROR: Can't setup links from LOCAL DOMAIN entry to tdomain/ositp/snadom
Description
The Gateway Administrative server detected an internal error while trying to initialize.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3073
ERROR: Can't add own process entry in shared memory
Description
The GWADM administrative server could not allocate an entry in the PROC table. This message indicates that the gateway processes terminated without relinquishing their slot in the PROC table. This message should not occur normally.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3074
ERROR: Can't create additional shared memory to create hash table
Description
The GWADM administrative server first estimates the size of shared memory required for the domain, creates the shared memory, and then doles out pieces of it for various sections. This message indicates that the GWADM could not create one of the tables in shared memory because there was no space left in shared memory, and it could not create additional segments to hold the new table.
Action
Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.
See Also
dmconfig(5)
3075
ERROR: Can't find LOCAL DOMAIN entry in table
Description
The GWADM administrative server received a request to dynamically update the LOCAL_DOMAIN entry. This message indicates that the update operation failed because it could not find the entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3076
ERROR: Can't find LOCAL DOMAIN entry by link
Description
The GWADM administrative server received a request to dynamically update the LOCAL_DOMAIN entry. This message indicates that the update operation failed because it could not find the entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3077
ERROR: Can't add DOMAIN ID entry for RDOM into table
Description
The GWADM administrative server received a request to dynamically add a remote domain. The server, at first, adds an entry in the DOMAINID table for the given remote domain. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3078
ERROR: Can't find DOMAIN ID entry for RDOM in table
Description
The GWADM administrative server received a request to dynamically add a REMOTE_DOMAIN entry. This message indicates that the add operation failed because it could not find an entry in the DOMAINID table it just added.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3079
ERROR: Can't add REMOTE DOMAIN entry into table
Description
The GWADM administrative server received a request to dynamically add a remote domain. The server, at first, adds an entry in the DOMAINID table for the given remote domain. Then, it adds an entry in the REMOTE_DOMAIN table. This message indicates that the second add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3080
ERROR: Can't setup links from REMOTE DOMAIN entry to tdomain/ositp/snadom
Description
The GWADM administrative server received a request to dynamically add an address for a remote domain. This message indicates that the add operation succeeded but it failed to set up links from the added entry to the list of addresses.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3081
ERROR: Can't add TDOMAIN entry into table
Description
The GWADM administrative server received a request to dynamically add an address for a domain. This message indicates that add operation failed. Check surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3082
ERROR: Can't setup links from LOCAL DOMAIN entry to tdomain
Description
The GWADM administrative server received a request to dynamically add a listening address for the local domain. After successfully adding the entry in the address table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3083
ERROR: Can't setup links from REMOTE DOMAIN entry to tdomain
Description
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3084
ERROR: Can't add OSITP entry into table
Description
The GWADM administrative server received a request to dynamically add an address for a domain. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3085
ERROR: Can't setup links from LOCAL DOMAIN entry to ositp
Description
The GWADM administrative server received a request to dynamically add a listening address for the local domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3086
ERROR: Can't setup links from REMOTE DOMAIN entry to ositp
Description
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3087
ERROR: Can't add SNADOM entry into table
Description
The GWADM administrative server received a request to dynamically add a SNADOM entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3088
ERROR: Can't setup links from LOCAL DOMAIN entry to snadom
Description
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3089
ERROR: Can't setup links from REMOTE DOMAIN entry to snadom
Description
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3090
ERROR: Can't add LOCAL SERVICE entry into table
Description
The GWADM administrative server received a request to dynamically add a LOCAL_SERVICE entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3091
ERROR: Can't setup links from LOCAL SERVICE entry to ACL entry
Description
The GWADM administrative server received a request to dynamically add a LOCAL_SERVICE entry. The add operation succeeded but GWADM failed to set up the link from the added entry to the entry in the ACL table.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3092
ERROR: Can't delete LOCAL SERVICE entry from table
Description
The GWADM administrative server received a request to dynamically delete a LOCAL_SERVICE entry. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3093
ERROR: Can't setup links from LOCAL SERVICE entry to ACL entry
Description
The GWADM administrative server received a request to dynamically add a LOCAL_SERVICE entry. The add operation succeeded but GWADM could not set up the link from the new entry to the ACL entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3094
ERROR: Can't delete LOCAL SERVICE entry from table
Description
The GWADM administrative server received a request to dynamically delete a LOCAL_SERVICE entry. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3095
ERROR: Can't add LOCAL SERVICE entry into table
Description
The GWADM administrative server received a request to dynamically add a LOCAL_SERVICE entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3096
ERROR: Can't setup links from LOCAL SERVICE entry to ACL entry
Description
The GWADM administrative server received a request to dynamically add a LOCAL_SERVICE entry. The add operation succeeded but GWADM failed to set up the link from the added entry to the entry in the ACL table.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3097
ERROR: Can't add REMOTE SERVICE entry into table
Description
The GWADM administrative server received a request to dynamically add a REMOTE_SERVICE entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3098
ERROR: Can't setup links from REMOTE SERVICE entry to routing/rdomentry
Description
The GWADM administrative server received a request to dynamically add a REMOTE_SERVICE entry. The add operation succeeded but GWADM failed to set up the link from the added entry to the entry in the RDOM and/or ROUTING entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3099
ERROR: Can't delete REMOTE SERVICE entry from table
Description
The GWADM administrative server received a request to dynamically delete a REMOTE_SERVICE entry. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
 |
 |
 |