Messages
Use the warning and error messages to identify the response from IBM® Security Directory Suite for the operations that you run against the server.
- GLPADC003E The directory server instance 'instance name' does not exist.
- GLPADC008E Incorrect version for Directory server instance: 'instance name'
- GLPADC010E Failed to generate unique port number for Cloudscape database while configuring the solution for instance: 'instance name'.
- GLPADC011E Failed to generate unique port number for remote API while configuring the solution for instance: 'instance name'
- GLPADM003E Unable to complete the initial feature registration.
- GLPADM005E Admin Audit log file 'file name' is full, unable to log any more records.
- GLPADM007E Admin server attempt to setsockopt() failed to set TCP_NODELAY; errno error value (error string).
- GLPADM008E Admin server call to setsockopt() to set keep alive failed; errno error value (error string).
- GLPADM016E A client sent non-secured communications to the SSL port.
- GLPADM018E Unable to open file 'file'. Try specifying the full path name.
- GLPADM019E Unable to create the necessary thread.
- GLPADM020E Configuration error: server using port port for both SSL and non-SSL.
- GLPADM021E An administrator DN must be specified in the adminDn line.
- GLPADM022E The -p option requires an integer to be specified for the port.
- GLPADM023E The -s option requires an integer to be specified for the secure port.
- GLPADM024E The program is unable to run because of an initialization error.
- GLPADM025E Admin server was unable to start because it could not write to the ibmdiradm.pid file.
- GLPADM026E You are not in the same primary group as the directory server instance owner 'instance name'. Only users in the same primary group as the directory server instance owner can start the Admin server of a directory server instance.
- GLPADM027E Extended operation OID failed, option decimal option is not valid for this request.
- GLPADM032E Failed to create Windows service for Admin server instance: 'instance name'.
- GLPADM035E Failed to stop Admin server instance: 'instance name'.
- GLPADM036E Unable to stop Admin server instance 'instance name', because the state of the server cannot be determined.
- GLPADM039E Failed to delete Windows service for Admin server instance: 'instance name'.
- GLPADM040E Unable to open audit log file 'filename'.
- GLPADM042E No Admin Audit entry found in the configuration file. Admin server starting with no auditing.
- GLPADM043E The -k and -i options cannot be used together.
- GLPADM044E The -k and -u options cannot be used together.
- GLPADM045E The -i and -u options cannot be used together.
- GLPADM046E Problems retrieving entry 'entry DN'.
- GLPADM047E Found an unknown attribute 'attribute name' in entry 'entry DN'.
- GLPADM051E Admin server received a request to start or restart the server with an unsupported option.
- GLPADM052E Incorrect port number specified: port number. Port number must be numeric, in the range 1 - 65535.
- GLPADM053W The Admin server audit configuration entry: entry DN is missing some values. The default values will be used.
- GLPADM059E The admin server configuration entry for backup and restore 'entry DN' attribute 'attribute' is missing or has an invalid value 'value'.
- GLPADM063E The backup requested by the admin server has failed.
- GLPADM066E The restore requested by the admin server has failed.
- GLPADM067E The admin server is currently performing a backup of the directory server.
- GLPADM068E The admin server is currently performing a restore of the directory server.
- GLPADM069W The admin server is stopping the directory server for a scheduled offline backup.
- GLPADM072W The admin server is not configured to perform regularly scheduled backups.
- GLPADM074E The admin server configuration entry for backup and restore 'entry DN' attribute 'attribute' value 'value' specifies an invalid path.
- GLPADM075E The admin server configuration entry for backup and restore 'entry DN' attribute 'attribute' value is not set.
- GLPADM076W The admin server will not backup or restore changelog data if change log is configured.
- GLPADR006E AD to TDS Synchronization for directory server instance: 'instance name' failed.
- GLPADR007E TDS server instance 'instance name' is not accessible.
- GLPADR008E AD to TDS Synchronization solution is not configured for TDS server instance 'instance name'.
- GLPADR009E Incorrect version for directory server instance 'instance name'
- GLPADR010E The directory server instance 'instance name' does not exist.
- GLPBLK002E Disconnect other applications from the directory database and restart program_name.
- GLPBLK003E Parsing entry failed. DN: Distinguished Name.
- GLPBLK007E The file system is full; bulkload cannot write to 'filename'.
- GLPBLK008E The bulkload utility was unable to read the file specified at line line number. The entry was ignored.
- GLPBLK009E Unsupported URL in the entry at line line number. The entry was ignored.
- GLPBLK010E An error occurred in the translation of a value to UTF-8 codeset at line line number. The entry was ignored.
- GLPBLK011E An unrecognized charset name, codeset name, was found in the LDIF file. No translation to UTF-8 was attempted.
- GLPBLK012E utility_program_name: Cannot authenticate DN and password.
- GLPBLK013E utility_program_name failed on 'file_operation' to file: file name.
- GLPBLK014E Disconnect other applications from the directory database and restart program_name.
- GLPBLK015E The -A option value must be 'yes' or 'no'.
- GLPBLK016E The -a option value must be 'parseonly', 'loadonly' or 'parse_and_load'.
- GLPBLK017E The -c option value must be 'yes' or 'no'.
- GLPBLK018E The -E option value must be an integer between 0 and 1000000.
- GLPBLK019E The -e option value must be 'yes' or 'no'.
- GLPBLK020E Starting with the IBM Tivoli Directory Server 6.3 release this message is deprecated.
- GLPBLK021E The -S option value must be 'yes', 'no', or 'only'.
- GLPBLK022E The -x option value must be 'yes' or 'no'.
- GLPBLK023E The -L option value is too long; maximum number of characters is number of characters.
- GLPBLK024E The -R option value must be 'yes' or 'no'.
- GLPBLK025E The -i option is required.
- GLPBLK026E Value of 0 specified for option -k not valid.
- GLPBLK027E The load action option (-a) must be 'parse_and_load' when the -k option is specified.
- GLPBLK028E The Remove tmp (-R option) must be yes when the -k option is specified.
- GLPBLK029W The -s option was specified with an incorrect character delimiter. The default delimiter '|' will be used.
- GLPBLK030E Run DB2CMD.EXE first, and then run bulkload within the "DB2 CLP" command interpreter.
- GLPBLK031E Options -o and -t are mutually exclusive.
- GLPBLK032E The -o file 'file_name' already exists.
- GLPBLK033E Options -G and -k are mutually exclusive.
- GLPBLK034E The -S option is not allowed when the -k option is specified.
- GLPBLK035W Previous LOAD failure detected in 'filename'. Bulkload will try to restart load operations. "ACTION" is set to LOADONLY.
- GLPBLK036W Parse only option was chosen last time and detected in 'filename'. But "ACTION" is not LOADONLY. Bulkload will back up the status file to 'filename.filename_suffix'.
- GLPBLK037E The -a 'loadonly' option was specified but there are no load files to load. 'filename' is not found. Bulkload will stop.
- GLPBLK038E The load only option is chosen but the bulkload status file is either not readable or corrupted. Bulkload will end.
- GLPBLK039E Bulkload failed to rename the old status file 'filename'. Bulkload will end.
- GLPBLK040E Bulkload failed to determine the home directory. Bulkload will end.
- GLPBLK041E Bulkload failed to determine import directory 'path'. Bulkload will end.
- GLPBLK042E Bulkload failed to create the temporary directory under 'path'. Bulkload will end.
- GLPBLK043E Bulkload failed to chdir to 'path'. Bulkload will end.
- GLPBLK045E Input data failed to pass schema checking or parsing completely.
- GLPBLK046E Entry 'DN of entry' above line line number violates the schema definition. The error code is return code.
- GLPBLK047E Entry 'DN of entry' above line line number does not contain objectclass.
- GLPBLK048E UUID 'UUID' in input file not valid.
- GLPBLK049E Entry DN above line line number contains an incorrect ACL definition.
- GLPBLK051E DN 'DN' detected at line line number not valid.
- GLPBLK052E DN 'DN' at line line number exceeds maximum length size limit.
- GLPBLK053W LDADPIMPORT directory is not consistent with the directory specified in 'filename'. For ACTION=LOADONLY, bulkload will use 'path' in filename.
- GLPBLK054W LDADPIMPORT directory is not consistent with the directory specified in 'filename'. Bulkload will use 'path'.
- GLPBLK056W Bulkload failed to remove temporary directory under 'path'.
- GLPBLK057E Error in translation of value from UTF-8 to a database codepage for entry 'DN of entry'.
- GLPBLK058E Entry 'DN of entry' already exists in the directory.
- GLPBLK059E Entry 'DN of entry' already exists in the input file.
- GLPBLK060E Cannot create DB2 table for attribute 'attribute name'.
- GLPBLK064E Entry 'DN of entry' at line line number does not exist in the directory .
- GLPBLK065E Attribute 'attribute name' at line line number is not defined in the schema.
- GLPBLK066E attribute 'attribute name' at line line number is not allowed with option -G.
- GLPBLK068E Attribute 'attribute name' has a maximum value length of integer. Current attribute value is of length integer.
- GLPBLK069E Bulkload error; cannot find input file 'file name'.
- GLPBLK070E Parent entry for 'DN of entry' does not exist.
- GLPBLK071E Bulkload is unable to run because of an initialization error.
- GLPBLK074E An internal error occurred while getting the directory database applications.
- GLPBLK098E An internal error occurred while processing the LDADPIMPORT directory.
- GLPBLK099E The file system is full or a load file exceeded maximum file size.
- GLPBLK100E An internal error occurred while attempting to generate the load script.
- GLPBLK101E An internal error occurred while attempting to stream out the status file.
- GLPBLK108E An internal error occurred while loading the data.
- GLPBLK109E script name failed! rc = rc. The status file file is created and temp directory directory will not be removed. See db2load.log in db2load directory for details.
- GLPBLK110E An internal error occurred while attempting to stream out the status file due to load failure.
- GLPBLK111E An internal error occurred while loading the attribute data.
- GLPBLK112E script name failed! rc = rc. The status file file is created and temp directory directory will not be removed. See db2load.log in db2load directory for details.
- GLPBLK113E An internal error occurred while attempting to stream out the status file due to attribute load failure.
- GLPBLK114E Bulkload failed to remove the ldapimport directory directory file. Bulkload will end.
- GLPBLK115E An internal error occurred while attempting to set file position during parsing.
- GLPBLK116E Line detected: line not valid.
- GLPBLK117E URL processing error at line: line
- GLPBLK118E Codepage conversion failed at line: line
- GLPBLK119E An internal error occurred while attempting to set file position during parsing entries.
- GLPBLK120E Line detected while parsing entries: line not valid.
- GLPBLK121E URL processing error while parsing entries at line: line
- GLPBLK122E Codepage conversion failed while parsing entries at line: line
- GLPBLK123E DN 'DN' detected at line line number while parsing entries not valid.
- GLPBLK124E Attribute 'attribute name' at line line number is not preceded by a DN.
- GLPBLK125E Codepage conversion failed while parsing entries at line: line
- GLPBLK126E Language tag not supported for attribute 'attribute name' in entry 'entry name' at line line number
- GLPBLK127E Language tag not supported for attribute 'attribute name' in entry 'entry name' at line line number
- GLPBLK128E An internal error occurred while attempting to open load file for attribute name.
- GLPBLK129E An internal error occurred while reading load file for attribute name at line line number.
- GLPBLK130E attribute name is not allowed at line line
- GLPBLK131E attribute name is not allowed at line line
- GLPBLK132E Line detected: line not valid.
- GLPBLK133E Codepage conversion failed at line: line
- GLPBLK134E Attribute 'attribute name' at line line number is not preceded by a DN.
- GLPBLK135E Codepage conversion failed at line: line
- GLPBLK136E Language tag not supported for attribute 'attribute name' in entry 'entry name' at line line number
- GLPBLK137E Language tag not supported for attribute 'attribute name' in entry 'entry name' at line line number
- GLPBLK138E An internal error occurred while attempting to open load file for attribute name.
- GLPBLK139E An internal error occurred while reading load file for attribute name at line line number.
- GLPBLK140E An internal error occurred while attempting to close file handles.
- GLPBLK142E An internal error occurred while attempting to stream out the status file.
- GLPBLK143E script name failed! rc = rc. The status file file is created and temp directory directory will not be removed. See db2load.log in db2load directory for details.
- GLPBLK144E An internal error occurred while attempting to stream out the status file due to load failure.
- GLPBLK145E Bulkload failed to remove the ldapimport directory directory file. Bulkload will end.
- GLPBLK146E The status file indicates attr failed but load message file indicates it finished the phase phase successfully. Bulkload will end.
- GLPBLK147E The file system is full or a load file exceeded maximum file size.
- GLPBLK148E An internal error occurred while attempting to generate the load script.
- GLPBLK149E An internal error occurred because bulkload failed to reset variables for the next cardinal number round of parse and load.
- GLPBLK152E Parsing entry failed at line line number.
- GLPBLK153E Operational attribute attribute name is specified more than once.
- GLPBLK154E Entry contains incorrect value for operational attribute attribute name
- GLPBLK155E Option -t is specified and entry contains operational attributes in plain text form.
- GLPBLK156E Option -t was specified and entry contains operational attributes in the LDAP control.
- GLPBLK157E Entry contains operational attributes in both LDAP control and plain text format.
- GLPBLK158E Nested groups exist in the database and nested group processing is not enabled. Bulkload will stop.
- GLPBLK159E Nested groups exist in the input file and nested group processing is not enabled. Bulkload will stop.
- GLPBLK161E Suffix entry 'Suffix entry DN' does not exist.
- GLPCAT001E Requested message number message_number beyond bounds of internal table.
- GLPCAT002E Cannot open message catalog file catalog_name.
- GLPCAT003E A character transformation error occurred while trying to output a message. The UTF-8 codepage conversion failed.
- GLPCCH004E Failed to add change log to directory server instance: 'instance name'.
- GLPCCH007E Failed to configure change log database 'database name' for directory server instance: 'instance name'.
- GLPCCH008E A change log database is already configured in directory server instance 'instance name'.
- GLPCCH009E A database instance is not configured for directory server instance 'instance name'.
- GLPCCH010E Unable to configure change log. No database is configured for directory server instance 'instance name'.
- GLPCCH011E A change log is already configured for directory server instance 'instance name'.
- GLPCCH015E The argument for the -m option must be an integer greater than or equal to 0.
- GLPCCH016E The argument for the -h option must be an integer greater than or equal to 0 and less than or equal to 24.
- GLPCCH017E The argument for the -y option must be an integer greater than or equal to 0.
- GLPCCH018E An internal error occurred while running the idscfgchglg command.
- GLPCCH019W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPCCH022E Failed to set change log maximum entries to 'number of entries'.
- GLPCCH025E Failed to set change log maximum age limit to 'number of days' days 'number of hours' hours.
- GLPCDB004E Failed to add database 'database name' to directory server instance: 'instance name'.
- GLPCDB007E Failed to configure database 'database name' for directory server instance: 'DB2 instance'.
- GLPCDB008E A database is already configured in directory server instance 'instance name'.
- GLPCDB009E A database instance is not configured for directory server instance 'instance name'.
- GLPCDB010E Failed to configure local loopback for directory server instance: 'instance name'.
- GLPCDB011E The specified database location 'location' is not a drive.
- GLPCDB012E The -a -t and -l options are required. The -w is only required if the -n is also specified.
- GLPCDB013E Unable to configure database. No database instance is configured for directory server instance 'instance name'.
- GLPCDB014E A database is already configured for directory server instance 'instance name'.
- GLPCDB016E The -w option is required.
- GLPCDB017E The database administrator user ID specified, 'user name', is not a valid name and violates the DB2 database name naming rules.
- GLPCDB018E The DB2 administrator ID or password you specified is not valid.
- GLPCDB019E The DB2 instance owner ID that you specified does not exist.
- GLPCDB020E The specified directory, 'filename', is not a valid directory, does not exist, or is not writable.
- GLPCDB021E The specified directory, 'filename', does not have enough free space. Specify an existing location that is writable with at least 80 MB of free space.
- GLPCDB025E An internal error occurred while running the idscfgdb command.
- GLPCDB026W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPCDB027E The database name specified, 'database name', is not a valid name and violates the DB2 database name naming rules.
- GLPCDB030E Failed to reconfigure database password.
- GLPCDB031E Unable to determine the primary group of the user 'user name'. The primary group of the DB2 database instance owner must be valid before a database can be configured.
- GLPCDB032E Unable to determine the primary group of the user 'user name'. The primary group of the DB2 database administrator must be valid before a database can be configured.
- GLPCDB033E The database instance owner, 'user name', and the database administrator, 'user name', must have the same primary group.
- GLPCDB034E An internal error occurred while retrieving the database instance for the directory server instance.
- GLPCDB036E The database name specified, 'database name', is reserved for the change log database of the directory server instance.
- GLPCDB037W The specified directory, 'directory', does not have read, write, and execute permissions for the primary group 'group name' of directory server instance owner 'username'.
- GLPCDB038E Unable to determine the ownership and permissions on the directory 'filename'.
- GLPCDB040E An incorrect value for the argument 'argname' is passed. The valid value for this argument is an integer greater than or equal to vldvalue.
- GLPCDB042E An incorrect value for the argument 'argname' is passed. The valid value for this argument is SMS or DMS.
- GLPCDB043W No change to the properties of tablespaces will occur as an existing database will be configured for the directory server instance 'instance name'.
- GLPCDB044E Sufficient disk space is not available for tablespace container.
- GLPCDB047E Error while removing online backup configuration.
- GLPCDB048E Both the arguments 'c' and 'k' can not be passed together.
- GLPCDB050E Specified a backup directory 'filename', that does not exist or is not accessible.
- GLPCDB051E Filename specified with the -u option is invalid.
- GLPCDB052E Filename specified with the -r option is invalid.
- GLPCDB053E Creating a DB2 database in a local code page with the -x option is not supported.
- GLPCFG001E All fields are required.
- GLPCFG002E Invalid DN.
- GLPCFG003E Passwords do not match.
- GLPCFG004E Server must be stopped before running this operation.Do you want to stop the server?
- GLPCFG005E Specified directory is not valid.
- GLPCFG006E The specified location "location" is not valid. Specify a valid local drive with at least 30 MB of free space.
- GLPCFG007E The specified location "location" is not valid. Specify a valid location with at least 30 MB of free space.
- GLPCFG009E "operation" failed.
- GLPCFG010E Specified file does not exist.
- GLPCFG011E No file name specified.
- GLPCFG012E Specified value is not a valid number.
- GLPCFG013W Disabling the change log will destroy the data currently in the change log database. Do you still want to continue?
- GLPCFG015W File already exists. Do you want to overwrite it?
- GLPCFG017E Deletion of a reserved schema file is not allowed.
- GLPCFG018E Deletion of a reserved suffix is not allowed.
- GLPCFG019W Are you sure you want to delete the selected suffix?
- GLPCFG020W Are you sure you want to delete the selected Suffixcount suffixes?
- GLPCFG021W Are you sure you want to delete the selected entry?
- GLPCFG022W Are you sure you want to delete the selected Entrycount entries?
- GLPCFG023W No suffixes are currently available.
- GLPCFG024W No schema files currently available.
- GLPCFG025E Failed to add suffix suffix.
- GLPCFG026E Failed to add file filename schema file.
- GLPCFG027E Failed to remove suffix suffix.
- GLPCFG028E Failed to remove schema file filenames.
- GLPCFG029E Specified database location has insufficient free space. Specify a valid location with minimum 80 MB of free space.
- GLPCFG030E Either the specified user ID or the password is invalid.
- GLPCFG031E The specified database is not valid. Enter a valid database.
- GLPCFG032E Failed to drop the current database instance.
- GLPCFG034E There is currently no database instance available.
- GLPCFG035E There is currently no database available.
- GLPCFG038E No database is currently configured.
- GLPCFG041E Failed to unconfigure database.
- GLPCFG042E Failed to start the task.
- GLPCFG043E Failed to initialize the task.
- GLPCFG044E Task is already running.
- GLPCFG045E IBM Security Directory Server not installed.
- GLPCFG048E Target directory could not be created.
- GLPCFG049E Database location not specified in the configuration file.
- GLPCFG050E DB2 could not be found on the system.
- GLPCFG053E Value specified must be in the range of 0 - 2147483647.
- GLPCFG054E A dependent task is already running or is in an incomplete state.
- GLPCFG066E The specified file system "location" is not a valid location.
- GLPCFG067E Invalid value for 'Days'. Value expected in the range 0 - 65535.
- GLPCFG068E Invalid value for 'Hours'. Value expected in the range 0 - 24.
- GLPCFG069E RDBM not installed.
- GLPCFG070E The specified location does not contain valid backup files of IBM Security Directory Server. Specify a valid location.
- GLPCFG072E One or more ports specified are the same. Specify unique ports.
- GLPCFG073E The IP address ip and port port combination is already in use by another directory server instance. Specify a unique IP and port combination.
- GLPCFG074E The user name and password do not match the credentials of any existing user on the system.
- GLPCFG075E The database names 'ldapclog' and 'ldapclgb' are reserved and cannot be used for normal database configuration.
- GLPCFG076E Select either the check box or at least one IP from list.
- GLPCFG077E The user name username is not a valid system user.
- GLPCFG078E DB2 instance InstanceName is already associated with another directory server instance.
- GLPCFG079E The user name cannot contain more than count characters.
- GLPCFG080E The user name is not a valid name and violates the directory server instance naming rules.Only the a-z, A-Z, and 0-9 characters are allowed. The user name cannot include accented characters or certain reserved keywords.
- GLPCFG081E The directory server instance 'DirInstanceName' already exists. Specify a unique value.
- GLPCFG082E The encryption seed must contain only printable ISO-8859-1 ASCII characters with values in the range of 33 to 126 inclusive.The encryption seed must be a minimum of 12 and a maximum of 1016 characters in length.
- GLPCFG083E Only a-z, A-Z, and 0-9 allowed.
- GLPCFG084E The user name cannot start with a number.
- GLPCFG085E The encryption seed string cannot start with a number.
- GLPCFG086E An internal error has occurred.
- GLPCFG087E The operation did not complete successfully.
- GLPCFG088E DB2 database is required to successfully migrate the specified directory server.
- GLPCFG089W You have chosen to delete directory server instance instname. This will result in deletion of the instance configuration file, schema files, log files, directories, and other directory server instance system files. The associated database (if any) will not be deleted. Do you want to continue?
- GLPCFG090W You have chosen to delete directory server instance instname and to destroy the associated database instance dbinst. This will result in deletion of the instance configuration file, schema files, log files, directories, and related database information. Do you want to continue ?
- GLPCFG091E The directory server instance is currently running. You must stop the directory server before deleting it.
- GLPCFG093E This directory server instance has no associated DB2 instance. Cannot proceed with database configuration.
- GLPCFG094W Database will be unconfigured. Do you want to continue?
- GLPCFG095W Database will be unconfigured and destroyed. Do you want to continue?
- GLPCFG097E Failed to set administrator DN.
- GLPCFG099E Failed to set administrator password.
- GLPCFG100E The default directory server instance could not be determined. Use the -I option to specify the instance, or set the IDS_LDAP_INSTANCE environment variable before launching idsxcfg.
- GLPCFG101E The directory server instance 'instance_name' does not exist.
- GLPCFG102E The directory server instance owner, 'user name', must be a member of the primary group, 'group name', of the database instance owner, 'user name'.
- GLPCFG103E The directory server instance owner, 'user name', must be a member of the group 'idsldap'.
- GLPCFG104E The password specified violates administrator password policy. A minimum of number of characters characters is required.
- GLPCFG105E The password specified violates administrator password policy. A minimum of number of characters alphabetic characters is required.
- GLPCFG106E The password specified violates administrator password policy. A minimum of number of characters non-alphabetic characters is required.
- GLPCFG107E The password specified violates administrator password policy. A maximum of number of characters repeated characters is allowed.
- GLPCFG108E The password specified violates administrator password policy. A minimum of number of characters characters must be different from the previous password.
- GLPCFG109E The backup directory specified 'directory', does not exist or is not accessible.
- GLPCFG110E An unsupported version was given for migration.
- GLPCFG111E Unable to locate file 'filename'.
- GLPCFG112E Unable to determine location of configuration file.
- GLPCFG113E Unable to read configuration file 'filename'.
- GLPCFG114E Files in backup directory 'directory' are determined to be of version 'version'. Migration will continue based on this migration path.
- GLPCFG115E The log file name and path information from the backed up configuration file will not be preserved by migration. Log file names and paths will be updated to be specific for a directory server instance.
- GLPCFG116E Unable to run command on directory server instance because the state of the server cannot be determined.
- GLPCFG117E A required field has not been entered.
- GLPCFG118W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPCFG119E Select a directory server instance.
- GLPCFG120E The encryption seed and salt values are required. If you do not want to specify these values, clear the Export data for AES-enabled destination server check box.
- GLPCFG121E The encryption salt must only contain printable ISO-8859-1 ASCII characters with values in the range of 33 to 126, and must be exactly 12 characters in length.
- GLPCFG122E The Admin DN and password must be configured before continuing with this operation.
- GLPCFG123W You have not changed the original settings. Do you want to continue?
- GLPCFG124E The database instance 'db2InstanceName' is not present on the system. Migration cannot continue.
- GLPCFG125E The database 'databaseName' is not present on the system. Migration cannot continue.
- GLPCFG126E The directory server instance owner, 'username', must be a member of the group 'Administrators'.
- GLPCFG127E 'root' must be a member of the primary group, 'groupName', of the database instance owner, 'username'.
- GLPCFG128E Encryption seed values do not match.
- GLPCFG129E Unable to connect to the server at ldapURL
- GLPCFG130E The server, ldapURL is running in configuration only mode
- GLPCFG131E The server, ldapURL is not running a supported version.
- GLPCFG132E No permission to access the server, ldapURL
- GLPCFG133E Administrator DN or password of the selected instance is not configured.
- GLPCFG134E No path specified.
- GLPCFG135E Unable to retrieve information from the specified server
- GLPCFG136E Path for backup images is required while setting up a peer or replica server.
- GLPCFG137E Unable to add or update the user.
- GLPCFG138E Provide the primary group of the user.
- GLPCFG139E Encryption salt value mismatch.
- GLPCFG140E Unable to load existing configuration.
- GLPCFG141W No performance tuning updates are requested. Do you want to continue?
- GLPCFG142E Unable to load 'statFile'
- GLPCFG143E Unable to fetch total number of entries and average size of an entry in server instance database. Use command line option to update 'inputFile'.
- GLPCFG144E The suffix 'suffix' conflicts with an existing suffix.
- GLPCFG145E The password specified violates administrator password policy. A maximum of number of characters consecutive repeated characters is allowed.
- GLPCFG146E Server must be started before running this operation.Do you want to start the server?
- GLPCFG147E Data not valid in 'field'.
- GLPCFG148E 'field value' is not a valid value.
- GLPCFG149E Specified location is not valid.
- GLPCFG150E Specified file already exists.
- GLPCFG151E Invalid administrator DN or password.
- GLPCFG152E None of the options is selected.
- GLPCFG153E Unable to locate the specified command. 'cmd'
- GLPCFG154E Unable to generate statistics using perftune, refer task messages.
- GLPCFG159E Failed to start administration server.
- GLPCFG160E Failed to stop administration server.
- GLPCFG164E Failed to stop server instance.
- GLPCFG168E Initial size must be greater than initialValue pages.
- GLPCFG169E IBM Tivoli Directory Integrator (TDI) is not detected on the system. If TDI is installed at custom install location then set IDS_LDAP_TDI_HOME to TDI install location and restart the utility.
- GLPCOM001E Creation of socket failed; errno error value (error string).
- GLPCOM002E The listen() failed; errno error value (error string).
- GLPCOM005E SocketInit failed for port port number.
- GLPCOM006E SocketInit failed for port port number.
- GLPCOM007E No objectclass was specified for entry entry DN.
- GLPCOM008E The required attribute attribute name is missing for entry entry DN.
- GLPCOM009E The attribute attribute name is not allowed for entry entry DN.
- GLPCOM012E Failed to load plugin from plugin location.
- GLPCOM013E Attribute attribute name not found in schema.
- GLPCOM014E Failed to log on user: user name.
- GLPCOM015E Failed to impersonate user.
- GLPCOM016E Windows operating system error
- GLPCOM017W Log file cleared.
- GLPCOM018E Call to setsockopt() to set reuse failed; errno error value (error string).
- GLPCOM019E The listen() failed; errno error value (error string).
- GLPCOM020E SocketInit failed for port port number.
- GLPCOM026E Objectclass objectclass name not found in schema.
- GLPCOM027E Attempt to bind failed with errno error value (error string).
- GLPCOM028E Codepage codepage value cannot be opened by LDAP server: errno message.
- GLPCOM029E LDAP Configuration file cannot be fully translated to UTF-8 codepage: errno message.
- GLPCOM032W Warning: The attribute table name table name is longer than 128 characters, so the table will be created with the name hashed table name.
- GLPCOM034E This command cannot be started while a backup for directory server instance instance name is in progress.
- GLPCOM035E This command cannot be started while a restore for directory server instance instance name is in progress.
- GLPCOM036E select() system call failed; errno error value (error string).
- GLPCOM037E This command cannot be started for directory server instance instance name while bulkload is in progress.
- GLPCRY003E The encryption seed must contain only printable ISO-8859-1 ASCII characters with values in the range of 33 to 126, and must be a minimum of 12 and a maximum of 1016 characters in length.
- GLPCRY004E The encryption salt must contain only printable ISO-8859-1 ASCII characters with values in the range of 33 to 126, and must be exactly 12 characters in length.
- GLPCRY007E The file name key stash file is inconsistent with the associated encrypted data.
- GLPCRY008E Attempting to write two-way encrypted data without the required key stash file consistency checking.
- GLPCRY009E Password value could not be decrypted.
- GLPCSC002E An internal error occurred while running the idscfgsch command.
- GLPCSC003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPCSC006E Failed to add schema file: 'schemafile'.
- GLPCSC008E The specified schema file 'schemafile' does not exist on the system or is not accessible.
- GLPCSC009E The schema file 'schemafile' already exists in the configuration file of the directory server instance.
- GLPCSC010E The -s option is required and is used to specify the name of the schema file to add.
- GLPCSC011E The specified schema file 'schemafile' is a directory.
- GLPCSF002E An internal error occurred while running the idscfgsuf command.
- GLPCSF003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPCSF006E Failed to add suffix: 'suffix'.
- GLPCSF008E The suffix 'suffix' conflicts with an existing suffix in the configuration file of the directory server instance.
- GLPCSF009E The -s option is required and is used to specify the name of the suffix to add.
- GLPCTL001E A directory server instance was not specified.
- GLPCTL004E Failed to create database instance: 'instance name'. The failure might have occurred because the system was not set up correctly before using the tool.
- GLPCTL007W Failed to remove database instance: 'instance name'.
- GLPCTL010E Failed to start database manager for database instance: 'instance name'.
- GLPCTL013W Failed to stop database manager for the database instance: 'instance name'.
- GLPCTL016W Failed to uncatalog database instance node: 'instance name'.
- GLPCTL019E Failed to catalog database instance node: 'instance name'. The failure might have occurred because the system was not set up correctly before using the tool.
- GLPCTL022E Failed to update the database manager: 'instance name'.
- GLPCTL025W Failed to enable multi-page file allocation: 'database name'
- GLPCTL028E Failed to create database: 'database name'. The failure might have occurred because the system was not set up correctly before using the tool.
- GLPCTL029E User 'user name' does not have correct system permissions to create a database in 'location'
- GLPCTL030E The DB2 administrator ID or password specified is not valid.
- GLPCTL033W Failed to remove database: 'database name'.
- GLPCTL036E Failed to update the database: 'database name'
- GLPCTL039E Failed to add local loopback to database: 'database name'. The failure might have occurred because the system was not set up correctly before using the tool.
- GLPCTL042W Failed to remove local loopback from database: 'database name'.
- GLPCTL045E Failed to add local loopback to change log database: 'database name'. The failure might have occurred because the system was not set up correctly before using the tool.
- GLPCTL048W Failed to remove local loopback from the changelog database: 'database name'.
- GLPCTL051E Failed to add TCP/IP services to database instance: 'instance name'. The failure might have occurred because the system was not set up correctly before using the tool.
- GLPCTL054W Failed to remove TCP/IP services from database instance: 'instance name'.
- GLPCTL055E Failed to load shared library 'library name'.
- GLPCTL056E Failed to load symbol from shared library 'library name'.
- GLPCTL058E The file specified to redirect the output to, 'filename', is a directory instead of a file.
- GLPCTL059E The file specified to redirect output to, 'filename', is not writable.
- GLPCTL060E The file specified to redirect output to, 'filename', could not be created.
- GLPCTL061E The file specified to redirect output to, 'filename', could not be opened.
- GLPCTL062E The specified IP address 'IP address' is not a valid IP address for this computer.
- GLPCTL064E Internal error setting terminal attribute.
- GLPCTL065E Unable to reset the display.
- GLPCTL066E The file 'filename' cannot be created. The location is not valid, is not writable, or is not accessible.
- GLPCTL067E The file 'filename' cannot be copied to 'filename'.
- GLPCTL068W Failed to delete the file: 'filename'.
- GLPCTL070W Failed to delete the directory: 'directory'.
- GLPCTL071E The directory server instance repository, 'filename', cannot be read. You do not have authority to read the repository and run this command.
- GLPCTL072E The directory server instance repository, 'filename', cannot be written to. You do not have authority to write to the repository and run this command.
- GLPCTL073E The log file, 'filename', cannot be written to. You do not have authority to write to the log and run this command.
- GLPCTL076W Failed to start admin server for directory server instance: 'instance name'.
- GLPCTL079W Failed to stop admin server for instance: 'instance name'.
- GLPCTL082W Failed to start directory server for directory server instance: 'instance name'.
- GLPCTL085W Failed to stop directory server for directory server instance: 'instance name'.
- GLPCTL086E The directory 'location' cannot be created. The location is not valid, is not writable, or is not accessible.
- GLPCTL087E The directory server instance 'instance name' does not exist.
- GLPCTL088E Unable to run the command on directory server instance 'instance name', while the directory server is running.
- GLPCTL089E Unable to run the command on directory server instance 'instance name', because the state of the directory server cannot be determined.
- GLPCTL090E Unable to run the command on directory server instance 'instance name' because the server configuration file (ibmslapd.conf) for the directory server instance could not be found.
- GLPCTL091E Unable to run the command on directory server instance 'instance name' because the configuration file, 'file name', does not exist, was not accessible, or could not be written to.
- GLPCTL092E Unable to run the command on directory server instance 'instance name'. The command can only be run on directory server instances at version 'version number'.
- GLPCTL093E The directory server instance configuration key stash file, 'filename', cannot be read. You do not have authority to read the repository and run this command.
- GLPCTL094E The directory server instance directory key stash file, 'filename', cannot be read. You do not have authority to read the repository and run this command.
- GLPCTL095E Failure to load key data from directory server instance configuration key stash file 'filename'.
- GLPCTL096E Failure to load key data from directory server instance configuration directory stash file 'filename'.
- GLPCTL097E The directory server instance ,'instance name', is a proxy server. The command cannot be run on a proxy server.
- GLPCTL100E Failed to back up database database name.
- GLPCTL103E Failed to restore backup database database name to configured database database name.
- GLPCTL104E The configuration key stash file data is inconsistent with the associated encrypted data in the configuration file 'filename'.
- GLPCTL105E The encryption synchronization attribute, ibm-slapdCryptoSync, could not be retrieved from directory server instance's configuration file. The attribute is required to validate encrypted data integrity.
- GLPCTL106E Failure to load key data from directory server instance configuration key stash file into memory.
- GLPCTL107E Failed to bind to the configuration file 'filename' of directory server instance 'instance name'. Bind failed with a return code of 'return code'.
- GLPCTL108E Unable to run the command on the directory server instance 'instance name' while the admin server is running.
- GLPCTL109E Unable to run the command on directory server instance 'instance name' because the state of the admin server cannot be determined.
- GLPCTL110E DB2 did not have sufficient access to back up the database to 'location'. The database instance owner 'user ID' and the owner's primary group must be able to access and write to the backup location.
- GLPCTL111E No directory server instance exists on the computer.
- GLPCTL112E Only the root user is authorized to run the command.
- GLPCTL117E The value specified for the 'option' option is blank.
- GLPCTL125E Failed to remove the online backup configuration for the database: 'database name'.
- GLPCTL129E Failed to remove the online backup configuration for the instance: 'instance name'.
- GLPCTL130E Error while allocating memory.
- GLPD2L003E Option -x is not allowed for a subtree that is not a replication context.
- GLPD2L004E db2ldif cannot authenticate DN and password.
- GLPD2L005E db2ldif failed on file_operation to file: file.
- GLPD2L006E db2ldif failed on file_operation to file: file.
- GLPD2L007E db2ldif failed on file_operation to file: file.
- GLPD2L008E db2ldif failed on file_operation to file: file.
- GLPD2L009E Entry DN of entry specified on db2ldif does not exist.
- GLPD2L010E db2ldif unable to run because of initialization error.
- GLPD2L012E Starting with the IBM Tivoli Directory Server 6.1 release this message is deprecated.
- GLPD2L013E The filter DN DN of filter specified is not valid.
- GLPD2L014E The filter entry DN of entry not found.
- GLPDBA002E idsdbmaint is unable to run because of initialization error.
- GLPDBA007E The tablespace LDAPSPACE creation failed.
- GLPDBA008E The tablespace USERSPACE1 creation failed.
- GLPDBA009E The tablespace LDAPSPACE deletion failed.
- GLPDBA010E The tablespace USERSPACE1 deletion failed.
- GLPDBA015E The tablespace LDAPSPACE import failed.
- GLPDBA016E The tablespace USERSPACE1 import failed.
- GLPDBA017E The tablespace LDAPSPACE export failed.
- GLPDBA018E The tablespace USERSPACE1 export failed.
- GLPDBA026W The db2inspect command failed for the table 'tabname'.
- GLPDBA035W Row compression could not be enabled for the table 'tabname'.
- GLPDBA045W The table 'tabname' has not been reorganized.
- GLPDBA047W Statistics on table 'tabname' have not been updated.
- GLPDBA048E The diagpath for database instance 'dbinstance' could not be determined.
- GLPDBA049E An incorrect value for the argument 'argname' is passed. The valid value for this argument is SMS or DMS.
- GLPDBA050E The 'work_dir' option is required with the 'ts_convertion' option.
- GLPDBA051E The specified directory, 'filename', is not a valid directory, does not exist, or is not writable.
- GLPDBA052E The specified directory, 'work_dir', does not have enough free space required for table space conversion.
- GLPDBA054E Unable to estimate the database size.
- GLPDBB002E Specified a backup directory, 'filename', that does not exist or is not accessible.
- GLPDBB003E An internal error occurred while running the idsdbback command.
- GLPDBB004W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPDBB005E The -k <backup dir> option is required. Use the -? option to see the syntax for the idsdbback command.
- GLPDBB006E Unable to back up database. No database instance is configured for directory server instance 'instance name'.
- GLPDBB007E Unable to back up database. No database is configured for directory server instance 'instance name'.
- GLPDBB010E Failed to back up directory server instance 'instance name'.
- GLPDBB011E Unable to retrieve the database name from the directory server instance's configuration file.
- GLPDBB012E Unable to retrieve the database instance name from the directory server instance's configuration file.
- GLPDBB013E Unable to retrieve the database administrator ID from the directory server instance's configuration file.
- GLPDBB014E Unable to retrieve the database administrator password from the directory server instance's configuration file.
- GLPDBB017E Failed to back up the configuration file for directory server instance 'instance name'.
- GLPDBB020E Failed to back up the key stash files for the directory server instance 'instance name'.
- GLPDBB023E Failed to back up the schema files for the directory server instance 'instance name'.
- GLPDBB024E The backup file file name cannot be created or is not writable.
- GLPDBB025E The backup file file name could not be created or was not writable.
- GLPDBB028E Failed to save backup information to a file.
- GLPDBB030E Starting with the IBM Tivoli Directory Server 6.2 release this message is deprecated. A dbback.dat file already exists in the specified location to back up the directory server instance. Specify a directory that does not already contain backup information or delete the backup information.
- GLPDBB031E The request to configure the database for online backups cannot be completed while the directory server is running.
- GLPDBB032W The space available for a future backup is too low. The current backup location: backup path has only free space in MB MB available and the backup just completed required used space in MB MB.
- GLPDBB035E Failed to back up the database properties file for the directory server instance 'instance name'.
- GLPDBB038E Failed to back up the command file for the directory server instance 'instance name'.
- GLPDBB041E Changelog not configured.
- GLPDBB044E Conflicting options in the command line.
- GLPDBB047E The specified path backup path cannot be used for a backup.
- GLPDBB050E The -u switch for online backups is a required command line agument when specifing the -a parameter to set the archive directory. Use the -? option to see the syntax for the idsdbback command.
- GLPDBB051E Failed to create path 'archive path ' for logging inactive log files.
- GLPDBM002E The -I option is required and is used to specify the directory server instance.
- GLPDBM003E The -N option is required and is used to specify the new DB2 install location.
- GLPDBM011E The DB2 start database manager command failed.
- GLPDBM012W The DB2 database manager is already active.
- GLPDBM014E The DB2 list database directory command failed.
- GLPDBM016E The DB2 connect to database command failed.
- GLPDBM018E The DB2 stop database manager command failed.
- GLPDBM023E Failed to updated the DB2 instance width space to 64 bits.
- GLPDBM025E The DB2 force application all failed.
- GLPDBM027E The DB2 terminate failed.
- GLPDBM029E The DB2 update DBM CFG failed.
- GLPDBM033E DB2 instance migration failed.
- GLPDBM035E DB2 database migration failed for database 'dbname'.
- GLPDBM043E DB2 rebind packages failed.
- GLPDBM045E DB2 activate database command for database 'dbname' failed.
- GLPDBM046W DB2 database is already active.
- GLPDBM051E The new DB2 location specified by the -N option is not a valid path.
- GLPDBM053E The new DB2 location does not support database migration.
- GLPDBM056E Directory instance specified by the -I option is not a valid instance.
- GLPDBM058E Could not find the DB2 instance name from the directory server instance server configuration file.
- GLPDBM060E Could not find the DB2 database name from the directory server instance server configuration file.
- GLPDBM062E The directory server instance version check failed.
- GLPDBM064E DB2 initial version check failed.
- GLPDBM066E Could not find the directory server instance repository file 'instinfo'.
- GLPDBM068E Could not find the directory server instance location 'instloc'.
- GLPDBM070E Could not find the directory server instance configuration file.
- GLPDBM072E Could not determine whether directory server instance 'instance name' is running as 32-bit or a 64-bit application.
- GLPDBM074E Could not find the DB2 install location from the ldapdb.properties file 'db2loc'.
- GLPDBM076E Could not find DB2 information for directory 'db2prop'.
- GLPDBM078E Update operation for 'db2prop' file in the install location failed.
- GLPDBM080E Update operation for 'db2prop' file for the directory server instance failed.
- GLPDBM083E Could not find the directory server instance specific ldapdb.properties file.
- GLPDBM089E Unable to run the command on directory server instance 'instance name', while the directory server is running.
- GLPDBR004E Failed to restore directory server instance 'instance name'.
- GLPDBR007E Failed to load the backup information from a file.
- GLPDBR008E The backup file file name does not exist or cannot be read.
- GLPDBR009E The location of directory server instance 'instance name' cannot be found.
- GLPDBR010E The file 'file name' located in the backup file 'file name', does not exist, was not accessible, or cannot be written to.
- GLPDBR011E The file 'file name' is missing the database backup information.
- GLPDBR014E Failed to restore the configuration file for the directory server instance 'instance name'.
- GLPDBR017W Failed to restore the key stash files for the directory server instance 'instance name'.
- GLPDBR020E Failed to restore one or more of the schema files for the directory server instance 'instance name'.
- GLPDBR021E Specified a backup directory, 'filename', that does not exist or is not accessible.
- GLPDBR022E The -k <backup dir> option is required. Use the -? option to see the syntax for the idsdbrestore command.
- GLPDBR023E Unable to restore the database. No database instance is configured for directory server instance 'instance name'.
- GLPDBR024E Unable to restore database. No database is configured for directory server instance 'instance name'.
- GLPDBR025E The backup file file name does not exist or cannot be accessed.
- GLPDBR027E An internal error occurred while running the idsdbrestore command.
- GLPDBR028W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPDBR029E The file 'file name' is missing the backup directory server version information.
- GLPDBR030E The file 'file name' is missing the backup operating system information.
- GLPDBR031E The file 'file name' contains information about a backed up directory server instance that does not match the version of directory server instance 'instance name'.
- GLPDBR032E The file 'file name' was backed up from a different operating system. The idsdbrestore command can only restore backup information that was backed up on the same operating system.
- GLPDBR033E The idsdbrestore command can only restore a database to the original database instance with the same database name. The backup up database 'database name' resided in database instance 'database instance' and the configured database 'database name' resides in database instance 'database instance'
- GLPDBR036E Failed to restore the database properties file for the directory server instance 'instance name'.
- GLPDBR039E Failed to restore the command files for the directory server instance 'instance name'.
- GLPDBR041E Unable to restore changelog data; changelog is not configured for this directory server instance.
- GLPDBR043E Conflicting options in the command line requesting a restore for the directory server instance.
- GLPDDS002E The -I option is required and is used to specify the instance name.
- GLPDDS003E The -B option is required and is used to specify the base DN for splitting.
- GLPDDS004E The -i option is required and is used to specify the input file for splitting.
- GLPDDS005E Specify the proxy server configuration file for splitting.
- GLPDDS006E Error while parsing command line arguments.
- GLPDDS007E Exiting ddsetup due to error processing the command line.
- GLPDDS008E Error while validating command line arguments.
- GLPDDS009E Input LDIF file file name does not exist.
- GLPDDS012E Exiting partitioning utility due to error in configuration.
- GLPDDS013E Input argument provided on the command line is missing a value.
- GLPDDS014E Input argument provided on the command line contains all spaces.
- GLPDDS025E The directory path provided by the -l option does not exist.
- GLPDDS027E Error extracting partitioning information from proxy configuration file.
- GLPDDS028E The instance proxy instance provided by -I option is not a proxy server instance.
- GLPDDS029E Number of partitions must be greater than zero.
- GLPDDS030E Number of partitions value exceeds the allowed limit of 50.
- GLPDDS031E Error opening input LDIF file file name.
- GLPDDS032E Exiting partitioning utility due to a setup error.
- GLPDDS033E The output file out file already exists. Exiting partitioning utility.
- GLPDDS034E Error opening output filename file. Exiting partitioning utility.
- GLPDDS035E Exiting partitioning utility due to an internal error.
- GLPDDS036E Error parsing the input LDIF file on line number line no.
- GLPDDS039E Incorrect option specified on the command line.
- GLPDDS041E The partition base DN base DN provided by the -B option is not part of the proxy server's namespace.
- GLPDDS042E Unable to load the partition plugin library.
- GLPDDS043E The partition base DN base DN provided by -B option does not exist in proxy server's configuration file.
- GLPDDS044E A split name does not exist in proxy server's configuration file.
- GLPDDS047E Value for attribute attr is missing.
- GLPDDS048E Failed to write output file filename.
- GLPDDS049E Unable to continue due to parsing errors.
- GLPDDS050E Unable to continue partitioning the entries.
- GLPDPW003E The -p option is required.
- GLPDPW008E Failed to set the directory server administrator password.
- GLPDPW011E Failed to set the directory server administrator DN.
- GLPDPW012E An internal error occurred while running the idsdnpw command.
- GLPDPW013W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPDPW014E The password specified violates administrator password policy. A minimum of number of characters characters is required.
- GLPDPW015E The password specified violates administrator password policy. A minimum of number of characters alphabetic characters is required.
- GLPDPW016E The password specified violates administrator password policy. A minimum of number of characters non-alphabetic characters is required.
- GLPDPW017E The password specified violates administrator password policy. A maximum of number of characters repeated characters is allowed.
- GLPDPW018E The password specified violates administrator password policy. A minimum of number of characters characters must be different from the previous password.
- GLPDPW020E The password specified violates administrator password policy. A maximum of number of characters consecutive repeated characters is allowed.
- GLPDSM008E Problem configuring the XML parser.
- GLPDSM010E Problem configuring the XML transformer.
- GLPDSM011E Problem reading or writing to file.
- GLPDSM012E Problem writing DOMSource to file: file name
- GLPDSM013E Error processing DSML BatchRequest.
- GLPDSM015E Element name must be element name .
- GLPDSM016E BatchResponse: Required elements not set.
- GLPDSM017E LdapResult: All required values are not set.
- GLPDSM018E Incorrect input (not all parentheses are matched): filter
- GLPDSM022E Incorrect input parameters. All options must use "-name value" syntax.
- GLPDSM025E Incorrect element name. Valid element names are: "authRequest", "searchRequest", "modifyRequest", "addRequest", "delRequest", "modDNRequest", "compareRequest", "abandonRequest", "extendedRequest", "searchResponse", "authResponse", "modifyResponse", "addResponse", "delResponse", "modDNResponse", "compareResponse", "extendedResponse", "errorResponse", "searchResultEntry", "searchResultReference", "searchResultDone".
- GLPDSM026E Input is not of valid Base 64 encoding: input value
- GLPDSM027E error details .
- GLPDSM028E No DsmlResponse returned.
- GLPDSM029E No security principal or credentials supplied.
- GLPDSM030E AbandonRequest is not supported.
- GLPDSM031E AbandonRequest: Incorrect abandonID.
- GLPDSM032E AbandonRequest: All required values are not set.
- GLPDSM033E AddRequest: Unable to add DsmlAttribute.
- GLPDSM034E AddRequest: Incorrect DN.
- GLPDSM035E AddRequest: All required values are not set.
- GLPDSM036E AttibuteDescriptions: Incorrect AttributeDescriptionValue.
- GLPDSM037E AttributeDescriptions: All required values are not set.
- GLPDSM038E AttributeValueAssertion: Incorrect element value.
- GLPDSM039E AttributeValueAssertion: Illegal attribute name.
- GLPDSM040E AttributeValueAssertion: All required values are not set.
- GLPDSM041E AuthRequest: All required values are not set.
- GLPDSM042E BatchMessage: All required values are not set.
- GLPDSM043E CompareRequest: All required values are not set.
- GLPDSM044E ErrorResponse: All required values are not set.
- GLPDSM045E DeleteRequest: All required values are not set.
- GLPDSM046E DsmlAttr: All required values are not set.
- GLPDSM047E DsmlValue: All required values are not set.
- GLPDSM048E ExtendedRequest: All required values are not set.
- GLPDSM049E Presence Filter: All required values are not set.
- GLPDSM050E Equality Filter: All required values are not set.
- GLPDSM051E ApproxMatch Filter: All required values are not set.
- GLPDSM052E GreaterOrEqual Filter: All required values are not set.
- GLPDSM053E LessOrEqual Filter: All required values are not set.
- GLPDSM054E Substrings Filter: All required values are not set.
- GLPDSM055E ExtensibleMatch Filter: All required values are not set.
- GLPDSM056E Filter does not match any supported filter types: filter
- GLPDSM057E Filter: All required values are not set.
- GLPDSM058E Internal Error (related to regular expressions).
- GLPDSM059E Filter has unmatched parentheses. The partial filter below includes the unmatched parenthesis: filter
- GLPDSM060E MatchingRuleAssertion: All required values are not set.
- GLPDSM061E ModifyDNRequest: All required values are not set.
- GLPDSM062E ModifyRequest: All required values are not set.
- GLPDSM063E SearchRequest: All required values are not set.
- GLPDSM064E SearchResponse: All required values are not set.
- GLPDSM065E SearchResultEntry: All required values are not set.
- GLPDSM066E SearchResultReference: Incorrect refURI.
- GLPDSM067E SearchResultReference: All required values are not set.
- GLPDSM068E SubstringFilter: All required values are not set.
- GLPDSM069E Problem opening log file: error details
- GLPDSM070E Incorrect escape sequence in input segment: input segment
- GLPDSM071E DsmlControl: All required values are not set.
- GLPDSM072E DsmlMessage: All required values are not set.
- GLPDSM073E DsmlModification: All required values are not set.
- GLPDSM074E Incorrect parameters in AuthRequest.
- GLPDSM075E Incorrect value for attribute RequestID.
- GLPDSM076E Incorrect value for attribute processing.
- GLPDSM077E Incorrect value for attribute responseOrder.
- GLPDSM078E Illegal value for attribute onError.
- GLPDSM079E DsmlRequest: Element name should be element name .
- GLPDSM080E AuthRequest must be the first element in BatchRequest.
- GLPDSM081E Required RequestID for AuthRequest not set.
- GLPDSM082E Required RequestID not set for element name .
- GLPDSM083E BatchRequest: Required elements are not set.
- GLPDSM084E Duplicate request ID found: request ID
- GLPGRP003E The -w option is required.
- GLPGRP008E Failed to set the user password.
- GLPGRP009E An internal error occurred while running the 'idsadduser' command.
- GLPGRP010W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPGRP011W The user 'user' already exists. The user will be recreated with modified properties.
- GLPGRP014E Script 'script' failed to create user 'user'.
- GLPGRP017E The user 'user' could not be added to group 'group'.
- GLPGRP018E The required options -u and -g are missing.
- GLPGRP027E Failed to create user 'user'. Error code returned by 'command' is error code.
- GLPGRP033W Cannot create group 'group'. Error code returned by 'command' is error code.
- GLPGRP035E Failed to delete user 'user'. Error code returned by 'command' is error code.
- GLPGRP036E Pwdadm failed to clear 'user' password.
- GLPGRP037E 'OS' is not a supported operating system.
- GLPGRP038E Unable to change the access of 'directory' directory.
- GLPGRP040W 'command' was unable to add user 'root' to group 'command'.
- GLPGRP043E Failed to create user 'user'. Error code returned by 'command' is error code.
- GLPGRP045W Failed to modify file '/etc/group'.
- GLPGRP046W The group 'group' is not defined locally in the '/etc/group' file.
- GLPGRP050E Required script 'script' not found.
- GLPGRP051E The 'User name' user cannot be recreated because an instance already exists for the user.
- GLPGRP052W If the Network Information Service (NIS) database is installed on the system, user properties modification is not recommended.
- GLPGRP054E The primary group, 'group name', of the user , 'user name', is not a valid name and violates the naming rules.
- GLPGRP055E The user ID specified, 'user name', is not a valid name and violates the naming rules.
- GLPHST002E An internal error occurred while running the idssethost command.
- GLPHST003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPHST008E Failed to configure the IP address information for directory server instance: 'instance name'.
- GLPHST009E The requested IP address change will cause a port conflict with another directory server instance.
- GLPHST010E The -i option is required and was not specified.
- GLPHST011W The Admin Server for the directory server instance is currently running and must be restarted for the change to the IP addresses to take effect.
- GLPHST012E The IP address specified 'IP Address' is not an existing IP Address on the computer.
- GLPICR003E The port number specified by the -a option must be an integer greater than 0 and less than or equal to 65535.
- GLPICR004E The port number specified by the -c option must be an integer greater than 0 and less than or equal to 65535.
- GLPICR005E The port number specified by the -p option must be an integer greater than 0 and less than or equal to 65535.
- GLPICR006E The port number specified by the -s option must be an integer greater than 0 and less than or equal to 65535.
- GLPICR007E The -I option is required and is used to specify the instance name.
- GLPICR008E The directory server instance name specified, 'instance name', is not a valid name and violates the directory server instance name naming rules.
- GLPICR009E The DB2 instance name specified, 'database name', is not a valid name and violates the DB2 instance name naming rules.
- GLPICR010E The DB2 instance name specified, 'db2 instance', must match an existing user ID on the operating system.
- GLPICR011E The directory server instance name specified, 'instance name', must match an existing user ID on the operating system. If a user is to be created, then the -G and -w options must be specified.
- GLPICR012E The -t option cannot be specified if the RDBM component of the server has not been installed on the operating system.
- GLPICR018E The -e option is required.
- GLPICR022E The directory server instance 'instance name' already exists.
- GLPICR023E An internal error occurred while creating the directory server instance.
- GLPICR024W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPICR027E Failed to register directory server instance: 'instance name'.
- GLPICR030E Failed to create directory server instance: 'instance name'.
- GLPICR033E Failed to add database instance 'DB2 instance' to directory server instance: 'instance name'.
- GLPICR036E Failed to create schema files for directory server instance: 'instance name'.
- GLPICR039E Failed to create log files for directory server instance: 'instance name'.
- GLPICR042E Failed to create configuration file for directory server instance: 'instance name'.
- GLPICR045E Failed to create key stash files for directory server instance: 'instance name'.
- GLPICR048E Failed to create profile scripts for directory server instance: 'instance name'.
- GLPICR051E Failed to create directories for directory server instance: 'instance name'.
- GLPICR054E Failed to create DB2 instance link for directory server instance: 'instance name'.
- GLPICR055E The -l option is required and is used to specify the location to create the directory server instance.
- GLPICR056E Failed to retrieve the home directory for the following user: 'user name'.
- GLPICR058E The specified directory, 'filename', is not a valid directory, does not exist, or is not writable.
- GLPICR059E The specified directory server instance location 'location' is not a drive.
- GLPICR060E The database instance specified 'DB2 instance' is already being used by another directory server instance.
- GLPICR063E Failed to create Windows service for the administration server for directory instance: 'instance name'.
- GLPICR064W The Windows service for the administration server for directory instance 'instance name' already exists.
- GLPICR067E Failed to create Windows service for directory server instance: 'instance name'.
- GLPICR068W The Windows service for directory server instance 'instance name' already exists.
- GLPICR071E Failed to add entry to /etc/inittab for the administration server for directory instance: 'instance name'.
- GLPICR072W The entry in /etc/inittab for the administration server for directory instance 'instance name' already exists.
- GLPICR075E Failed to configure ports and IP addresses for directory server instance: 'instance name'.
- GLPICR076E The directory server instance 'instance name' already exists.
- GLPICR079E Failed to configure key stash files for directory server instance: 'instance name'.
- GLPICR080E The specified directory, 'filename', does not have enough free space. Specify an existing location that is writable with at least 30 MB of free space.
- GLPICR083E Failed to configure database instance 'DB2 instance' for directory server instance: 'DB2 instance'.
- GLPICR087E Failed to configure schema files for directory server instance: 'instance name'.
- GLPICR090E Failed to configure log files for directory server instance: 'instance name'.
- GLPICR091E A database instance is already configured in directory server instance 'instance name'.
- GLPICR092E The encryption seed must only contain printable ISO-8859-1 ASCII characters with values in the range of 33 to 126 inclusive, and must be a minimum of 12 and a maximum of 1016 characters in length.
- GLPICR093E The IP address specified 'IP Address' is not an existing IP address on the computer.
- GLPICR094E The ports numbers specified by the -a, -c, -p or -s options must not match each other and must not cause a conflict between any ports in the configuration file of the directory server instance.
- GLPICR095E Port 'port number' is already being used by another directory server instance.
- GLPICR096E The primary group, 'group name', of the user , 'user name', is not a valid name and violates the name naming rules.
- GLPICR097E Unable to determine the primary group of the user 'user name'. The primary group of the directory server instance owner must be validated before a directory server instance can be created.
- GLPICR098E The primary group, 'group name', of the user , 'user name', is not a valid name and violates the name naming rules.
- GLPICR099E Unable to determine the primary group of the user 'user name'. The primary group of the DB2 database instance owner must be valid before a directory server instance can be created.
- GLPICR100E The directory server instance owner, 'user name', must be a member of the primary group, 'group name', of the database instance owner, 'user name'.
- GLPICR101E The directory server instance owner, 'user name', must be a member of the group 'idsldap'.
- GLPICR102E 'root' must be a member of the primary group, 'group name', of the database instance owner, 'user name'.
- GLPICR105E Failed to add instance information to the .profile file for directory server instance: 'instance name'.
- GLPICR108E Failed to add environment variables for directory server instance: 'instance name'.
- GLPICR111E Failed to create ibmslapdService.cmd file for directory server instance: 'instance name'.
- GLPICR114E Failed to create ibmdiradmService.cmd file for directory server instance: 'instance name'.
- GLPICR115E Cannot configure database instance because the directory server instance 'instance name' does not exist.
- GLPICR116E The -C option cannot be specified if the RDBM component of the server has not been installed on the operating system.
- GLPICR117E A database instance is already configured for directory server instance 'instance name'.
- GLPICR120E Failed to create runtime executable for directory server instance: 'instance name'.
- GLPICR121E The directory server instance owner, 'user name', must be a member of the group 'Administrators'.
- GLPICR122E The specified directory, 'directory', does not have read, write, and execute permissions for the directory server instance owner 'username'.
- GLPICR123E Unable to determine the ownership and permissions on the directory 'filename'.
- GLPICR124E The location of directory server instance 'instance name' cannot be found.
- GLPICR125E The directory server instance 'instance name' is a proxy server instance for which a database instance cannot be configured.
- GLPICR126E A directory server instance with a DB2 database instance cannot be created because the necessary libraries are not loaded.
- GLPICR128E The encryption salt must contain only printable ISO-8859-1 ASCII characters with values in the range of 33 to 126 inclusive, and must be exactly 12 characters in length.
- GLPICR129E Error on running the idsadduser program.
- GLPICR131E The -G option must be specified in conjunction with -w and vice-versa.
- GLPICR132E The directory server instance owner, 'user name', must be a member of the group 'db2group'.
- GLPICR135E Failed to set the DB2 registry for database instance 'DB2 instance' to allow DB2 SELECTIVITY.
- GLPICR136W The DB2 registry for database instance 'DB2 instance' could not be set to allow DB2 SELECTIVITY but 'IBMSLAPD_USE_SELECTIVITY' is set to 'NO'.
- GLPIDL002E The LDAP URL for the source directory server instance, the -sU option, must be provided.
- GLPIDL003E The administrator DN for the source directory server instance, the -sD option, must be provided.
- GLPIDL004E The administrator DN for the new directory server instance, the -D option, must be provided.
- GLPIDL005E The directory path for the backup of the DB2 database, the -L option, must be provided.
- GLPIDL006E The -x and -r options cannot be used together.
- GLPIDL007E The -x and -p options cannot be used together.
- GLPIDL008E The -L option is required with the -r option. Include a directory path for the database backup and restore.
- GLPIDL009E The -w option is required.
- GLPIDL010E The LDAP URL given for the source directory server instance, the -sU option, is not a valid LDAP URL.
- GLPIDL012E The -sw option is required.
- GLPIDL014E The -a option is required.
- GLPIDL016E Unable to determine what mode the source directory server is running in.
- GLPIDL017E The source directory server is running in configuration only mode.
- GLPIDL018E The source directory server is configured as a proxy server.
- GLPIDL019E The source directory server is configured as an RDBM server.
- GLPIDL021E The encryption seed specified does not match the encryption seed for the source directory server instance.
- GLPIDL022E The encryption seed or encryption salt value could not be retrieved from the source directory server instance.
- GLPIDL024E The source directory server is not running IBM Security Directory Server Version 6.4.
- GLPIDL025E The source directory server type could not be determined.
- GLPIDL027E The directory server instance 'instance name' does not exist.
- GLPIDL028E The specified directory, 'directory', is not a valid directory, does not exist, or is not accessible. Cannot restore database.
- GLPIDL029E The -x and -L options cannot be used together.
- GLPIDL030W The online backup of the source directory server instance database was not successful. Data will not be restored to the new directory server instance.
- GLPIDL031E Cannot establish a connection with the source directory server instance using the LDAP URL provided: 'ldapurl'.
- GLPIDL032E Unable to retrieve the operating system information for the target and source server systems.
- GLPIDL034W The configuration information from the source server for 'configType' could not be copied.
- GLPIDL035W The information for SSL configuration from the source directory server has been copied. Ensure that all necessary files are in place before starting the directory server instance. If desired, set ibm-slapdSslPKCS11Enabled to true.
- GLPIDL036W Unable to transfer one or both of the key database and key stash files for SSL configuration from the source server.
- GLPIDL037W An SSL connection has not been established with the source directory server instance; therefore, information about the SSL configuration of that server will not be copied to the new directory server instance.
- GLPIDL038W The Kerberos configuration information from the source directory server instance has been copied to the target instance, but Kerberos is not currently enabled for the instance. Verify that the information is accurate and applicable to this system and modify the ibm-slapdKrbEnable attribute to be TRUE.
- GLPIDL039W Kerberos is configured for the source directory server instance, but the target system does not support Kerberos. The configuration information will not be copied to the target system.
- GLPIDL040W The restore of the DB2 database associated with the directory server instance was not successful. Data for the source directory server instance will not be loaded.
- GLPIDL041W Any additional plugins defined on the source directory server instance will not be copied to the target directory server instance configuration file. If necessary, plugins must be made available to the target system and added to the configuration file before use.
- GLPIDL051W The replication configuration was not successful. The online backup of the source server will not be performed.
- GLPIDL053W The restore of the database was not successful or was not attempted due to a previous error. For replication to be fully configured, the data must be loaded on the target directory server instance.
- GLPIDL055W Unable to set the server ID. Replication could not be configured.
- GLPIDL060W Replication could not be configured because the source directory server is not currently configured as a master server.
- GLPIDL061W Replication could not be configured because the source directory server is currently configured as a gateway server in the replication topology.
- GLPIDL063W The DB2 backup and restore operations are not permitted between the target operating system, 'targetOS', and the source operating system, 'sourceOS'.
- GLPIDL065E The database instance owner's password (-a option) cannot be specified when a proxy server is being cloned (-x option).
- GLPIDL066E The bind dn and pw to connect to the source server must be the admin DN and PW.
- GLPIDL067W The 'dn' entry cannot be copied to the target server. This entry must be created manually.
- GLPIDL068E The directory server instance name specified, 'instance name', must match an existing user ID on the operating system. If a user is to be created, then the -G and -a options must be specified.
- GLPIDL069E The -G option must be specified in conjunction with -a and vice-versa when deploying a proxy instance.
- GLPIDL070E Restore is not pending for the directory server instance 'instance name'.
- GLPIDP004E Failed to delete directory server instance: 'instance name'.
- GLPIDP007E Failed to remove the DB2 database instance from directory server instance: 'instance name'.
- GLPIDP010E Failed to delete schema files for directory server instance: 'instance name'.
- GLPIDP013E Failed to delete log files for directory server instance: 'instance name'.
- GLPIDP016E Failed to delete configuration file for directory server instance: 'instance name'.
- GLPIDP019E Failed to delete key stash files for directory server instance: 'instance name'.
- GLPIDP022E Failed to delete profile scripts for directory server instance: 'instance name'.
- GLPIDP025E Failed to delete directories for directory server instance: 'instance name'.
- GLPIDP028E Failed to delete DB2 instance link for directory server instance: 'instance name'.
- GLPIDP031W Failed to delete Windows service for the admin server for directory server instance 'instance name'.
- GLPIDP034W Failed to delete Windows service for directory server instance: 'instance name'.
- GLPIDP037W Failed to remove entry from /etc/inittab for the admin server for directory server instance 'instance name'.
- GLPIDP038E The directory server instance 'instance name' does not exist.
- GLPIDP041E Failed to unregister directory server instance: 'instance name'.
- GLPIDP042E The -I option is required and is used to specify the instance name.
- GLPIDP046E The directory server instance 'instance name' does not exist.
- GLPIDP049E An internal error occurred while deleting the directory server instance.
- GLPIDP050W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPIDP051E The directory server instance 'instance name' does not exist.
- GLPIDP052E The location of directory server instance 'instance name' cannot be found.
- GLPIDP055E Failed to unconfigure database instance 'DB2 instance' for directory server instance: 'DB2 instance'.
- GLPIDP056E A database instance is not configured for directory server instance 'instance name'.
- GLPIDP059E Failed to remove instance information from the .profile file for directory server instance: 'instance name'.
- GLPIDP062E Failed to remove environment variables for directory server instance: 'instance name'.
- GLPIDP065E Failed to delete the ibmslapdService.cmd file for directory server instance: 'instance name'.
- GLPIDP068E Failed to delete the ibmdiradmService.cmd file for directory server instance: 'instance name'.
- GLPIDP069E The -r option cannot be specified if the RDBM component of the server has not been installed on the operating system.
- GLPIDP070E A database instance is not configured for directory server instance 'instance name'.
- GLPIDP074E Failed to delete the runtime executable for directory server instance: 'instance name'.
- GLPIDP076E Failed to delete the ldapdb.properties file for directory server instance: 'instance name'.
- GLPIDP080E Failed to remove backup files for directory server instance: 'instance name' from 'backup path'.
- GLPIDP081W The backup location for directory server instance 'instance name' was not configured.
- GLPIDP082W The backup location 'backup path' for directory server instance 'instance name' does not exist.
- GLPILT002E An internal error occurred while running the idsilist command.
- GLPILT003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPILT018E The -a and -r options cannot be specified at the same time.
- GLPISA004E You must be the root user to run this command.
- GLPISA006E Not a supported operating system: OS
- GLPISA007E Unexpected program name: program name
- GLPISA010E Wrong version of program name. The correct version must be: Version Dir
- GLPISA013W Target file not found: Target File
- GLPISA016E Bitmode=BITMODE is not a supported bit mode.
- GLPISA017E Failed to run: command to execute
- GLPISA018W Not setting this link: link to set
- GLPISA019E Cannot set and remove link in one command.
- GLPISA020E Option was not correctly specified.
- GLPISA021E Invalid argument=option argument
- GLPISA023W Overriding conflict of set description is not allowed because a version of IBM Security Directory Server that is before 6.0 exists.
- GLPISA025W Conflicts found. Cannot set links for set description.
- GLPISA035E Lists to copy are empty or corrupted.
- GLPISA036E From and to lists to copy have unmatched number of elements
- GLPISA037W Not a valid IDSWebApp.war file.
- GLPISA042E The specified profile already exists. Specify another name.
- GLPISA045E The command line parameter, parameter, is not valid. Use -usage to see the available command line options.
- GLPISA046E The IDSWebApp.war uninstallation failed. Upgrade cannot continue.
- GLPISA047E The Embedded WAS PreUpgrade failed. Upgrade cannot continue.
- GLPISA048E The Embedded WAS PostUpgrade failed. Upgrade cannot continue.
- GLPISA049E Error copying the IDSWebApp.war file. Upgrade cannot continue.
- GLPISA050E Error running wsadmin command. Upgrade cannot continue.
- GLPISA052E The specified profile already exists. Specify another name.
- GLPISA053E The current Embedded WebSphere Application Server directory contains a deployed IBM Security Directory Server Web Administration Tool. Upgrade cannot continue.
- GLPISA054E The current IBM Security Directory Web Administration tool must be installed.
- GLPISA055E Cannot back up previous IDSWebApp configuration. Upgrade cannot continue.
- GLPISA056E Cannot restore previous IDSWebApp configuration. Backed up files stored at: RESTORE
- GLPJBP006E Error occurred while connecting to server: error details.
- GLPJBP007E Exception occurred while initializing server "server name" for SSL. Required parameters are missing. Required parameters: TrustStore, TrustStorePwd, TrustStoreType, KeyStore, KeyStorePwd, KeyStoreType.
- GLPJBP011E Tool is unable to start.
- GLPJBP013E Exception: exception text
- GLPJBP015E Failed to determine the server version for one of the servers.
- GLPJBP016W Password policy is not enabled on one of the servers. Password policy attributes on entries will be ignored during comparisons.
- GLPJBP017E Cannot open the specified file for LDIF output generation.LDIF file will not be created.
- GLPJBP018E Exception occurred while closing the LDIF file: exception details
- GLPJBP019E Missing arguments: Value not specified for argument name.
- GLPJBP020W The supplier and consumer servers have different encryption seed or salt values. The operation will take longer.
- GLPJBP021E Missing required argument; refer to the usage description for valid syntax.
- GLPJBP022E Exception occurred while adding DN to LDIF file: exception details
- GLPJBP023E Exception occurred while deleting DN from LDIF file: exception details
- GLPJBP024E Exception occurred while modifying DN in LDIF file: exception details
- GLPJBP025E Unable to search RootDSE: DirContext is Null.
- GLPJBP026E No RootDSE attributes were returned.
- GLPJBP027E Error occurred during enumeration of attributes from entry name.
- GLPJBP028E Error occurred while reading rootDSE attributes: error details
- GLPJBP029E No naming contexts were found in the rootDSE for this server.
- GLPJBP030E No subschemasubentry found in rootDSE.
- GLPJBP031E An exception occurred during search: exception details.
- GLPJBP032E Error occurred while processing search results for server: error details.
- GLPJBP033E Error occurred while setting environment variables: error details.
- GLPJBP034E Unable to continue. IBM Tivoli Directory Server version 5.1 or higher is required.
- GLPJBP039W The supplier and consumer servers have different encryption settings. The operation may take longer.
- GLPJBP040E Error while retrieving attributes of base DN.
- GLPJBP041E Exception occurred while processing DN.
- GLPJBP042E Exception occurred while fetching attributes from server.
- GLPJBP043E Exception occurred.
- GLPJBP044E Exception occurred while writing binary data to LDIF file.
- GLPJBP045E Invalid entry format for: count or port.
- GLPJBP046E Missing JSSE package for SSL connection.
- GLPJBP047E Specified SASL mechanism is not available for server server name.
- GLPJBP048E Unable to fix entry
- GLPJBP049E Error occurred while retrieving filter ACL support of the server.
- GLPJBP050E Error occurred while quiescing the server.
- GLPJBP051E Error occurred while unquiescing the server.
- GLPJBP052E Error occurred while retrieving type of the server.
- GLPJBP054E Error occurred while setting the replication controls.
- GLPJBP055E Supplier and consumer servers cannot be the same.
- GLPJBP056E Internal error occurred.
- GLPKEY002E The -s option is required and is used to specify the salt value.
- GLPKEY003E The -l option is required and is used to specify the location to create the directory key stash file.
- GLPKEY004E The specified directory, 'location', is not a valid directory, does not exist, or is not writable.
- GLPKEY005E The -e option is required.
- GLPKEY007E The encryption seed must contain only printable ISO-8859-1 ASCII characters with values in the range of 33 to 126 inclusive, and must be a minimum of 12 and a maximum of 1016 characters in length.
- GLPKEY008E The encryption salt must contain only printable ISO-8859-1 ASCII characters with values in the range of 33 to 126 inclusive, and must be exactly 12 characters in length.
- GLPKEY010E The directory key stash file file name cannot be created or was not writable.
- GLPKEY013E Failed to create directory key stash file: 'filename'.
- GLPKEY014E An internal error occurred while creating the directory key stash file.
- GLPKEY015W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPL2D002E ldif2db: entry ending on line line number in LDIF file filename does not have a valid separator. The entry is ignored.
- GLPL2D004E ldif2db: Cannot authenticate DN and password.
- GLPL2D005E ldif2db failed on file_operation to file: file.
- GLPL2D006E ldif2db cannot connect to the directory database at this time.
- GLPL2D007E Database is set to read-only in the IBM Security Directory Server configuration file. No entries can be loaded.
- GLPL2D008E The attribute attribute name on line line number is not preceded by a dn.
- GLPL2D009E Importing the entry dn is not supported by ldif2db.
- GLPL2D010E Importing the entry dn is not supported by ldif2db.
- GLPL2D011E The -i option is required.
- GLPL2D012E The -r option value must be 'yes' or 'no'.
- GLPL2D013E The -W option requires a file name to be specified.
- GLPL2D014E Suffix entry has not been created for entry DN of entry.
- GLPL2D015E Cannot find input file filename.
- GLPL2D016E An error occurred during RDBM backend initialization, rc = error code.
- GLPL2D017E ldif2db unable to run because of initialization error.
- GLPL2D018E Input file contains incorrect data at line line number.
- GLPLMT002E Could not archive file file1 to file2 : file permissions.
- GLPLMT003E Could not archive file file1 to file2 : not enough space.
- GLPLMT005E Value of attribute is invalid
- GLPLMT007E file will not be archived. attribute is not set
- GLPLMT013E Cannot contact CARS server hostname at port
- GLPLMT014E Error sending data to CARS server hostname at port
- GLPLMT016E Invalid command line options. The -I option cannot be specified with -t -a and -p.
- GLPLMT017E The instance instancename specified does not exist.
- GLPLMT018E The instance instancename specified does not match with the OS user running the Log Management tool.
- GLPLMT019E Only root user can perform this operation.
- GLPLMT020E Invalid command line options. The -k option cannot be specified with -t -a and -p.
- GLPLMT021E Unable to obtain port number for TDI server: Max retries exceeded.
- GLPLMT022E Log Management capability for this server instance is already enabled.
- GLPLMT023E Log Management capability for this server instance is already disabled.
- GLPLMT024E Unable to get TDI server's port number.
- GLPLMT025E File file does not exist. Unable to get TDI server's port number.
- GLPLMT027E Invalid command line options. The -k option can be used only in conjunction with -I.
- GLPMIG003E Specified a backup directory, 'directory', that does not exist or is not accessible.
- GLPMIG004E Cannot read V3.modifiedschema file in the 'directory' directory.
- GLPMIG005E Unable to modify V3.modifiedschema file with information in 'filename' file.
- GLPMIG006E Unable to copy file 'filename1' to 'filename2'.
- GLPMIG007E Unable to create file, 'filename'.
- GLPMIG009E Unable to read file, 'file', in directory, 'directory'.
- GLPMIG010E Unable to copy file 'filename1' to 'filename2' file.
- GLPMIG011E Unable to read file, 'filename'.
- GLPMIG012E Unable to delete file, 'filename'.
- GLPMIG013E Unable to write file, 'filename', to directory, 'directory'.
- GLPMIG014E Unable to read schema files from directory, 'directory'.
- GLPMIG015E Unable to write schema files to directory, 'directory'.
- GLPMIG016E The location for the directory server instance 'instance name' cannot be found.
- GLPMIG017E Unable to migrate the schema files from version 'starting version' to version 'ending version'.
- GLPMIG019E Files in backup directory, 'directory', are determined to be of version, 'version'. This is an unsupported migration path.
- GLPMIG020E Unable to locate file, 'filename', in directory, 'directory'.
- GLPMIG022E All necessary files for directory server instance, 'instance name', cannot be found in directory, 'directory'.
- GLPMIG023W Migration has checked the V3.modifiedschema file against the base schema files for any definition collisions. If any collisions are reported, these will be automatically resolved.
- GLPMIG024E Unable to migrate the configuration file from version 'starting version' to version 'ending version'.
- GLPMIG026E Unable to read in configuration file, 'filename'.
- GLPMIG030W The files in the backup directory, 'directory name', are determined to be from version 3.2.2. Due to database compatibility issues, any database information contained in the configuration file will not be migrated.
- GLPMIG034E The -u option must be specified for the backup directory.
- GLPMIG036W The log file name and path information from the backed up configuration file will not be preserved by migration. Log file names and paths will be updated to be specific for a directory server instance.
- GLPMIG040E The DB2 database instance listed in the backed up configuration file cannot be found on the system.
- GLPMIG041E The database name listed in the backed up configuration file cannot be found on the system.
- GLPMIG042E The changelog database name listed in the backed up configuration file cannot be found on the system.
- GLPMIG043W Not all of the schema files included in the configuration file have been found in the backup directory. Check the file names and paths for the included schema files before starting the server.
- GLPMIG044W The file, 'file name', is included in the configuration file but could not be found in the given backup directory, 'directory'.
- GLPMIG046E The DB2 database instance, 'instance name', from the backed up configuration file was found on the system. However, a matching user ID does not exist on the operating system.
- GLPMIG047W The database instance name , 'database instance name', is being overridden by the database instance information from the backed up configuration file. The database instance name, 'database instance name', will be used instead.
- GLPMIG048W The schema files were not migrated and must be migrated manually.
- GLPMIG049E The backup directory must not be specified for this migration scenario.
- GLPMIG051E Encryption key or encryption salt value must not be specified for this migration scenario.
- GLPMIG053E DB2 version specified in the file 'prop_file_name' is not valid.
- GLPMIG054E An error occurred while migrating schema and configuration files. The files were successfully restored to their original state.
- GLPMIG055E An error occurred while migrating schema and configuration files. The files could not be restored to their original state.
- GLPMIG057E Error while allocating memory.
- GLPMIG058E Unable to migrate a RDBM instance into a PROXY only installation environment.
- GLPMIG059W Unable to start the task of DB2 instance and database migration because of insufficient information.
- GLPMIG068E Unable to retrieve DB2 information from the ldapdb.properties file.
- GLPMIG074E Remote migration is detected on the system when the server instance already exists.
- GLPPFT001E Error while extracting information from the server configuration file fileName.
- GLPPFT002E Unable to find input configuration file fileName.
- GLPPFT004E Unable to find the status file fileName.
- GLPPFT006E Incorrect combination of command line options. Monitor switches can either be enabled or disabled.
- GLPPFT018E The database instance name was not found in the server configuration file.
- GLPPFT019E An error result was returned from DB2. Reason: error details
- GLPPFT020E Syntax error found in the property file pfile line number: lineno
- GLPPFT021E Unable to bind to server.
- GLPPFT022E Incorrect command line option specified.
- GLPPFT023E Incorrect filtercache size specified.
- GLPPFT025E Out of memory.
- GLPPFT026E An internal error occurred while running the idsperftune command.
- GLPPFT027E Value specified for DB2 parameter dbparam 'dbval' should be less than dbval .
- GLPPFT029W Not enough data available to perform the advanced tuning operation.
- GLPPRT002E An internal error occurred while running the idssetport command.
- GLPPRT003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPPRT010E Failed to set port to 'port number' for directory server instance: 'instance name'.
- GLPPRT013E Failed to set secure port to 'port number' for directory server instance: 'instance name'.
- GLPPRT016E Failed to set admin server port to 'port number' for directory server instance: 'instance name'.
- GLPPRT019E Failed to set admin server secure port to 'port number' for directory server instance: 'instance name'.
- GLPPRT020E The port number specified by the -a option must be an integer greater than 0 and less than or equal to 65535.
- GLPPRT021E The port number specified by the -c option must be an integer greater than 0 and less than or equal to 65535.
- GLPPRT022E The port number specified by the -p option must be an integer greater than 0 and less than or equal to 65535.
- GLPPRT023E The port number specified by the -s option must be an integer greater than 0 and less than or equal to 65535.
- GLPPRT024E The port numbers specified by the -a, -c, -p, and -s options must not match each other and must not cause a conflict between any ports in the configuration file of the directory server instance.
- GLPPRT025E Port 'port number' is already being used by another directory server instance.
- GLPPRT026E The -a, -c, -p, or -s option is required to specify a port to configure.
- GLPPRT027W The admin server for the directory server instance is currently running and must be restarted for the change to the port to take effect.
- GLPPRT028W The admin server for the directory server instance is currently running and must be restarted for the change to the secure port to take effect.
- GLPPXY001E Unable to connect to back-end server host name on port port number. Verify that the back-end server is started.
- GLPPXY002E The URL ldap:// qualified URL is invalid.
- GLPPXY004E Connection to back-end server host name:port number is down.
- GLPPXY005E The bind method "bind method" specified under config DN section is invalid. Reverting to SIMPLE bind.
- GLPPXY006E The specified proxy connection pool size number of connections in section config file DN is invalid.
- GLPPXY007E The specified server host name cannot be contacted after attempts attempts. Server will be unavailable.
- GLPPXY008E The server host name:port does not support the required control OID.
- GLPPXY009E The server host name:port does not support the required capability OID.
- GLPPXY010E The configuration file does not contain any entries for back-end servers. No data will be available.
- GLPPXY011E Proxy server is unable to bind to host host name using the credentials bind DN used.
- GLPPXY012E The credentials bind DN used supplied for host host name are not administrative.
- GLPPXY013E There are no data partitions defined in the configuration file. No data will be available.
- GLPPXY014E The specified DN object DN is not held in any of the proxied contexts.
- GLPPXY015E A referral was returned while performing an operation on object DN.
- GLPPXY016E The back-end server server ID is down.
- GLPPXY017E Error error string occurred for back-end server 'server ID': GSSAPI bind failed using principal name 'dn'.
- GLPPXY018E The DN original entry DN cannot be modified to new object DN.
- GLPPXY019E Entry DN of entry specified on bind does not exist.
- GLPPXY020E Entry DN of entry specified on compare does not exist.
- GLPPXY021E Entry DN of entry to be deleted does not exist.
- GLPPXY022E Entry DN of entry to be modified does not exist.
- GLPPXY023E Entry DN of entry to be renamed or moved does not exist.
- GLPPXY024E The entry object DN already exists.
- GLPPXY025E The server server ID is down. Failing over to server server ID.
- GLPPXY026E The value of ibm-slapdProxyNumPartitions in entry config file entry DN must be greater than zero.
- GLPPXY027E The DN config entry DN specified for attribute attribute name in entry config entry DN is not valid.
- GLPPXY028E The DN back-end Server config entry DN is not located anywhere in the configuration file.
- GLPPXY029E The value of ibm-slapdProxyPartitionIndex in entry config file entry DN must be greater than zero.
- GLPPXY030E The server host name:port does not support the required extension OID.
- GLPPXY031E All back-end servers in server group DN are down.
- GLPPXY033E Internal transaction Tran Id against back-end server ldap url was stopped.
- GLPPXY036E All writable back-end servers within the partition name partition are unavailable. All write operations will fail until a writable back-end server is back online.
- GLPPXY037E The primary write server host name:port for the partition name partition is down. Failing over to server: host name:port.
- GLPPXY038E All back-end servers within the partition name partition are unavailable.
- GLPPXY039E A partition number number that is not valid is returned by the DN partitioning plugin for DN.
- GLPPXY044E The back-end server server ID is unresponsive.
- GLPPXY046E The back-end server server ID is started in configuration only mode.
- GLPPXY047E Unable to retrieve the server ID for the back-end server server ID.
- GLPPXY048E The back-end server server ID is currently running in configuration only mode.
- GLPPXY049E There was an error while parsing required information from the back-end server server ID.
- GLPPXY050E Transaction request to back-end server server host name and port failed because too many connections are currently in use by transactions.
- GLPPXY051E Request to back-end server server host name and port failed because all the connections are currently in use by transactions.
- GLPPXY052W More than one attribute: attribute type defined in the entry: entry DN. Only the first attribute value attribute value will be used.
- GLPPXY053E Failed to add back-end server stored in entry: entry DN.
- GLPPXY064W All writable back-end servers within tier previous tier number of partition partition name are unavailable. Failing over to tier next tier number.
- GLPPXY067E The specified proxy status interval status interval in section config file dn is invalid.
- GLPPXY074E Unsupported scope specified on ibm-allMembers search. Only base level ibm-allMembers searches are allowed.
- GLPPXY077E The proxy server configuration is missing the required split container for cn=ibmpolicies.
- GLPPXY080E Unsupported scope specified on ibm-allGroups search. Only base level ibm-allGroups searches are allowed.
- GLPPXY081E Unsupported NULL based subtree search requested.
- GLPPXY082E Unsupported attribute attribute type on compare request.
- GLPPXY083E Update operations are not allowed on the split point entry entry DN.
- GLPPXY084W The local administrator entry DN has requested the schema updates. The updates will not be propagated to the backend servers.
- GLPRDB001E Error code error_code from function:" SQL function " error message .
- GLPRDB002W utility program name: number added entries have been successfully added out of number attempted attempted.
- GLPRDB003E database name parameter is missing from LDAP directory configuration file.
- GLPRDB004E The directory server is unable to connect to the database.
- GLPRDB005E DN does not have permission to all parts of the filter or the RDN. The search operation cannot return any results.
- GLPRDB006E Only one attribute-value pair can be compared at a time.
- GLPRDB007E When adding the ownerPropagate field, the entryOwner field must also be added.
- GLPRDB008E When adding the aclPropagate field, the aclEntry field must also be added.
- GLPRDB009E An explicit ACL must be set in order to change or delete this attribute value.
- GLPRDB010E An explicit owner must be set in order to change or delete this attribute value.
- GLPRDB011E Cannot delete and change the same attribute.
- GLPRDB012E Starting with the IBM Tivoli Directory Server 6.1 release this message is deprecated.
- GLPRDB013E The DnType type value specified in the aclentry is not valid. Valid values are: 'access-id', 'group', and 'role'.
- GLPRDB014E The prefix prefix value specified for a permission set is not valid. Valid prefixes are: 'normal', 'critical', 'sensitive', 'system', 'restricted' and 'object'.
- GLPRDB015E DB2 codepage cannot be determined.
- GLPRDB016E DB2 codepage codepage number is not supported by the LDAP server.
- GLPRDB017E XPG4 codepage codepage number cannot be opened by LDAP server: error message.
- GLPRDB018E Incoming data cannot be fully translated to DB2 codepage: codepage number.
- GLPRDB019E Entry entry DN cannot be modified.
- GLPRDB020E Entry entry DN cannot be modified.
- GLPRDB021E The length length specified for attribute attribute exceeds the maximum schema length.
- GLPRDB022E Specified DB2 column length length for attribute attribute must match the length defined for the attribute syntax.
- GLPRDB023W The server is not caching attributes for search filter resolution because not enough memory was configured for attribute caching.
- GLPRDB024E The server cannot load attribute caching because an internal error occurred.
- GLPRDB025E The server cannot cache the objectclass attribute when the environment variable OC_ALIAS is set to Yes.
- GLPRDB026E The server cannot cache attribute attribute name for search filter resolution because it is not a supported attribute.
- GLPRDB027E The server cannot load all configured attribute caches for search filter resolution because not enough memory was configured to hold all configured attribute caches.
- GLPRDB028E The server deleted the cache for attribute attribute_name for search filter resolution because not enough memory was configured to hold all attribute caches configured.
- GLPRDB029E The server deleted the cache for attribute attribute_name for search filter resolution because an error occurred that would have caused the cache to become corrupted.
- GLPRDB030E Migration of the REF attribute table failed.
- GLPRDB031E Failed to drop the unique constraint for attribute attribute_name.
- GLPRDB032E Failed to add the unique constraint for attribute attribute_name.
- GLPRDB033E The server cannot support language tags for attribute attribute_name.
- GLPRDB034E Because attribute attribute name is not defined in the schema, the unique attributes feature cannot be supported for this attribute.
- GLPRDB035E Because attribute attribute name is defined to allow language tags, the unique attributes feature cannot be supported for this attribute.
- GLPRDB036E The unique attributes feature does not support attribute attribute_name. The list of attributes the unique attributes feature does not support includes, but is not limited to, the following: operational attributes, configuration attributes, binary attributes, and the cn and objectclass attributes.
- GLPRDB037E The unique attributes feature does not support attribute attribute_name. The list of attributes the unique attributes feature does not support includes, but is not limited to, the following: operational attributes, configuration attributes, binary attributes, and the objectclass attribute.
- GLPRDB038E utility_program_name is unable to connect to the database.
- GLPRDB039E database_userid parameter is missing from LDAP directory configuration file.
- GLPRDB040E database_user_password parameter is missing from LDAP directory configuration file.
- GLPRDB041E When adding the ownerPropagate field, the entryOwner field must also be added.
- GLPRDB042E When deleting the entryOwner field, the ownerPropagate field must also be deleted.
- GLPRDB043E When adding the aclPropagate field, the aclEntry field must also be added.
- GLPRDB044E When deleting the aclEntry field, the aclPropagate field must also be deleted.
- GLPRDB045E Unable to connect to database; program terminating.
- GLPRDB046E Unable to connect to database; program terminating.
- GLPRDB047E Moving entry 'entry DN' to suffix suffix is not allowed.
- GLPRDB048E Moving entry 'entry DN' is not allowed.
- GLPRDB049E Moving entry to 'new entry DN' is not allowed.
- GLPRDB050E Attribute attribute name was not found in the schema definition.
- GLPRDB051E Entry DN of entry already exists.
- GLPRDB052E Entry DN of entry already exists.
- GLPRDB053E Entry DN of entry violates the schema definition.
- GLPRDB054E Entry DN of entry violates the schema definition.
- GLPRDB055E Parent entry does not exist for entry DN of entry.
- GLPRDB056E Parent entry does not exist for entry DN of entry.
- GLPRDB057E Parent entry does not exist for entry DN of entry.
- GLPRDB058E Entry size size is greater than the maximum size supported (max size).
- GLPRDB059E An SQL call failed: SQL routine name.
- GLPRDB060E Entry DN of entry specified on bind does not exist.
- GLPRDB061E Entry DN of entry specified on compare does not exist.
- GLPRDB062E Entry DN of entry to be deleted does not exist.
- GLPRDB063E Entry DN of entry to be modified does not exist.
- GLPRDB064E Entry DN of entry to be renamed or moved does not exist.
- GLPRDB065E The new superior DN DN of entry that the entry was to be moved to does not exist.
- GLPRDB066E The attribute attribute name with value attribute value already exists.
- GLPRDB067E Entry DN of entry does not contain attribute attribute name.
- GLPRDB068E Entry DN of entry does not contain attribute attribute name with value attribute value.
- GLPRDB069E Attribute attribute name has a maximum value length of max length. Current attribute value is of length current length.
- GLPRDB070E DB2CLI error, SQL data is: native return code=DB2 rc, SQL state=DB2 SQL state, SQL message=message text.
- GLPRDB071E An error occurred during backend identifier backend initialization, rc = return code.
- GLPRDB072E Distinguished name DN might have partial access.
- GLPRDB073E Starting with the IBM Tivoli Directory Server 6.1 release this message is deprecated.
- GLPRDB074E Replication conflict adding DN occurred. The entry was replaced.
- GLPRDB075E Replication conflict: an add of entry DN was rejected because it had an older timestamp.
- GLPRDB076E Specified attribute length attribute length for attribute attribute name must not be less than the length currently defined for the attribute.
- GLPRDB077E Modifying attribute table name, column name, or syntax is not allowed when the attribute attribute name already contains data.
- GLPRDB078E Specified attribute length attribute length for attribute attribute name causes the total size of columns to exceed the maximum record size.
- GLPRDB079W Attribute table name attribute name is longer than 16 characters. The current table name current table name for this attribute is being renamed to table name.
- GLPRDB080E To increase the maximum length of attribute attribute name, its data type must be either VARCHAR, VARGRAPHIC or LONG VARCHAR.
- GLPRDB081E Transaction log is either full or running out of disk space. The current database operation will be rolled back to the last committed state.
- GLPRDB082E The request to increase the size of attribute attribute name was not completed successfully due to failed DB2 operation(s). A partial change (creation of the temporary table temporary table name) has been committed in the database. Issue the modify request again or remove the temporary table temporary table name from your database.
- GLPRDB083E The server cannot be started because a newer version of the IBM Security Directory Server is already installed and configured on the system.
- GLPRDB084E Failed to complete the internal data migration.
- GLPRDB085E Failed to complete the internal data migration for long table names.
- GLPRDB086E Failed to rename the attribute table table name to new table name.
- GLPRDB087E Failed to rename the attribute index index name to new index name.
- GLPRDB088E Entry DN of entry contains an incorrect ACL definition.
- GLPRDB089E The directory server is unable to log on as the database administrator.
- GLPRDB090E Failed to complete the internal data migration for objectclass index.
- GLPRDB091W Attribute attribute name is not indexed but is used in searches number times.
- GLPRDB092E Modifications to object class ibm-pwdGroupAndIndividualPolicies or attribute ibm-pwdGroupAndIndividualEnabled are allowed only for the global password policy entry.
- GLPRDB093E The specified access class access class permission, invalid permission, is not valid. Valid permissions are valid permissions.
- GLPRDB098E Data conversion for encrypted attribute attribute name failed.
- GLPRDB101W Encrypted attribute attribute_name cannot be made unique.
- GLPRDB102W Unique attribute attribute_name cannot be encrypted.
- GLPRDB103E The password policy entry DN of entry referenced by entry DN of entry is not valid.
- GLPRDB104E The DN of the password policy entry DN of entry referenced by entry DN of entry cannot be found.
- GLPRDB105E The password policy entry DN of entry is in use and cannot be renamed or deleted.
- GLPRDB106W The ibm-pwdPolicy attribute in password policy entry DN of entry is set to TRUE, but the ibm-pwdPolicy attribute in the global password policy is set to FALSE. No password policy will be evaluated or enforced.
- GLPRDB108E The creation of a suffix entry DN of suffix failed.
- GLPRDB109E The server does not support automatic creation of a suffix entry using this RDN DN of suffix . An administrator must create the entry before entries can be added under this suffix.
- GLPRDB110E Attribute ibm-pwdPolicyStartTime in entry DN of entry cannot be set to a future time. The value of the attribute is value.
- GLPRDB111E The server is unable to use the username and password combination for the DB2 instance owner in the configuration file to establish a connection to the database.
- GLPRDB112E An attempt to delete entry entry name failed. The return code from creating a tombstone is LDAP return code.
- GLPRDB113E An attempt to delete entry entry name failed. The return code from the delete operation is LDAP return code.
- GLPRDB114W The deleted entry entry name has been restored, but the entry's group membership is not restored.
- GLPRDB118E Failed to update the database configuration for LOGARCHMETH1 for database database to method archive method.
- GLPRDB121W All members of group 'group DN' have been replaced.
- GLPRDB122E The environment variables LDAP_MAXCARD and IBMSLAPD_USE_SELECTIVITY cannot both be set to YES.
- GLPRDB131E Failed to update DB2 statistics for table 'table name' for instance 'instance name' with SQLCODE DB2 sqlcode.
- GLPRDB132E Reading the database for the eid entry id returned null data.
- GLPRDB133E The attribute attr type contains a language tag, but language tags are not enabled.
- GLPRDB134E The maximum filter limit that is set in IDS_MAX_SEARCH_FILTER_LEVEL =max filter exceeded for the assertion control on the host, host, with conn id, conn id and is bound with dn, dn
- GLPRDB145E Invalid replication filter attribute value specified in entry ' entry dn'.
- GLPRDB146E Replication filter value is not specified.
- GLPRDB147W Attribute attribut name is not found in schema.
- GLPRPL001E Unable to connect to replica host name on port port number. Verify that the replica is started.
- GLPRPL003W The DN of the credential entry entry name defined for the replication agreement entry name cannot be found.
- GLPRPL004E The credential entry entry name defined for the replication agreement entry name is not valid.
- GLPRPL005E The credential entry entry name is in use and cannot be deleted.
- GLPRPL006E For the replica group entry entry name, the parent entry must be an ibm-replicationContext entry.
- GLPRPL007E For the replica subentry entry entry name, the parent entry must be an ibm-replicaGroup entry.
- GLPRPL008E For the replication agreement entry DN of entry, the parent entry must be an ibm-replicaSubentry entry.
- GLPRPL009E Master DN and Admin DN cannot be the same.
- GLPRPL010E The consumer URL defined in replication agreement entry entry name is a duplicate.
- GLPRPL011E Initial server startup has not been done.
- GLPRPL012W Server migration in progress; wait for migration to complete. Server migration might take several minutes.
- GLPRPL013E The value of the ibm-slapdMigrationInfo attribute must contain a valid version number and server type.
- GLPRPL014E The schedule DN object entry name cannot be found.
- GLPRPL015W Invalid port port type specified: port number. Port number must be numeric, in the range 1 - 65535. Server starting in configuration only mode on port type port port number.
- GLPRPL016E Internal processing error in server; replication thread cannot start.
- GLPRPL019E Unable to create schedule for replica 'entry name'; all changes will be replicated immediately.
- GLPRPL020E Unable to locate schedule entry with DN 'entry name'.
- GLPRPL021E Error on schedule entry with DN 'entry name' attribute attribute name value 'attribute value'. Value ignored.
- GLPRPL022W Replica 'entry name' missing schedule DN; all changes will be replicated immediately.
- GLPRPL023E Error retrieving pending changes for replica 'entry name'. Will try again.
- GLPRPL024E Error retrieving data for replica 'entry name' change ID change id entry 'entry name' return code 'return code'. Will try again.
- GLPRPL025E Error while removing status entry for replica 'entry name'.
- GLPRPL026E Error while updating status for replica 'entry name' to last change ID change id.
- GLPRPL027W Error while parsing data for change ID change id for replica 'entry name'. Will try again.
- GLPRPL032E Error error string occurred for replica 'entry name': add failed for entry 'entry name' change ID change id.
- GLPRPL033E Error error string occurred for replica 'entry name': modify failed for entry 'entry name' change ID change id.
- GLPRPL034E Error error string occurred for replica 'entry name': rename failed for entry 'entry name' change ID change id.
- GLPRPL035E Error error string occurred for replica 'entry name': delete failed for entry 'entry name' change ID change id.
- GLPRPL036E Error 'error string' occurred for replica 'entry name': bind failed using masterDn 'DN'.
- GLPRPL037E Error error string occurred for replica 'entry name': GSSAPI bind failed using principal name 'DN'.
- GLPRPL038E Error error string occurred for replica 'entry name': EXTERNAL bind failed.
- GLPRPL039W Replication agreement 'entry name' has consumer server ID 'server id', but connected to server with ID 'server id'.
- GLPRPL040W Replication for replica 'replication agreement DN' will continue to retry the same update after receiving an error.
- GLPRPL041W Replication for replica 'replication agreement DN' will continue to the next update after receiving an error.
- GLPRPL042W Replication continuing for replica 'replication agreement DN' after logging update type for entry 'update entry DN' ignoring error: LDAP return code LDAP error description additional error message.
- GLPRPL043W Replication continuing for replica 'replication agreement DN' after skipping update type for entry 'update entry DN' because of error: LDAP return code LDAP error description additional error message.
- GLPRPL044E Server failed to acquire Kerberos credential for the replica 'replication agreement DN'.
- GLPRPL045E Unable to connect to replica host name on port port number. Verify that the replica is started.
- GLPRPL046W The DN of the credential entry credential entry name defined for the replication agreement agreement entry name cannot be found.
- GLPRPL047E The DN of the credential entry credential entry name defined for the replication agreement agreement entry name cannot be found.
- GLPRPL048E The consumer URL defined in replicaAgreement entry name is a duplicate.
- GLPRPL049E The value of the ibm-slapdMigrationInfo attribute must contain a valid version number.
- GLPRPL051E Error error string occurred for replica 'entry name': delete failed for entry 'entry name' change ID change id.
- GLPRPL053E Error retrieving pending change count for replica 'entry name'.
- GLPRPL054E Error while removing status entry for replica 'entry name'.
- GLPRPL055E The schedule DN object entry name cannot be found.
- GLPRPL056E The schedule DN object entry name cannot be found.
- GLPRPL057E The schedule DN object entry name cannot be found.
- GLPRPL058E The schedule DN object entry name cannot be found.
- GLPRPL059E The schedule DN object entry name cannot be found.
- GLPRPL060E Error while updating status for replica 'entry name' to last change ID change id.
- GLPRPL061E Invalid port type port specified: port number. Port number must be numeric, in the range 1 - 65535. Server starting in configuration only mode with port type port port number.
- GLPRPL062E Transaction time limit of time limit exceeded.
- GLPRPL063E Cannot move 'entry DN' from one replication context to another.
- GLPRPL064E The replication configuration could not be read.
- GLPRPL065E The replication configuration DN object entry name cannot be found.
- GLPRPL066E Error on configuration entry with DN 'entry name'; required attribute attribute name is missing.
- GLPRPL067E Error on configuration entry with DN 'entry name' attribute attribute name value 'attribute value'. Value ignored.
- GLPRPL068E Error initializing the log used for replication errors.
- GLPRPL070E Propagation of replication topology entries to host hostname port port number failed with error code rc.
- GLPRPL074W Replication conflict: a modify of 'entry name' was rejected because it had an older timestamp.
- GLPRPL075W Replication conflict: a conflict is detected on a modify operation of DN 'entry name'. The reason for this conflict is because the entry has been modified on this server before the entry was modified on the supplier.
- GLPRPL076W Replication conflict: a conflict is detected on a modify operation of DN 'entry name'. An earlier update on the supplier has not yet been applied to this server.
- GLPRPL078W The extended operation cannot replicate to target server host port port number because the target server does not support replication topology entries.
- GLPRPL079E The extended operation cannot replicate entries to the target server hostname port port number because the target server does not have the suffix suffix.
- GLPRPL083W Replication conflict: re-add of DN 'entry name' to host hostname port port number failed.
- GLPRPL084E Replication conflict: re-add of DN 'entry name' to resolve a conflict will not continue because the entry is too large.
- GLPRPL085E Unable to format a string requiring number of bytes bytes in only numberAvailable bytes.
- GLPRPL086E Attribute 'attribute name' is missing from entry 'entry DN'.
- GLPRPL087E The Replication Topology extended operation failed to quiesce the context entry name on host hostname port port number. The operation will not continue with this server.
- GLPRPL089E The Replication Topology extended operation failed to unquiesce the context entry name on host hostname port port number. The operation will not continue with this server.
- GLPRPL091E The Replication Topology extended operation failed to add a suffix entry name to the configuration file of target host hostname port port number. The operation will not continue with this server.
- GLPRPL093E The Replication Topology extended operation failed to purge the queue that is associated with the replication agreement entry name on host hostname port port number.
- GLPRPL095E The supplier of the Replication Topology extended operation failed to contact target host hostname port port number using replication agreement entry name.
- GLPRPL097E Error initializing or writing to the log used for replication conflict resolution.
- GLPRPL098E The Replication Topology extended operation timed out.
- GLPRPL100E The update logged as a failure with error ID error ID for replication agreement DN 'replication agreement' failed on attempt attempt number with LDAP return code LDAP error text.
- GLPRPL103E Unable to log failure in replication error log for replication agreement DN 'replication agreement for entry with change ID change id.
- GLPRPL104W Reached or exceeded the limit max replication errors for the replication error log for replication agreement DN 'replication agreement'.
- GLPRPL105W Approaching the limit max replication errors for the replication error log for replication agreement DN 'replication agreement'. The current number of logged failures is replication error count.
- GLPRPL110E Replication for DN 'replication agreement' terminated because of an unsupported replication method. method.
- GLPRPL111W Replication for DN 'replication agreement' set to use the limit of max connections for consumer connections.
- GLPRPL112W Replication for DN 'replication agreement' set to use the default number default connections for consumer connections.
- GLPRPL113E Unable to create replication agent on connection connection ID for DN 'replication agreement', replication terminating.
- GLPRPL115W Replication for DN 'replication agreement' encountered a gap in the change IDs: current change ID followed last change ID.
- GLPRPL116E Replication for DN 'replication agreement' encountered a gap in the change IDs: current change ID followed last change ID after trying one more time but is continuing.
- GLPRPL117E Unable to log additional replication failures in replication error log for replication agreement DN 'replication agreement because the number of logged entries exceeds the limit; replication is waiting for the log to be cleared.
- GLPRPL118E Replication for replica 'repl_agmt_dn' will continue to retry the same failed update with change ID change id until it is successful.
- GLPRPL119W Replica 'entry name' will use single-threaded, synchronous replication, instead of the method in the replication agreement.
- GLPRPL120E Error occurred processing the replica URL for replication agreement 'repl_agmt_dn'.
- GLPRPL121E The operation being performed on DN 'dn' is not allowed in a transaction.
- GLPRPL124W Change cannot be replicated because it contains attributes that require a secure connection.
- GLPRPL125E Cannot replicate to consumer because it does not support encrypted attributes. Replica: 'replication agreement'.
- GLPRPL126E Cannot replicate to consumer because it does not support the current password encryption setting. Replica: 'replication agreement'.
- GLPRPL127W Change cannot be replicated because consumer does not support encrypted attributes.
- GLPRPL129E Creation of surrogate entry 'entry name' on partial replica hostname port port number failed.
- GLPRPL131W The replication filter entry filter entry name defined for the replication agreement agreement entry name cannot be found.
- GLPRPL132E The replication filter entry filter entry name defined for the replication agreement agreement entry name cannot be found.
- GLPRPL133W The operational attribute op attr name specified as part of the replication filter inclusion/exclusion list is not allowed.
- GLPRPL138W Consumer server on host host name, port port number, does not support the requested password encryption format.
- GLPRPL139E The filter entry entry name is in use and cannot be deleted.
- GLPRPL141W Consumer server on host host name, port port number, does not support the requested attribute encryption format.
- GLPRPL142W Internal search for the parent entry dn failed.
- GLPRPL143E The attribute attribute name specified in the replication filter is not found in the schema.
- GLPRPL144E The objectclass objectclass name specified in the replication filter is not found in the schema.
- GLPRPL145E Invalid replication filter 'attribute value' specified in entry ' entry dn'.
- GLPRPL146W Replication conflict: modification to 'entry name' was rejected because it has modification timestamp equal to the target entry timestamp.
- GLPRPL147E Cannot replicate to consumer because it does not support SHA2 and Salted SHA2 algorithm families. Replica: 'replication agreement'.
- GLPRPL50E The value of the ibm-slapdMigrationInfo attribute must contain a valid server type.
- GLPRUN002E The idsrunstats tool is unable to run because of initialization error.
- GLPRUN004E Failed to retrieve the list of tables to update index statistics.
- GLPRUN007W Index statistics on table 'tabname' could not be updated at this time.
- GLPSCH001E Data source: file name: line line number: expected Object ID, but could not find it at or before variable.
- GLPSCH002E Data source: file name: line line number: expected one of the following: variables, but could not find it at or before variable.
- GLPSCH003E Data source: file name: line line number: expected digit after '.', but could not find it at or before variable.
- GLPSCH004E Data source: file name: line line number: expected non-empty quoted string, but could not find it at or before variable.
- GLPSCH005E Data source: file name: line line number: expected number after brace, but could not find it at or before variable.
- GLPSCH006E Data source: file name: line line number: expected '}' after '{ <number>', but could not find it at or before variable.
- GLPSCH007E Data source: file name: line line number: expected a quoted string, but could not find it at or before variable.
- GLPSCH008E Data source: file name: line line number: expected a quoted string or open parenthesis, but could not find it at or before variable.
- GLPSCH009E Data source: file name: line line number: expected an LDAP description string, but could not find it at or before variable.
- GLPSCH010E Data source: file name: line line number: expected a quoted LDAP description string, but could not find it at or before variable.
- GLPSCH011E Data source: file name: line line number: expected a quoted LDAP description string or open parenthesis, but could not find it at or before variable.
- GLPSCH012E Data source: file name: line line number: encountered non-terminated quoted string at or before variable.
- GLPSCH013E Data source: file name: line line number: encountered unexpected end of input.
- GLPSCH014E Data source: file name: line line number: input not valid at or before variable.
- GLPSCH015E Data source: file name: line line number: expected usage specification, but could not find it at or before variable.
- GLPSCH016E Data source: file name: line line number: expected one or two quoted strings (database table and/or column names), but could not find them at or before variable.
- GLPSCH017E Data source: file name: line line number: expected ACCESS-CLASS specification, but could not find it at or before variable.
- GLPSCH018E Data source: file name: line line number: variable variable has already been defined.
- GLPSCH019E Data source: file name: line line number: found duplicated definition for variable variable.
- GLPSCH020E Data source: file name: line line number: attribute type variable already has an IBM extended definition.
- GLPSCH021E Data source: file name: line line number: all alternate definitions of same variable must be in a single file. variable is also defined in variable.
- GLPSCH022E Data source: file name: line line number: inconsistent variable, variable and variable (with object ID variable).
- GLPSCH023E Data source: file name: line line number: variable variable does not have a syntax definition.
- GLPSCH024E Operation not valid. Expected one of the following operations: variable.
- GLPSCH025E variable variable not found when processing variable variable.
- GLPSCH026E variable variable does not exist; delete operation failed.
- GLPSCH027E variable variable does not exist; replace operation failed.
- GLPSCH028E variable variable does not have a syntax definition.
- GLPSCH029E Attempt to delete variable failed. The specified object ID object ID and name name do not refer to the same variable.
- GLPSCH030E Attempt to replace variable failed. The specified object ID object ID and name name do not refer to the same variable.
- GLPSCH031E variable variable already exists; add operation failed.
- GLPSCH032E variable variable cannot be deleted. It is still being used.
- GLPSCH033E Missing LDAP V3 specification for variable attribute.
- GLPSCH034E attribute variable and its supertype super have different usages.
- GLPSCH035E Cycle, attribute, detected in supertype specification.
- GLPSCH036E Cycle, class, detected in superclass specification.
- GLPSCH037E entity variable was not provided. Must be provided as quoted string.
- GLPSCH038E entity string must be provided as string, but was provided as string.
- GLPSCH039E string quoted string must be provided as string with inherited properties or IBM extensions string, but was provided as string with inherited properties or IBM extensions string.
- GLPSCH040E The IBM extension for string quoted string must be provided as string, but was provided as string.
- GLPSCH041E Data source: file name: line line number: expected ENCRYPT specification, but could not find it at or before variable.
- GLPSCH042E Data source: file name: line line number: expected RETURN-VALUE specification, but could not find it at or before variable.
- GLPSCH043E Attribute attribute name cannot be encrypted. The server does not support encryption for syntax syntax name.
- GLPSCH044E Attribute attribute name cannot be encrypted.
- GLPSCH046W matching rule type Matching Rule matching rule name for attribute attribute name is not compatible with its syntax syntax name
- GLPSCH047E Password attribute attribute name cannot be encrypted in the schema.
- GLPSCH049W matching rule type Matching Rule matching rule name for attribute attribute name is not consistent with other matching rules defined for this attribute in terms of case-sensitivity handling.
- GLPSCH050E Length attribute length for attribute attribute name is less than the minimum length of 32 for an AES-encrypted value.
- GLPSCH052W Invalid value 'value' set for attribute encryption. Assuming AES256 encryption format.
- GLPSRV005E Server was unable to decode input data from the client (connection ID: connid, IP address: )ip_addr, Port: port) while processing operation: operation.
- GLPSRV006E Unable to open file 'file'. Try specifying the full path name.
- GLPSRV007E Error while trying to allocate memory.
- GLPSRV008E Unable to create necessary thread.
- GLPSRV010E Server unable to start due to attribute dependency check failure.
- GLPSRV011E Server cannot use port port for both SSL and non-SSL.
- GLPSRV012E A primary administrator DN and administrator PW must be specified in the server configuration.
- GLPSRV013E Attempt to initialize administrative connection failed, error value (error string).
- GLPSRV014E An attempt to set a TCP/IP parameter has failed. The operating system returned error error value (error string).
- GLPSRV022E Failed to initialize secure connection from client (connection ID: connid, IP address: ip_addr, Port: port).
- GLPSRV027E Server failed to acquire Kerberos credential.
- GLPSRV028E Mapping from Kerberos principal to LDAP DN failed because more than one krbPrincipalName is found.
- GLPSRV029E SASL GSSAPI bind request from client failed due to a token that is not valid.
- GLPSRV030E Maximum operations per transaction maximum operations exceeded.
- GLPSRV031E Maximum number of transactions maximum transactions exceeded.
- GLPSRV032E Time limit of time limit for a transaction was exceeded and all of the operations in the transaction were rolled back.
- GLPSRV036E Errors were encountered while starting the server; started in configuration only mode.
- GLPSRV037E Failed to change file to file name.
- GLPSRV038W Using default file file name.
- GLPSRV039E Configuration entry: entry DN contains an line that is not valid: entry attribute : attribute value
- GLPSRV040E Server starting in configuration only mode due to errors.
- GLPSRV042W Server responding to a large backlog of requested client operations. There are number of pending requests pending requests.
- GLPSRV043W Server response to the backlog of requested client operations has completed. number of completed requests requests completed.
- GLPSRV044W Client connection from IP address bound as bind DN closed by server.
- GLPSRV045W Automatically closed number of connections idle client connections.
- GLPSRV046W No anonymous binds will be allowed.
- GLPSRV047W Anonymous binds will be allowed.
- GLPSRV051W Anonymous binds will no longer be accepted. Closed number of connections existing anonymous client connections; number of connections will be closed as soon as possible.
- GLPSRV052W Processing unbind request from the directory administrator. Closed number of connections client connections; another number of connections client connections will be closed as soon as possible.
- GLPSRV053E Server unable to respond to the large backlog of client requests.
- GLPSRV054E Unable to enable tracing dynamically.
- GLPSRV056E Server unable to disable tracing dynamically.
- GLPSRV058E Unable to set debug level for server debugging.
- GLPSRV059W Debug level set to debug_output_level.
- GLPSRV060E Unable to set debug output file name for the server.
- GLPSRV062E Attribute attribute name in entry entry name specified the Kerberos ID for an administrator incorrectly.
- GLPSRV063E Unable to complete registration of all supported features.
- GLPSRV064E Failed to initialize plugin name.
- GLPSRV065E Values for the attribute attribute name are not unique. The attribute attribute name was removed from the unique attribute entry: entry name.
- GLPSRV066E DIGEST-MD5 bind attempt failed because the value for the component name component in the response was not valid.
- GLPSRV067E DIGEST-MD5 bind attempt for username was unsuccessful because the username did not match an entry.
- GLPSRV068E DIGEST-MD5 bind attempt for username was unsuccessful because the username matched more than one entry.
- GLPSRV069E DIGEST-MD5 bind attempt was unsuccessful because the response from the client was improperly formatted.
- GLPSRV070E DIGEST-MD5 bind attempt for username was unsuccessful because the password was incorrect.
- GLPSRV071E DIGEST-MD5 bind attempt for username was unsuccessful because the user did not have proxy authority.
- GLPSRV072E Mapping from Kerberos principal to LDAP DN failed because more than one altSecurityIdentities exists.
- GLPSRV073E Attribute attribute name in entry entry name specified the Kerberos ID for an administrator incorrectly.
- GLPSRV074E Attribute attribute name in entry entry name specified the Kerberos ID for an administrator incorrectly.
- GLPSRV075E Bad Administrator Kerberos ID defined in attribute attribute name in entry entry name. The Kerberos ID must start with 'ibm-kn=' or 'ibm-kerberosName='.
- GLPSRV076E Transaction time limit of time limit exceeded. No future operations requested in this transaction are allowed. Transaction rolled back.
- GLPSRV077E Unable to enable tracing at startup.
- GLPSRV078W Server trace enabled.
- GLPSRV079E Unable to set the server debug level at startup.
- GLPSRV080W Server debug level set to debug_output_level.
- GLPSRV081E Unable to set the server debug output file name at startup.
- GLPSRV083E Unable to enable server tracing as requested on the command line.
- GLPSRV084W Trace enabled from command line.
- GLPSRV085E An attempt to set the TCP/IP keep alive option has failed. The operating system returned error error value (error string).
- GLPSRV087E The -a and -n options cannot be used together.
- GLPSRV088E The server is unable to run because of initialization error.
- GLPSRV089E Server unable to start because the server could not write to the slapd.pid file.
- GLPSRV090E Maximum number of operations per transaction, maximum operations, exceeded.
- GLPSRV091E Null based one level search is not supported.
- GLPSRV092E No values for type attribute name.
- GLPSRV093E version number is an unsupported LDAP version.
- GLPSRV094E The value attribute value is not a valid value for attribute ibm-slapdServerBackend. The attribute takes either "RDBM", "PROXY" or "FDPROXY" as its values.
- GLPSRV095E Plugin type plugin type with path plugin path is not supported. Plugin not loaded.
- GLPSRV096E Bind attempt by DN DN and source IP address IP Address was unsuccessful.
- GLPSRV097E Internal processing error in the server; return code return code from pthread library.
- GLPSRV099E Unable to open audit log file 'filename'.
- GLPSRV100E Audit log file 'filename' is full, unable to log any more records.
- GLPSRV101E Problems retrieving entry 'entry DN' in the server configuration.
- GLPSRV103E Found an unknown attribute 'attribute name' in entry 'entry DN'.
- GLPSRV106E Communications error: error string.
- GLPSRV114E Server failed to start normally with SSL; starting in configuration only mode without SSL.
- GLPSRV115E The operator is not in the same primary group as the directory server instance owner 'instance name'. Only users in the same primary group as the directory server instance owner can start a directory server instance.
- GLPSRV119E Failed to create Windows service for directory server instance: 'instance name'.
- GLPSRV122E Failed to stop directory server instance: 'instance name'.
- GLPSRV123E Unable to stop directory server instance 'instance name' because the state of the server cannot be determined.
- GLPSRV126E Failed to delete Windows service for directory server instance: 'instance name'.
- GLPSRV127E The -k and -i options cannot be used together.
- GLPSRV128E The -k and -u options cannot be used together.
- GLPSRV129E The -i and -u options cannot be used together.
- GLPSRV131E The -k and -c options cannot be used together.
- GLPSRV132E The -k and -a options cannot be used together.
- GLPSRV133E The -k and -n options cannot be used together.
- GLPSRV135E A problem was encountered while retrieving server configuration entries for subtree 'subtree DN'.
- GLPSRV136E text
- GLPSRV137E The Administrative Password Policy settings in the server configuration are not valid.
- GLPSRV138W A client connection from IP address bound as bind DN closed by the server.
- GLPSRV139W A client connection from IP address bound as bind DN closed by the server.
- GLPSRV140E An unsupported operation was requested within a transaction. Transaction transaction ID rolled back.
- GLPSRV141E An unsupported operation was requested within a transaction after a prepare transaction extended operation request. Transaction transaction ID rolled back.
- GLPSRV142E An unsupported extended operation was requested within a transaction after a prepare transaction extended operation request. Transaction transaction ID rolled back.
- GLPSRV143E Transaction time limit between prepare and commit or roll back exceeded. Transaction transaction ID rolled back.
- GLPSRV144E Extended operation OID failed, option decimal option is not valid for this request.
- GLPSRV145E The modify request failed because proxy split name is not unique.
- GLPSRV146E The add request failed because proxy split name is not unique.
- GLPSRV147W Connection write time limit exceeded. Connection from IP address bound as bind DN will be closed.
- GLPSRV148W Transaction with ID transaction ID submitted by bind DN will be rolled back due to an error (LDAP error) in an operation.
- GLPSRV149E Ulimit entry entry DN is not present in the server configuration.
- GLPSRV150E Input not valid for option ulimit option.
- GLPSRV151E Prescribed soft limit is out of range or greater than hard limit value for option ulimit option.
- GLPSRV153W The server was not able to accept a requested client connection. The maximum capacity of message has been reached. This error has occurred message times.
- GLPSRV154E A new persistent search request could not be handled by the server.
- GLPSRV161W There are no Administrative Password Policy settings in the server configuration.
- GLPSRV162W Referral 'referral' not valid.
- GLPSRV163E Pass-through bind failed on 'URL' for entry 'bind DN'.
- GLPSRV164E Pass-through bind failed because the attribute 'attribute name' has multiple values in entry 'EntryDN'.
- GLPSRV165E Pass-through authentication failed due to a timeout.
- GLPSRV166E The pass-through search to get mapped DN for the bind DN 'bind DN', returned more than one entry.
- GLPSRV167E Nested subtrees '1st subtree DN' and '2nd subtree DN' found in pass-through authentication configuration.
- GLPSRV168E Attribute mapping is configured for attribute 'attribute name', which is not present in the schema.
- GLPSRV169W Attribute mapping is configured for attribute 'attribute name', which is not present in the schema for pass-through directory server 'URL'.
- GLPSRV170E Attribute name 'attribute name' that is not valid specified in attribute mapping.
- GLPSRV171E Specified attribute mapping 'attribute map' is not valid.
- GLPSRV172E Pass-through attribute mapping is configured for bind DN 'bind DN' but the entry is missing.
- GLPSRV173E Value for attribute 'attribute name' not valid in entry 'entry DN'.
- GLPSRV174E Pass-through subtree 'subtree DN' conflicts with restricted subtree 'restricted subtree DN'.
- GLPSRV175W Unable to check schema of pass-through directory 'URL' for attribute 'attribute name', received return code LDAP return code.
- GLPSRV177W Directory server instance unable to shut down; exiting now.
- GLPSRV178E Internal error while processing plugin type plugin type with path plugin path.
- GLPSRV179E The pass-through URL 'URL' is not valid.
- GLPSRV181E The pass-through authentication bind failed during attribute mapping with rc=rc.
- GLPSRV182E Failed to connect to pass-through directory 'URL'.
- GLPSRV183E Unable to modify log path to 'path' for the 'entry DN'. The file already exists on the system.
- GLPSRV184E Unable to modify log path to 'path' for the 'entry DN'. The 'entry DN' entry is already configured with that log file path.
- GLPSRV185E Unable to modify log path to 'path' for the 'entry DN'. The file cannot be written to.
- GLPSRV186W The proxy server has temporarily suspended reading client requests from the network.
- GLPSRV188E Sort control missing in virtual list view search request.
- GLPSRV191E Terminating server because of initialization errors.
- GLPSRV192E Server is unable to start because the server could not write to the slapd.properties file.
- GLPSRV203W The server has temporarily suspended reading client requests from the network. There are number of writewaiters of number of total workers worker threads attempting to write results.
- GLPSRV204W The server has temporarily suspended reading client requests from the network number of times times. There are number of writewaiters of number of total workers worker threads attempting to write results.
- GLPSRV208W Persistent search is not supported on subtree dn.
- GLPSRV209W Message for support team: additional text.
- GLPSRV217W Invalid value 'value' set for ibm-slapdPwEncryption attribute. Assuming AES256 encryption format.
- GLPSRV218E User provided encrypted string is badly formatted.
- GLPSRV224E No entry matching the search criterion 'value' was found.
- GLPSRV225E Too many entries matching the search criterion 'value' were found.
- GLPSRV226E The maximum filter limit that is set in IDS_MAX_SEARCH_FILTER_LEVEL, max filter exceeded for the search on the host, host with conn id, conn id and is bound with dn=dn
- GLPSSL002E File I/O error on opening SSL key database file key database filename.
- GLPSSL003E Open of SSL key database file key database filename failed.
- GLPSSL004E SSL key database file key database filename is in an unknown format.
- GLPSSL005E The password supplied for key database file key database filename is not correct.
- GLPSSL006E A memory allocation error occurred processing SSL key database file key database filename.
- GLPSSL007E SSL socket initialization failed due to a problem with creating the key pair.
- GLPSSL008E An incorrect label was specified for SSL key database key database filename.
- GLPSSL009E An incorrect value of cipher spec was given for the SSL cipher specification.
- GLPSSL010E No SSL ciphers were specified.
- GLPSSL011E The certificate in the SSL key database file key database filename has expired.
- GLPSSL012E The certificate certificate label in the SSL key database file is not valid.
- GLPSSL013E The certificate is of an unsupported type in the SSL key database file key database filename.
- GLPSSL014E No certificate exists in SSL key database file filename.
- GLPSSL015E The underlying secure socket was closed.
- GLPSSL016E An SSL error of error code was encountered contacting consumer server host name, port port number.
- GLPSSL017E The required SSL shared libraries could not be loaded.
- GLPSSL018E The required SSL shared libraries encountered an internal load error.
- GLPSSL019E The SSL layer has reported an unidentified internal error, SSL extended error code:error code.
- GLPSSL020E The SSL layer has reported a bad parameter.
- GLPSSL021E An attempt has been made to use a domestic key database with an export version of the SSL library.
- GLPSSL022E Secure socket client authentication error occurred.
- GLPSSL023W Attempted to configure server for SSL in a non-SSL version of the product.
- GLPSSL024E Failed to start with SSL. Starting in configuration only mode without SSL.
- GLPSSL026E SSL socket initialization failed due to a problem with creating a handle.
- GLPSSL027E SSL socket initialization failed due to a problem with initializing a handle.
- GLPSSL031W The server is operating in FIPS mode for the SSL layer but not the underlying cryptographic layer.
- GLPSSL033E Unable to load the specified PKCS#11 library library.
- GLPSSL034E A PKCS#11 token token is not present in the slot.
- GLPSSL035E The password/pin to access the PKCS#11 token is not valid.
- GLPSSL036E A PKCS#11 token label token label is not valid.
- GLPSSL038W Unable to start the server in FIPS Mode. Turning off the FIPS Support.
- GLPSSL040E An incorrect value of protocol was given for the security protocol specification.
- GLPSSL041E An incorrect value of mode was given for the Suite B specification.
- GLPSSL042E An incorrect value of sigalg was given for the signature algorithm specification.
- GLPUCH004E Failed to remove change log from directory server instance: 'instance name'.
- GLPUCH007E Failed to unconfigure change log database 'database name' for directory server instance: 'DB2 instance'.
- GLPUCH008E A change log database is not configured for directory server instance 'instance name'.
- GLPUCH009E A database instance is not configured for directory server instance 'instance name'.
- GLPUCH010E Unable to unconfigure the change log. No change log is configured for directory server instance 'instance name'.
- GLPUCH012E An internal error occurred while running the idsucfgchglg command.
- GLPUCH013W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPUDB004E Failed to remove the DB2 database from directory server instance: 'instance name'.
- GLPUDB007E Failed to unconfigure database 'database name' for directory server instance: 'DB2 instance'.
- GLPUDB008E A database is not configured for directory server instance 'instance name'.
- GLPUDB009E Failed to unconfigure local loopback for directory server instance: 'instance name'.
- GLPUDB010E A database is not configured for directory server instance 'instance name'.
- GLPUDB011E A database instance is not configured for directory server instance 'instance name'.
- GLPUDB012E An internal error occurred while running the idsucfgdb command.
- GLPUDB013W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPUDB014E Unable to unconfigure database. No database is configured for directory server instance 'instance name'.
- GLPUDB024E Inactive logs for directory server instance 'instance name' could not be removed from location 'inactive log path'.
- GLPUDB025E The database backup file for directory server instance 'instance name' named 'backup file name' could not be removed.
- GLPUSC002E An internal error occurred while running the idsucfgsch command.
- GLPUSC003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPUSC006E Failed to remove schema file: 'schemafile'.
- GLPUSC008E The schema file 'schemafile' does not exist in the configuration file of the directory server instance.
- GLPUSC009E Deletion of a system defined schema file 'schemafile' is not allowed.
- GLPUSC010E The -s option is required and is used to specify the name of the schema file to remove.
- GLPUSF002E An internal error occurred while running the idsucfgsuf command.
- GLPUSF003W The program did not complete successfully. View earlier error messages for information about the exact error.
- GLPUSF006E Failed to remove suffix: 'suffix'.
- GLPUSF008E The suffix 'suffix' does not exist in the configuration file of the directory server instance.
- GLPUSF009E Deletion of the system defined suffix 'suffix' is not allowed.
- GLPUSF010E The -s option is required and is used to specify the name of the suffix to remove.
- GLPWCO002E Select an entry.
- GLPWCO003E Cannot connect to the server.
- GLPWCO005E Select a row.
- GLPWCO006E The server is running in configuration only mode. This task cannot be initialized.
- GLPWCO008E A server with the same hostname and port already exists.
- GLPWCO009E The administration port specified is already in use.
- GLPWCO010E Authentication error: Either the user name or password (or both) is incorrect, or the password has expired.
- GLPWCO011E Communications error: Unable to connect to the specified LDAP server.
- GLPWCO012E Login failed: The server is currently unwilling to accept the bind. The specified account might be locked.
- GLPWCO013E LDAP server error: Unable to connect to the specified LDAP server using the existing connection settings.
- GLPWCO014E Internal error: An internal error occurred while trying to authenticate the user.
- GLPWCO015E Parameter error: Either the user name or the password or both were not specified.
- GLPWCO016E Unknown error: Attempted to access this page without all required parameters.
- GLPWCO017E The current user does not have access to this page. Current session might have timed out.
- GLPWCO018E Error: Current password incorrect.
- GLPWCO019E Error: Confirmation password incorrect.
- GLPWCO020W Are you sure you want to delete the selected server?
- GLPWCO021E Unauthorized access. The user is not a console administrator.
- GLPWCO022W The password must be changed before access can be granted to the LDAP data.
- GLPWCO023W The account is locked.
- GLPWCO024W The password was reset and must be changed now.
- GLPWCO025W The password cannot be changed. The user does not have the authority to modify the password.
- GLPWCO026W The current password was not supplied or is not correct.
- GLPWCO027W Incorrect password syntax.
- GLPWCO028W The password is too short.
- GLPWCO029W The current password is not old enough and cannot be changed at this time.
- GLPWCO030W The password specified is incorrect. The password has already been used.
- GLPWCO031W number of binds LDAP binds remain before the account will be locked.
- GLPWCO032W Password will expire after number of seconds seconds.
- GLPWCO033E Connected to administration server. This task cannot be initialized.
- GLPWCO034E Server with the same server name already exists.
- GLPWCO035W Connected to administration server. Not all operations are available.
- GLPWCO036E Incorrect port in Server entry.
- GLPWCO037E Incorrect server entry. Provide the server entry in the following format 'hostname:port'.
- GLPWCO038W Changes made to the schema are not propagated to the back-end servers. For changing the schema of the back-end servers, changes must be made on the back-end servers.
- GLPWCO039E Key database password does not match.
- GLPWCO040E Trust database password does not match.
- GLPWCO041E Insufficient access rights.
- GLPWCO042E Password is required if an ssl key database path is specified.
- GLPWCO043E SSL key database path is required if the password for an ssl key database file is specified.
- GLPWCO044E SSL key database file name is not valid.
- GLPWCO045E Password is required if an trust database path is specified.
- GLPWCO046E Trust database path is required if the password for an trust database file is specified.
- GLPWCO047E Trust database file name is not valid.
- GLPWDM001E An error occurred connecting to server server name: error.
- GLPWDM002E An error occurred while disconnecting from the server server name: error.
- GLPWDM003E An error occurred while adding entry entry DN : error.
- GLPWDM004E An error occurred while deleting the entry DN. The logged in user cannot delete that user's own entry.
- GLPWDM005E An error occurred while deleting entry entry DN: error.
- GLPWDM006E The language tag already exists: tag.
- GLPWDM007E Entry already exists: entry DN.
- GLPWDM008E The user already exists: user DN.
- GLPWDM009E The group already exists: user DN.
- GLPWDM010E Cannot delete non-leaf node entry entry DN.
- GLPWDM011E Missing required attributes on entry entry DN: error.
- GLPWDM012E Error: Entry entry DN does not exist.
- GLPWDM013E The current operation cannot continue.
- GLPWDM014E An error occurred opening the context for server server name: error.
- GLPWDM015E An error occurred while retrieving attributes for entry : error.
- GLPWDM016E An error occurred setting attributes for entry : error.
- GLPWDM017E Editing RDN entry entry DN failed.
- GLPWDM018E An error occurred renaming entry entry DN: error.
- GLPWDM019E The context was null on entry entry DN.
- GLPWDM020E An error occurred while performing a search operation on the directory server.
- GLPWDM022E An error occurred while retrieving attributes for the rootDSE search on server server name: error
- GLPWDM023E Unable to read any naming context from the directory server.
- GLPWDM024E Unable to read any subschemaSubentry from the directory server.
- GLPWDM026E An error occurred searching server server name: error.
- GLPWDM027E An error occurred while browsing search results for server server name: error.
- GLPWDM028W An error occurred while retrieving entries. The server does not support paging, sorting, or both. Displaying the first number entries: error.
- GLPWDM029E The search base DN entry DN does not exist.
- GLPWDM030E Encountered unknown attribute: attribute ID.
- GLPWDM032E Incorrect input ACL DN.
- GLPWDM033E Error: incorrect input ACL DN details.
- GLPWDM035W Are you sure you want to delete the entry : entry?
- GLPWDM036W Are you sure you want to delete the selected static group DN?
- GLPWDM037W Are you sure you want to delete the selected member?
- GLPWDM038W Are you sure you want to delete the selected entry : Entry DN ?
- GLPWDM039W Are you sure you want to delete the selected non-leaf node and all its children : Entry DN ?
- GLPWDM041E A leaf node cannot be expanded.
- GLPWDM042E Incorrect group name.
- GLPWDM043E Select an attribute from the Available attributes list to add to the Selected required attributes list.
- GLPWDM044E Select an attribute to be removed from the Selected required attributes list.
- GLPWDM045E Select an attribute from the Selected required attributes list to move it to the Selected optional attributes list.
- GLPWDM046E Select an attribute from the Available attributes list to add to the Selected optional attributes list.
- GLPWDM047E Select an attribute to be removed from the Selected optional attributes list.
- GLPWDM048E Select an attribute from the Selected optional attributes list to move it to the Selected required attributes list.
- GLPWDM049E Collapse operation cannot occur. The top-level entries are already displayed.
- GLPWDM050E No auxiliary object classes are available to be deleted.
- GLPWDM051E Not a valid user.
- GLPWDM052W Are you sure you want to delete the selected auxiliary object classes ?
- GLPWDM053E Cannot read all ACL information. Contact the directory server administrator to check the ACLs for this entry.
- GLPWDM054E Cannot read all Owner information. Contact the directory server administrator to check the owners on this entry.
- GLPWDM055E The syntax of the language tag is incorrect.
- GLPWDM056E Enter a search condition.
- GLPWDM057E Enter a search condition.
- GLPWDM058E This value already exists. Add a different value.
- GLPWDM059E No value was specified for the Value field.
- GLPWDM060E No value is specified for the Subject DN field on the Owners panel.
- GLPWDM061E No value is specified for the Group DN field on the Static memberships panel.
- GLPWDM062E No value is specified for the attribute to be added on the Enter multiple values panel.
- GLPWDM063E No value is specified for the given attribute in the Value field on the Language tag values panel.
- GLPWDM064E No value is specified for the Nested group DN field on the Nested groups panel.
- GLPWDM065E No value is specified for the member field of Static group members panel.
- GLPWDM066E No value is specified for the uniqueMember field on the Static group members panel.
- GLPWDM067E All fields on the Required attributes page are required.
- GLPWDM068E The RDN must be provided.
- GLPWDM069E Select at least one auxiliary object class for deletion.
- GLPWDM070E All the users under the realm are already members of the selected group. No more users can be added to this group.
- GLPWDM071E ACLs cannot be edited for entries under cn=configuration
- GLPWDM072E The DN Subject DN is not valid for the type Subject Type.
- GLPWDM073E The current server data will be loaded. However, there are pending changes that are not yet saved in the current group memberships table of the Static memberships panel. Do you want to make these changes?
- GLPWDM074E The current server data will be loaded. However, there are pending changes that are not yet saved in the static group members table of the Static group members panel. Do you want to retain these changes?
- GLPWDM075E The current server data will be loaded. However, there are pending changes that are not yet saved in the unique members table of Static group members panel. Do you want to retain these changes?
- GLPWDM076E The selected entry is not a group. This option is not valid. Select a group entry or make this entry a group by adding appropriate auxiliary classes.
- GLPWDM077E Incorrect DN entry. Specify a valid DN.
- GLPWDM078W The directory server entries have not been loaded into the table. Only the user changes will be removed from the table. Are you sure you want to remove all the entries in the table?
- GLPWDM079E Cannot remove a MUST attribute: attribute name
- GLPWDM080E Are you sure you want to remove all the table entries?
- GLPWDM081E Possible duplicate value(s) exist for attribute name attribute on the server: server name
- GLPWDM082E One or more of the entries selected in the table already exist and will be ignored.
- GLPWDM083E The value entered is not a valid static group DN. Specify a valid static group entry.
- GLPWDM084E An error occurred in the Referral panel while retrieving the list of attributes from the directory server.
- GLPWDM085E Incorrect Base DN.
- GLPWDM086E Malformed referral URL.
- GLPWDM087E Date format is incorrect. Provide the date value in date format format for column ''column''.
- GLPWDM088W Are you sure you want to delete the selected binary data entry?
- GLPWDM089E File cannot be uploaded on Web server or file not found.
- GLPWDM091E Select a binary data entry to delete.
- GLPWDM092E Select only one binary data entry to export.
- GLPWDM096W Are you sure you want to remove all the encrypted attributes?
- GLPWDM097E Not a valid realm location. The Parent DN field value is not allowed.
- GLPWDM099E Not a valid template location. The Parent DN field value is not allowed.
- GLPWDM100E A template or entry with the same name already exists in the specified location.
- GLPWDM101E Incorrect administrator group container location.
- GLPWDM102E Incorrect user container location.
- GLPWDM103E Not a valid group container location.
- GLPWDM104E This template is in use by one or more realms and cannot be deleted.
- GLPWDM105E The specified administrator group is not a group.
- GLPWDM106E The selected tab name tab cannot be moved.
- GLPWDM107E The selected tab cannot be moved down because the tab is already at the bottom of the list.
- GLPWDM108E A tab with this name already exists.
- GLPWDM109E The tab name cannot be renamed. A tab with this name already exists.
- GLPWDM110W Are you sure you want to delete the selected tab?
- GLPWDM111E The tabs NOT_DISPLAYED and REQUIRED cannot be deleted.
- GLPWDM112E All required attributes must be on a displayed tab.
- GLPWDM113E No naming attribute was found in the selected object classes. Select object classes with at least one naming attribute.
- GLPWDM114E There is no template associated with this realm
- GLPWDM115E An error occurred while adding the user to the group.
- GLPWDM116E An error occurred while removing the user from the group.
- GLPWDM117E No realms were found. Add a realm and then access the selected panel.
- GLPWDM119E Some of the changes could not be saved.
- GLPWDM120W The entry entry DN has been successfully added. Would you like to add a similar entry?
- GLPWDM121E Select an object class.
- GLPWDM122E No value was specified for the Value field.
- GLPWDM124E Select a role for the administrative group member.
- GLPWDM125E Member member does not exist in the Directory Information Tree (DIT).
- GLPWDM126W Not all values are fetched for this entry. Displaying number of values fetched of total number of values total values.
- GLPWDM127E Incorrect search filter filter for users in the realm realm name : error message.
- GLPWDM128E Illegal combination for the attribute.
- GLPWDM129E Are you sure you want to delete selected ACL objects ?
- GLPWRM001E Select a node in the tree.
- GLPWRM002E Failed to suspend replication for selected replication agreement.
- GLPWRM003E Failed to resume replication for selected replication agreement.
- GLPWRM004E Failed to force replication for selected replication agreement.
- GLPWRM005E Failed to skip the blocking unreplicated change for the selected replication agreement.
- GLPWRM006E Failed to skip all unreplicated changes for selected replication agreement.
- GLPWRM008E Failed to configure subtree as a replication context.
- GLPWRM009E Failed to modify the selected replication context.
- GLPWRM010E Unable to add the default group under the replicated subtree.
- GLPWRM011E Connected to administration server. Replication management cannot function in this mode.
- GLPWRM012E Unable to add the subentry: subentry.
- GLPWRM013E Unable to delete the subentry: subentry.
- GLPWRM014E Unable to add the agreement: agreement name.
- GLPWRM015E Unable to edit the agreement: agreement name.
- GLPWRM016E Unable to delete the agreement: agreement name.
- GLPWRM017E Unable to add the daily schedule: schedule name.
- GLPWRM018E Unable to edit the daily schedule: schedule name.
- GLPWRM019E Unable to copy the daily schedule: schedule name.
- GLPWRM020E Server is running in configuration only mode. Replication management cannot function in this mode.
- GLPWRM021E Unable to add the weekly schedule: schedule name.
- GLPWRM022E Unable to edit the weekly schedule: schedule name.
- GLPWRM023E Unable to delete the replication filter object.
- GLPWRM024E Unable to edit the replication filter object.
- GLPWRM025E Unable to retrieve the suffixes from the server.
- GLPWRM026E Unable to get the list of available daily schedules from the server.
- GLPWRM027E Unable to retrieve the list of available weekly schedules from the server.
- GLPWRM028E Unable to get the list of available credentials from the server.
- GLPWRM029E Unable to get the server ID of the server you are connected to.
- GLPWRM030E Unable to get the server ID of the replica server.
- GLPWRM031E Unable to get server ID of the master server. A valid server ID must be provided for a peer master topology to work.
- GLPWRM032E Unable to get the hostname of the server.
- GLPWRM033E Unable to add the ibm-slapdSupplier credential object.
- GLPWRM034E Unable to modify the ibm-slapdSupplier credential object.
- GLPWRM035E Unable to delete the ibm-slapdSupplier credential object.
- GLPWRM036E Unable to add the ibm-slapdReplication credential object.
- GLPWRM037E Unable to modify the ibm-slapdReplication credential object.
- GLPWRM038E Unable to delete the ibm-slapdReplication credential object.
- GLPWRM039E Unable to add the simple credential.
- GLPWRM040E Unable to add the replication filter object.
- GLPWRM041E Unable to modify the simple credential.
- GLPWRM042E Unable to add the Kerberos credential.
- GLPWRM043E Unable to modify the Kerberos credential.
- GLPWRM044E Unable to add the SSL credential.
- GLPWRM045E Unable to modify the SSL credential.
- GLPWRM046E Unable to delete the credential object.
- GLPWRM047E Unable to add the container object under localhost.
- GLPWRM048E Unable to quiesce the subtree.
- GLPWRM049E Unable to unquiesce the subtree.
- GLPWRM050E Unable to get the credential object from the server.
- GLPWRM051E Error in retrieving the enabled capabilities from the root DSE.
- GLPWRM052E Unable to get the values from cn=replication, cn=configuration.
- GLPWRM053E Unable to set the values in cn=replication, cn=configuration.
- GLPWRM054E Unable to search for the replication container object under localhost.
- GLPWRM055E Unable to search for the default group under the replicated subtree.
- GLPWRM056E Unable to search for the replicated subtrees under the suffixes.
- GLPWRM057E Unable to convert the string to name.
- GLPWRM058E Unable to search for the master credential object.
- GLPWRM059E Unable to search for the supplier credential objects.
- GLPWRM060E Unable to search the directory.
- GLPWRM061E Daily schedule daily schedule name has been deleted.
- GLPWRM062E The selected string is not a schedule.
- GLPWRM063E The cascading replication extended operation failed.
- GLPWRM064E Server server name reported an error from server server name. The logged-in user does not have authority to perform this operation.
- GLPWRM065E error message replica details agreement DN details
- GLPWRM066E Replication context is already in the requested state.
- GLPWRM067E The specified change is not the next change to replicate. The server might already have replicated this change.
- GLPWRM068E Server server name reported an error from server server name. Operation did not complete within the specified time.
- GLPWRM069E Replication from supplier replica supplier replica to consumer replica consumer replica did not complete.
- GLPWRM070E Server server name reported an error from server server name. Operation failed with result code result code.
- GLPWRM071E 'Create missing parent entries' will only be considered when replication filter DN is specified.
- GLPWRM072E Error occurred on the agreement to server server name.
- GLPWRM073E Unable to add the container object under IBMpolicies.
- GLPWRM074E Unable to search for the replication container object under IBMpolicies.
- GLPWRM075E Entry already exists in the list.
- GLPWRM076E Error occurred setting the gateway and master servers.
- GLPWRM078E Master DN cannot be the same as the administrator DN.
- GLPWRM079E Replication error control extended operation failed.
- GLPWRM080E Schedule does not exist or was deleted.
- GLPWRM081E Failed to create topology on consumer consumer name. Synchronize the topology on the new server. Refer to the IBM Security Directory Server Installation and Configuration Guide for instructions.
- GLPWRM082E Failed to create supplier credentials on consumer consumer name. The supplier credentials must be created on the consumer for replication to work. Refer to the IBM Security Directory Server Administration Guide for instructions.
- GLPWRM083E Failed to connect to consumer server consumer name.
- GLPWRM084E Failed to start consumer server consumer name.
- GLPWRM085E Cannot connect to administration server.
- GLPWRM086E Failed to restart to consumer server server name.
- GLPWRM088E The server server name is a proxy server. A proxy server cannot be added to the replication topology
- GLPWRM089E Cannot move source server because there are agreements associated with it.
- GLPWRM090E The requested operation cannot be performed. The server being promoted is already a master server.
- GLPWRM091E The requested operation cannot be performed. The old and new suppliers cannot both be master servers.
- GLPWRM092E Cannot connect to server. The manage topology function must connect to the server being promoted to perform this operation.
- GLPWRM093E The selected node cannot be deleted.
- GLPWRM094W Consumer server server name must be restarted for the supplier credential to take effect. Do you want to restart the server?
- GLPWRM095E Cannot edit the ACL for this subtree. One can only edit the ACL on a server that is a master server for this subtree.
- GLPWRM096E The selected node cannot be moved.
- GLPWRM097E Cannot delete a node that has agreements under it.
- GLPWRM098E The selected node cannot be edited.
- GLPWRM099E Hostname or port not provided.
- GLPWRM100E Referral LDAP URL not valid.
- GLPWRM101E Cannot delete this subtree. There are non-empty ibm-replicaGroup objects under this replication context.
- GLPWRM102E The entry does not exist or the logged-in user does not have sufficient authority to perform this operation.
- GLPWRM103E No credential selected to edit.
- GLPWRM104E No credential selected.
- GLPWRM105E Cannot create replicated subtree at subtree DN. Access control is not defined properly for this entry.
- GLPWRM106E Failed to promote a replica under a master server. There is no replica subentry corresponding to the server to which the Web Administration Tool is connected.
- GLPWRM107E Agreement agreement name does not have a valid replica ID defined. First set the replica ID in all agreements supplying agreement name. If there are multiple masters, it might be necessary to change this agreement under each master.
- GLPWRM108E Cannot promote server to master. The server being promoted must be a leaf replica with no subordinate replicas.
- GLPWRM109E This server cannot be promoted to a master server.
- GLPWRM110E The source server and the destination server are the same. Select a different destination server.
- GLPWRM111E Unable to delete the subtree
- GLPWRM112E Unable to get ACL information.
- GLPWRM113E The time selected has already been scheduled.
- GLPWRM114E Select a subtree.
- GLPWRM115E Select an entry in the table to remove.
- GLPWRM116E Unable to add schedule. The schedule object schedule object name already exists.
- GLPWRM117E Master DN cannot be the same as the administrator DN.
- GLPWRM118E Default credential has already been deleted.
- GLPWRM119E Passwords do not match.
- GLPWRM120E Select an entry in the list.
- GLPWRM121E The subtree subtree DN already has a supplier object associated with it. Choose a different replicated subtree.
- GLPWRM122E Replica bind DN is a required field.
- GLPWRM123E Bind password is a required field.
- GLPWRM124E This subtree was originally created as a non-replicated subtree. To create credentials in this subtree, the subtree must be initialized for replication with this server as the master. Click OK to initialize the subtree.
- GLPWRM125E Confirm password is a required field.
- GLPWRM126E Passwords do not match.
- GLPWRM127E Simple bind credential details not specified.
- GLPWRM128E Credential not selected.
- GLPWRM129E Select a replication filter.
- GLPWRM130E Unable to add the credential. The credential object credential object name already exists.
- GLPWRM131E Unable to add the replication filter. The filter object filter object name already exists.
- GLPWRM132E Select at least one object class or select the check box to include all object classes.
- GLPWRM133E Select at least one attribute or select the check box to include all attributes.
- GLPWRM134W You have requested to skip all unreplicated changes for this agreement.Click OK to continue with this request, or click Cancel.
- GLPWRM136W Are you sure you want to delete the selected node node names from the topology ?
- GLPWRM137W Warning: All the agreements under the selected master will be deleted. Are you sure you want to continue?
- GLPWRM138W This subtree is a non-replicated subtree. To edit ACLs for this subtree, the subtree must be initialized for replication with this server as the master. Click OK to continue.
- GLPWRM139W The current server to which you are connected to will become a master for this subtree. Are you sure you want to continue?
- GLPWRM140W If you cancel this request, the new server will not be added to the topology. Are you sure you want to cancel?
- GLPWRM141W If you cancel this request, the move operation will not be completed. Are you sure you want to cancel?
- GLPWRM142W Are you sure you want to quiesce the subtree subtree DN?
- GLPWRM143W Are you sure you want to delete the subtree subtree DN?
- GLPWRM144W Are you sure you want to unquiesce the subtree subtree DN?
- GLPWRM145W Are you sure you want to delete this daily schedule?
- GLPWRM146W Are you sure you want to delete this weekly schedule?
- GLPWRM147W Are you sure you want to remove this entry?
- GLPWRM148W Are you sure you want to delete the selected credential object?
- GLPWRM149W Are you sure you want to delete this replication filter object?
- GLPWRM156E The selected node is neither a master nor a gateway. Select a master or gateway node and then click View server.
- GLPWRM165E The selected node is neither a master nor a gateway. Select a master or gateway node and then click View schedule.
- GLPWRM168E Incorrect DN: DN.
- GLPWRM904E This subtree was originally created as a non-replicated subtree. To create replication filters in this subtree, the subtree must be initialized for replication with this server as the master. Click OK to initialize the subtree.
- GLPWRM9838W Warning: This will only delete the agreement agreement with the selected supplier.If this node consumes changes from other suppliers, you must delete each of those agreements separately in order to completely remove it from the topology.
- GLPWRP001E Ran wrapper script on an unsupported operating system: OS
- GLPWRP002E The program program name is not installed or could not be found.
- GLPWRP003E The java command at location is not installed or could not be found.
- GLPWRP004W Could not remove oldest archived core file because write access is needed for: filename.
- GLPWRP006E The DB2 property file 'filename' is not available.
- GLPWRP007E The instance instance is not created or could not be found.
- GLPWRP008E The instance instance is either not a TDS version version instance or it does not exist.
- GLPWRP009E The instance type (PROXY or RDBM) for instance instance was not found.
- GLPWRP010E The executable 'progname' cannot be used on the PROXY server instance 'instance'.
- GLPWRP011E The executable progname cannot be used on the default PROXY server instance instance.
- GLPWRP012E An invalid file name was specified.
- GLPWRP013E DB2 versions prior to 9.1 are not supported.
- GLPWRP014E A supported version of IBM DB2 is not installed on the system, or the ldapdb.properties file does not contain information about the supported IBM DB2 version.
- GLPWSA004E Some of the changes could not be saved.
- GLPWSA005E Cannot connect to administration server.
- GLPWSA006E The confirmation password for simple bind is incorrect.
- GLPWSA009E Passwords do not match.
- GLPWSA010E The confirmation password is incorrect on the certificate revocation panel.
- GLPWSA011E The Certificate revocation list DN was not created. The input value might be incorrect.
- GLPWSA012E The Kerberos DN was not created. The value provided might be incorrect.
- GLPWSA015E Incorrect Directory Server administrator DN syntax.
- GLPWSA016E Incorrect Directory Server administrator DN.
- GLPWSA017E Incorrect Kerberos ID.
- GLPWSA018E Incorrect syntax for Kerberos ID.
- GLPWSA019E Incorrect prefix for Kerberos DN.
- GLPWSA020E Passwords do not match. Some changes were saved.
- GLPWSA021E PKCS#11 interface support is enabled. All fields must be completed and you must select either the key storage or the accelerator mode option or both. Some of the changes were saved.
- GLPWSA022E Passwords do not match. Some changes were saved and will take effect after the server is restarted.
- GLPWSA023E PKCS#11 interface support is enabled. All fields must be completed and you must select either the key storage or the accelerator mode option or both. Some of the changes were saved and will take effect after the server is restarted.
- GLPWSA024E PKCS#11 interface support is enabled. All fields must be completed and you must select either the key storage or the accelerator mode option or both.
- GLPWSA025W Are you sure you want to delete the selected administrative group member DN?
- GLPWSA026W Are you sure you want to delete the selected suffix DN?
- GLPWSA027E Current password is incorrect.
- GLPWSA028E Secure port and unsecure port cannot have the same value.
- GLPWSA031E The administrator DN value already exists.
- GLPWSA032E The selected available attribute already exists under cn=localhost.
- GLPWSA033E The selected available attribute already exists under cn=IBMpolicies.
- GLPWSA034E The selected available attribute already exists in the list of cached attributes under database.
- GLPWSA035E The selected available attribute already exists in the list of cached attributes under changelog.
- GLPWSA036E This suffix DN value already exists.
- GLPWSA037W Are you sure you want to clear the log file?
- GLPWSA038E Select at least one DN or IP address to disconnect.
- GLPWSA039W Are you sure you want to disconnect all connections?
- GLPWSA040E Failed to either add or edit password policy object.
- GLPWSA041E The specified administrator DN already exists. Specify a new administrator DN.
- GLPWSA042E Type a valid value for the server realm in the Digest-MD5 panel.
- GLPWSA043E Type a valid value for the Username attribute in the Digest-MD5 panel.
- GLPWSA044W Are you sure you want to delete the selected back-end directory servers?
- GLPWSA045W Are you sure you want to delete all back-end directory servers?
- GLPWSA046E Passwords do not match.
- GLPWSA050E An error occurred while editing a back-end directory server.
- GLPWSA051E An error occurred while adding the back-end directory server.
- GLPWSA052E An error occurred while deleting back-end directory servers.
- GLPWSA053E An error occurred while loading back-end directory server information.
- GLPWSA054E Kerberos is not enabled for the proxy server.
- GLPWSA055E Incorrect suffix DN.
- GLPWSA056E Incorrect DN specified for displaying entry details.
- GLPWSA057E Incorrect DN specified as partition base DN, while adding a split.
- GLPWSA058E Incorrect DN specified for the bind DN.
- GLPWSA059E Select a referral entry to remove from the table.
- GLPWSA060E Select a suffix DN entry to remove from the table.
- GLPWSA061E Select a suffix DN entry in the table to edit.
- GLPWSA062E No partition entry is selected. Select an entry in the partition entries table to display the associated servers.
- GLPWSA063E No partition base DN entry is selected. Select the partition base DN entry in the table for which you want to perform the resume role operation.
- GLPWSA064E No back-end directory server entry is selected. Select the back-end directory server entry in the table for which you want to perform the resume role operation.
- GLPWSA065E No partition base DN entry is selected. Select the partition base DN entry you want to delete.
- GLPWSA066E No partition base DN entry is selected. Select the entry in the table for the partition base DN to edit.
- GLPWSA067E No back-end directory server entry is selected. Select the back-end directory server entry to delete.
- GLPWSA068E No back-end directory server entry is selected. Select the entry in the table for the back-end directory server to edit.
- GLPWSA069E No back-end directory server entry is selected. Select a back-end directory server entry in the table for which you want to view the corresponding partition bases.
- GLPWSA070E Suffix DN value is incorrect. Type a valid DN.
- GLPWSA071W Are you sure you want to delete the selected back-end directory server split entry?
- GLPWSA072W Are you sure you want to delete the selected partition base DN entry?
- GLPWSA073W Are you sure you want to delete all the back-end directory server splits?
- GLPWSA074E Incorrect partition index value. Partition index value is more than the number of partitions.
- GLPWSA075E Incorrect number of partitions. There exists a partition index value greater than the specified number of partitions.
- GLPWSA076E The specified back-end directory server entry already exists.
- GLPWSA077E The specified partition base already exists.
- GLPWSA078E The specified suffix DN already exists.
- GLPWSA079E An error occurred.
- GLPWSA080E An error occurred while adding the partition base.
- GLPWSA081E An error occurred while editing the partition base.
- GLPWSA082E An error occurred while deleting the partition base.
- GLPWSA084E Resume role extended operation failed because the selected back-end directory server does not exist.
- GLPWSA086E The format of the split name is incorrect.
- GLPWSA088E Type a valid entry DN to search.
- GLPWSA089E You clicked 'Select a file containing multiple DN'. Type the name of a file containing multiple DNs, or select a file using the Browse button, and then click Submit to submit the file on the Web server. Then click Show entry details.
- GLPWSA090E File cannot be uploaded on Web server or file not found.
- GLPWSA093E Error retrieving information for entry: DN
- GLPWSA094E Error retrieving information for the following entries: DNs
- GLPWSA104E Select a role.
- GLPWSA105W Connected to administration server. Not all values are available.
- GLPWSA106E Select an administration group member DN from the table.
- GLPWSA108E You have selected a subtree that is not a suffix. Parent entries for this subtree will not be available for pass-through authentication. Do you want to continue ?
- GLPWSA109E Incorrect port.
- GLPWSA110E Specify the Subtree DN.
- GLPWSA111E Cannot connect to Pass-through server.
- GLPWSA112E Entries under suffixes 'cn=configuration', 'cn=schema', 'cn=pwdpolicy,cn=ibmpolicies', 'cn=changelog', and 'cn=localhost' cannot be configured for pass-through authentication.
- GLPWSA113E Another subtree under this suffix is already configured for pass-through authentication. Select a subtree in a different suffix.
- GLPWSA114E Password policy rule violated. Verify the input given.
- GLPWSA115E Subtree DN is not specified.
- GLPWSA116W Do you want to remove the selected subtree DN?
- GLPWSA117W Do you want to remove the configured subtree?
- GLPWSA118E The number of registrations per connection cannot be more than the total registrations.
- GLPWSA119W Select only one back-end directory server to edit.
- GLPWSA120W Select only one back-end directory server to view partition bases.
- GLPWSA121E The number of database connections for replication cannot exceed the total number of database connections.
- GLPWSA122E Failed to enable / disable multiple password policy.
- GLPWSA123E Global password policy object cannot be deleted.
- GLPWSA124E Failed to delete the password policy object.
- GLPWSA125E Select a role for the administrative group member.
- GLPWSA126W Are you sure you want to delete the selected proxy server group DN entry?
- GLPWSA130E Selected back-end directory server list is empty.
- GLPWSA132E Error performing operation.
- GLPWSA133E Password policy object with the name policy name already exists.
- GLPWSA134E Password policy object policy name is in use by some user or group and it cannot be deleted.
- GLPWSA135W Are you sure you want to delete the selected password policy object?
- GLPWSA136W Are you sure you want to change the number of partition for the split?
- GLPWSA137E A parent node or a child node of the specified suffix DN value already exists. The specified suffix DN value cannot be added.
- GLPWSA138E The number of elements from a single search that can be added to the search filter cache should not exceed the number of elements in a search filter cache.
- GLPWSA150E The backup/restore directory path specified is invalid.
- GLPWSA155E The backup/restore directory path is not specified.
- GLPWSA156E The value of password monitoring interval is out of range.
- GLPWSA157W Are you sure you want to delete the selected referral/s?
- GLPWSA847E Failed to start the server.
- GLPWSA848E Failed to stop the server.
- GLPWSA849E Failed to restart the server.
Parent topic: Messages