IBM Security Directory Server Version 6.3

IBM Security Directory ServerVersion 6.3.1

Error Message Reference

GC27-2751-01

��

NoteBefore using this information and the product it supports, read the general information under “Notices” on page 193.

Edition notice

Note: This edition applies to version 6.3.1 of IBM Security Directory Server licensed program (product number5724-J39 ) and to all subsequent releases and modifications until otherwise indicated in new editions.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this publication . . . . . . . . ixAccess to publications and terminology . . . . . ixAccessibility . . . . . . . . . . . . . . xTechnical training . . . . . . . . . . . . xiSupport information . . . . . . . . . . . xiStatement of Good Security Practices . . . . . . xi

Chapter 1. Overview . . . . . . . . . 1Message format . . . . . . . . . . . . . 1

Message ID format . . . . . . . . . . . . 1Component identifiers . . . . . . . . . . 1Severity . . . . . . . . . . . . . . . 3

Presentation of messages . . . . . . . . . . 3

Chapter 2. Messages . . . . . . . . . 5

Notices . . . . . . . . . . . . . . 193

Index . . . . . . . . . . . . . . . 197

iii

iv IBM Security Directory Server: Error Message Reference

Figures

v

vi IBM Security Directory Server: Error Message Reference

Tables

1. Component identifiers and their descriptions 2

vii

viii IBM Security Directory Server: Error Message Reference

About this publication

IBM® Security Directory Server, previously known as IBM Tivoli® Directory Server,is an IBM implementation of Lightweight Directory Access Protocol for thefollowing operating systems:v Microsoft Windowsv AIX®

v Linux (System x®, System z®, System p®, and System i®)v Solarisv Hewlett-Packard UNIX (HP-UX) (Itanium)

IBM Security Directory Server Version 6.3.1 Error Message Reference provides a list ofall warning and error messages that are associated with IBM Security DirectoryServer.

Access to publications and terminologyThis section provides:v A list of publications in the “IBM Security Directory Server library.”v Links to “Online publications” on page x.v A link to the “IBM Terminology website” on page x.

IBM Security Directory Server library

The following documents are available in the IBM Security Directory Serverlibrary:v IBM Security Directory Server, Version 6.3.1 Product Overview, GC27-6212-00

Provides information about the IBM Security Directory Server product, newfeatures in the current release, and system requirements information.

v IBM Security Directory Server, Version 6.3.1 Quick Start Guide, GI11-9351-01Provides help for getting started with IBM Security Directory Server. Includes ashort product description and architecture diagram, and a pointer to the productdocumentation website and installation instructions.

v IBM Security Directory Server, Version 6.3.1 Installation and Configuration Guide,SC27-2747-01Contains complete information for installing, configuring, and uninstalling IBMSecurity Directory Server. Includes information about upgrading from a previousversion of IBM Security Directory Server.

v IBM Security Directory Server, Version 6.3.1 Administration Guide, SC27-2749-01Contains instructions for administrative tasks through the Web Administrationtool and the command line.

v IBM Security Directory Server, Version 6.3.1 Command Reference, SC27-2753-01Describes the syntax and usage of the command-line utilities included with IBMSecurity Directory Server.

v IBM Security Directory Server, Version 6.3.1 Server Plug-ins Reference , SC27-2750-01Contains information about writing server plug-ins.

v IBM Security Directory Server, Version 6.3.1 Programming Reference, SC27-2754-01

ix

Contains information about writing Lightweight Directory Access Protocol(LDAP) client applications in C and Java™.

v IBM Security Directory Server, Version 6.3.1 Performance Tuning and CapacityPlanning Guide, SC27-2748-01Contains information about tuning the directory server for better performance.Describes disk requirements and other hardware requirements for directories ofdifferent sizes and with various read and write rates. Describes known workingscenarios for each of these levels of directory and the disk and memory used;also suggests rules of thumb.

v IBM Security Directory Server, Version 6.3.1 Troubleshooting Guide, GC27-2752-01Contains information about possible problems and corrective actions that can betaken before you contact IBM Software Support.

v IBM Security Directory Server, Version 6.3.1 Error Message Reference, GC27-2751-01Contains a list of all warning and error messages associated with IBM SecurityDirectory Server.

Online publications

IBM posts product publications when the product is released and when thepublications are updated at the following locations:

IBM Security Directory Server documentation websiteThe http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDS.doc/welcome.htm site displays the documentationwelcome page for this product.

IBM Security Systems Documentation Central and Welcome pageIBM Security Systems Documentation Central provides an alphabetical listof all IBM Security Systems product documentation. You can also find linksto the product documentation for specific versions of each product.

Welcome to IBM Security Systems documentation provides andintroduction to, links to, and general information about IBM SecuritySystems documentation.

IBM Publications CenterThe http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss site offers customized search functions to help you find all the IBMpublications you need.

IBM Terminology website

The IBM Terminology website consolidates terminology for product libraries in onelocation. You can access the Terminology website at http://www.ibm.com/software/globalization/terminology.

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

For more information, see the Accessibility Appendix in the IBM Security DirectoryServer Product Overview.

x IBM Security Directory Server: Error Message Reference

http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDS.doc/welcome.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.IBMDS.doc/welcome.htm

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Security%20Systems%20Documentation%20Central/page/Welcome

http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/index.jsp

http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

http://www-05.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

http://www.ibm.com/software/globalization/terminology

http://www.ibm.com/software/globalization/terminology

Technical trainingFor technical training information, see the following IBM Education website athttp://www.ibm.com/software/tivoli/education.

Support informationIBM Support assists with code-related problems and routine, short durationinstallation or usage questions. You can directly access the IBM Software Supportsite at http://www.ibm.com/software/support/probsub.html.

IBM Security Directory Server Troubleshooting Guide provides details about:v What information to collect before you contact IBM Support.v The various methods for contacting IBM Support.v How to use IBM Support Assistant.v Instructions and problem-determination resources to isolate and fix the problem

yourself.

Note: The Community and Support tab on the product documentation canprovide additional support resources.

Statement of Good Security PracticesIT system security involves protecting systems and information throughprevention, detection, and response to improper access from within and outsideyour enterprise. Improper access can result in information being altered, destroyed,misappropriated, or misused or can result in damage to or misuse of your systems,including for use in attacks on others. No IT system or product should beconsidered completely secure and no single product, service or security measurecan be completely effective in preventing improper use or access. IBM systems,products and services are designed to be part of a comprehensive securityapproach, which will necessarily involve additional operational procedures, andmay require other systems, products or services to be most effective. IBM DOESNOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES AREIMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THEMALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.

About this publication xi

http://www.ibm.com/software/tivoli/education

http://www.ibm.com/software/support/probsub.html

xii IBM Security Directory Server: Error Message Reference

Chapter 1. Overview

Use the list of all warning and error messages that are associated with IBMSecurity Directory Server as a reference when you are troubleshooting issues.

Message formatA displayed or printed message can appear by itself or with other information,such as a time stamp.

A message consists of a message identifier (ID) and message text. A messagenumber is also associated with a message.

Message ID formatA message ID consists of 10 alphanumeric characters that uniquely identify themessage.

The message ID is composed of the following identifiers:v A 3-character product identifierv A 3-character component or subsystem identifierv A 3-digit serial numberv A 1-character type code indicating the severity of the message

The product identifier for IBM Security Directory Server is GLP.

The following list shows examples of valid message IDs:GLPCTL007WGLPICR015IGLPRDB002EGLPSRV029EGLPCCH001IGLPSSL027E

Component identifiersMessages that are associated with IBM Security Directory Server contain certaincomponent identifiers that are indicated in the message ID.

1

Messages that are associated with IBM Security Directory Server contain thecomponent or subsystem identifiers that are shown in the following table:

Table 1. Component identifiers and their descriptions

Component identifier Component

ADC Active Directory synchronization configuration

ADM Administration server process

ADR Active Directory synchronization run time

BLK The bulkload utility

CAT Catalog files

CCH The idscfgchglg utility

CDB The idscfgdb utility

CFG The idsxcfg and idsxinst utilities

COM Common server libraries

CRY Encryption seed and encryption salt

CSC The idscfgsch utility

CSF The idscfgsuf utility

CTL Common configuration tools libraries

D2L The db2ldif utility

DBA The idsdbmaint utility

DBB The dbback utility

DBM The idsdbmigr utility

DBR The dbrestore utility

DDS The ddsetup utility

DPW The idsdnpw utility

DSM DSML

GRP The idsadduser utility

HST The idssethost utility

ICR The idsicrt utility

IDL The idsideploy utility

IDP The idsidrop utility

ILT The idsilist utility

INS Installation

ISA Installation utilities

JBP The ldapdiff utility

KEY The idsgendirksf utility

L2D The ldif2db utility

LMT Log management

MIG The idsimigr utility

PFT Performance tuning tool

PRT The idssetport utility

PXY Proxy server

RDB Server RDBM

2 IBM Security Directory Server: Error Message Reference

Table 1. Component identifiers and their descriptions (continued)

Component identifier Component

RPL Server replication

RUN The runstats utility

SCH Schema

SRV Server front end

SSL Server SSL

UCH The idsucfgchglg utility

UDB The idsucfgdb utility

USC The idsucfgsch utility

USF The idsucfgsuf utility

WCO Web Administration Tool: Console administration

WDM Web Administration Tool: Schema management, Directorymanagement, Realms and templates, Users and groups

WRM Web Administration Tool: Replication management

WRP Wrapper script messages

WSA Web Administration Tool: Server administration, Proxyadministration, User properties

SeverityThe severity is indicated by the last character in the message ID.

I Indicates Informational message.

Provides information or feedback about normal events that occur.GLPCCH012I Change log will be configured.GLPCDB028I Reconfiguring database password.GLPADM010I Admin server is configured for secure connections.

W Indicates Warning message.

These messages indicates that a potentially undesirable conditionsoccurred, but processing can continue. The following messages showexamples of the warning that are generated:GLPCFG019W Are you sure you want to delete the selected suffix?GLPSRV084W Trace enabled from command line.GLPWCO035W Connected to administration server. Not all operations are available.

E Indicates Error message.

These messages indicates that a problem occurred that requiresintervention or correction before processing can continue. The followingmessages show examples of the error that are generated:GLPCDB034E An internal error occurred while retrieving the

database instance for the directory server instance.GLPBLK024E The -R option value must be ’yes’ or ’no’.GLPSSL008E An incorrect label was specified for SSL key database

key_database_filename.

Presentation of messagesA message consists of different parts such as the message ID, explanation, operatorresponse, administrator response, and programmer response.

The following list describes the different parts of the message explanations.

Chapter 1. Overview 3

ExplanationDescribes the meaning of the message, including why the message wasgenerated. The message might describe what system actions were taken asa result of the message.

Operator ResponseProvides information on how to correct the problem.

Administrator ResponseProvides information on how to correct the problem if SystemAdministrator authority is required.

Programmer ResponseDescribes the corrective actions a System Programmer should take.


Chapter 2. Messages

Use the warning and error messages to identify the response from IBM SecurityDirectory Server for the operations that you run against the server.

GLPADC003E The directory server instance 'instancename' does not exist.

Explanation: Incorrect instance name, or the instanceis not configured properly.

User response: Create or configure the instance andconfigure the synchronization feature.

GLPADC008E Incorrect version for Directory serverinstance: 'instance name'

Explanation: Only instances created with IBM TivoliDirectory Server V6.1 and higher are supported by theAD to TDS Synchronization solution.

User response: Verify that the instance used toconfigure the AD to TDS Synchronization solution wascreated using a supported version of IBM SecurityDirectory Server.

GLPADC010E Failed to generate unique portnumber for Cloudscape database whileconfiguring the solution for instance:'instance name'.

Explanation: The command could not generate aunique port number for the Cloudscape database.There were port number conflicts at various randomport numbers generated by the command.

User response: Configure a unique, non-conflictingport number in the instance home directory (in thesolution.properties file) for thecom.ibm.di.store.database property.

GLPADC011E Failed to generate unique portnumber for remote API whileconfiguring the solution for instance:'instance name'

Explanation: The command could not generate aunique port number for the remote API parameter.There were port number conflicts at various randomport numbers generated by the command.

User response: Configure a unique, non-conflictingport number in the instance home directory (in thesolution.properties file) for the api.remote.naming.portproperty.

GLPADM003E Unable to complete the initialfeature registration.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV063E. The Administration Server was unable toregister all the known features. This functionality isnecessary for the Web Administration Tool console, aswell as for any clients wanting to access thisinformation.

User response: Verify that the configuration filesettings are correct, especially those regarding plug-ins.If the problem persists, contact an IBM SoftwareSupport representative.

GLPADM005E Admin Audit log file 'file name' isfull, unable to log any more records.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV100E. The Admin server audit log is full. Thisprohibits the Admin Server from logging any moreaudit records.

User response: Verify that the system is not out ofdisk space, that the audit log exists and is writable.Also, verify that location where the file resides still hasspace.

GLPADM007E Admin server attempt to setsockopt()failed to set TCP_NODELAY; errno errorvalue (error string).

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV014E. The Admin server received the specifiederror attempting to set the socket option:TCP_NODELAY.

User response: Ensure that TCP/IP is operatingcorrectly.

GLPADM008E Admin server call to setsockopt() toset keep alive failed; errno error value(error string).

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV085E. The Admin server received the specifiederror attempting to set the socket option: keep alive.


5

GLPADM016E A client sent non-securedcommunications to the SSL port.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV022E. The Admin server determined that aclient sent non-encrypted data to the secure port. Therequest from the client is ended.

User response: If a command utility such asldapsearch is called by the client and securecommunications is intended, make sure the -Z (usesecure communications) parameter is specified. If theclient does not intend to use secure communications,then specify the nonsecure port.

Programmer response: If secure communications isintended, make sure the client calls ldap_ssl_start. Ifsecure communications is not intended, then specifythe nonsecure port.

GLPADM018E Unable to open file 'file'. Tryspecifying the full path name.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV006E. The Admin server is unable to open thespecified configuration file.

User response: Correct the file name and restart theserver, or contact the administrator.

GLPADM019E Unable to create the necessarythread.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV008E. The Admin server is unable to obtain thenecessary resources to create a required thread. If thefailure occurs during startup of the LDAP Server, theprogram ends. If the failure occurs while processing anew client request or initializing securecommunications for a client request, the programcontinues, but the request is not completed.

User response: Verify that the system is notoverloaded and is configured correctly.

GLPADM020E Configuration error: server usingport port for both SSL and non-SSL.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV011E. The Admin server is listening on thespecified port for both secure and nonsecure requests.

User response: Reconfigure the secure or nonsecureport and restart the Admin server.

GLPADM021E An administrator DN must bespecified in the adminDn line.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV012E. The LDAP Server encountered a blankadminDN parameter in the configuration file.

User response: Set the Administrator DN in theconfiguration file.

GLPADM022E The -p option requires an integer tobe specified for the port.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. Anon-integer value was specified for the server portnumber.

User response: Specify an integer when using the -poption.

GLPADM023E The -s option requires an integer tobe specified for the secure port.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. Anon-integer value was specified for the server secureport number.

User response: Specify an integer when using the -soption.

GLPADM024E The program is unable to runbecause of an initialization error.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV088E. The ibmdiradm program is unable to runbecause of an initialization error.

User response: View the earlier error message to seewhy the directory server did not start. If no previouserror message was printed, contact IBM SoftwareSupport.

GLPADM025E Admin server was unable to startbecause it could not write to theibmdiradm.pid file.

Explanation: The Admin server failed to start becauseit was unable to write the PID of the process to theibmdiradm.pid file of the directory server instance.

User response: Verify that the location where the PIDfile is going to be created is writable and accessible byyour user ID. This file must be created in the local tmpdirectory of the directory server instance (for example,in the ibmslapd-instancname\tmp directory).

GLPADM016E • GLPADM025E


GLPADM026E You are not in the same primarygroup as the directory server instanceowner 'instance name'. Only users in thesame primary group as the directoryserver instance owner can start theAdmin server of a directory serverinstance.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV115E. The program failed to start because youdo not have the same primary group as the directoryserver instance owner.

User response: Validate the primary group of thedirectory server instance owner. If you do not have thesame primary group, you are not authorized to startthe directory server instance.

GLPADM027E Extended operation OID failed,option decimal option is not valid for thisrequest.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV144E. The option is not valid for the specifiedextended operation.

User response: Make sure the correct option is usedwith the extended operation request.

GLPADM032E Failed to create Windows service forAdmin server instance: 'instance name'.

Explanation: The Admin server could not be installedas a Windows service.

User response: Look in the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPADM035E Failed to stop Admin server instance:'instance name'.

Explanation: The program failed to successfully stopthe Admin server. The error might have occurredbecause the Admin server was already stopped.

User response: Verify that the Admin server exists onthe computer and is running. If necessary, stop theAdmin server manually using the kill command onAIX, Linux, Solaris, and HP-UX systems or through theWindows Services panel on Windows systems.

GLPADM036E Unable to stop Admin serverinstance 'instance name', because the stateof the server cannot be determined.

Explanation: An attempt was made to stop the Adminserver instance and its state could not be determined.

User response: This error most likely occurred

because you do not have sufficient access to check thestatus of the Admin server. Verify that the Adminserver ibmdiradm.pid file has sufficient access for youto read it.

GLPADM039E Failed to delete Windows service forAdmin server instance: 'instance name'.

Explanation: The program failed to delete theWindows service for the Admin server instance.

User response: Verify that the Windows service for theAdmin server still exists. If it does not exist, no furtheraction is required. If the Windows service does exist,attempt to recreate the problem using the same Adminserver instance. If the problem persists, contact IBMSoftware Support.

GLPADM040E Unable to open audit log file'filename'.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. TheAdmin server is unable to open the audit log file.

User response: Make sure the server ID has access tothe directories in the file name path and the file itself.

GLPADM042E No Admin Audit entry found in theconfiguration file. Admin server startingwith no auditing.

Explanation: The Admin Audit entry is missing fromthe configuration file. The Admin server will not auditany operations.

User response: See the IBM Security Directory ServerAdministration Guide for instructions for enablingAdmin server auditing.

GLPADM043E The -k and -i options cannot be usedtogether.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV127E. You attempted to stop the Admin serverinstance and register the Admin server instance as aWindows service at the same time.

User response: Specify only the -k or -i option.

GLPADM044E The -k and -u options cannot beused together.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV128E. You attempted to stop the Admin serverinstance and unregister the Admin server instance as aWindows service at the same time.

User response: Specify only the -k or -u option.


Chapter 2. Messages 7

GLPADM045E The -i and -u options cannot be usedtogether.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV129E. You attempted to register and unregisterthe Admin server instance as a Windows service at thesame time.

User response: Specify only the -i or -u option.

GLPADM046E Problems retrieving entry 'entry DN'.

Explanation: The Admin server could not retrieve thecontent of an entry from the configuration file.

User response: Make sure the specified entry is in theconfiguration file.

GLPADM047E Found an unknown attribute'attribute name' in entry 'entry DN'.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. SeeGLPSRV103E. An unknown attribute was encounteredin the configuration file entry.

User response: Make sure correct attributes arespecified for the entry.

GLPADM051E Admin server received a request tostart or restart the server with anunsupported option.

Explanation: The Admin server will only start orrestart the server with the -a or -n option. The requestto start or restart failed.

User response: Make sure correct options arespecified.

GLPADM052E Incorrect port number specified: portnumber. Port number must be numeric,in the range 1 - 65535.

Explanation: The specified port number is not valid.

User response: Specify an integer within the 1 - 65535range.

GLPADM053W The Admin server auditconfiguration entry: entry DN is missingsome values. The default values will beused.

Explanation: The Admin server audit configurationentry does not contain all the attributes. Default valueswill be used for all missing values.

User response: Correct the entry to contain all theconfigurable values.

GLPADM059E The admin server configuration entryfor backup and restore 'entry DN'attribute 'attribute' is missing or has aninvalid value 'value'.

Explanation: The admin server configuration entrydoes not contain all of the required attributes or theattribute value is not valid.

User response: Correct the server configuration entryfor backup and restore.

GLPADM063E The backup requested by the adminserver has failed.

Explanation: The current directory serverconfiguration and database files have not been backedup. If there was a successful backup from before thisrequest, the files from this previous backup are stillavailable and any restore requests will be from this lastsuccessful backup.

User response: See messages from the backupcommand to determine the cause and possibleresolution of the error.

GLPADM066E The restore requested by the adminserver has failed.

Explanation: The directory server configuration anddatabase files have not been restored.

User response: See messages from the restorecommand to determine the cause and possibleresolution of the error.

GLPADM067E The admin server is currentlyperforming a backup of the directoryserver.

Explanation: The directory server configuration anddatabase files are being backed up. No additionalrequests to backup or restore can be serviced at thistime.

User response: Resubmit the request after the backupis complete.

GLPADM068E The admin server is currentlyperforming a restore of the directoryserver.

Explanation: The directory server configuration anddatabase files are being restored. No additional requeststo start, backup or restore can be serviced at this time.

User response: Resubmit the request after the restoreis complete.



GLPADM069W The admin server is stopping thedirectory server for a scheduled offlinebackup.

Explanation: The directory server configuration anddatabase files are being backed up offline. The directoryserver will be restarted when the backup is complete.

User response: Use online backup to avoid stoppingthe directory server to do a backup.

GLPADM072W The admin server is not configuredto perform regularly scheduled backups.

Explanation: The admin server configuration entry forbackup and restore operations does not include arecurring backup schedule. For online backups, theinactive log files in the backup location must beremoved manually to prevent the disk from filling up.

User response: Set the recurring schedule if you wantthe admin server to perform unattended backups alongwith cleaning up inactive log files.

GLPADM074E The admin server configuration entryfor backup and restore 'entry DN'attribute 'attribute' value 'value' specifiesan invalid path.

Explanation: The admin server configuration entrymust specify a fully qualified path on the samemachine as the directory server that can be written toby the directory instance owner.

User response: Correct the specified backup path inthe server configuration entry for backup and restore.

GLPADM075E The admin server configuration entryfor backup and restore 'entry DN'attribute 'attribute' value is not set.

Explanation: The admin server configuration entrymust specify a fully qualified path on the samemachine as the directory server that can be written toby the directory instance owner. The current value isNONE.

User response: Correct the specified backup path inthe server configuration entry for backup and restore.

GLPADM076W The admin server will not backupor restore changelog data if change logis configured.

Explanation: The admin server configuration entry forbackup and restore operations specifies that changelogdata must not to be included.

User response: If changelog data should be backed upand restored along with the directory data, change theconfiguration.

GLPADR006E AD to TDS Synchronization fordirectory server instance: 'instance name'failed.

Explanation: AD to TDS Synchronization failed

User response: Verify that the adsync_public.prop andadsync_private.prop files exist in the solution directory.Also refer to the log file present in the logs folder inthe solution directory for more details about the failure.

GLPADR007E TDS server instance 'instance name' isnot accessible.

Explanation: The TDS server instance is not accessible.

User response: Verify the status of the TDS serverinstance, and then start the instance if it is not running.

GLPADR008E AD to TDS Synchronization solutionis not configured for TDS serverinstance 'instance name'.

Explanation: The AD to TDS Synchronization solutionis not configured for the TDS server instance. Configurethe solution and then run the synchronization.

User response: Configure the solution and then runthe synchronization utility.

GLPADR009E Incorrect version for directory serverinstance 'instance name'

Explanation: Only instances created with IBM TivoliDirectory Server V6.1 and higher are supported by theAD to TDS Synchronization solution.

User response: Verify that the instance used toconfigure the AD to TDS Synchronization solution wascreated using a supported version of IBM SecurityDirectory Server.

GLPADR010E The directory server instance 'instancename' does not exist.

Explanation: Incorrect instance name, or the instanceis not configured properly.

User response: Create or configure the instance andconfigure the synchronization feature.

GLPBLK002E Disconnect other applications fromthe directory database and restartprogram_name.

Explanation: The bulkload utility cannot be run whenother applications are attached to the directorydatabase.

User response: Make sure that the directory server isnot running and that there are no other applicationsattached to the directory database.

GLPADM069W • GLPBLK002E


GLPBLK003E Parsing entry failed. DN: DistinguishedName.

Explanation: The bulkload utility failed to parse theentry with the specified distinguished name in theinput LDIF file.

User response: Modify the entry with the specifieddistinguished name in the input LDIF file.

GLPBLK007E The file system is full; bulkloadcannot write to 'filename'.

Explanation: The bulkload utility cannot write thetemporary files to the directory as specified by the -Lflag. (The default is the idsslapd-<instance name>/tmpdirectory.)

User response: If this is an AIX, Linux, Solaris, orHP-UX system and free disk space is still available, setthe ulimit for files to unlimited. Otherwise, increase thefree disk space on the specified file system and retrybulkload. If this problem still exists, use the -k optionto reduce the temporary file size.

GLPBLK008E The bulkload utility was unable toread the file specified at line line number.The entry was ignored.

Explanation: The bulkload utility cannot read the fileas specified by the URL at the indicated line number inthe input LDIF file.

User response: Ensure that the file specified by theURL exists and retry bulkload.

GLPBLK009E Unsupported URL in the entry at lineline number. The entry was ignored.

Explanation: The URL at the indicated line number inthe input LDIF file is not supported. Only file URLs aresupported in an LDIF file.

User response: Correct the URL at the specified linenumber and retry bulkload. File URLs take thefollowing form: attribute:< file:///path (where pathsyntax depends on operating system). For example, thefollowing are valid file Web addresses: jpegphoto:<file:///d:\temp\photos\myphoto.jpg (DOS/Windowsstyle paths) jpegphoto:< file:///etc/temp/photos/myphoto.jpg (UNIX style paths)

GLPBLK010E An error occurred in the translation ofa value to UTF-8 codeset at line linenumber. The entry was ignored.

Explanation: The bulkload or ldif2db utility cannottranslate the value at the indicated line number in theinput LDIF file into the UTF-8 codeset.

User response: Ensure that all characters in the valueare valid and retry the utility.

GLPBLK011E An unrecognized charset name, codesetname, was found in the LDIF file. Notranslation to UTF-8 was attempted.

Explanation: The charset directive in the input LDIFfile is not recognized or supported. The list ofsupported charset values can be found in the Appendixfor LDAP data interchange format under IANAcharacter sets supported by platform in the IBMSecurity Directory Server Administration Guide.

User response: Correct the charset value in the LDIFfile.

GLPBLK012E utility_program_name: Cannotauthenticate DN and password.

Explanation: The credentials entered are not valid.There is an error verifying the DN and password.

User response: Enter a valid DN and password.

GLPBLK013E utility_program_name failed on'file_operation' to file: file name.

Explanation: The bulkload utility failed on theoperation specified to the file indicated.

User response: Check the file indicated for theoperation that failed and correct the problem.

GLPBLK014E Disconnect other applications fromthe directory database and restartprogram_name.

Explanation: The bulkload utility cannot be run whenother applications are attached to the directorydatabase.

User response: Make sure that the directory server isnot running and that there are no other applicationsattached to the directory database.

GLPBLK015E The -A option value must be 'yes' or'no'.

Explanation: You specified an incorrect parameterwith the -A option.

User response: Specify 'yes' or 'no' with the -A option.Use the -? option to see the usage for the bulkloadcommand.

GLPBLK016E The -a option value must be'parseonly', 'loadonly' or'parse_and_load'.

Explanation: You specified an incorrect parameterwith the -a option.

User response: Specify 'parseonly', 'loadonly' or'parse_and_load' with the -a option. Use the -? optionto see the usage for the bulkload command.

GLPBLK003E • GLPBLK016E


GLPBLK017E The -c option value must be 'yes' or'no'.

Explanation: You specified an incorrect parameterwith the -c option.

User response: Specify 'yes' or 'no' with the -c option.Use the -? option to see the usage for the bulkloadcommand.

GLPBLK018E The -E option value must be aninteger between 0 and 1000000.

Explanation: You specified an out of range value forthe -E option.

User response: Specify an integer between 0 and1000000 with the -e option. Use the -? option to see theusage for the bulkload command.

GLPBLK019E The -e option value must be 'yes' or'no'.

Explanation: You specified an incorrect parameterwith the -e option.

User response: Specify 'yes' or 'no' with the -e option.Use the -? option to see the usage for the bulkloadcommand.

GLPBLK020E Starting with the IBM TivoliDirectory Server 6.3 release this messageis deprecated.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.3 release this message is deprecated.

GLPBLK021E The -S option value must be 'yes','no', or 'only'.

Explanation: You specified an incorrect parameterwith the -S option.

User response: Specify 'yes', 'no', or 'only' with the -Soption. Use the -? option to see the usage for thebulkload command.

GLPBLK022E The -x option value must be 'yes' or'no'.

Explanation: You specified an incorrect parameterwith the -x option.

User response: Specify 'yes' or 'no' with the -x option.Use the -? option to see the usage for the bulkloadcommand.

GLPBLK023E The -L option value is too long;maximum number of characters isnumber of characters.

Explanation: You specified a directory that was toolong for the -L option.

User response: Specify a directory path that is lessthan the maximum number of characters with the -Loption. Use the -? option to see the usage for thebulkload command.

GLPBLK024E The -R option value must be 'yes' or'no'.

Explanation: You specified an incorrect parameterwith the -R option.

User response: Specify 'yes' or 'no' with the -R option.Use the -? option to see the usage for the bulkloadcommand.

GLPBLK025E The -i option is required.

Explanation: You did not specify the -i option, whichis the input file for bulkload.

User response: Specify the -i option. Use the -? optionto see the usage for the bulkload command.

GLPBLK026E Value of 0 specified for option -k notvalid.

Explanation: You specified 0 with the -k option, whichis not valid.

User response: Specify the -k option with a validvalue. Use the -? option to see the usage for thebulkload command.

GLPBLK027E The load action option (-a) must be'parse_and_load' when the -k option isspecified.

Explanation: You specified -a with an incorrect optionwhile using the -k option.

User response: Specify the -a option with the'parse_and_load' value when using the -k option. Usethe -? option to see the usage for the bulkloadcommand.

GLPBLK028E The Remove tmp (-R option) must beyes when the -k option is specified.

Explanation: You specified -R with an incorrect optionwhile using the -k option.

User response: Specify the -R with the 'yes' valuewhen using the -k option. Use the -? option to see theusage for the bulkload command.

GLPBLK029W The -s option was specified with anincorrect character delimiter. The defaultdelimiter '|' will be used.

Explanation: The specified string delimiter is notvalid. Acceptable characters are any of the following: %& ' ( ) * , . / : ; < > ? |

GLPBLK017E • GLPBLK029W


User response: Specify a valid string delimiter withthe -s option. Use the -? option to see the usage for thebulkload command.

GLPBLK030E Run DB2CMD.EXE first, and then runbulkload within the DB2 CLP commandinterpreter.

Explanation: The bulkload utility must be run from aDB2 command window.

User response: Start bulkload from a DB2 commandwindow.

GLPBLK031E Options -o and -t are mutuallyexclusive.

Explanation: Only one of the -o or -t options isallowed.

User response: Specify either the -o or -t option. Usethe -? option to see the usage for the bulkloadcommand.

GLPBLK032E The -o file 'file_name' already exists.

Explanation: The output file for timestamps andibm-entryuuid already exists.

User response: Rename or delete the existing file, orspecify a different output file.

GLPBLK033E Options -G and -k are mutuallyexclusive.

Explanation: Only one of the -G or -k options isallowed.

User response: Specify either the -G or -k option. Usethe -? option to see the usage for the bulkloadcommand.

GLPBLK034E The -S option is not allowed whenthe -k option is specified.

Explanation: Only one of the -S ONLY or -k options isallowed.

User response: Specify either the -S ONLY or -koption. Use the -? option to see the usage for thebulkload command.

GLPBLK035W Previous LOAD failure detected in'filename'. Bulkload will try to restartload operations. ACTION is set toLOADONLY.

Explanation: The bulkload utility has been restarted.A previous bulkload attempt failed while attempting toload the specified file. The load will be attemptedagain.

User response: Look for additional messages that give

an indication of the success or failure of the restartedload.

GLPBLK036W Parse only option was chosen lasttime and detected in 'filename'. ButACTION is not LOADONLY. Bulkloadwill back up the status file to'filename.filename_suffix'.

Explanation: The bulkload utility has been restarted,but LOADONLY was not specified. The status file fromthe previous run will be saved as indicated.

User response: Look for additional messages that givean indication of the success or failure of the restartedbulkload.

GLPBLK037E The -a 'loadonly' option was specifiedbut there are no load files to load.'filename' is not found. Bulkload willstop.

Explanation: Option -a was set to LOADONLY, butthe bulkload_status file was not found. LOADONLYcan succeed only if a previous invocation of bulkloadsuccessfully parsed the LDIF file. If the LDIF waspreviously parsed, then the bulkload status file namemight have been incorrectly specified.

User response: Run bulkload with other -a optionvalues (parseonly, parse_and_load) so that the LDIF fileis parsed, or specify the correct filename. Use the -?option to see the usage for the bulkload command.

GLPBLK038E The load only option is chosen butthe bulkload status file is either notreadable or corrupted. Bulkload willend.

Explanation: The option -a is set to LOADONLY, butthe bulkload_status file is not readable or corrupted.

User response: Run bulkload with other -a optionvalues (parseonly, parse_and_load). Use the -? option tosee the usage for the bulkload command.

GLPBLK039E Bulkload failed to rename the oldstatus file 'filename'. Bulkload will end.

Explanation: The -a option is not LOADONLY, but theprevious bulkload_status file cannot be renamed.

User response: Rename or delete the old status fileand restart bulkload.

GLPBLK040E Bulkload failed to determine thehome directory. Bulkload will end.

Explanation: On Windows operating systems,bulkload uses the registry to determine the home(installation) directory.

User response: Check the Windows registry and



verify that the IBM Security Directory Server iscorrectly installed and registered.

GLPBLK041E Bulkload failed to determine importdirectory 'path'. Bulkload will end.

Explanation: Bulkload cannot determine the importdirectory path.

User response: Check that the path exists and ensurethat it is accessible.

GLPBLK042E Bulkload failed to create thetemporary directory under 'path'.Bulkload will end.

Explanation: Bulkload cannot create the temporarydirectory under the specified import directory path.


GLPBLK043E Bulkload failed to chdir to 'path'.Bulkload will end.

Explanation: Bulkload cannot change the directory(chdir) to the specified import directory path.


GLPBLK045E Input data failed to pass schemachecking or parsing completely.

Explanation: Schema or syntax errors are detected ininput data. Bulkload will skip the data LOAD phase.

User response: Correct the reported errors and trybulkload again.

GLPBLK046E Entry 'DN of entry' above line linenumber violates the schema definition.The error code is return code.

Explanation: The entry DN above the line specified inthe error message violates the schema definition.Bulkload is unable to process that entry.


GLPBLK047E Entry 'DN of entry' above line linenumber does not contain objectclass.

Explanation: The entry DN above the line specified inthe error message does not contain objectclass.Bulkload is unable to process that entry.


GLPBLK048E UUID 'UUID' in input file not valid.

Explanation: An incorrect UUID exists in the bulkloadfile that bulkload was processing. Bulkload is unable toprocess that entry.


GLPBLK049E Entry DN above line line numbercontains an incorrect ACL definition.

Explanation: The entry DN above the line specified inthe error message contains an incorrect ACL definition.Bulkload is unable to process that entry.


GLPBLK051E DN 'DN' detected at line line numbernot valid.

Explanation: The DN at the line specified in the errormessage is not valid. Bulkload is unable to process thatentry.


GLPBLK052E DN 'DN' at line line number exceedsmaximum length size limit.

Explanation: The DN at the line specified in the errormessage is too long. Bulkload is unable to process thatentry.


GLPBLK053W LDADPIMPORT directory is notconsistent with the directory specifiedin 'filename'. For ACTION=LOADONLY,bulkload will use 'path' in filename.

Explanation: The LDADPIMPORT directory specifiedin the bulkload status is not consistent with what hasbeen specified from the command line. Therefore, thedirectory specified in the bulkload status file will beused.

User response: Verify that the directory used is valid.

GLPBLK054W LDADPIMPORT directory is notconsistent with the directory specifiedin 'filename'. Bulkload will use 'path'.

Explanation: The LDADPIMPORT directory specifiedin the bulkload status is not consistent with what hasbeen specified from the command line. Therefore, thedirectory specified in the bulkload status file will beused.

User response: Verify that the directory used is valid.

GLPBLK041E • GLPBLK054W


GLPBLK056W Bulkload failed to remove temporarydirectory under 'path'.

Explanation: Bulkload cannot remove the temporarydirectory under the specified import directory path.

User response: Ensure that the temporary directorycan be removed. Ensure that the server ID has writeaccess to the directory and no other applications areusing the directory.

GLPBLK057E Error in translation of value fromUTF-8 to a database codepage for entry'DN of entry'.

Explanation: Bulkload cannot translate the value fromUTF-8 to a database codeset for the specified entry inthe input LDIF file.

User response: Ensure that all characters in the entryare valid and retry bulkload.

GLPBLK058E Entry 'DN of entry' already exists inthe directory.

Explanation: The specified entry in the input LDIF filealready exists in the directory.

User response: Remove the entry from the input fileand retry bulkload.

GLPBLK059E Entry 'DN of entry' already exists inthe input file.

Explanation: The specified entry already exists in theinput LDIF file.

User response: Remove the duplicated entry from theinput file and retry bulkload.

GLPBLK060E Cannot create DB2 table for attribute'attribute name'.

Explanation: Bulkload failed to create a DB2 table forthe specified attribute.

User response: Check the DB2 error log and correctpossible resource problems.

GLPBLK064E Entry 'DN of entry' at line line numberdoes not exist in the directory .

Explanation: The specified group entry in the inputLDIF file does not exist in the directory.

User response: Add the group entry into the directoryand retry bulkload.

GLPBLK065E Attribute 'attribute name' at line linenumber is not defined in the schema.

Explanation: Attributes used in the entry must bedefined in the schema for bulkload to process properly.

User response: Check the attribute name and verifythat it is defined in the schema.

GLPBLK066E attribute 'attribute name' at line linenumber is not allowed with option -G.

Explanation: The -G option allows member anduniquemember attributes only.

User response: Remove the incorrect attributes in theLDIF file.

GLPBLK068E Attribute 'attribute name' has amaximum value length of integer.Current attribute value is of lengthinteger.

Explanation: The attribute value to be added is longerthan the maximum length defined in the schema.Adding the entry failed.

User response: Specify a shorter value for theattribute and try loading the entry again.

GLPBLK069E Bulkload error; cannot find input file'file name'.

Explanation: Bulkload cannot find the specified inputLDIF file.

User response: Verify the name of the input file andtry again.

GLPBLK070E Parent entry for 'DN of entry' does notexist.

Explanation: The load of an entry failed because theparent DN does not exist or the suffix DN is notdefined in the configuration file.

User response: Correct the DN in the LDIF file or, inthe case of a missing suffix, add the suffix DN into theconfiguration file and try loading again.

GLPBLK071E Bulkload is unable to run because ofan initialization error.

Explanation: Bulkload is unable to start because of aninitialization error.

User response: View earlier error messages todetermine why bulkload did not start. If no previouserror message was printed, contact IBM SoftwareSupport.

GLPBLK056W • GLPBLK071E


GLPBLK074E An internal error occurred whilegetting the directory databaseapplications.

Explanation: Bulkload is unable to continue due to aninternal error.

User response: If the problem persists, contact IBMSoftware Support.

GLPBLK098E An internal error occurred whileprocessing the LDADPIMPORTdirectory.



GLPBLK099E The file system is full or a load fileexceeded maximum file size.

Explanation: Bulkload generates temporary files underthe instance owner's tmp directory or the directoryspecified with the -L option. Either the file system isfull or, on AIX, Linux, Solaris, and HP-UX systems, themaximum file size limit has been reached. Bulkload isunable to continue.


GLPBLK100E An internal error occurred whileattempting to generate the load script.



GLPBLK101E An internal error occurred whileattempting to stream out the status file.



GLPBLK108E An internal error occurred whileloading the data.



GLPBLK109E script name failed! rc = rc. The statusfile file is created and temp directorydirectory will not be removed. Seedb2load.log in db2load directory fordetails.

Explanation: An error occurred while loading thedata.

User response: If the db2load.log is not found, thenthe script failed due to database connection relatedfailures.

GLPBLK110E An internal error occurred whileattempting to stream out the status filedue to load failure.



GLPBLK111E An internal error occurred whileloading the attribute data.




Explanation: An error occurred while loading theattribute data.


GLPBLK113E An internal error occurred whileattempting to stream out the status filedue to attribute load failure.



GLPBLK114E Bulkload failed to remove theldapimport directory directory file.Bulkload will end.

Explanation: The temporary ldapimport directorycould not be deleted by bulkload. Directory data, up tothis point, is loaded into the database successfully.



User response: You can remove the directorymanually.

GLPBLK115E An internal error occurred whileattempting to set file position duringparsing.



GLPBLK116E Line detected: line not valid.

Explanation: bulkload could not parse the line.bulkload detected data on the specified line that is notvalid.

User response: Determine the cause of the parsingerror and then fix the input file and try again.

GLPBLK117E URL processing error at line: line



GLPBLK118E Codepage conversion failed at line:line



GLPBLK119E An internal error occurred whileattempting to set file position duringparsing entries.


User response: If the problem persists, then contactIBM Software Support.

GLPBLK120E Line detected while parsing entries:line not valid.



GLPBLK121E URL processing error while parsingentries at line: line



GLPBLK122E Codepage conversion failed whileparsing entries at line: line



GLPBLK123E DN 'DN' detected at line line numberwhile parsing entries not valid.

Explanation: The DN at the line specified in the errormessage is not valid. Bulkload is unable to process thatentry.


GLPBLK124E Attribute 'attribute name' at line linenumber is not preceded by a DN.

Explanation: Entries in the LDIF file must begin witha DN. Bulkload detected an attribute without apreceding DN on the specified line.

User response: Correct the reported error and tryagain.

GLPBLK125E Codepage conversion failed whileparsing entries at line: line

Explanation: Bulkload could not parse the line.Bulkload detected data on the specified line that is notvalid.


GLPBLK126E Language tag not supported forattribute 'attribute name' in entry 'entryname' at line line number

Explanation: Language tag is not allowed for thereported attribute.

User response: Remove the language tag from theattribute and try again.






GLPBLK128E An internal error occurred whileattempting to open load file for attributename.


User response: If the problem persists, contact IBMSofware Support.

GLPBLK129E An internal error occurred whilereading load file for attribute name atline line number.



GLPBLK130E attribute name is not allowed at lineline

Explanation: If aclSource value equals the entry DN,then it is an explicit ACL and the aclEntry andaclPropagate values must be specified.

User response: Determine the cause of the parsingerror. Then fix the input file and the entry if the entrywas loaded into the directory.

GLPBLK131E attribute name is not allowed at lineline

Explanation: If ownerSource value equals the entryDN, then it is an explicit owner and theownerPropagate and entryOwner values must bespecified.


GLPBLK132E Line detected: line not valid.

Explanation: bulkload could not parse the line.bulkload detected data that is not valid on the specifiedline.



Explanation: bulkload could not parse the line.bulkload detected data that is not valid on the specifiedline.


GLPBLK134E Attribute 'attribute name' at line linenumber is not preceded by a DN.

Explanation: Entries in the LDIF file must begin witha DN. Bulkload detected an attribute without apreceding DN on the specified line.

User response: Correct the reported error and tryagain.


Explanation: Bulkload could not parse the line.Bulkload detected data on the specified line that is notvalid.








GLPBLK138E An internal error occurred whileattempting to open load file for attributename.





GLPBLK139E An internal error occurred whilereading load file for attribute name atline line number.



GLPBLK140E An internal error occurred whileattempting to close file handles.



GLPBLK142E An internal error occurred whileattempting to stream out the status file.




Explanation: An error occurred while loading thedata.


GLPBLK144E An internal error occurred whileattempting to stream out the status filedue to load failure.


User response: If the problem persists, then contactIBM Software Support.

GLPBLK145E Bulkload failed to remove theldapimport directory directory file.Bulkload will end.

Explanation: The temporary ldapimport directorycould not be deleted by bulkload. Directory data, up tothis point, is loaded into the database successfully.

User response: You can remove the directorymanually.

GLPBLK146E The status file indicates attr failed butload message file indicates it finished thephase phase successfully. Bulkload willend.

Explanation: Bulkload is attempting to recover from apreviously failed load operation. But the load messagefile indicates that the load completed successfully.

User response: Remove the bulkload status file andthe ldapimport directory. Start the ibmslapd server andverify that the data is loaded correctly.

GLPBLK147E The file system is full or a load fileexceeded maximum file size.

Explanation: Bulkload generates temporary files underthe instance owner's tmp directory or the directoryspecified with the -L option. Either the file system isfull or, on AIX, Linux, Solaris, and HP-UX systems, themaximum file size limit has been reached. Bulkload isunable to continue.


GLPBLK148E An internal error occurred whileattempting to generate the load script.



GLPBLK149E An internal error occurred becausebulkload failed to reset variables for thenext cardinal number round of parse andload.



GLPBLK152E Parsing entry failed at line linenumber.

Explanation: The bulkload utility failed to parse theentry at the specified line in the input LDIF file.

User response: Modify the entry above the specifiedline in the input LDIF file.



GLPBLK153E Operational attribute attribute name isspecified more than once.

Explanation: An entry in the input LDIF file can onlyhave a single value for the specified attribute.

User response: Modify the entry in the input LDIFfile.

GLPBLK154E Entry contains incorrect value foroperational attribute attribute name

Explanation: The entry contains an value that is notvalid for the specified attribute.


GLPBLK155E Option -t is specified and entrycontains operational attributes in plaintext form.

Explanation: Option -t is specified to takecreatetimestamp and modifytimestamp values from afile. But the entry contains operational attributes inplain text form. This violates the schema rule thatoperational attributes must be single-valued.


GLPBLK156E Option -t was specified and entrycontains operational attributes in theLDAP control.

Explanation: Option -t was specified to takecreatetimestamp and modifytimestamp values from afile. But the entry contains operational attribute in theLDAP control. This violates the schema rule thatoperational attributes must be single-valued.


GLPBLK157E Entry contains operational attributesin both LDAP control and plain textformat.

Explanation: The entry contains operational attributesin LDAP control and plain text format. This violates theschema rule that operational attributes must besingle-valued.


GLPBLK158E Nested groups exist in the databaseand nested group processing is notenabled. Bulkload will stop.

Explanation: A nested group entry has been found inthe directory database, and nested group processing inbulkload is not enabled. This can affect data integrity.

User response: Enable nested group processing inbulkload and try again.

GLPBLK159E Nested groups exist in the input fileand nested group processing is notenabled. Bulkload will stop.

Explanation: A nested group entry has been found inthe input file, and nested group processing in bulkloadis not enabled. This can affect data integrity.

User response: Enable nested group processing inbulkload and try again.

GLPBLK161E Suffix entry 'Suffix entry DN' does notexist.

Explanation: The suffix entry does not exist in thedatabase nor in the input LDIF file. Parsing of the childentries in the LDIF file cannot continue.

User response: Add the suffix entry in the LDIF fileand try loading again.

GLPCAT001E Requested message numbermessage_number beyond bounds ofinternal table.

Explanation: The correct message cannot be loggedbecause the requested message ID number is incorrect.

User response: Report the message ID number to IBMSoftware Support.

GLPCAT002E Cannot open message catalog filecatalog_name.

Explanation: The translated messages cannot belogged because the specified message catalog filecannot be located.

User response: Check that the appropriate languagepackage is correctly installed, and that the locale andall language-related environment variables are setcorrectly.

GLPCAT003E A character transformation erroroccurred while trying to output amessage. The UTF-8 codepageconversion failed.

Explanation: An error occurred while convertinginput data to UTF8 or to a local codepage on thesystem. The program failed to convert arguments thatwere part of a message that was going to be output.

User response: Check that the appropriate languagepackage is correctly installed, and that the locale andall language-related environment variables are setcorrectly. Also, verify that the TISDIR environmentvariable has been set. If the problem persists, contactIBM Software Support.

GLPBLK153E • GLPCAT003E


GLPCCH004E Failed to add change log to directoryserver instance: 'instance name'.

Explanation: The program failed to add the changelog to the directory server instance.

User response: Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, look in the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCCH007E Failed to configure change logdatabase 'database name' for directoryserver instance: 'instance name'.

Explanation: An internal error occurred while tryingto configure the change log database in the directoryserver instance configuration file.

User response: See the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCCH008E A change log database is alreadyconfigured in directory server instance'instance name'.

Explanation: The program tried to configure a changelog database for a directory server instance but one wasalready configured.

User response: Unconfigure the current change logdatabase from the directory server instance, if a newchange log database needs to be configured.

GLPCCH009E A database instance is not configuredfor directory server instance 'instancename'.

Explanation: A change log database for a directoryserver instance can be created only if a databaseinstance is already configured.

User response: A database is configured using theidscfgdb command and a database instance isconfigured using the idsicrt command. Configure thedatabase instance and database using these commandsbefore attempting to create a change log database.

GLPCCH010E Unable to configure change log. Nodatabase is configured for directoryserver instance 'instance name'.

Explanation: A change log database can be configuredonly if a database is already configured.

User response: A database is configured using theidscfgdb command. Configure a database with thiscommand before attempting to configure a change log.

GLPCCH011E A change log is already configuredfor directory server instance 'instancename'.

Explanation: A change log database is alreadyconfigured for the directory server instance specified.

User response: Unconfigure the current change logdatabase from the directory server instance, if a newchange log database needs to be configured.

GLPCCH015E The argument for the -m option mustbe an integer greater than or equal to 0.

Explanation: The option specified requires that theargument specified must be an integer greater than orequal to zero.

User response: Specify a positive integer for theargument.

GLPCCH016E The argument for the -h option mustbe an integer greater than or equal to 0and less than or equal to 24.

Explanation: The option specified requires that theargument specified must be an integer greater than orequal to zero and less than or equal to 24.


GLPCCH017E The argument for the -y option mustbe an integer greater than or equal to 0.

Explanation: The option specified requires that theargument specified must be an integer greater than orequal to zero.


GLPCCH018E An internal error occurred whilerunning the idscfgchglg command.

Explanation: An internal error occurred while runningthe idscfgchglg command. This might have occurredbecause the program ran out of memory.

User response: See IBM Security Directory ServerProduct Overview for information about hardware andsoftware requirements. If all requirements are met, runthe command again. If the problem persists, contactIBM Software Support.

GLPCCH019W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.

Explanation: An error was encountered while runningthe program.

User response: View the earlier error messages for

GLPCCH004E • GLPCCH019W


information about the exact error.

GLPCCH022E Failed to set change log maximumentries to 'number of entries'.

Explanation: An internal error occurred while tryingto set the Change log maximum entries in theconfiguration file of the directory server instance. Nochanges were made to the configuration file.


GLPCCH025E Failed to set change log maximumage limit to 'number of days' days 'numberof hours' hours.

Explanation: An internal error occurred while tryingto set the Change log maximum age in theconfiguration file of the directory server instance. Nochanges were made to the configuration file.


GLPCDB004E Failed to add database 'database name'to directory server instance: 'instancename'.

Explanation: The program failed to add the databaseto the directory server instance.


GLPCDB007E Failed to configure database 'databasename' for directory server instance: 'DB2instance'.

Explanation: An internal error occurred while tryingto configure the database in the directory serverinstance configuration file.


GLPCDB008E A database is already configured indirectory server instance 'instance name'.

Explanation: A database is already configured for thespecified directory server instance.

User response: Unconfigure the current database fromthe directory server instance, if a new database needsto be configured.

GLPCDB009E A database instance is not configuredfor directory server instance 'instancename'.

Explanation: Tried to create a database for a directoryserver instance and a database instance is notconfigured.

User response: Create a database only if a databaseinstance is first configured.

GLPCDB010E Failed to configure local loopback fordirectory server instance: 'instance name'.

Explanation: The program failed to configure localloopback for the directory server instance.


GLPCDB011E The specified database location'location' is not a drive.

Explanation: The location chosen to configure adatabase is not a drive. On the Windows operatingsystem, the location must be a file system drive and nota directory.

User response: Verify that the location specified exists,that it is writable and that it has the necessary freespace, or choose another location that meets the criteria.

GLPCDB012E The -a -t and -l options are required.The -w is only required if the -n is alsospecified.

Explanation: The -a -t and -l options must be specifiedto configure a database. The -w is required only if the-n is also specified.

User response: Specify the -a -t and -l to configure adatabase. Also, specify the -w if the -n option is beingused. If a database is configured and you need tochange the database administrator's password, use the-w option only.

GLPCDB013E Unable to configure database. Nodatabase instance is configured fordirectory server instance 'instance name'.

Explanation: A database can be configured only if adatabase instance is already configured.

User response: A database instance is configured

GLPCCH022E • GLPCDB013E


when a directory server instance is created. If you haveremoved the database instance or deleted the databaseinstance from the configuration file, either reconfiguremanually or recreate the directory server instance.

GLPCDB014E A database is already configured fordirectory server instance 'instance name'.

Explanation: A database is already configured for thedirectory server instance specified.

User response: Unconfigure the database if anotherdatabase needs to be configured. Otherwise, no furtheraction is necessary.

GLPCDB016E The -w option is required.

Explanation: The -w option is required to specify thepassword of the database administrator.

User response: Specify the -w option or do not runthe command with the -n option (in no-prompt mode)to avoid this error. Use the -? option to see the syntaxfor the command.

GLPCDB017E The database administrator user IDspecified, 'user name', is not a valid nameand violates the DB2 database namenaming rules.

Explanation: The program failed because a user namethat is not valid was specified.

User response: Specify a user name according to thefollowing rules: The user name must contain 1 to 8characters. The name cannot be 'USERS', 'ADMINS','GUESTS', 'PUBLIC', or 'LOCAL'. The name cannotbegin with 'IBM', 'SQL', or 'SYS'. The name cannotinclude accented characters. The name can include onlythe following characters: A through Z, a through z, and0 through 9. The name must begin with one of thefollowing characters: A through Z or a through z.

GLPCDB018E The DB2 administrator ID orpassword you specified is not valid.

Explanation: The DB2 administrator ID specified doesnot exist or the password specified is not valid for theDB2 administrator ID.

User response: Specify an existing user ID on thesystem and the valid password for the DB2administrator ID. Verify that the user ID has apassword that is valid and ready to use. For example,the password cannot be expired or waiting for afirst-time validation of any kind. You might be able toverify that the password is correctly set by attemptingto telnet into the computer using the user ID.

GLPCDB019E The DB2 instance owner ID that youspecified does not exist.

Explanation: The DB2 instance owner ID specifieddoes not exist on the system.

User response: Specify an existing user ID on thesystem for the DB2 instance owner ID.

GLPCDB020E The specified directory, 'filename', isnot a valid directory, does not exist, or isnot writable.

Explanation: The directory specified to create thedatabase is a location that is not valid, is not writable,or is not accessible.

User response: Verify that the location where thedatabase is going to be created is a valid location onthe system and that you have access to write to thatlocation. The directory must exist.

GLPCDB021E The specified directory, 'filename', doesnot have enough free space. Specify anexisting location that is writable with atleast 80 MB of free space.

Explanation: The directory specified in which to createthe database does not have enough free space. Thelocation must have at least 80 MB of free space.

User response: Verify that the location where theinstance is going to be created is a valid location on thesystem and that you have access to write to thatlocation. The directory must exist and must have 80MB of free space.

GLPCDB025E An internal error occurred whilerunning the idscfgdb command.

Explanation: An internal error occurred while runningthe idscfgdb command. This might have occurredbecause the program ran out of memory.


GLPCDB026W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.


User response: View the earlier error messages forinformation about the exact error.

GLPCDB014E • GLPCDB026W


GLPCDB027E The database name specified, 'databasename', is not a valid name and violatesthe DB2 database name naming rules.

Explanation: The program failed because an invalidDB2 database name was specified.

User response: Specify a DB2 database nameaccording to the following rules: The directory serverinstance name must contain 1 to 8 characters. The namecannot be 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC', or'LOCAL'. The name cannot begin with 'IBM', 'SQL', or'SYS'. The name cannot include accented characters.The name can only include the following characters: Athrough Z, a through z, and 0 through 9. The namemust begin with one of the following characters: Athrough Z or a through z.

GLPCDB030E Failed to reconfigure databasepassword.

Explanation: An internal error occurred while tryingto reconfigure the database password.


GLPCDB031E Unable to determine the primarygroup of the user 'user name'. Theprimary group of the DB2 databaseinstance owner must be valid before adatabase can be configured.

Explanation: The program is unable to validate theprimary group of the DB2 database instance owner.This is most likely an internal error.

User response: Verify that the user name exists on thecomputer and has a primary group assigned to theuser. If the user name and primary group are valid,contact IBM Software Support.

GLPCDB032E Unable to determine the primarygroup of the user 'user name'. Theprimary group of the DB2 databaseadministrator must be valid before adatabase can be configured.

Explanation: The program is unable to validate theprimary group of the DB2 database administrator. Thisis most likely an internal error.

User response: Verify that the user name exists on thecomputer and has a primary group assigned to theuser. If the user name and primary group are valid,contact IBM Software Support.

GLPCDB033E The database instance owner, 'username', and the database administrator,'user name', must have the same primarygroup.

Explanation: The database instance owner anddatabase administrator must be members of the sameprimary group. If this is not true, the directory serverinstance is unable to use DB2 correctly.

User response: Modify the database administrator sothat it has the same primary group as the databaseinstance owner configured for the directory serverinstance.

GLPCDB034E An internal error occurred whileretrieving the database instance for thedirectory server instance.

Explanation: The program encountered an internalerror trying to retrieve the database instance name fromthe directory server instance's configuration file.


GLPCDB036E The database name specified, 'databasename', is reserved for the change logdatabase of the directory server instance.

Explanation: The program failed because a DB2database name was specified that is reserved for thechange log of the directory server instance.

User response: Specify a DB2 database nameaccording to the following rules: The directory serverinstance name must contain 1 to 8 characters. The namecannot be 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC', or'LOCAL'. The name cannot begin with 'IBM', 'SQL', or'SYS'. The name cannot include accented characters.The name can only include the following characters: Athrough Z, a through z, and 0 through 9. The namemust begin with one of the following characters: Athrough Z or a through z.

GLPCDB037W The specified directory, 'directory',does not have read, write, and executepermissions for the primary group 'groupname' of directory server instance owner'username'.

Explanation: The directory specified does not haveread, write, and execute permissions for the primarygroup of the directory server instance owner. Thesepermissions are required for the primary group of thedirectory server instance owner to be able to create atable space directory for the database that will beconfigured for the directory server instance.

User response: Verify that the location where thedatabase will be created is a valid location on the

GLPCDB027E • GLPCDB037W


system and that the primary group of the directoryserver instance owner has write access to that location.The primary group of the directory server instanceowner might not be able to start the directory serverinstance if the permissions on the database location arenot set correctly.

GLPCDB038E Unable to determine the ownershipand permissions on the directory'filename'.

Explanation: The command was unable to determinethe ownership and permissions of the directory wherethe database was going to be created.

User response: Verify that the location where thedatabase will be created is a valid location on thesystem and that the primary group of the directoryserver instance owner has write access to that location.In addition, verify that owner and group owner of thedirectory are still a valid user and group on theoperating system.

GLPCDB040E An incorrect value for the argument'argname' is passed. The valid value forthis argument is an integer greater thanor equal to vldvalue.

Explanation: The value passed to this argument is nota valid value.

User response: Pass a valid value to the argument, orremove the argument if you want to go for the defaultvalue.

GLPCDB042E An incorrect value for the argument'argname' is passed. The valid value forthis argument is SMS or DMS.

Explanation: The value passed for this argument isnot a valid value.

User response: Pass a valid value to the argument, orremove the argument if you want to go for the defaultvalue.

GLPCDB043W No change to the properties oftablespaces will occur as an existingdatabase will be configured for thedirectory server instance 'instance name'.

Explanation: A database is already created for thespecified directory server instance.

User response: Unconfigure the current database fromthe directory server instance if a new database needs tobe configured.

GLPCDB044E Sufficient disk space is not availablefor tablespace container.

Explanation: The free disk space available forcontainer is not sufficient.

User response: Increase the free disk space by deletingunnecessary files or extending the filesystem, reducethe size of tablespace or provide another location withmore free disk space, or create tablespace using the -mSMS option.

GLPCDB047E Error while removing online backupconfiguration.

Explanation: An error occurred while removing onlinebackup configuration.


GLPCDB048E Both the arguments 'c' and 'k' can notbe passed together.

Explanation: Either you can configure online backupor remove online backup configuration if alreadyconfigured.

User response: Select one of the arguments that isapplicable.

GLPCDB050E Specified a backup directory 'filename',that does not exist or is not accessible.

Explanation: An incorrect backup directory wasspecified for backing up the database for the directoryserver instance.

User response: Specify a directory that exists and iswritable.

GLPCDB051E Filename specified with the -u optionis invalid.

Explanation: Value specified with -u option is not avalid filename.

User response: Specify a correct filename and retrythe operation.

GLPCDB052E Filename specified with the -r optionis invalid.

Explanation: Value specified with -r option is not avalid filename.

User response: Specify a correct filename and retrythe operation.

GLPCDB038E • GLPCDB052E


GLPCDB053E Creating a DB2 database in a localcode page with the -x option is notsupported.

Explanation: DB2 9.5 and later changed the defaultdatabase creation from local code page to UTF8.

User response: Configure a DB2 database without the-x option.

GLPCFG001E All fields are required.

Explanation: One or more fields do not have anyvalue. You must specify values for all the fields.

User response: Complete all fields on the panel.

GLPCFG002E Invalid DN.

Explanation: A DN is specified that does not conformto the standards. You must use a well-formeddistinguished name; for example, 'cn=user, o=ibm,c=us'.

User response: Verify that a valid DN with correctsyntax is specified.

GLPCFG003E Passwords do not match.

Explanation: The current panel has a field for thepassword and another for confirming the password.The password entered in the two fields must be exactlythe same in order to set the password. These fields arecase-sensitive. The values specified in the two fields donot match.

User response: Verify that the values in the two fieldsare exactly the same. This includes the case of eachcharacter.

GLPCFG004E Server must be stopped beforerunning this operation.Do you want tostop the server?

Explanation: The operation being attempted requiresthe directory server to be stopped before the operationcan be run.

User response: Stop the directory server instance forwhich this tool is being run and then retry theoperation.

GLPCFG005E Specified directory is not valid.

Explanation: The directory path specified does notexist on the system, is not accessible because ofinsufficient access rights for the user running this tool,or is not a directory.

User response: Verify that the path is an existingdirectory on the system and the user has sufficientaccess rights for it.

GLPCFG006E The specified location location is notvalid. Specify a valid local drive with atleast 30 MB of free space.

Explanation: The current task requires a minimum of30 MB of free space on a valid drive on the operatingsystem for successful completion. The drive must belocal to the system and not a network drive. The drivespecified for this operation does not satisfy thisrequirement.

User response: Verify that the drive has at least 30 MBof free space and is a local drive on the system.

GLPCFG007E The specified location location is notvalid. Specify a valid location with atleast 30 MB of free space.

Explanation: The current task requires a minimum of30 MB of free space in a valid location on the operatingsystem for successful completion. The location specifiedfor this operation does not satisfy this requirement.

User response: Verify that the location is valid andthat it has at least 30 MB of free space.

GLPCFG009E operation failed.

Explanation: The current operation has failed.

User response: Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, see the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.

GLPCFG010E Specified file does not exist.

Explanation: The file path specified does not exist onthe system, is not accessible because of insufficientaccess rights for the user running this tool, or is not afile.

User response: Verify that the path is an existing fileon the system and that the user has sufficient accessrights for it.

GLPCFG011E No file name specified.

Explanation: An attempt has been made to completethe operation without specifying a file name. Thecurrent panel has a field that requires a file path andname to complete the operation.

User response: Verify that a valid file name and filepath are specified in the required field.

GLPCDB053E • GLPCFG011E


GLPCFG012E Specified value is not a valid number.

Explanation: The field is a numeric field and requiresa valid numeric value. The value cannot contain anycharacters other than 0-9 (and '-' to specify a negativevalue).

User response: Enter a valid number.

GLPCFG013W Disabling the change log willdestroy the data currently in the changelog database. Do you still want tocontinue?

Explanation: If the change log database is disabled, allinformation in the change log database is destroyed.

User response: Confirm whether you want to disablethe change log.

GLPCFG015W File already exists. Do you want tooverwrite it?

Explanation: A file already exists with the same namein the specified location. Continuing with the operationwill overwrite it.

User response: Confirm whether you want the file tobe overwritten. If not, specify a different file name.

GLPCFG017E Deletion of a reserved schema file isnot allowed.

Explanation: The directory server has some reserved,pre-defined schema files (for example: V3.system.oc)that are required by the server. These files cannot bedeleted. You are attempting to delete one of thesereserved schema files.

User response: Do not attempt to delete any of thereserved schema files.

GLPCFG018E Deletion of a reserved suffix is notallowed.

Explanation: The directory server has some reserved,pre-defined suffixes (for example: cn=localhost) that arerequired by the server. These suffixes cannot bedeleted. You are attempting to delete one of thesereserved suffixes.

User response: Do not attempt to delete any of thereserved suffixes.

GLPCFG019W Are you sure you want to delete theselected suffix?

Explanation: Continuing with this operation willdelete the suffix from the directory.

User response: Confirm whether you want to deletethe suffix.

GLPCFG020W Are you sure you want to delete theselected Suffixcount suffixes?

Explanation: Continuing with this operation willdelete the selected suffixes from the directory.

User response: Confirm whether you want to deletethe suffixes.

GLPCFG021W Are you sure you want to delete theselected entry?

Explanation: Continuing with this operation willdelete the selected entry from the directory.

User response: Confirm whether you want to deletethe entry.

GLPCFG022W Are you sure you want to delete theselected Entrycount entries?

Explanation: Continuing with this operation willdelete the selected entries from the directory.

User response: Confirm whether you want to deletethe entries.

GLPCFG023W No suffixes are currently available.

Explanation: No suffixes are currently available in thedirectory server instance.

User response: If you believe that suffixes are presentin the directory server instance, verify that the directoryserver configuration file is present and not corrupted. Ifthe file is present and is not corrupted, see the IBMSecurity Directory Server Troubleshooting Guide forinformation about debugging the program, or contactIBM Software Support.

GLPCFG024W No schema files currently available.

Explanation: No schema files are currently availablefor the directory server instance.

User response: Refer to the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.

GLPCFG025E Failed to add suffix suffix.

Explanation: The suffix could not be added to thedirectory server.


GLPCFG012E • GLPCFG025E


GLPCFG026E Failed to add file filename schema file.

Explanation: The schema file could not be added tothe directory server.

User response: Check to see if access permissions tothe directory are available. Alternatively, refer to theIBM Security Directory Server Troubleshooting Guidefor information about debugging the program, orcontact IBM Software Support.

GLPCFG027E Failed to remove suffix suffix.

Explanation: The suffix could not be removed fromthe directory server.


GLPCFG028E Failed to remove schema file filenames.

Explanation: The schema file could not be removedfrom the directory server.


GLPCFG029E Specified database location hasinsufficient free space. Specify a validlocation with minimum 80 MB of freespace.

Explanation: The database location requires aminimum of 80 MB of free space on a valid drive onthe operating system in order to successfully completethe operation. The drive must be local to the systemand not a network drive. The drive specified for thisoperation does not satisfy this requirement.

User response: Verify that the drive has at least 80 MBof free space and is a local drive on the system.

GLPCFG030E Either the specified user ID or thepassword is invalid.

Explanation: The specified user ID is not a valid useron the operating system, or the password for thespecified user is incorrectly entered.

User response: Check to see if the specified user is anoperating system user. If the user ID is valid, verifythat the password is correctly entered. Passwords arecase-sensitive.

GLPCFG031E The specified database is not valid.Enter a valid database.

Explanation: A database name was specified thatcould not be found on the system. To configure anexisting database, a valid database name must bespecified. The database must exist on the system.

User response: Verify that the database nameprovided exists on the system.

GLPCFG032E Failed to drop the current databaseinstance.

Explanation: The database instance could not beremoved from the system. The database instance mightbe locked or in use by another process, or the operatormight not have sufficient privileges to delete thedatabase instance.


GLPCFG034E There is currently no databaseinstance available.

Explanation: There is no database instance configuredor available for the directory server instance. Adatabase instance is required for the current task tocontinue.

User response: Check to see if the database instance iscorrectly installed and configured, or create andconfigure a new database instance and then proceed.

GLPCFG035E There is currently no databaseavailable.

Explanation: There is no database configured oravailable for the directory server instance. A database isrequired for the current task to continue.

User response: Check to see if the database iscorrectly installed and configured, or create andconfigure a new database and then proceed.

GLPCFG038E No database is currently configured.

Explanation: There is no database configured oravailable for the directory server instance. A database isrequired for the current task to continue.

User response: Check to see if the database iscorrectly installed and configured, or create andconfigure a new database and then proceed.



GLPCFG041E Failed to unconfigure database.

Explanation: An error occurred while unconfiguringthe database.


GLPCFG042E Failed to start the task.

Explanation: The current task could not be started.This is normally caused by an internal errorencountered by the tool.

User response: Verify that there are no otherdependent operations running, which might beblocking this task from running. Also verify that thedirectory and the database are correctly configured.

GLPCFG043E Failed to initialize the task.

Explanation: The current task could not be started.This is normally caused by an internal errorencountered by the tool.

User response: Verify that there are no otherdependent operations running, which might beblocking this task from running. Also verify that thedirectory and the database are correctly configured.

GLPCFG044E Task is already running.

Explanation: The current task is already in progress.Another similar task cannot be run simultaneously.

User response: Wait for the current task to becompleted, and then try again.

GLPCFG045E IBM Security Directory Server notinstalled.

Explanation: IBM Security Directory Server does notseem to be installed on the system. Cannot continuewith current task.

User response: Check to see if IBM Security DirectoryServer is correctly installed on the system. Also checkto see if the environment is correctly set up. Thenlaunch the IBM Security Directory Server InstanceAdministration Tool again. If the problem persists, referthe IBM Security Directory Server TroubleshootingGuide for information about debugging the program,or contact IBM Software Support.

GLPCFG048E Target directory could not be created.

Explanation: The program failed to create the targetdirectory. This problem can occur for various reasons.

User response: Ensure that sufficient access rights aregranted to create the target directory and that sufficientfree space is available for the program.

GLPCFG049E Database location not specified in theconfiguration file.

Explanation: The program could not obtain locationinformation about the database from the directoryserver's configuration file.

User response: Ensure that the directory server'sconfiguration file is not corrupted, or replace theconfiguration file with a backed up copy (after makinga backup of the current configuration file).Alternatively, contact IBM Software Support.

GLPCFG050E DB2 could not be found on thesystem.

GLPCFG053E Value specified must be in the rangeof 0 - 2147483647.

Explanation: The number of entries in the change logdatabase can be from a minimum of 0 to a maximumof 214748364.

User response: Enter a valid number in the allowablerange.

GLPCFG054E A dependent task is already runningor is in an incomplete state.

Explanation: The current task cannot be startedbecause a similar or dependent task is already inprogress. Running dependent tasks in parallel can haveunpredictable results.

User response: Ensure that the dependent task hasterminated successfully before starting the new task.Alternatively, make a backup of theINSTANCE_HOME/tmp directory contents, and deletethe directory contents. Then try the task again. If theproblem persists, refer to the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.

GLPCFG066E The specified file system location isnot a valid location.

Explanation: The location path specified does not existon the system, is not accessible because of insufficientaccess rights for the user running this tool, or is not adirectory.

User response: Verify that the path is an existing



location on the system and that the user has sufficientaccess rights for it.

GLPCFG067E Invalid value for 'Days'. Valueexpected in the range 0 - 65535.

Explanation: The value specified for Days is not validor is not within the range of 0-65535.

User response: Specify a value within the range of0-65535.

GLPCFG068E Invalid value for 'Hours'. Valueexpected in the range 0 - 24.

Explanation: The value specified for Hours is notvalid or is not within the range of 0-24.

User response: Verify that a value within the range of0 - 24 is specified.

GLPCFG069E RDBM not installed.

Explanation: The program could not find RDBM(specifically DB2) installed on the system.

User response: Ensure that a valid RDBM (specificallyDB2) is installed on the system.

GLPCFG070E The specified location does notcontain valid backup files of IBMSecurity Directory Server. Specify avalid location.

Explanation: The specified location does not containfiles that contain information about the data to bemigrated, or the backed up files have been corrupted.

User response: Verify that the path is valid and thatthe files required for migration are present at thatlocation. Ensure that the program has sufficient accessrights for the location.

GLPCFG072E One or more ports specified are thesame. Specify unique ports.

Explanation: Two or more ports were specified to aduplicate value. The non-secure slapd, secure slapd,non-secure administration server, and secureadministration server ports must all be unique for aparticular directory server instance.

User response: Verify that all four ports have differentvalues.

GLPCFG073E The IP address ip and port portcombination is already in use byanother directory server instance.Specify a unique IP and portcombination.

Explanation: The specified IP address and portcombination is already being used by an existing

directory server instance on the same system. On asystem with multiple directory server instances, theport and IP address combination used by an instancemust be unique across all the instances.

User response: Try using other values of ports andexisting IP addresses on the system to find a uniqueavailable combination.

GLPCFG074E The user name and password do notmatch the credentials of any existinguser on the system.

Explanation: The user name and correspondingpassword must be those of a valid user on the system.

User response: Verify that the correct user name andpassword are entered, or create an appropriate user onthe system before carrying out this task. Note thatpasswords are case-sensitive.

GLPCFG075E The database names 'ldapclog' and'ldapclgb' are reserved and cannot beused for normal database configuration.

Explanation: The database names 'ldapclog' and'ldapclgb' are reserved names for the change logdatabase used by the IBM Security Directory Server.These databases cannot be used for storing directorydata.

User response: Specify a valid database name.

GLPCFG076E Select either the check box or at leastone IP from list.

Explanation: It is required that the IP settings areconfigured for a directory server instance. Either selecta specific IP address or specify that the instance listensto any of the IP addresses configured on the system.

User response: Select either the check box or at leastone IP address from the list of available IP addresses.

GLPCFG077E The user name username is not a validsystem user.

Explanation: The user name supplied must be that ofa valid user on the system. The user name must bebetween 1 and 8 characters. It cannot be any of thefollowing: 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC','LOCAL'. It cannot begin with 'IBM', 'SQL', 'SYS'. Itcannot include accented characters.

User response: Enter a valid user name.

GLPCFG078E DB2 instance InstanceName is alreadyassociated with another directory serverinstance.

Explanation: The DB2 instance name specified isalready in use by another directory server instance. TheDB2 instance must be unique for each directory server



instance. During migration, the DB2 instance name isread from the backup configuration file. That particularDB2 instance must be present on the system and cannotbe associated with any other directory server instance,or the migration will fail.

User response: Verify that an available DB2 instancename is specified, and not one that is alreadyassociated with another directory server instance. Incase of migration, ensure that the DB2 instance readfrom the backup configuration file actually exists on thesystem and is not associated with any other directoryserver instance.

GLPCFG079E The user name cannot contain morethan count characters.

Explanation: The user name supplied must be that ofa valid user on the system. The user name mustcontain between 1 and 8 characters. It cannot be any ofthe following: 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC','LOCAL'. It cannot begin with 'IBM', 'SQL', 'SYS'. Itcannot include accented characters.

User response: Verify that the name does not exceedthe character limit.

GLPCFG080E The user name is not a valid nameand violates the directory serverinstance naming rules.Only the a-z, A-Z,and 0-9 characters are allowed. The username cannot include accented charactersor certain reserved keywords.

Explanation: The user name specified can contain onlycharacters a-z, A-Z, and 0-9. It cannot be any of thefollowing: 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC','LOCAL'. It cannot begin with 'IBM', 'SQL', 'SYS'. Itcannot include accented characters. Also, on AIX,Linux, Solaris, and HP-UX, the user name cannot be'root'.

User response: Verify that the name containscharacters in the specified range only.

GLPCFG081E The directory server instance'DirInstanceName' already exists. Specifya unique value.

Explanation: The directory server instance is createdwith the same name as the specified user name. Adirectory server instance with the specified user namealready exists on the system. During migration, theuser name is shown pre-filled with the DB2 instancename detected from the backup configuration file. If adirectory server instance with the same name alreadyexists on the system, you cannot continue withmigration until a different user name is specified.

User response: Verify that a unique and valid systemuser name is specified. Also, check that there is notalready a directory server instance with the same name.

GLPCFG082E The encryption seed must containonly printable ISO-8859-1 ASCIIcharacters with values in the range of 33to 126 inclusive.The encryption seedmust be a minimum of 12 and amaximum of 1016 characters in length.

Explanation: The encryption seed string must containat least 12 characters in the range of a-z, A-Z, and 0-9.

User response: Verify that the seed string satisfies thisrequirement.

GLPCFG083E Only a-z, A-Z, and 0-9 allowed.

Explanation: Only characters in the range a-z, A-Z,and 0-9 are allowed.

User response: Verify that the above requirement issatisfied.

GLPCFG084E The user name cannot start with anumber.

Explanation: The user name must start with acharacter in the range a-z or A-Z. The first charactercannot be a number.

User response: Verify that the user name is valid.

GLPCFG085E The encryption seed string cannotstart with a number.

Explanation: The encryption seed string must startwith a character in the range a-z or A-Z. The firstcharacter cannot be a number.

User response: Verify that the encryption seed stringis valid.

GLPCFG086E An internal error has occurred.

Explanation: An internal error occurred.

User response: Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, see the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.

GLPCFG087E The operation did not completesuccessfully.

Explanation: The current operation could notcomplete successfully.

User response: Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, see the IBM Security Directory ServerTroubleshooting Guide for information about



debugging the program, or contact IBM SoftwareSupport.

GLPCFG088E DB2 database is required tosuccessfully migrate the specifieddirectory server.

Explanation: Migration of a directory server requiresthat DB2 be installed on the system. This is because thebacked up files contain database configurationinformation.

User response: Verify that DB2 is installed andcorrectly set up before continuing with migration.

GLPCFG089W You have chosen to delete directoryserver instance instname. This will resultin deletion of the instance configurationfile, schema files, log files, directories,and other directory server instancesystem files. The associated database (ifany) will not be deleted. Do you wantto continue?

Explanation: Deletion of the directory server instanceresults in deletion of the instance specific configurationfiles, log files, instance specific directories, schema files,and all other files that store the current instance'sconfiguration settings and other information. Theassociated database, if there is one, will not be deletedor tampered with in any way.

User response: Confirm whether you want to deletethe directory server instance.

GLPCFG090W You have chosen to delete directoryserver instance instname and to destroythe associated database instance dbinst.This will result in deletion of theinstance configuration file, schema files,log files, directories, and relateddatabase information. Do you want tocontinue ?

Explanation: Deletion of the directory server instanceresults in deletion of the instance specific configurationfiles, log files, instance specific directories, schema files,and all other files that store the current instance'sconfiguration settings and other information. Theassociated database instance (and databases containedwithin that instance) will also be destroyed, along withany data present in the databases.

User response: Confirm whether you want to destroythe directory server instance and associated databaseinstance.

GLPCFG091E The directory server instance iscurrently running. You must stop thedirectory server before deleting it.

Explanation: A directory server instance cannot bedeleted if it is currently running.

User response: Stop the directory server instance andretry the delete operation.

GLPCFG093E This directory server instance has noassociated DB2 instance. Cannot proceedwith database configuration.

Explanation: The directory server instance does nothave a DB2 instance.

User response: Create a DB2 instance for the specifieddirectory server instance and then proceed withdatabase configuration.

GLPCFG094W Database will be unconfigured. Doyou want to continue?

Explanation: Continuing with the current task willresult in the directory server instance losing itsdatabase configuration information.

User response: Confirm whether you want tounconfigure the database information.

GLPCFG095W Database will be unconfigured anddestroyed. Do you want to continue?

Explanation: Continuing with the current task willresult in the directory server instance losing itsdatabase configuration information. It will also destroythe associated database and directory data within thatdatabase.

User response: Confirm whether you want tounconfigure and destroy the database information.

GLPCFG097E Failed to set administrator DN.

Explanation: The program failed to set theadministrator DN.

User response: Verify that the instance is installedproperly and the operator has sufficient access rights toperform the operation. Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, see the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.



GLPCFG099E Failed to set administrator password.

Explanation: The program failed to set theadministrator password.

User response: Verify that the instance is installedproperly and the operator has sufficient access rights toperform the operation. Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, see the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.

GLPCFG100E The default directory server instancecould not be determined. Use the -Ioption to specify the instance, or set theIDS_LDAP_INSTANCE environmentvariable before launching idsxcfg.

Explanation: The program failed to determine theinstance associated with the current idsxcfg session.This failure can occur if no instance exists or if morethan one instance exists.

User response: Ensure that a directory server instanceexists, or create one using the idsicrt command or theIBM Security Instance Administration Tool. You can usethe -I option with the idsxcfg command or set theIDS_LDAP_INSTANCE environment variable to theinstance you want to configure using idsxcfg.

GLPCFG101E The directory server instance'instance_name' does not exist.

Explanation: The program could not locate theinstallation home of the specified instance.

User response: Ensure that the instance namespecified exists and is valid. If the problem persistsrefer to the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program, or contact IBM SoftwareSupport.

GLPCFG102E The directory server instance owner,'user name', must be a member of theprimary group, 'group name', of thedatabase instance owner, 'user name'.

Explanation: The directory server instance ownermust be a member of the primary group of thedatabase instance owner. They need not be in the sameprimary group, but the directory server instance ownermust be in that primary group.

User response: Add the directory server instanceowner user name to the primary group of the directoryserver instance owner.

GLPCFG103E The directory server instance owner,'user name', must be a member of thegroup 'idsldap'.

Explanation: The directory server instance ownermust be a member of the idsldap group.

User response: Add the directory server instanceowner user name to the idsldap group.

GLPCFG104E The password specified violatesadministrator password policy. Aminimum of number of characterscharacters is required.

Explanation: You specified a password that violatesthe administrator password policy because the lengthof the password was too short.

User response: Specify a password that is greater thanor equal to the length specified in the error message.

GLPCFG105E The password specified violatesadministrator password policy. Aminimum of number of charactersalphabetic characters is required.

Explanation: You specified a password that violatesthe administrator password policy because thepassword does not contain enough alphabeticcharacters.

User response: Specify a password that has sufficientalphabetic characters to comply with the administratorpassword policy.

GLPCFG106E The password specified violatesadministrator password policy. Aminimum of number of charactersnon-alphabetic characters is required.

Explanation: You specified a password that violatesthe administrator password policy because thepassword does not contain enough non-alphabeticcharacters.

User response: Specify a password that has sufficientnon-alphabetic characters to comply with theadministrator password policy.

GLPCFG107E The password specified violatesadministrator password policy. Amaximum of number of charactersrepeated characters is allowed.

Explanation: You specified a password that violatesthe administrator password policy because thepassword has too many repeated characters.

User response: Specify a password that does notcontain more than the maximum number of repeatedcharacters to comply with the administrator passwordpolicy. The maximum number of repeated characters is



shown in the error message.

GLPCFG108E The password specified violatesadministrator password policy. Aminimum of number of characterscharacters must be different from theprevious password.

Explanation: You specified a password that violatesthe administrator password policy because thispassword does not have enough characters that differfrom the previous password.

User response: Specify a password that does not havetoo many matching characters from the previouspassword to comply with the administrator passwordpolicy. The minimum number of characters that mustdiffer is shown in the error message.

GLPCFG109E The backup directory specified'directory', does not exist or is notaccessible.

Explanation: A backup directory that is not valid wasspecified for migrating an older directory serverinstance.

User response: Specify a directory that exists andcontains configuration and schema files that can bemigrated.

GLPCFG110E An unsupported version was givenfor migration.

Explanation: Unable to migrate from the IBM SecurityDirectory Server version given.

User response: Ensure that the correct version of thefiles are in the backup directory. Otherwise, this is not asupported migration path.

GLPCFG111E Unable to locate file 'filename'.

Explanation: A file required for migration cannot belocated in the backup directory.

User response: Ensure that all files are backed up andtry the migration again. See the IBM Security DirectoryServer Installation and Configuration Guide forinformation about files required for migration.

GLPCFG112E Unable to determine location ofconfiguration file.

Explanation: Cannot read the required configurationfile. Migration cannot continue.

User response: Ensure that the configuration file existsin the migration backup and is readable.

GLPCFG113E Unable to read configuration file'filename'.

Explanation: Cannot read required configuration file.Migration cannot continue.

User response: Ensure that the given file exists and isreadable.

GLPCFG114E Files in backup directory 'directory' aredetermined to be of version 'version'.Migration will continue based on thismigration path.

GLPCFG115E The log file name and pathinformation from the backed upconfiguration file will not be preservedby migration. Log file names and pathswill be updated to be specific for adirectory server instance.

Explanation: Because multiple directory serverinstances are supported on a system, the log files havebeen relocated to the log directory for a particulardirectory server instance. The log file names mighthave also been changed.

User response: The path and name changes must benoted and reflected in any applications that depend onthem.

GLPCFG116E Unable to run command on directoryserver instance because the state of theserver cannot be determined.

Explanation: An attempt was made to run thecommand on the directory server instance and its statecould not be determined.

User response: This error most likely occurredbecause you do not have sufficient access to check thestatus of the server. Verify that the server's slapd.pidfile has sufficient access for you to read it. Also checkto see if the server is configured properly.

GLPCFG117E A required field has not been entered.

Explanation: One or more required fields do not haveany value.

User response: Verify that all required fields havebeen filled with correct values.

GLPCFG118W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPCFG108E • GLPCFG118W


GLPCFG119E Select a directory server instance.

Explanation: The current operation cannot continueuntil you select a directory server instance.

User response: Choose an existing directory serverinstance before continuing with the current operation.

GLPCFG120E The encryption seed and salt valuesare required. If you do not want tospecify these values, clear the Exportdata for AES-enabled destination servercheck box.

Explanation: If the exported data must be imported toan AES enabled directory server, the encryption seedand salt values of the destination server must bespecified. If the encryption seed and salt values of thedestination server are the same as those on the sourceserver, clear the Export data for AES-enableddestination server check box.

User response: Enter the encryption seed and saltvalues, or clear the check box.

GLPCFG121E The encryption salt must only containprintable ISO-8859-1 ASCII characterswith values in the range of 33 to 126,and must be exactly 12 characters inlength.

Explanation: The encryption salt must meet theserequirements.

User response: Enter a valid encryption salt value thatmeets the requirements.

GLPCFG122E The Admin DN and password mustbe configured before continuing withthis operation.

Explanation: The Admin DN and password must beset for the selected operation.

User response: Set the Admin DN and password andthen retry the operation.

GLPCFG123W You have not changed the originalsettings. Do you want to continue?

Explanation: You chose to edit some of the settingsbut did not change any of them.

User response: Change some of the settings andcontinue, or cancel the operation.

GLPCFG124E The database instance'db2InstanceName' is not present on thesystem. Migration cannot continue.

Explanation: The backup configuration file contains areference to a database instance that does not exist onthe system. For migration to continue, this database

instance must be created on the system, or the instanceinformation must be removed from the backupconfiguration file.

User response: Create the required DB2 instance onthe system, or if the database instance exists, ensurethat it is correctly set up. Alternatively, remove thedatabase instance information from the backupconfiguration file. Only advanced users shouldmanually edit the backup configuration file.

GLPCFG125E The database 'databaseName' is notpresent on the system. Migration cannotcontinue.

Explanation: The backup configuration file contains areference to a database that does not exist on thesystem. For migration to continue, this database mustbe created on the system, or the database informationmust be removed from the backup configuration file.

User response: Create the required database on thesystem, or if the database exists, ensure that it iscorrectly set up and is present in the appropriatedatabase instance. Alternatively, remove the databaseinformation from the backup configuration file. Onlyadvanced users should manually edit the backupconfiguration file.

GLPCFG126E The directory server instance owner,'username', must be a member of thegroup 'Administrators'.

Explanation: The directory server instance ownermust be a member of the Windows Administratorsgroup.

User response: Add the directory server instanceowner user name to the Windows Administratorsgroup or choose another user name that is already inthe Administrators group.

GLPCFG127E 'root' must be a member of theprimary group, 'groupName', of thedatabase instance owner, 'username'.

Explanation: The root user must be a member of thedatabase instance owner's primary group.

User response: Add root to the database instanceowner's primary group.

GLPCFG128E Encryption seed values do not match.

Explanation: The current panel has a field for theencryption seed value and another for encryption seedconfirmation. The encryption seed values entered in thetwo fields must be exactly the same in order to set thefinal seed value. The values specified in the two fieldsdo not match. These fields are case-sensitive.

User response: Verify that the values entered are



exactly the same. This includes the case of eachcharacter.

GLPCFG129E Unable to connect to the server atldapURL

Explanation: Unable to connect to the specifieddirectory server.

User response: Verify that the specified LDAP URL isvalid.

GLPCFG130E The server, ldapURL is running inconfiguration only mode

Explanation: The specified server is running inconfiguration only mode.

User response: Verify that the server specified by theLDAP URL is not running in configuration mode.

GLPCFG131E The server, ldapURL is not running asupported version.

Explanation: The specified server is running theprevious version of IBM Security Directory Server.

User response: Ensure that the server specified by theLDAP URL is running the latest version of IBMSecurity Directory Server.

GLPCFG132E No permission to access the server,ldapURL

Explanation: No permission is granted on thespecified server.

User response: Verify that the user has sufficientaccess rights.

GLPCFG133E Administrator DN or password of theselected instance is not configured.

Explanation: Administrator DN and password of theselected instance must be configured.

User response: Configure the administrator DN andpassword for the selected instance.

GLPCFG134E No path specified.

Explanation: An attempt has been made to completethe operation without specifying the directory path.The directory path is required.

User response: Specifiy a valid directory path.

GLPCFG135E Unable to retrieve information fromthe specified server

Explanation: Unable to retrieve information (includingconfiguration mode, server back-end type, and version)from source server.

User response: Verify that an entry exists.

GLPCFG136E Path for backup images is requiredwhile setting up a peer or replica server.

Explanation: Path for the backup images is requiredwhile setting up peer or replica server.

User response: Verify that the option to copy datafrom the source instance is checked.

GLPCFG137E Unable to add or update the user.

Explanation: Add or update operation failed for thespecified user.

User response: Verify that the user information isvalid.

GLPCFG138E Provide the primary group of theuser.

Explanation: Primary group is required.

User response: Provide the primary group for theuser.

GLPCFG139E Encryption salt value mismatch.

Explanation: The current panel has a field forencryption salt value and another for encryption saltconfirmation. The encryption salt values entered in thefields must be exactly the same in order to set the finalencryption salt value. The values specified in the twofields do not match. These fields are case-sensitive.

User response: Verify that the values entered in thetwo fields are exactly the same. This includes the caseof each character.

GLPCFG140E Unable to load existing configuration.

Explanation: Unable to load the existing configurationfrom the external properties file.

User response: Verify that the external properties fileand configuration file to read this properties file are inplace.

GLPCFG141W No performance tuning updates arerequested. Do you want to continue?

Explanation: No performance tuning updates will beperformed.

User response: Confirm whether performance tuningupdates are required or not.

GLPCFG129E • GLPCFG141W


GLPCFG142E Unable to load 'statFile'

Explanation: Unable to load status file.

User response: Verify that the status file exists at thespecified location.

GLPCFG143E Unable to fetch total number ofentries and average size of an entry inserver instance database. Use commandline option to update 'inputFile'.

Explanation: Unable to fetch total number of entriesand average size of an entry in server instancedatabase.

User response: Use command line option to updateperftune_input.conf file.

GLPCFG144E The suffix 'suffix' conflicts with anexisting suffix.

Explanation: The suffix conflicts with an existingsuffix in configuration file.

User response: Nested suffix addition is not allowed.

GLPCFG145E The password specified violatesadministrator password policy. Amaximum of number of charactersconsecutive repeated characters isallowed.

Explanation: You specified a password that violatesthe administrator password policy because thepassword has too many consecutive repeatedcharacters.

User response: Specify a password that does not havetoo many consecutive repeated characters to complywith the administrator password policy. The maximumnumber of consecutive repeated characters was shownin the error message.

GLPCFG146E Server must be started before runningthis operation.Do you want to start theserver?

Explanation: The operation being attempted requiresthe directory server to be started before the operationcan be run.

User response: Start the directory server instance forwhich this tool is being run and then retry theoperation.

GLPCFG147E Data not valid in 'field'.

Explanation: Invalid data for the given field

User response: Verify that the input for the given fieldis valid

GLPCFG148E 'field value' is not a valid value.

Explanation: Invalid data for the given field

User response: Verify that the input for the given fieldis valid

GLPCFG149E Specified location is not valid.

Explanation: The directory or file path specified doesnot exist on the system, is not accessible because ofinsufficient access rights for the user running this tool.

User response: Verify that the path is an existingdirectory or file on the system and the user hassufficient access rights for it.

GLPCFG150E Specified file already exists.

Explanation: The specified file already exist indirectory. Please specify non-existing file.

User response: Provide non-existing file.

GLPCFG151E Invalid administrator DN orpassword.

Explanation: Specified administrator DN or passwordis incorrect.

User response: Verify the specified administrator DNor password.

GLPCFG152E None of the options is selected.

Explanation: None of the options is selected.

User response: Verify that atleast one of the options isselected.

GLPCFG153E Unable to locate the specifiedcommand. 'cmd'

Explanation: Unable to locate the specified command.

User response: Verify the specified location

GLPCFG154E Unable to generate statistics usingperftune, refer task messages.

Explanation: Error occurred while executing perftune.

User response: Error occurred while executingperftune.

GLPCFG159E Failed to start administration server.

GLPCFG160E Failed to stop administration server.



GLPCFG164E Failed to stop server instance.

GLPCFG168E Initial size must be greater thaninitialValue pages.

Explanation: Invalid value for initial size

User response: Verify that the input for the initial sizeis valid

GLPCFG169E IBM Tivoli Directory Integrator (TDI)is not detected on the system. If TDI isinstalled at custom install location thenset IDS_LDAP_TDI_HOME to TDIinstall location and restart the utility.

Explanation: The utility has failed to detect IBM TivoliDirectory Integrator as it is either not installed orinstalled at custom install location.

User response: If IBM Tivoli Directory Integrator isinstalled at custom install location then setIDS_LDAP_TDI_HOME environment variable to IBMTivoli Directory Integrator install location and restartthe program.

GLPCOM001E Creation of socket failed; errno errorvalue (error string).

Explanation: The server received the specified errorattempting to create a socket.


GLPCOM002E The listen() failed; errno error value(error string).

Explanation: The server received the specified errorattempting to listen on the socket.


GLPCOM005E SocketInit failed for port port number.

Explanation: The server is unable to initialize thespecified port for communications using IPV6 on theWindows operating system.

User response: Ensure that TCP/IP is operatingcorrectly. Check for other error messages. Ensure thatno other applications are running on the specified port.


Explanation: The server is unable to initialize thespecified port for communications.


GLPCOM007E No objectclass was specified forentry entry DN.

Explanation: All entries must have an objectclassattribute.

User response: Verify the LDIF syntax and retry therequest.

GLPCOM008E The required attribute attribute nameis missing for entry entry DN.

Explanation: An attribute required by the entry'sobjectclass was not provided.


GLPCOM009E The attribute attribute name is notallowed for entry entry DN.

Explanation: A specified attribute is not allowed bythe entry's objectclass.


GLPCOM012E Failed to load plugin from pluginlocation.

Explanation: The server failed to load the plugin.

User response: Make sure that the plugin path nameand the initial function name are specified correctly.

GLPCOM013E Attribute attribute name not found inschema.

Explanation: All attributes used in a request must bedefined in the server's schema files.


GLPCOM014E Failed to log on user: user name.

Explanation: The application was unable to log in tothe Windows operating system as the specified user.

User response: Verify the Windows user settings andmake sure that the account exists and is not expired,that the password is valid, and that the user is able tolog on.

GLPCOM015E Failed to impersonate user.

Explanation: The application was unable to becomethe Windows user.

User response: Verify the Windows user settings andensure that the account exists and is not expired, thatthe password is valid, and that the user is able to logon.

GLPCFG164E • GLPCOM015E


GLPCOM016E Windows operating system error

Explanation: The Windows operating system gave anerror when running a command.

User response: Refer to the Windows documentationfor this problem.

GLPCOM017W Log file cleared.

Explanation: One of the directory server log files wascleared by the user.

User response: If the action was unexpected, checkthe audit log (if enabled) to determine which clientissued the operation.

GLPCOM018E Call to setsockopt() to set reusefailed; errno error value (error string).

Explanation: The server received the specified errorattempting to set the socket option: reuse.


GLPCOM019E The listen() failed; errno error value(error string).

Explanation: The server received the specified errorattempting to listen on the socket using IPV6 on theWindows operating system.



Explanation: The server is unable to initialize thespecified port for communications using IPV6.


GLPCOM026E Objectclass objectclass name not foundin schema.

Explanation: All objectclasses used in a request mustbe defined in the server's schema files.


GLPCOM027E Attempt to bind failed with errnoerror value (error string).

Explanation: The server received the specified errorattempting to bind to the socket.


GLPCOM028E Codepage codepage value cannot beopened by LDAP server: errno message.

Explanation: The specified code page cannot beopened.

User response: Ensure that the correct code page isspecified and installed.

GLPCOM029E LDAP Configuration file cannot befully translated to UTF-8 codepage: errnomessage.

Explanation: The server failed to translate theconfiguration file to UTF-8.

User response: Ensure that the correct code page isspecified and installed and that the characters in theconfiguration file are valid.

GLPCOM032W Warning: The attribute table nametable name is longer than 128 characters,so the table will be created with thename hashed table name.

Explanation: The maximum table name lengthsupported by DB2 is 128 bytes. When a table name isnot specified in DBNAME and attribute name is longerthan 128 bytes, a unique 128-byte table name isgenerated using the first 121 bytes of the attributename followed by 7-byte hashed value of the attributename.

User response: No further action is required.

GLPCOM034E This command cannot be startedwhile a backup for directory serverinstance instance name is in progress.

Explanation: This command cannot run at the sametime as a backup.

User response: Wait for the backup to complete andthen retry the request.

GLPCOM035E This command cannot be startedwhile a restore for directory serverinstance instance name is in progress.

Explanation: This command cannot run at the sametime as a restore.

User response: Wait for the restore to complete andthen retry the request.

GLPCOM036E select() system call failed; errno errorvalue (error string).

Explanation: The server received the specified errorattempting to read client activity.


GLPCOM016E • GLPCOM036E


GLPCOM037E This command cannot be started fordirectory server instance instance namewhile bulkload is in progress.

Explanation: This command cannot run at the sametime as bulkload.

User response: Wait for bulkload to complete andthen retry the request.

GLPCRY003E The encryption seed must containonly printable ISO-8859-1 ASCIIcharacters with values in the range of 33to 126, and must be a minimum of 12and a maximum of 1016 characters inlength.

Explanation: The program failed because an incorrectencryption seed value was specified.

User response: Specify an encryption seed value thatcomplies with the supported format.

GLPCRY004E The encryption salt must contain onlyprintable ISO-8859-1 ASCII characterswith values in the range of 33 to 126,and must be exactly 12 characters inlength.

Explanation: The program failed because an incorrectencryption salt value was specified.

User response: Specify an encryption salt value thatcomplies with the supported format.

GLPCRY007E The file name key stash file isinconsistent with the associatedencrypted data.

Explanation: The key stash file does not match theassociated encrypted data. The program cannot bestarted if this inconsistency is encountered.


GLPCRY008E Attempting to write two-wayencrypted data without the required keystash file consistency checking.

Explanation: The program is unable to determinewhether the data being written was two-way encryptedusing a matching key stash file. The data cannot bewritten because it might introduce cryptographicinconsistency.


GLPCRY009E Password value could not bedecrypted.

Explanation: The password is corrupted, or theconfiguration file has been edited manually and nowthe encryption and decryption keys do not match.

User response: Re-enter the password in clear textand restart the server; the password will bere-encrypted by the server.

GLPCSC002E An internal error occurred whilerunning the idscfgsch command.

Explanation: An internal error occurred while runningthe idscfgsch command. This might have occurredbecause the program ran out of memory.


GLPCSC003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPCSC006E Failed to add schema file: 'schemafile'.

Explanation: An error occurred while trying to addthe schema file to the configuration file of the directoryserver instance.

User response: Look for previous error messages thatmight have been generated for details on how torespond. If no other error messages are present, contactIBM Software Support.

GLPCSC008E The specified schema file 'schemafile'does not exist on the system or is notaccessible.

Explanation: A schema file can be added to aconfiguration file of the directory server instance only ifthe schema file exists on the system and is accessible.

User response: Specify a schema file that exists on thesystem and ensure that the file is readable.

GLPCSC009E The schema file 'schemafile' alreadyexists in the configuration file of thedirectory server instance.

Explanation: Tried to add a schema file that is alreadyconfigured.

GLPCOM037E • GLPCSC009E


User response: If needed, specify a schema file thathas not been configured using the idscfgsch command.

GLPCSC010E The -s option is required and is usedto specify the name of the schema file toadd.

Explanation: The -s option was not specified and it isrequired.

User response: Specify the -s option. Use the -? optionto see the syntax for the command.

GLPCSC011E The specified schema file 'schemafile' isa directory.

Explanation: A schema file can be added to aconfiguration file of the directory server instance only ifthe schema file exists on the system and is a file, not adirectory.

User response: Specify a schema file that exists on thesystem and is readable. Verify that the schema filespecified is not a directory.

GLPCSF002E An internal error occurred whilerunning the idscfgsuf command.

Explanation: An internal error occurred while runningidscfgsuf command. This might have occurred becausethe program ran out of memory.

User response: See IBM Security Directory ServerProduct Overview for information about hardware andsoftware requirements. If all requirements are met,attempt to run the command again. If the problempersists, contact IBM Software Support.

GLPCSF003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.


User response: View the earlier error messages forinformation about the exact error. If the problempersists, contact IBM Software Support.

GLPCSF006E Failed to add suffix: 'suffix'.

Explanation: An error occurred while trying to addthe suffix to the configuration file of the directoryserver instance.


GLPCSF008E The suffix 'suffix' conflicts with anexisting suffix in the configuration fileof the directory server instance.

Explanation: Tried to add a suffix which is eitheralready configured, or is a parent or child of a suffixthat is already configured for the directory serverinstance. Nested suffixes are not allowed. Suffixescannot be sub-entries of one another.

User response: None.

GLPCSF009E The -s option is required and is usedto specify the name of the suffix to add.



GLPCTL001E A directory server instance was notspecified.

Explanation: The command requires that a directoryserver instance be specified.

User response: Specify a directory server instancewith the -I option or set the directory server instanceusing the environment variable IDS_LDAP_INSTANCE.

GLPCTL004E Failed to create database instance:'instance name'. The failure might haveoccurred because the system was not setup correctly before using the tool.

Explanation: The program failed while trying to createa database instance.

User response: Review the information aboutconfiguring the database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configurationtools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase instance will be created. In addition, look inthe directory server's DB2 Command Log File and thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated.After verifying and correcting all required systemsettings, run the configuration tool again. If theprogram still fails, look in the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCTL007W Failed to remove database instance:'instance name'.

Explanation: The program failed to successfullyremove the database instance. This might havehappened because the database instance did not exist.

GLPCSC010E • GLPCTL007W


User response: Verify that the database instance stillexists on the system. This can be achieved with thedb2ilist command. If the database instance has beenremoved, no further action is necessary. In addition,look in the directory server's DB2 Command Log Fileand the directory server instance's DB2 logs foradditional errors or warnings that might have beengenerated. If the configuration tools continue to showthis warning message, restart the computer and try toproduce the warning again before contacting IBMSoftware Support.

GLPCTL010E Failed to start database manager fordatabase instance: 'instance name'.

Explanation: The program failed to start the databasemanager for the database instance.

User response: Verify that the system has enoughvirtual memory for the buffer pool setup for thedatabase. Refer to the IBM Security Directory ServerPerformance Tuning Guide for information aboutconfiguring the buffer pool size for a database. Verifythat the environment variable DB2COMM is not setbefore running the tool. In addition, look in thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated.

GLPCTL013W Failed to stop database manager forthe database instance: 'instance name'.

Explanation: The program failed to stop the databasemanager for the database instance.

User response: Verify that other applications are notconnected to a database under the DB2 instance beingaffected. Verification might be necessary if the programdoes not complete successfully. In addition, look in thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated. Ifthe configuration tools continue to show this warningmessage, restart the computer and try to produce thewarning again before contacting IBM Software Support.

GLPCTL016W Failed to uncatalog database instancenode: 'instance name'.

Explanation: The program failed to successfullyuncatalog the database instance node. This might havehappened because the database instance did not existon the system.

User response: Verify that the database instance stillexists by using the db2ilist command. If the databaseinstance does not exist, no further action is necessary.Verification might be necessary only if the programdoes not complete successfully. In addition, look in thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated. Ifthe configuration tools continue to show this warningmessage, restart the computer and try to produce thewarning again before contacting IBM Software Support.

GLPCTL019E Failed to catalog database instancenode: 'instance name'. The failure mighthave occurred because the system wasnot set up correctly before using thetool.

Explanation: The program failed while trying tocatalog a database instance node.

User response: Review the information aboutconfiguring a database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configurationtools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase will be created. In addition, look in thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated.After verifying and correcting all required systemsettings, run the configuration tool again. If theprogram still fails, look in the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCTL022E Failed to update the databasemanager: 'instance name'.

Explanation: The program failed while attempting toupdate the database manager. The failure occurredwhile updating the Query Heap Size (query_heap_sz)of the DB2 database manager to 2048 Pages where eachPage is 4 KB.


GLPCTL025W Failed to enable multi-page fileallocation: 'database name'

Explanation: The program failed while enablingmulti-page file allocation on the database beingconfigured. This is a performance enhancement for thedatabase and will not stop the configuration processfrom completing successfully.

User response: On AIX, Linux, Solaris, and HP-UXsystems, verify that the login shell for the DB2 instanceowner ID, DB2 administrator ID, and root default shellis the Korn shell script (/usr/bin/ksh). In addition,look in the directory server's DB2 Command Log Filefor additional errors or warnings that might have beengenerated. The db2empfa DB2 command can then berun against the configured database manually to enablemulti-page file allocation.

GLPCTL010E • GLPCTL025W


GLPCTL028E Failed to create database: 'databasename'. The failure might have occurredbecause the system was not set upcorrectly before using the tool.

Explanation: The program failed while trying to createa database.

User response: Review the information aboutconfiguring the database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configurationtools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase will be created. Verify that the password ofthe specified user has not expired and the account ofthe user has not been locked out. After verifying andcorrecting all required system settings, run theconfiguration tool again. If the program still fails, lookin the IBM Security Directory Server TroubleshootingGuide for information about debugging the programand contacting IBM Software Support.

GLPCTL029E User 'user name' does not have correctsystem permissions to create a databasein 'location'

Explanation: The program failed while trying to createa database because the DB2 administrator ID specifieddid not have the necessary permissions.

User response: Review the information aboutconfiguring the database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configurationtools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase will be created. In addition, look in thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated.After verifying and correcting all required systemsettings, run the configuration tool again.

GLPCTL030E The DB2 administrator ID orpassword specified is not valid.

Explanation: The DB2 administrator ID specified didnot exist or the password specified was not valid forthe DB2 administrator ID. This error was detectedwhile trying to create the DB2 database.

User response: Specify an existing user ID on thesystem and the valid password. Verify that the user IDhas a password that is valid and ready to use. Forexample, the password cannot be expired or waiting fora first-time validation of any kind. You might be able toverify that the password is correctly set by attemptingto telnet into the computer using the user ID.

GLPCTL033W Failed to remove database: 'databasename'.

Explanation: The program failed to successfullyremove the database. This might have happenedbecause the database did not exist.

User response: Verify that the database still exists onthe system. If the database has been removed, nofurther action is necessary. If the configuration toolscontinue to show this warning message, restart thecomputer and try to produce the warning again beforecontacting IBM Software Support.

GLPCTL036E Failed to update the database: 'databasename'

Explanation: An internal error occurred while tryingto update the database.


GLPCTL039E Failed to add local loopback todatabase: 'database name'. The failuremight have occurred because the systemwas not set up correctly before using thetool.

Explanation: The program failed while trying to addlocal loopback to the database. This means it failed toadd a database alias for the database being configured.

User response: Review the information aboutconfiguring the database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configurationtools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase will be created. In addition, look in thedirectory server's DB2 Command Log File and thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated.After verifying and correcting all required systemsettings, run the configuration tool again. If theprogram still fails, look in the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCTL042W Failed to remove local loopback fromdatabase: 'database name'.

Explanation: The program failed to successfullyremove the database local loopback. This might havehappened because the database alias did not exist.

GLPCTL028E • GLPCTL042W


User response: If the configuration tools continue toshow this warning message, restart the computer andtry to produce the warning again before contacting IBMSoftware Support.

GLPCTL045E Failed to add local loopback to changelog database: 'database name'. The failuremight have occurred because the systemwas not set up correctly before using thetool.

Explanation: The program failed while trying to addlocal loopback to the changelog database. This means itfailed to add a database alias for the database beingconfigured.

User response: Review the information aboutconfiguring the database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configurationtools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase will be created. In addition, look in thedirectory server's DB2 Command Log File and thedirectory server instance's DB2 logs for additionalerrors or warnings that might have been generated.After verifying and correcting all required systemsettings, run the configuration tool again. If theprogram still fails, look in the IBM Security DirectoryServer Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCTL048W Failed to remove local loopback fromthe changelog database: 'database name'.

Explanation: The program failed to successfullyremove the changelog database local loopback. Thismight have happened because the database alias didnot exist.

User response: Look in the directory server's DB2Command Log File for additional errors or warningsthat might have been generated. If the configurationtools continue to show this warning message, restartthe computer and try to produce the warning againbefore contacting IBM Software Support.

GLPCTL051E Failed to add TCP/IP services todatabase instance: 'instance name'. Thefailure might have occurred because thesystem was not set up correctly beforeusing the tool.

Explanation: The program failed while trying to addTCP/IP services to a database instance.

User response: Review the information aboutconfiguring the database in the IBM Security DirectoryServer Installation and Configuration Guide and verifythat the required system settings for the configuration

tools are correctly set. This includes requirementsregarding user setup, group setup, and the free spaceand write permissions on the location where thedatabase instance will be created. In addition, look inthe directory server's DB2 Command Log File and thedirectory server instance's DB2 logs for additional erroror warnings that might have been generated. Afterverifying and correcting all required system settings,run the configuration tool again. If the program stillfails, look in the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPCTL054W Failed to remove TCP/IP servicesfrom database instance: 'instance name'.

Explanation: The program failed to successfullyremove the TCP/IP services from database instance.

User response: Verify that the database instance stillexists on the system. This can be achieved with thedb2ilist command. If the database instance has beenremoved, no further action is necessary. In addition,look in the directory server's DB2 Command Log Fileand the directory server instance's DB2 logs foradditional errors or warnings that might have beengenerated. If the configuration tools continue to showthis warning message, restart the computer and try toproduce the warning again before contacting IBMSoftware Support.

GLPCTL055E Failed to load shared library 'libraryname'.

Explanation: The program failed to load thelibidsdbutils shared library.

User response: Verify that the shared library exists onthe system. The library might not have yet beeninstalled. Also, verify that the path and library pathhave been set correctly to find the IBM SecurityDirectory Server installed libraries.

GLPCTL056E Failed to load symbol from sharedlibrary 'library name'.

Explanation: The program failed to load a symbolfrom the libidsdbutils shared library.

User response: Contact IBM Software Support.

GLPCTL058E The file specified to redirect theoutput to, 'filename', is a directory insteadof a file.

Explanation: An attempt was made to redirect theoutput to a directory. The output of the program canonly be redirected to a file.

User response: Specify a file name that exists or canbe created and is writable.

GLPCTL045E • GLPCTL058E


GLPCTL059E The file specified to redirect outputto, 'filename', is not writable.

Explanation: An attempt was made to redirect theoutput to a file that the user does not have permissionto write to.


GLPCTL060E The file specified to redirect outputto, 'filename', could not be created.

Explanation: An attempt was made to redirect theoutput to a file that the user could not create.


GLPCTL061E The file specified to redirect outputto, 'filename', could not be opened.

Explanation: An attempt was made to redirect theoutput to a file that the user does not have permissionto open.


GLPCTL062E The specified IP address 'IP address' isnot a valid IP address for this computer.

Explanation: You specified an IP address not availablefor use by the computer.

User response: Specify an IP address on which thecomputer can bind to ports.

GLPCTL064E Internal error setting terminalattribute.

Explanation: The program encountered an internalerror while trying to set the terminal display.

User response: Open a new command line windowand attempt to run the command again.

GLPCTL065E Unable to reset the display.

Explanation: The program encountered an internalerror while trying to reset the terminal display.

User response: Open a new command line if theproblem persists.

GLPCTL066E The file 'filename' cannot be created.The location is not valid, is not writable,or is not accessible.

Explanation: The file to create is not valid, is notwritable, or is not accessible.

User response: Verify that the location specified forthe file is a valid location on the system and that you

have access to write to that location. If the locationdoes not seem to be valid and the problem persists,contact IBM Software Support.

GLPCTL067E The file 'filename' cannot be copied to'filename'.

Explanation: The file could not be copied to thespecified location.

User response: Verify that the location specified forthe file is a valid location on the system and that youhave access to write to that location. Verify that the fileto be copied exists, is a valid location on the computer,can be accessed, and has sufficient space. If the locationseems to be valid and the problem persists, contact IBMSoftware Support.

GLPCTL068W Failed to delete the file: 'filename'.

Explanation: The program failed to delete thespecified file.

User response: Verify that the file has the correctpermissions so that it can be deleted. Delete the filemanually if necessary and if the file still exists.

GLPCTL070W Failed to delete the directory:'directory'.

Explanation: The program failed to delete thespecified directory.

User response: Verify that the directory has the correctpermissions so that it can be deleted. Delete thedirectory manually if necessary and if the directoryexists.

GLPCTL071E The directory server instancerepository, 'filename', cannot be read. Youdo not have authority to read therepository and run this command.

Explanation: The directory server instance repositorycould not be read. The directory server instancerepository must be readable to run the command.

User response: Verify that the directory serverinstance repository location exists and that you havepermission to read the file. The file is most likely notreadable because you do not have permission to readthe file or the location where the directory serverinstance repository is located. This command can onlybe run by members of the Administrators group onWindows systems and by members of the idsldapgroup on AIX, Linux, Solaris, and HP-UX systems. OnAIX, Linux, Solaris, and HP-UX systems, verify that theidsldap user and idsldap group exist on the computer.



GLPCTL072E The directory server instancerepository, 'filename', cannot be writtento. You do not have authority to write tothe repository and run this command.

Explanation: The directory server instance repositorycould not be written to. The directory server instancerepository must be writable to run the command.

User response: Verify that the directory serverinstance repository location exists and that you havepermission to write to the file. The file is most likelynot writable because you do not have permission toaccess the file or the location where the directory serverinstance repository is located. This command can onlybe run by members of the Administrators group onWindows systems and by the root user on AIX, Linux,Solaris, and HP-UX systems.

GLPCTL073E The log file, 'filename', cannot bewritten to. You do not have authority towrite to the log and run this command.

Explanation: The log file could not be written to. Thelog file must be writable to run the command.

User response: Verify that the log file location existsand that you have permission to write to the file. Thefile is most likely not writable because you do not havepermission to access the file or the location where thelog file is located. This command can only be used byusers with sufficient authority.

GLPCTL076W Failed to start admin server fordirectory server instance: 'instance name'.

Explanation: The program failed to start the adminserver. The error might have occurred because the portthe admin server was going to use was already in use.

User response: Verify that admin server exists on thecomputer and is not started. If necessary, change theport if it is being used by another program, directoryserver instance, or admin server.

GLPCTL079W Failed to stop admin server forinstance: 'instance name'.

Explanation: The program failed to stop the adminserver. The error might have occurred because theadmin server was already stopped.

User response: Verify that admin server exists on thecomputer and is running. If necessary, stop the adminserver manually.

GLPCTL082W Failed to start directory server fordirectory server instance: 'instance name'.

Explanation: The program failed to start the directoryserver for the directory server instance. The error mighthave occurred because the port the directory server wasgoing to use was already in use.

User response: Verify that directory server instanceexists on the computer and is not started. If necessary,change the port if it is being used by another program,directory server instance, or admin server. The use theidsilist command with the -a option to see what portsare currently configured for each directory serverinstance.

GLPCTL085W Failed to stop directory server fordirectory server instance: 'instance name'.

Explanation: The program failed to stop the directoryserver for the instance. The error might have occurredbecause the directory server instance was alreadystopped.

User response: Verify that the directory serverinstance exists on the computer and is running. Ifnecessary, stop the directory server manually.

GLPCTL086E The directory 'location' cannot becreated. The location is not valid, is notwritable, or is not accessible.

Explanation: The directory to create is not valid, is notwritable, or is not accessible.

User response: Verify that the location specified forthe directory is a valid location on the system and thatyou have access to write to that location. If the locationdoes not seem to be valid and the problem persists,contact IBM Software Support.

GLPCTL087E The directory server instance 'instancename' does not exist.

Explanation: Specified a directory server instance thatdoes not exist.

User response: Specify a valid existing directoryserver instance name. Specify a directory serverinstance with the -I option or set the directory serverinstance using the environment variableIDS_LDAP_INSTANCE.

GLPCTL088E Unable to run the command ondirectory server instance 'instance name',while the directory server is running.

Explanation: An attempt was made to run thecommand on the directory server instance while thedirectory server is running.

User response: Stop the directory server for theinstance before attempting to run the command. Verifythe directory server is running by trying to connect tothe directory server for the instance.



GLPCTL089E Unable to run the command ondirectory server instance 'instance name',because the state of the directory servercannot be determined.

Explanation: An attempt was made to run thecommand on the directory server instance and the stateof the directory server for the instance could not bedetermined.

User response: This error most likely occurredbecause you do not have sufficient access to check thestatus of the server. Verify that you have read access forthe server's process ID file (slapd.pid).

GLPCTL090E Unable to run the command ondirectory server instance 'instance name'because the server configuration file(ibmslapd.conf) for the directory serverinstance could not be found.

Explanation: An attempt was made to run thecommand on the directory server instance but theserver configuration file (ibmslapd.conf) for thedirectory server instance could not be found.


GLPCTL091E Unable to run the command ondirectory server instance 'instance name'because the configuration file, 'file name',does not exist, was not accessible, orcould not be written to.

Explanation: An attempt was made to run thecommand on the directory server instance but theinstance's the server configuration file (ibmslapd.conf)does not exist, was not accessible, or could not bewritten to.

User response: Verify that the directory serverinstance server configuration file exists and that youhave access to it. If the configuration file does not exist,you will most likely have to recreate the directoryserver instance.

GLPCTL092E Unable to run the command ondirectory server instance 'instance name'.The command can only be run ondirectory server instances at version'version number'.

Explanation: An attempt was made to run thecommand on a directory server instance that is not atthe same version as this tool.

User response: Specify a directory server instance thatis at the same version as the tool.

GLPCTL093E The directory server instanceconfiguration key stash file, 'filename',cannot be read. You do not haveauthority to read the repository and runthis command.

Explanation: The directory server instanceconfiguration key stash file could not be read. Youmust have read access to the directory server instanceconfiguration key stash file to run the command.

User response: Verify that the directory serverinstance configuration key stash file exists and that youhave permission to read the file. The file is most likelynot readable because you do not have permission toread the file or the location where the directory serverinstance configuration key stash file is located. If thefile does not exist, contact IBM Software Support tohave the configuration key stash file regenerated.

GLPCTL094E The directory server instance directorykey stash file, 'filename', cannot be read.You do not have authority to read therepository and run this command.

Explanation: The directory server instance directorykey stash file could not be read. You must have readaccess to the directory server instance configuration keystash file to run the command.

User response: Verify that the directory serverinstance directory key stash file exists and that youhave permission to read the file. The file is most likelynot readable because you do not have permission toread the file or the location where the directory serverinstance directory key stash file is located. If the filedoes not exist, contact IBM Software Support to havethe configuration key stash file regenerated.

GLPCTL095E Failure to load key data fromdirectory server instance configurationkey stash file 'filename'.

Explanation: The program encountered an internalerror while loading the key data from the directoryserver instance configuration key stash file.

User response: Your directory server instanceconfiguration key stash file might be corrupted. ContactIBM Software Support.

GLPCTL096E Failure to load key data fromdirectory server instance configurationdirectory stash file 'filename'.

Explanation: The program encountered an internalerror while loading the key data from the directoryserver instance directory key stash file.

User response: Your directory server instancedirectory key stash file might be corrupted. ContactIBM Software Support.



GLPCTL097E The directory server instance ,'instancename', is a proxy server. The commandcannot be run on a proxy server.

Explanation: The command was run against adirectory server instance that is a proxy server; thecommand is not supported on a proxy server.

User response: Run the command only againstdirectory server instances that are not proxy servers.

GLPCTL100E Failed to back up database databasename.

Explanation: The program was unable to back up thedatabase.

User response: Check the directory server instance'sDB2 log for DB2 error messages. The DB2 errormessages might indicate why the program could notback up the database. Also, check the previous errormessages for reasons why the backup failed. Verify thatthe database exists on the system.

GLPCTL103E Failed to restore backup databasedatabase name to configured databasedatabase name.

Explanation: The program was unable to restore thebackup database to the configured database.

User response: Check the directory server instance'sDB2 log for DB2 error messages. The DB2 errormessages might indicate why the program could notrestore the database. Also, check the previous errormessages for reasons why the restore failed. Verify thatthe database exists on the system.

GLPCTL104E The configuration key stash file datais inconsistent with the associatedencrypted data in the configuration file'filename'.

Explanation: The configuration key stash file datadoes not match the associated encrypted data that isstored in the directory server instance's configurationfile. The command cannot run correctly if aninconsistency is encountered.


GLPCTL105E The encryption synchronizationattribute, ibm-slapdCryptoSync, couldnot be retrieved from directory serverinstance's configuration file. Theattribute is required to validateencrypted data integrity.

Explanation: The program failed to retrieve theibm-slapdCryptoSync attribute from the configuration

file of the directory server instance. The attribute isrequired to perform encrypted data integrity checking.


GLPCTL106E Failure to load key data fromdirectory server instance configurationkey stash file into memory.

Explanation: The program encountered an internalerror while loading the key data from the directoryserver instance configuration key stash file intomemory.

User response: Your directory server instanceconfiguration key stash file might be corrupted. Verifythat the configuration key stash file for the directoryserver instance exists and is accessible. If remotemigration is being performed, then verify that theendianness of source system and the target system aresame. If system on which the backup was taken was alittle endian system, and the system on which themigration is being performed is a big endian system, orvice-versa, then key stash file is not usable. Ensure thatboth the systems have same endianness. If the problempersists, contact IBM Software Support.

GLPCTL107E Failed to bind to the configuration file'filename' of directory server instance'instance name'. Bind failed with a returncode of 'return code'.

Explanation: The program encountered an errorbinding to the configuration file of the directory serverinstance. This error can occur if an LDIF syntax error ispresent in the file. This error can also occur if aconfiguration file that is not valid is specified. Theexact error can be determined by running the programwith tracing turned on.

User response: Look in the IBM Security DirectoryServer Troubleshooting Guide for information aboutenabling tracing for IBM Security Directory Serverprograms using the ldtrc command. Then run theprogram again with the same options but include the-d 65535 option (or -h 65535 depending on the programyou are running). Look at the trace output generated todetermine why the bind to the configuration file hasfailed, and respond accordingly. If the problem persists,contact IBM Software Support.

GLPCTL108E Unable to run the command on thedirectory server instance 'instance name'while the admin server is running.

Explanation: An attempt was made to run thecommand on the directory server instance while theadmin server is running.

User response: Stop the admin server for the directory



server instance before attempting to run the command.To test if the admin server is running, try to connect tothe admin server for the directory server instance.

GLPCTL109E Unable to run the command ondirectory server instance 'instance name'because the state of the admin servercannot be determined.

Explanation: An attempt was made to run thecommand on the directory server instance and the stateof the admin server could not be determined.

User response: This error most likely occurredbecause you do not have sufficient access to check thestatus of the admin server. Verify that you have readaccess to the admin server process ID file(ibmdiradm.pid).

GLPCTL110E DB2 did not have sufficient access toback up the database to 'location'. Thedatabase instance owner 'user ID' andthe owner's primary group must be ableto access and write to the backuplocation.

Explanation: The program failed to back up thedatabase because DB2 did not have access to write tothe specified location. The database instance owner andthe primary group of the database instance owner mustbe able to read and write to the backup location.

User response: Verify that the database instanceowner and the primary group of the database instanceowner have access to read and write to the specifiedbackup location. This includes any parent directorieswhere the backup location resides. In addition, on AIX,Linux, Solaris, and HP-UX platforms the permissionsmust be set properly, even if you are running as theroot user.

GLPCTL111E No directory server instance exists onthe computer.

Explanation: No directory server instance exists on thecomputer. The command requires that an existingdirectory server instance be specified.

User response: Use the idsicrt command to create adirectory server instance. If you do not have permissionto run the command, contact your systemadministrator.

GLPCTL112E Only the root user is authorized torun the command.

Explanation: You tried to run a command that onlythe root user on the operating system is authorized torun.

User response: Run the command as the root user onthe operating system. Contact your systemadministrator if you have further questions.

GLPCTL117E The value specified for the 'option'option is blank.

Explanation: The value specified for the option cannotbe blank.

User response: Specify a valid value and retry thecommand.

GLPCTL125E Failed to remove the online backupconfiguration for the database: 'databasename'.

Explanation: An internal error occurred while tryingto remove the online backup configuration of thedatabase.

User response: Review earlier error messagesgenerated by the program to determine how to respondto this error. If no error messages were displayed, seethe IBM Security Directory Server TroubleshootingGuide for information about debugging the programand contacting IBM Software Support.

GLPCTL129E Failed to remove the online backupconfiguration for the instance: 'instancename'.

Explanation: An internal error occurred while tryingto remove the online backup configuration of thedatabase.

User response: Review earlier error messagesgenerated by the program to determine how to respondto this error. If no error messages were displayed, seethe IBM Security Directory Server TroubleshootingGuide for information about debugging the programand contacting IBM Software Support.

GLPCTL130E Error while allocating memory.

Explanation: The command is unable to allocate thenecessary storage to continue processing.


GLPD2L003E Option -x is not allowed for a subtreethat is not a replication context.

Explanation: The db2ldif utility provides a -s <subtreeDN> option to export a specific subtree. If the subtreeis a replication context, this option can be combinedwith the -x option to exclude the nested subtree frombeing exported.

User response: Ensure that the subtree DN in the -soption is a replication context, or remove the -x wheninvoking the db2ldif utility.

GLPCTL109E • GLPD2L003E


GLPD2L004E db2ldif cannot authenticate DN andpassword.

Explanation: The credentials entered were not valid.There was an error verifying the DN and password.


GLPD2L005E db2ldif failed on file_operation to file:file.

Explanation: The db2ldif utility failed to reopen thefile indicated for writing.



Explanation: The db2ldif utility failed to open the fileindicated for writing.



Explanation: The db2ldif utility failed to write to thefile indicated.



Explanation: The db2ldif utility failed to write to thefile indicated.


GLPD2L009E Entry DN of entry specified on db2ldifdoes not exist.

Explanation: The db2ldif utility failed because thesubtree DN specified as the root of the subtree to beexported was not found.

User response: Correct the DN in the db2ldif requestand try again.

GLPD2L010E db2ldif unable to run because ofinitialization error.

Explanation: db2ldif is unable to start because of aninitialization error.

User response: View the earlier error message to seewhy db2ldif did not run. If no previous error messagewas shown, contact IBM Software Support.

GLPD2L012E Starting with the IBM Tivoli DirectoryServer 6.1 release this message isdeprecated.

Explanation: db2ldif is unable to start because of aninitialization error.

User response: View the earlier error message to seewhy db2ldif did not run. If no previous error messagewas shown, contact IBM Software Support.

GLPD2L013E The filter DN DN of filter specified isnot valid.

GLPD2L014E The filter entry DN of entry not found.

GLPDBA002E idsdbmaint is unable to run becauseof initialization error.

Explanation: idsdbmaint is unable to start because ofinitialization error.

User response: View earlier error message to see whyidsdbmaint did not run. If no previous error messagewas printed, contact IBM Software Support.

GLPDBA007E The tablespace LDAPSPACE creationfailed.

Explanation: idsdbmaint is unable to create ldapspacetablespace.


GLPDBA008E The tablespace USERSPACE1 creationfailed.

Explanation: idsdbmaint is unable to createuserspace1 tablespace.


GLPDBA009E The tablespace LDAPSPACE deletionfailed.

Explanation: idsdbmaint is unable to delete ldapspacetablespace.


GLPDBA010E The tablespace USERSPACE1deletion failed.

Explanation: idsdbmaint is unable to deleteuserspace1 tablespace.

GLPD2L004E • GLPDBA010E



GLPDBA015E The tablespace LDAPSPACE importfailed.

Explanation: idsdbmaint is unable to import tables tothe ldapspace tablespace.


GLPDBA016E The tablespace USERSPACE1 importfailed.

Explanation: idsdbmaint is unable to import tables tothe userspace1 tablespace.


GLPDBA017E The tablespace LDAPSPACE exportfailed.

Explanation: idsdbmaint is unable to export tablesfrom the ldapspace tablespace.


GLPDBA018E The tablespace USERSPACE1 exportfailed.

Explanation: idsdbmaint is unable to export tablesfrom the userspace1 tablespace.


GLPDBA026W The db2inspect command failed forthe table 'tabname'.

Explanation: idsdbmaint is unable to perform DB2inspect on the table.


GLPDBA035W Row compression could not beenabled for the table 'tabname'.

GLPDBA045W The table 'tabname' has not beenreorganized.

GLPDBA047W Statistics on table 'tabname' have notbeen updated.

GLPDBA048E The diagpath for database instance'dbinstance' could not be determined.

Explanation: idsdbmaint is unable to find DB2diagnostic data directory path. DB2 database parameterDIAGPATH is not set.


GLPDBA049E An incorrect value for the argument'argname' is passed. The valid value forthis argument is SMS or DMS.

Explanation: The value passed for this argument isnot a valid value.

User response: Pass a valid value to the argument.

GLPDBA050E The 'work_dir' option is required withthe 'ts_convertion' option.

Explanation: A required parameter was not passedduring execution of this command.

User response: Specify the required options forexecution of the command.

GLPDBA051E The specified directory, 'filename', isnot a valid directory, does not exist, or isnot writable.

Explanation: The directory specified to create thedatabase is a location that is not valid, is not writable,or is not accessible.

User response: Verify that the location where thedatabase is going to be created is a valid location onthe system and that you have access to write to thatlocation. The directory must exist.

GLPDBA052E The specified directory, 'work_dir',does not have enough free spacerequired for table space conversion.

Explanation: The directory specified to be used astemporary work directory does not have enough freespace.

User response: Specify a location that has enough freespace to carry out the operation.

GLPDBA015E • GLPDBA052E


GLPDBA054E Unable to estimate the database size.

Explanation: Unable to estimate the database size.

User response: Run the tool in debug mode to seewhy idsdbmaint did not run. If no error message wasprinted, contact IBM Software Support.

GLPDBB002E Specified a backup directory,'filename', that does not exist or is notaccessible.

Explanation: An incorrect backup directory wasspecified for backing up the database for the directoryserver instance.


GLPDBB003E An internal error occurred whilerunning the idsdbback command.

Explanation: An internal error occurred while runningthe idsdbback command. This might have occurredbecause the program ran out of memory.


GLPDBB004W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPDBB005E The -k <backup dir> option isrequired. Use the -? option to see thesyntax for the idsdbback command.

Explanation: The other options were specified and the-k <backup dir> option was not.

User response: Try specifying the -k <backup dir>option with a valid directory to which you can back upthe database.

GLPDBB006E Unable to back up database. Nodatabase instance is configured fordirectory server instance 'instance name'.

Explanation: A database can be backed up only if adatabase instance and database are already configured.

User response: A database instance is configuredwhen a directory server instance is created. If you haveremoved the database instance or deleted the database

instance from the configuration file, reconfiguremanually or recreate the directory server instance.

GLPDBB007E Unable to back up database. Nodatabase is configured for directoryserver instance 'instance name'.

Explanation: A database can be backed up only if adatabase is already configured.

User response: A database is configured using theidscfgdb command. Configure a database with thiscommand before attempting to back up a database.

GLPDBB010E Failed to back up directory serverinstance 'instance name'.

Explanation: The program was unable to back up thedirectory server instance.

User response: Verify that the directory instance has aconfiguration file, schema files, key stash files, and adatabase configured. Verify that you have access toread all of these files. In addition, view earlier errormessages to see why the program failed to back up thefiles. If there are no earlier error messages, contact IBMSoftware Support.

GLPDBB011E Unable to retrieve the database namefrom the directory server instance'sconfiguration file.

Explanation: The program tried to retrieve thedatabase name from the directory server instanceconfiguration file and a failure occurred.

User response: Verify that the directory serverinstance has a database configured and that thedatabase name exists in the configuration file. If theseare set correctly and the error continues to occur,contact IBM Software Support.

GLPDBB012E Unable to retrieve the databaseinstance name from the directory serverinstance's configuration file.

Explanation: The program tried to retrieve thedatabase instance name from the directory serverinstance configuration file and a failure occurred.

User response: Verify that the directory serverinstance has a database instance configured and thatthe database instance name exists in the configurationfile. If the configuration seems to be correct and theerror continues to occur, contact IBM Software Support.

GLPDBB013E Unable to retrieve the databaseadministrator ID from the directoryserver instance's configuration file.

Explanation: The program tried to retrieve thedatabase administrator ID from the directory server

GLPDBA054E • GLPDBB013E


instance configuration file and a failure occurred.

User response: Verify that the directory serverinstance has a database configured and that thedatabase administrator ID exists in the configurationfile. If the configuration seems to be correct and theerror continues to occur, contact IBM Software Support.

GLPDBB014E Unable to retrieve the databaseadministrator password from thedirectory server instance's configurationfile.

Explanation: The program tried to retrieve thedatabase administrator password from the directoryserver instance configuration file and a failure occurred.

User response: Verify that the directory serverinstance has a database configured and that thedatabase administrator password exists in theconfiguration file. If the configuration seems to becorrect and the error continues to occur, contact IBMSoftware Support.

GLPDBB017E Failed to back up the configurationfile for directory server instance 'instancename'.

Explanation: The program was unable to back up theconfiguration file for the directory server instance.

User response: Verify that the directory serverinstance has a configuration file. Verify that you haveaccess to read the configuration file. In addition, viewearlier error messages to see why the program failed toback up the files. If there are no earlier error messages,contact IBM Software Support.

GLPDBB020E Failed to back up the key stash filesfor the directory server instance 'instancename'.

Explanation: The program was unable to back up thekey stash files for the directory server instance.

User response: Verify that the directory serverinstance has key stash files. Verify that you have accessto read the key stash files. In addition, view earliererror messages to see why the program failed to backup the files. If there are no earlier error messages,contact IBM Software Support.

GLPDBB023E Failed to back up the schema files forthe directory server instance 'instancename'.

Explanation: The program was unable to back up theschema files for directory server instance.

User response: Verify that the directory instance hasschema files. Verify that you have access to read theschema files. In addition, view earlier error messages tosee why the program failed to back up the files. If there

are no earlier error messages, contact IBM SoftwareSupport.

GLPDBB024E The backup file file name cannot becreated or is not writable.

Explanation: The program was unable to open orwrite to the file that will contain the backupinformation.

User response: Verify that the directory where the fileis being written has the appropriate write permissions.

GLPDBB025E The backup file file name could not becreated or was not writable.

Explanation: The program was unable to open orwrite to the file that will contain the backupinformation.


GLPDBB028E Failed to save backup information toa file.

Explanation: The program was unable to save thebackup information to a file.

User response: View earlier error messages to see whyprogram failed to back up the files. If there are noearlier error messages, contact IBM Software Support.

GLPDBB030E Starting with the IBM TivoliDirectory Server 6.2 release this messageis deprecated. A dbback.dat file alreadyexists in the specified location to backup the directory server instance. Specifya directory that does not already containbackup information or delete thebackup information.

Explanation: The program found existing backupinformation in the specified location. The program willnot back up the information to a location that alreadycontains backup information.

User response: Specify a directory that does notalready contain backup information or delete thebackup information.

GLPDBB031E The request to configure the databasefor online backups cannot be completedwhile the directory server is running.

Explanation: The command has detected that thedirectory server is running or some application isconnected to the databases that are to be configured foronline backups. It is necessary to stop the server orapplication for this initial configuration and backup.

User response: Stop the directory server andterminate any applications connected to the databases

GLPDBB014E • GLPDBB031E


before reissuing the command.

GLPDBB032W The space available for a futurebackup is too low. The current backuplocation: backup path has only free space inMB MB available and the backup justcompleted required used space in MB MB.

Explanation: The available space must be sufficient forthe current and next backup. For online backups, thefree space must also include space for the inactive logfiles.

User response: Increase the amount of available spaceon the file system used for backup or switch to adifferent location.

GLPDBB035E Failed to back up the databaseproperties file for the directory serverinstance 'instance name'.

Explanation: The program was unable to back up thedatabase properties file for the directory serverinstance.

User response: Verify that the directory serverinstance has a database properties file. Verify that youhave access to read the database properties file. Inaddition, view earlier error messages to see why theprogram failed to back up the files. If there are noearlier error messages, contact IBM Software Support.

GLPDBB038E Failed to back up the command filefor the directory server instance 'instancename'.

Explanation: The program was unable to back up thecommand files for the directory server instance.

User response: Verify that the directory serverinstance has command files. Verify that you have accessto read the command files. In addition, view earliererror messages to see why the program failed to backup the files. If there are no earlier error messages,contact IBM Software Support.

GLPDBB041E Changelog not configured.

Explanation: The request to backup changelog datacannot be done since the directory server instance isnot configured for changelog.

User response: Do not include the option to includebacking up changelog data for this server instance.

GLPDBB044E Conflicting options in the commandline.

Explanation: The option to backup the changelogdatabase conflicts with the option to skip backing upthe database.

User response: Do not include both the option to skip

backing up the database and the option to includebacking up changelog data for this server instance.

GLPDBB047E The specified path backup path cannotbe used for a backup.

Explanation: There was a problem creating a file ordirectory in the specified path.

User response: Check the ownership and permissionsfor the path to be used for the backup. The directoryserver instance owner should have permission to readand write files in that directory.

GLPDBB050E The -u switch for online backups is arequired command line agument whenspecifing the -a parameter to set thearchive directory. Use the -? option tosee the syntax for the idsdbbackcommand.

Explanation: The -a <archive dir> parameter wasspecified and the -u option was not. This parameter isonly valid for online backups.

User response: Try again specifying the -u optionalong with -a.

GLPDBB051E Failed to create path 'archive path ' forlogging inactive log files.

Explanation: The -a <archive dir> parameter wasspecified and the directory does not exist and cannot becreated.

User response: Check the file permissions for the pathspecified for archiving inactive log files.

GLPDBM002E The -I option is required and is usedto specify the directory server instance.

Explanation: The -I option to specify the instancename was not specified and it is required.

User response: Specify the -I option. Use the -? optionto see the syntax for the command.

GLPDBM003E The -N option is required and isused to specify the new DB2 installlocation.

Explanation: The -N option to specify the DB2 9.1location was not specified and it is required.

User response: Specify the -N option. Use the -?option to see the syntax for the command.

GLPDBM011E The DB2 start database managercommand failed.

Explanation: The DB2 start database managercommand failed.

GLPDBB032W • GLPDBM011E


User response: Detailed information about the errorcan be found in the idsdbmigr.log file. Correct the errorand run the command again. If the problem persists,contact IBM Software Support.

GLPDBM012W The DB2 database manager isalready active.

GLPDBM014E The DB2 list database directorycommand failed.

Explanation: The DB2 list database directorycommand failed


GLPDBM016E The DB2 connect to databasecommand failed.

Explanation: The DB2 connect to database commandfailed


GLPDBM018E The DB2 stop database managercommand failed.

Explanation: The DB2 stop database managercommand failed.


GLPDBM023E Failed to updated the DB2 instancewidth space to 64 bits.

Explanation: The DB2 command db2iupdt failed.


GLPDBM025E The DB2 force application all failed.

Explanation: The DB2 force application all commandfailed.


GLPDBM027E The DB2 terminate failed.

Explanation: The DB2 terminate command failed.


GLPDBM029E The DB2 update DBM CFG failed.

Explanation: The DB2 update DBM CFG commandfailed.


GLPDBM033E DB2 instance migration failed.

Explanation: The DB2 command db2imigr failed.


GLPDBM035E DB2 database migration failed fordatabase 'dbname'.

Explanation: The DB2 migrate database commandfailed.


GLPDBM043E DB2 rebind packages failed.

Explanation: The DB2 command db2rbind failed.


GLPDBM045E DB2 activate database command fordatabase 'dbname' failed.

Explanation: The DB2 activate database commandfailed.


GLPDBM012W • GLPDBM045E


GLPDBM046W DB2 database is already active.

GLPDBM051E The new DB2 location specified bythe -N option is not a valid path.

Explanation: The location specified by the -N optiondoes not exist or is not a directory.

User response: Correct the error and run thecommand again. If the problem persists, contact IBMSoftware Support.

GLPDBM053E The new DB2 location does notsupport database migration.

Explanation: The new DB2 location should containdb2 version 9 and above.


GLPDBM056E Directory instance specified by the -Ioption is not a valid instance.

Explanation: The idsdbmigr tool will work only forTDS version 6.1 or later instances.

User response: Use the idsimigr command to migratesupported versions of directory server instances. If theproblem persists, contact IBM Software Support.

GLPDBM058E Could not find the DB2 instancename from the directory server instanceserver configuration file.

Explanation: The directory server instanceconfiguration file does not contain the DB2 instancename, specified by the ibm-slapdDbInstance attribute.


GLPDBM060E Could not find the DB2 databasename from the directory server instanceserver configuration file.

Explanation: The directory server instance serverconfiguration file does not contain the DB2 instancename, specified by the ibm-slapdDbName attribute.


GLPDBM062E The directory server instance versioncheck failed.

Explanation: This version of idsdbmigr tool will workonly with IBM Tivoli Directory Server version 6.2instances.

User response: Use the idsdbmigr command onlywith supported versions of the directory serverinstance. If the problem persists, contact IBM SoftwareSupport.

GLPDBM064E DB2 initial version check failed.

Explanation: The DB2 version specified in theldapdb.properties file is lower than the supported DB2version for migration. DB2 migration is supported fromversion 8 and 9.1 to higer versions.


GLPDBM066E Could not find the directory serverinstance repository file 'instinfo'.

Explanation: The file idsinstances.ldif in theidsinstinfo directory could not be found.


GLPDBM068E Could not find the directory serverinstance location 'instloc'.

Explanation: The file idsinstances.ldif in theidsinstinfo directory does not contain the instancelocation.


GLPDBM070E Could not find the directory serverinstance configuration file.

Explanation: The directory server instance serverconfiguration file ibmslapd.conf in the instance homedirectory could not be found.


GLPDBM072E Could not determine whetherdirectory server instance 'instance name'is running as 32-bit or a 64-bitapplication.

Explanation: A 32 or 64-bit directory could not befound in the install location/sbin directory.


GLPDBM046W • GLPDBM072E


GLPDBM074E Could not find the DB2 installlocation from the ldapdb.properties file'db2loc'.

Explanation: The directory server instanceldapdb.properties file does not contain the DB2 installlocation or version, specified by thecurrentDB2InstallPath and currentDB2Version attribute.


GLPDBM076E Could not find DB2 information fordirectory 'db2prop'.

Explanation: The directory server instanceldapdb.properties file does not contain the DB2 installlocation or version, specified by thecurrentDB2InstallPath and currentDB2Version attribute.


GLPDBM078E Update operation for 'db2prop' file inthe install location failed.

Explanation: The Security Directory Server installldapdb.properties file was not updated.

User response: Manually create or update the file withthe currentDB2InstallPath and currentDB2Versionattributes.

GLPDBM080E Update operation for 'db2prop' file forthe directory server instance failed.

Explanation: The directory server instanceldapdb.properties file was not updated.

User response: To start the directory server instance,manually update or create the file with the attributescurrentDB2InstallPath and currentDB2Version.

GLPDBM083E Could not find the directory serverinstance specific ldapdb.properties file.

Explanation: The directory server instanceldapdb.properties file was not found. This file identifiesthe version of DB2 used by the instance.


GLPDBM089E Unable to run the command ondirectory server instance 'instance name',while the directory server is running.

Explanation: An attempt was made to run thecommand on the directory server instance while thedirectory server is running.

User response: Stop the directory server for theinstance before attempting to run the command.

GLPDBR004E Failed to restore directory serverinstance 'instance name'.

Explanation: The program was unable to restore thegiven directory server instance.

User response: Verify that the directory instance wasbacked up properly and that the backup still exists.

GLPDBR007E Failed to load the backup informationfrom a file.

Explanation: The program was unable to load thebackup information from a file.

User response: View earlier error messages to see whyprogram failed to load the backup information. If anearlier error message was not printed, contact IBMSoftware Support.

GLPDBR008E The backup file file name does notexist or cannot be read.

Explanation: The program was unable to open the filethat will hold all of the backup information.

User response: Verify that the directory where the fileis being read has the appropriate permissions and thatthe file exists on the system.

GLPDBR009E The location of directory serverinstance 'instance name' cannot be found.

Explanation: Tried to delete a directory server andcannot find the location of the directory server instance.

User response: Try to run the command again. If theproblem continues look in the directory server instancerepository to verify that the location is registered. If thelocation is not registered, register the location. If thecommand still fails, contact IBM Software Support.

GLPDBR010E The file 'file name' located in thebackup file 'file name', does not exist,was not accessible, or cannot be writtento.

Explanation: An attempt was made to restore adirectory server instance, but one of the files to restorewas not found. The file was referenced in the backupfile, which holds the name of all files that will berestored.

User response: Verify that the backup information inthe backup file is valid and that all of the filesreferenced in the backup file exist and are valid.

GLPDBM074E • GLPDBR010E


GLPDBR011E The file 'file name' is missing thedatabase backup information.

Explanation: An attempt was made to restore adirectory server instance, but the database backupinformation could not be found. The information wasnot present in the backup file.

User response: Verify that the backup information inthe backup file is valid and that all of the filesreferenced in the backup file exist and are valid. Verifythat the 'database' and 'dbinstance' tags exist in thebackup file.

GLPDBR014E Failed to restore the configuration filefor the directory server instance 'instancename'.

Explanation: The program was unable to restore theconfiguration file for the directory server instance.

User response: Verify that the directory instance has aconfiguration file. Verify that you have access to readand write to the current configuration file. Yourdirectory server instance might now be in aninconsistent state due to not restoring the oldconfiguration file. In addition, view earlier errormessages to see why the program failed to restore thefiles. If an earlier error message was not printed,contact IBM Software Support.

GLPDBR017W Failed to restore the key stash filesfor the directory server instance 'instancename'.

Explanation: The program was unable to restore thekey stash files for the directory server instance.

User response: Verify that the directory instance haskey stash files. Verify that you have access to read andwrite to the current key stash files for the directoryserver instance. Your directory server instance mightnow be in an inconsistent state due to having an out ofsync stash file. In addition, view earlier error messagesto see why the program failed to restore files. If anearlier error message was not printed, contact IBMSoftware Support.

GLPDBR020E Failed to restore one or more of theschema files for the directory serverinstance 'instance name'.

Explanation: The program was unable to restore oneor more of schema files for the directory serverinstance.

User response: Verify that the directory serverinstance has schema files. Verify that you have access toread and write over the current set of schema filesconfigured for the directory server instance. Yourdirectory server instance might now be in aninconsistent state due to missing schema files. Inaddition, view earlier error messages to see why the

program failed to restore the files. If an earlier errormessage was not printed, contact IBM SoftwareSupport.

GLPDBR021E Specified a backup directory,'filename', that does not exist or is notaccessible.

Explanation: An incorrect backup directory wasspecified for restoring the database for the directoryserver instance.


GLPDBR022E The -k <backup dir> option isrequired. Use the -? option to see thesyntax for the idsdbrestore command.

Explanation: The -k <backup dir> option was notgiven.

User response: Specify the -k <backup dir> optionwith a valid directory to obtain the backed upinformation.

GLPDBR023E Unable to restore the database. Nodatabase instance is configured fordirectory server instance 'instance name'.

Explanation: A database can be restored only if adatabase instance and database are already configured.

User response: A database instance is configuredwhen a directory server instance is created. If you haveremoved the database instance or deleted the databaseinstance from the configuration file, reconfiguremanually or recreate the directory server instance.

GLPDBR024E Unable to restore database. Nodatabase is configured for directoryserver instance 'instance name'.

Explanation: A database can be restored only if adatabase is already configured.

User response: A database is configured using theidschgdb command. Configure a database with thiscommand before attempting to back up a database.

GLPDBR025E The backup file file name does notexist or cannot be accessed.

Explanation: The program was unable to open or readthe file that holds all of the backup information.

User response: Verify that the directory where the fileis being written has the appropriate write permissionsand that the directory contains a dbback.dat file.

GLPDBR011E • GLPDBR025E


GLPDBR027E An internal error occurred whilerunning the idsdbrestore command.

Explanation: An internal error occurred while runningthe idsdbrestore command. This might have occurredbecause the program ran out of memory.


GLPDBR028W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPDBR029E The file 'file name' is missing thebackup directory server versioninformation.

Explanation: An attempt was made to restore adirectory server instance, but the directory serverversion information cannot be found. The informationwas not present in the backup file.

User response: Verify that the backup information inthe backup file is valid and that all of the filesreferenced in the backup file exist and are valid. Verifythat the 'instanceVersion' tag exists in the backup file.

GLPDBR030E The file 'file name' is missing thebackup operating system information.

Explanation: An attempt was made to restore adirectory server instance, but the operating systeminformation cannot be found. The information was notpresent in the backup file.

User response: Verify that the backup information inthe backup file is valid and that all of the filesreferenced in the backup file exist and are valid. Verifythat the 'platform' tag exists in the backup file.

GLPDBR031E The file 'file name' containsinformation about a backed up directoryserver instance that does not match theversion of directory server instance'instance name'.

Explanation: An attempt was made to restore adirectory server instance but the information backed upis from a different directory server instance level. Thetool can only restore into a directory server instance atthe same version as the backed up data.

User response: Verify that the 'instanceVersion' tag

exists in the backup file and that it matches the versionof the directory server instance you are trying torestore. If the information does not match, the backedup information cannot be restored into the specifieddirectory server instance.

GLPDBR032E The file 'file name' was backed upfrom a different operating system. Theidsdbrestore command can only restorebackup information that was backed upon the same operating system.

Explanation: An attempt was made to restore adirectory server instance but the information backed upis from a different operating system.

User response: Verify that the 'platform' tag exists inthe backup file and that the value associated with thetag matches the operating system you are currentlyrunning on. If the operating system does not match,then the backed up information was backed up on adifferent operating system. The tool does not supportrestores across operating systems.

GLPDBR033E The idsdbrestore command can onlyrestore a database to the originaldatabase instance with the samedatabase name. The backup up database'database name' resided in databaseinstance 'database instance' and theconfigured database 'database name'resides in database instance 'databaseinstance'

Explanation: An attempt was made to restore adirectory server instance but the backed up databaseand database instance do not match the configureddatabase and database instance.

User response: Use the db2restore utility on adirectory server instance that has a matching databaseand database instance configured. If you must restorethe specified directory server instance, unconfigure thedatabase and database instance for the directory serverinstance and reconfigure it to use the matchingdatabase instance and database.

GLPDBR036E Failed to restore the databaseproperties file for the directory serverinstance 'instance name'.

Explanation: The program was unable to restore thedatabase properties file for the directory serverinstance.

User response: Verify that the directory instance has adatabase properties file. Verify that you have access toread and write to the current database properties filefor the directory server instance. In addition, viewearlier error messages to see why the program failed torestore files. If an earlier error message was not printed,contact IBM Software Support.

GLPDBR027E • GLPDBR036E


GLPDBR039E Failed to restore the command filesfor the directory server instance 'instancename'.

Explanation: The program was unable to restore thecommand files for the directory server instance.

User response: Verify that the directory instance hascommand files. Verify that you have access to read andwrite to the current command files for the directoryserver instance. In addition, view earlier error messagesto see why the program failed to restore files. If anearlier error message was not printed, contact IBMSoftware Support.

GLPDBR041E Unable to restore changelog data;changelog is not configured for thisdirectory server instance.

Explanation: The request to restore changelog datacannot be done since the directory server instance isnot configured for changelog.

User response: Do not include the option to includerestoring changelog data for this directory serverinstance.

GLPDBR043E Conflicting options in the commandline requesting a restore for thedirectory server instance.

Explanation: The option to restore the changelogdatabase conflicts with the option to skip restoring thedatabase.

User response: Do not include both the option to skiprestoring the database and the option to includerestoring changelog data.

GLPDDS002E The -I option is required and is usedto specify the instance name.

Explanation: The -I option was not specified and it isrequired.

User response: Specify the -I option. Use the -? optionto see the usage for the command.

GLPDDS003E The -B option is required and is usedto specify the base DN for splitting.

Explanation: The -B option was not specified and it isrequired.

User response: Specify the -B option. Use the -?option to see the usage for the command.

GLPDDS004E The -i option is required and is usedto specify the input file for splitting.

Explanation: The -i option was not specified and it isrequired.

User response: Specify the -i option. Use the -? optionto see the usage for the command.

GLPDDS005E Specify the proxy serverconfiguration file for splitting.

Explanation: The required proxy server configurationfile could not be located.

User response: Specify the -f option with the name ofthe proxy server configuration file.

GLPDDS006E Error while parsing command linearguments.

Explanation: The command line arguments could notbe parsed.

User response: Use the -? option to see the usage forthe command.

GLPDDS007E Exiting ddsetup due to errorprocessing the command line.

Explanation: A problem was encountered processingthe command line.

User response: Correct any reported errors. Use the -?option to see the usage for the command.

GLPDDS008E Error while validating command linearguments.

Explanation: A problem occurred while validating thecommand line arguments.

User response: Correct the error. Use the -? option tosee the usage for the command.

GLPDDS009E Input LDIF file file name does notexist.

Explanation: The input file specified cannot be found.

User response: Verify that the input file exists and tryagain.

GLPDDS012E Exiting partitioning utility due toerror in configuration.

Explanation: A problem was encountered whileprocessing the proxy server configuration.

User response: Correct any reported errors and tryagain.

GLPDDS013E Input argument provided on thecommand line is missing a value.

Explanation: The input argument provided on thecommand line must have a value.

User response: Provide the correct argument on thecommand line.

GLPDBR039E • GLPDDS013E


GLPDDS014E Input argument provided on thecommand line contains all spaces.

Explanation: Input argument provided on thecommand line contains all spaces.

User response: Provide the correct argument on thecommand line.

GLPDDS025E The directory path provided by the -loption does not exist.

Explanation: The directory path for the output filesmust exist before running this command.

User response: Create the directory and try runningthe command again.

GLPDDS027E Error extracting partitioninginformation from proxy configurationfile.

Explanation: There is a problem with the proxy serverconfiguration.

User response: Correct any reported errors in theserver configuration and try again.

GLPDDS028E The instance proxy instance providedby -I option is not a proxy serverinstance.

GLPDDS029E Number of partitions must be greaterthan zero.

Explanation: The number of partitions must be greaterthan zero.

User response: Specify a number of partitions that isgreater than zero.

GLPDDS030E Number of partitions value exceedsthe allowed limit of 50.

Explanation: The number of partitions value exceedsthe allowed limit of 50.

User response: Specify a valid number of partitionsthat is within the allowed limit.

GLPDDS031E Error opening input LDIF file filename.

Explanation: There was an error opening the inputLDIF file.

User response: Verify the input file exists and tryagain.

GLPDDS032E Exiting partitioning utility due to asetup error.

Explanation: There is a problem in preparation of theinput or output files.

User response: Correct any error reported in earliermessages and try again.

GLPDDS033E The output file out file already exists.Exiting partitioning utility.

Explanation: The output file already exists and willnot be overwritten.

User response: Delete the output file or use a differentname and try again.

GLPDDS034E Error opening output filename file.Exiting partitioning utility.

Explanation: There was an error opening the outputfile.

User response: Ensure that files can be created in thespecified output directory and try again.

GLPDDS035E Exiting partitioning utility due to aninternal error.

Explanation: The utility encountered an unrecoverableerror trying to execute operations in parallel.


GLPDDS036E Error parsing the input LDIF file online number line no.

Explanation: There was an error parsing the inputLDIF file.

User response: Correct the error in the input file,delete any output files produced earlier and try again.

GLPDDS039E Incorrect option specified on thecommand line.

Explanation: An incorrect option was specified on thecommand line.

User response: Use the -? option to see the usage forthe command.

GLPDDS041E The partition base DN base DNprovided by the -B option is not part ofthe proxy server's namespace.

Explanation: The DN specified as the partition base isoutside of the namespaces supported by the proxyserver instance.

User response: Check the values of theibm-slapdSuffix attribute in the proxy server

GLPDDS014E • GLPDDS041E


configuration for the ibm-slapdProxyBackend entry thatdefine the namespaces supported by the proxy serverfor this instance. The partition base DN must beincluded in one of these namespaces. Supply a differentvalue for the base DN on the command line or correctthe proxy server's configuration to include a newnamespace for the base DN.

GLPDDS042E Unable to load the partition pluginlibrary.

Explanation: Failed to load the plugin library that isused to partition the entries in the input file.

User response: If the default partition plugin is notbeing used, check the path for the plugin library in theproxy server's configuration. Otherwise, check to makesure the default plugin library file was installedproperly.

GLPDDS043E The partition base DN base DNprovided by -B option does not exist inproxy server's configuration file.

Explanation: The partition base DN does not exist inthe proxy server's configuration file.

User response: Correct the proxy server'sconfiguration file or specify a different partition baseDN on the command line.

GLPDDS044E A split name does not exist in proxyserver's configuration file.

Explanation: The required attributeibm-slapdProxySplitName does not exist in the proxyserver's configuration file.

User response: Correct the error in the proxy serverconfiguration file and try again.

GLPDDS047E Value for attribute attr is missing.

Explanation: A required value is missing from theproxy server configuration.

User response: Correct the proxy server configurationand try again.

GLPDDS048E Failed to write output file filename.

Explanation: Failed to write the output file.

User response: Correct the error.

GLPDDS049E Unable to continue due to parsingerrors.

Explanation: Terminating due to an error encounteredwhile parsing the entries from the input LDIF file.


GLPDDS050E Unable to continue partitioning theentries.

Explanation: There were unrecoverable errors whilepartitioning the entries.


GLPDPW003E The -p option is required.

Explanation: The -p option is required to specify thepassword of the directory server administrator.

User response: Specify the -p option or do not run thecommand in no-prompt mode to avoid this error. Usethe -? option to see the syntax for the command.

GLPDPW008E Failed to set the directory serveradministrator password.

Explanation: An internal error occurred while tryingto configure the database administrator password.


GLPDPW011E Failed to set the directory serveradministrator DN.

Explanation: An internal error occurred while tryingto configure the database administrator DN.


GLPDPW012E An internal error occurred whilerunning the idsdnpw command.

Explanation: An internal error occurred while runningthe idsdnpw command. This might have occurredbecause the program ran out of memory.


GLPDPW013W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPDDS042E • GLPDPW013W


GLPDPW014E The password specified violatesadministrator password policy. Aminimum of number of characterscharacters is required.

Explanation: You specified a password that violatesthe administrator password policy because the lengthof the password was too short.

User response: Specify a password that is greater thanor equal to the length specified in the error message.

GLPDPW015E The password specified violatesadministrator password policy. Aminimum of number of charactersalphabetic characters is required.

Explanation: You specified a password that violatesthe administrator password policy because thepassword does not contain enough alphabeticcharacters.

User response: Specify a password that has sufficientalphabetic characters to comply with the administratorpassword policy.

GLPDPW016E The password specified violatesadministrator password policy. Aminimum of number of charactersnon-alphabetic characters is required.

Explanation: You specified a password that violatesthe administrator password policy because thepassword does not contain enough non-alphabeticcharacters.

User response: Specify a password that has sufficientnon-alphabetic characters to comply with theadministrator password policy.

GLPDPW017E The password specified violatesadministrator password policy. Amaximum of number of charactersrepeated characters is allowed.

Explanation: You specified a password that violatesthe administrator password policy because thepassword has too many repeated characters.

User response: Specify a password that does not havetoo many repeated characters to comply with theadministrator password policy. The maximum numberof repeated characters was shown in the error message.

GLPDPW018E The password specified violatesadministrator password policy. Aminimum of number of characterscharacters must be different from theprevious password.

Explanation: You specified a password that violatesthe administrator password policy because it does not

have enough characters that differ from the previouspassword.

User response: Specify a password that does not havetoo many matching characters from the previouspassword to comply with the administrator passwordpolicy. The minimum number of characters that mustdiffer was shown in the error message.

GLPDPW020E The password specified violatesadministrator password policy. Amaximum of number of charactersconsecutive repeated characters isallowed.

Explanation: You specified a password that violatesthe administrator password policy because thepassword has too many consecutive repeatedcharacters.

User response: Specify a password that does not havetoo many consecutive repeated characters to complywith the administrator password policy. The maximumnumber of consecutive repeated characters was shownin the error message.

GLPDSM008E Problem configuring the XML parser.

Explanation: An exception occurred: unable to loadand instantiate the XML parser class.

User response: Verify that the configuration settings ofthe XML parser are correct.

GLPDSM010E Problem configuring the XMLtransformer.

Explanation: An exception condition occurred duringthe transformation process.

User response: Verify the configuration settings of theXML transformer tool.

GLPDSM011E Problem reading or writing to file.

Explanation: An error occurred while reading from orwriting to the configuration file. The user might nothave enough permission to access the files at thespecified location, or the file might not exist at therequired location.

User response: Check to see if the file is present andthe user has permissions to read or write to theconfiguration file; otherwise, contact the systemadministrator.

GLPDSM012E Problem writing DOMSource to file:file name

Explanation: An exception condition occurred duringthe transformation process. There is a problem writingthe DOMSource to an output file.

GLPDPW014E • GLPDSM012E


User response: Verify the configuration settings of theXML transformer tool and that the file is accessible tothe logged-in user.

GLPDSM013E Error processing DSMLBatchRequest.

Explanation: The error might have occurred for one ofthe following reasons: An XMLReader might havefound an unrecognized feature or property identifier.An XMLReader cannot perform the requestedoperation. An error occurred while parsing the data.

User response: Check for these error conditions andcorrect any that you find.

GLPDSM015E Element name must be element name .

Explanation: The batch response element name doesnot match the node name.

User response: Specify the same name for both thebatch response element name and the node name.

GLPDSM016E BatchResponse: Required elementsnot set.

Explanation: An error occurred in setting the batchresponse for batch messages having a valid batchsearch response.

User response: Specify all required elements for thebatch response.

GLPDSM017E LdapResult: All required values arenot set.

Explanation: The return code of the LDAP result doesnot fall in the valid range of codes. The result code iseither less than 0 or greater than 81.

User response: Specify a valid result code that isgreater than or equal to 0 and less than or equal to 81.

GLPDSM018E Incorrect input (not all parenthesesare matched): filter

Explanation: The specified filter does not have equalnumber of matching opening and closing parentheses.

User response: Provide valid input, so that theopening and closing parentheses match, while setting afilter.

GLPDSM022E Incorrect input parameters. Alloptions must use -name value syntax.

Explanation: The specified input parameters areincorrect. The options must use the -name value syntax;for example, an input file can be specified as -iinputFile.ext.

User response: Specify valid input parameters withproper syntax.

GLPDSM025E Incorrect element name. Validelement names are: authRequest,searchRequest, modifyRequest,addRequest, delRequest,modDNRequest, compareRequest,abandonRequest, extendedRequest,searchResponse, authResponse,modifyResponse, addResponse,delResponse, modDNResponse,compareResponse, extendedResponse,errorResponse, searchResultEntry,searchResultReference,searchResultDone.

Explanation: The element name specified is not valid.

User response: Specify a valid element name.

GLPDSM026E Input is not of valid Base 64encoding: input value

Explanation: The specified input is not base 64encoded text.

User response: Specify input that is valid base 64encoded text.

GLPDSM027E error details .

Explanation: The error occurred while converting \XXescape sequences to their ASCII equivalents. This erroroccurs when there is a problem parsing the data.Improper escape sequences might have been used.

User response: Use proper escape sequences.

GLPDSM028E No DsmlResponse returned.

Explanation: An error occurred while processing aDSML request. An error might have occurred for one ofthe following reasons: A problem occurred whilecreating the XML Document builder. A problemoccurred while retrieving namespace information. Aproblem occurred while validating the schema. Thespecified credentials might be incorrect or the specifiedaccount might not have permissions to execute theoperation.

User response: Contact the directory administrator.

Administrator response: Contact IBM SoftwareSupport.

GLPDSM029E No security principal or credentialssupplied.

Explanation: The security principal and credentials arerequired parameters for successful authentication byDigest. At least one of the parameters was notsupplied.

GLPDSM013E • GLPDSM029E


User response: Supply valid security principal andcredentials for successful authentication by Digest.

GLPDSM030E AbandonRequest is not supported.

Explanation: The Abandon operation is not supportedby the LDAP server.

User response: Contact IBM Software Support formore information.

GLPDSM031E AbandonRequest: IncorrectabandonID.

Explanation: The ID for the abandon requestoperation is not valid. The ID might be null or empty.

User response: Specify a valid ID for the abandonrequest operation.

GLPDSM032E AbandonRequest: All required valuesare not set.

Explanation: An Abandon ID is needed for theabandon request operation. The required parameter isnot specified.

User response: Provide all required elements andattributes.

GLPDSM033E AddRequest: Unable to addDsmlAttribute.

Explanation: An error occurred while adding a DSMLattribute that is null.


GLPDSM034E AddRequest: Incorrect DN.

Explanation: The specified DN is invalid; it is eithernull or zero length.

User response: Specify a correct DN for theAddRequest operation.

GLPDSM035E AddRequest: All required values arenot set.

Explanation: A DN is needed for the add requestoperation. The DN is null.

User response: Specify a valid DN.

GLPDSM036E AttibuteDescriptions: IncorrectAttributeDescriptionValue.

Explanation: An error occurred while setting thevalue. The specified value of the attribute is either zerolength or null.

User response: Specify a valid attribute descriptionvalue for the attribute.

GLPDSM037E AttributeDescriptions: All requiredvalues are not set.

Explanation: The attribute descriptor must have atleast one valid value for the requested operation. Theattribute does not have a value.


GLPDSM038E AttributeValueAssertion: Incorrectelement value.

Explanation: An error occurred while setting a valuefor the element. The element value is not valid. Thevalue might be null or empty.

User response: Specify a valid element value to be setfor the attribute.

GLPDSM039E AttributeValueAssertion: Illegalattribute name.

Explanation: An error occurred while setting a valuefor the attribute. The attribute name is not valid. Theattribute name might be null or empty.

User response: Specify a valid attribute name for theelement.

GLPDSM040E AttributeValueAssertion: All requiredvalues are not set.

Explanation: Attribute name, value, and base 64encoded value cannot be null for the requestedoperation. At least one of the required parameters isnull.


GLPDSM041E AuthRequest: All required values arenot set.

Explanation: The security principal required for thesuccessful completion of the authorization requestoperation is null.

User response: Specify a valid security principal.

GLPDSM042E BatchMessage: All required valuesare not set.

Explanation: The message type is incorrectly set.

User response: Specify a valid message type.

GLPDSM043E CompareRequest: All required valuesare not set.

Explanation: Attribute value, DN, and assertion valuecannot be null for the compare request operation. Oneof the required parameters is null.




GLPDSM044E ErrorResponse: All required valuesare not set.

Explanation: The required type of the error message isnull.

User response: Specify a valid error message type.

GLPDSM045E DeleteRequest: All required valuesare not set.

Explanation: The DN is null.

User response: Specify a valid DN.

GLPDSM046E DsmlAttr: All required values are notset.

Explanation: The attribute name is null.

User response: Specify a valid attribute name.

GLPDSM047E DsmlValue: All required values arenot set.

Explanation: The attribute value and its base 64encoded value cannot be null for the requestedoperation. At least one of the required parameters isnull.


GLPDSM048E ExtendedRequest: All requiredvalues are not set.

Explanation: The extended operation request name oftype NumericOID cannot be null for the requestedextended operation. The request name is null.

User response: Specify a valid extended operationrequest name of type NumericOID.

GLPDSM049E Presence Filter: All required valuesare not set.

Explanation: The presence filter is null.

User response: Use proper escape sequences.

GLPDSM050E Equality Filter: All required valuesare not set.

Explanation: The name or value of the equality filterobject is null.

User response: Specify a valid name and value for theequality filter object.

GLPDSM051E ApproxMatch Filter: All requiredvalues are not set.

Explanation: The name or value of the approximatematch filter object is null.

User response: Specify a valid name and value for theapproximate match filter object.

GLPDSM052E GreaterOrEqual Filter: All requiredvalues are not set.

Explanation: The name or value of the greater orequal match filter object is null.

User response: Specify a valid name and value for thegreater or equal match filter object.

GLPDSM053E LessOrEqual Filter: All requiredvalues are not set.

Explanation: The name or value of the less or equalmatch filter object is null.

User response: Specify a valid name and value for theless or equal match filter object.

GLPDSM054E Substrings Filter: All required valuesare not set.

Explanation: The name or value of the substring filterobject is null.

User response: Specify a valid name and value for thesubstring filter object.

GLPDSM055E ExtensibleMatch Filter: All requiredvalues are not set.

Explanation: The name or value of the extensible filterobject is null.

User response: Specify a valid name and value for theextensible filter object.

GLPDSM056E Filter does not match any supportedfilter types: filter

Explanation: The given filter name does not matchany of the supported filter types.

User response: Provide a valid supported filter type.

GLPDSM057E Filter: All required values are not set.

Explanation: A filter is required for the successfulcompletion of the requested operation. The filter is notspecified.

User response: Specify a valid filter.



GLPDSM058E Internal Error (related to regularexpressions).

Explanation: An error occurred parsing the filter. Thespecified LDAP filter has incorrect syntax. An exampleof a valid LDAP filter is (&(cn=Bob)(sn=Garcia)).

User response: Provide valid input that can besuccessfully parsed.

GLPDSM059E Filter has unmatched parentheses.The partial filter below includes theunmatched parenthesis: filter

Explanation: The syntax of the specified filter isincorrect. One or more closing parentheses is missing.

User response: Match each opening parenthesis with aclosing parenthesis, such that the filter has equalnumbers of opening and closing parentheses.

GLPDSM060E MatchingRuleAssertion: All requiredvalues are not set.

Explanation: The matching rule value and its base 64encoded value are needed for the matching ruleassertion operation. Not all required parameters areprovided.


GLPDSM061E ModifyDNRequest: All requiredvalues are not set.

Explanation: The old DN and new DN are mandatoryattributes for modifying the DN of an entry. One ormore of these attributes was not provided.

User response: Specify the new DN and the old DNwith the request for modifying the DN.

GLPDSM062E ModifyRequest: All required valuesare not set.

Explanation: The Modify request operation requires aDN on which to operate. This DN was not provided.

User response: Provide the DN that the modifyrequest operation will modify.

GLPDSM063E SearchRequest: All required valuesare not set.

Explanation: Search filter, base DN, and scope levelderefAliases values are required for performing asearch operation. One or more of these requiredparameters were not provided for the search operation.

User response: Provide all required elements.

GLPDSM064E SearchResponse: All required valuesare not set.

Explanation: An error occurred while performing thesearch operation. The search result is null.

User response: Provide valid search operationparameters.

GLPDSM065E SearchResultEntry: All requiredvalues are not set.

Explanation: The search DN is not specified.

User response: Specify a valid search DN.

GLPDSM066E SearchResultReference: IncorrectrefURI.

Explanation: The reference URI is incorrect. An erroroccurred while setting the reference URI for the searchoperation.

User response: Specify a valid response URI.

GLPDSM067E SearchResultReference: All requiredvalues are not set.

Explanation: The search result reference requires atleast one reference URI. No reference URI wasspecified.

User response: Specify at least one reference URI forthe search result reference operation.

GLPDSM068E SubstringFilter: All required valuesare not set.

Explanation: The substring filter requires an attributeof type AttributeDescriptionValue. This requiredattribute is missing.

User response: Specify a valid attribute of typeAttributeDescriptionValue.

GLPDSM069E Problem opening log file: error details

Explanation: An error occurred opening the log file.The user might not have enough permission to accessthe log file at the specified location.

User response: Contact the system administrator.

GLPDSM070E Incorrect escape sequence in inputsegment: input segment

Explanation: An error occurred while parsing theinput segment. The input segment is not parsable.

User response: Specify a valid parsable inputsegment.



GLPDSM071E DsmlControl: All required values arenot set.

Explanation: DSML control type NumericOID is arequired parameter. The control type is null.

User response: Specify a valid control type.

GLPDSM072E DsmlMessage: All required valuesare not set.

Explanation: All required elements and attributesmust be provided for the DSML message. Some of therequired parameters are not provided.


GLPDSM073E DsmlModification: All requiredvalues are not set.

Explanation: The attribute to be modified andoperation to be performed for that attribute arerequired parameters for the requested operation. Atleast one of the required parameters is null.


GLPDSM074E Incorrect parameters in AuthRequest.

Explanation: The parameters passed for theauthorization process are incorrect. Either the DSMLRequest ID is incorrect or another error occurred whileauthorizing.

User response: Provide valid parameters whilerequesting authorization.

GLPDSM075E Incorrect value for attributeRequestID.

Explanation: The DSML Request ID is incorrect.

User response: Pass a valid Request ID.

GLPDSM076E Incorrect value for attributeprocessing.

Explanation: The values provided are incorrect.Processing of attributes cannot resume.

User response: Provide valid values for attributeprocessing.

GLPDSM077E Incorrect value for attributeresponseOrder.

Explanation: The response order value is incorrect.The value must be either sequential or unordered.

User response: Specify a valid value for responseorder.

GLPDSM078E Illegal value for attribute onError.

Explanation: The value of the onError attribute isincorrect; it is either null, blank, or 'exit' or 'resume'.

User response: Specify a valid value for the onErrorattribute.

GLPDSM079E DsmlRequest: Element name shouldbe element name .

Explanation: The batch request element name doesnot match the node name.

User response: Specify the same name for both thebatch request element name and the node name.

GLPDSM080E AuthRequest must be the firstelement in BatchRequest.

Explanation: The authRequest parameter is not thefirst element in the BatchRequest.

User response: Specify the authRequest parameter asthe first element in the BatchRequest.

GLPDSM081E Required RequestID forAuthRequest not set.

Explanation: The RequestID parameter, which isrequired for the AuthRequest operation, is notprovided.

User response: Specify a valid RequestID parameterfor the AuthRequest operation.

GLPDSM082E Required RequestID not set forelement name .

Explanation: The RequestID parameter is a mandatoryparameter. An error occurred because the RequestIDparameter is not provided.

User response: Specify a valid RequestID parameter.

GLPDSM083E BatchRequest: Required elements arenot set.

Explanation: RequestID in a batchRequest is null.

User response: Specify a valid requestID in abatchRequest.

GLPDSM084E Duplicate request ID found: requestID

Explanation: An identical request ID is alreadypresent in the DSMLRequest. A duplicate value is notallowed. This ID is not case sensitive.

User response: Specify a unique request ID in theDSMLRequest.



GLPGRP003E The -w option is required.

Explanation: The -w option is required to specify thepassword of the system user.

User response: Specify the -w option or do not runthe command in no-prompt mode to avoid this error.Use the -? option to see the syntax for the command.

GLPGRP008E Failed to set the user password.

Explanation: An internal error occurred while tryingto set the password.


GLPGRP009E An internal error occurred whilerunning the 'idsadduser' command.

Explanation: An internal error occurred while runningthe idsadduser command. This might have occurredbecause the program ran out of memory.


GLPGRP010W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPGRP011W The user 'user' already exists. Theuser will be recreated with modifiedproperties.

GLPGRP014E Script 'script' failed to create user'user'.



GLPGRP017E The user 'user' could not be added togroup 'group'.

Explanation: Either the member being added isalready part of this group or the member's accounttype is invalid. This error will occur only on Windowsplatform.

User response: Correct the problem and retry theoperation.

GLPGRP018E The required options -u and -g aremissing.

Explanation: The -u and -g options are required tocreate the system user.

User response: Specify the -u and -g option to avoidthis error. Use the -? option to see the syntax for thecommand.

GLPGRP027E Failed to create user 'user'. Error codereturned by 'command' is error code.

Explanation: The system user creation command fails.

User response: Attempt to run the command againafter rectifying the problem specified by the returnerror code. If the problem persists, contact IBMSoftware Support.

GLPGRP033W Cannot create group 'group'. Errorcode returned by 'command' is error code.

Explanation: The system group creation commandfails.

User response: Attempt to run the command againafter rectify the problem specified by the return errorcode. If the problem persists, contact IBM SoftwareSupport.

GLPGRP035E Failed to delete user 'user'. Error codereturned by 'command' is error code.

Explanation: The command fails, it may be user iscurrently logged in.

User response: Attempt to run the command again. Ifthe problem persists, contact IBM Software Support.

GLPGRP036E Pwdadm failed to clear 'user'password.

GLPGRP037E 'OS' is not a supported operatingsystem.

GLPGRP038E Unable to change the access of'directory' directory.

GLPGRP040W 'command' was unable to add user'root' to group 'command'.

Explanation: The system command fails.

User response: Attempt to run the command againafter rectifying the problem specified by the returnerror code. If the problem persists, contact IBMSoftware Support.

GLPGRP003E • GLPGRP040W


GLPGRP043E Failed to create user 'user'. Error codereturned by 'command' is error code.

Explanation: The system command fails.

User response: Attempt to run the command againafter rectify the problem specified by the return errorcode. If the problem persists, contact IBM SoftwareSupport.

GLPGRP045W Failed to modify file '/etc/group'.

GLPGRP046W The group 'group' is not definedlocally in the '/etc/group' file.

GLPGRP050E Required script 'script' not found.

GLPGRP051E The 'User name' user cannot berecreated because an instance alreadyexists for the user.

GLPGRP052W If the Network Information Service(NIS) database is installed on thesystem, user properties modification isnot recommended.

GLPGRP054E The primary group, 'group name', ofthe user , 'user name', is not a valid nameand violates the naming rules.

Explanation: The program failed because the primarygroup of the directory server instance owner that wasto be created is not valid.

User response: Specify a primary group name thatadheres to the following rules: The primary groupname must contain 1 to 8 characters. The name cannotbe 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC', or'LOCAL'. The name cannot begin with 'IBM', 'SQL', or'SYS'. The name cannot include accented characters.The name can only include the following characters:A-Z, a-z, and 0-9. The name must begin with one of thefollowing characters: A-Z or a-z. Or, change theprimary group of the user specified to above thenaming rules.

GLPGRP055E The user ID specified, 'user name', isnot a valid name and violates thenaming rules.

Explanation: The program failed because a user namethat is not valid was specified.

User response: Specify a user name according to thefollowing rules: The user name must contain 1 to 8characters. The name cannot be 'USERS', 'ADMINS','GUESTS', 'PUBLIC', or 'LOCAL'. The name cannotbegin with 'IBM', 'SQL', or 'SYS'. The name cannotinclude accented characters. The name can include onlythe following characters: A through Z, a through z, and

0 through 9. The name must begin with one of thefollowing characters: A through Z or a through z.

GLPHST002E An internal error occurred whilerunning the idssethost command.

Explanation: An internal error occurred while runningthe idssethost command. This might have been causedbecause the program ran out of memory.


GLPHST003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPHST008E Failed to configure the IP addressinformation for directory serverinstance: 'instance name'.

Explanation: An error occurred while trying toconfigure the IP address information for the directoryserver instance.


GLPHST009E The requested IP address change willcause a port conflict with anotherdirectory server instance.

Explanation: Specified an IP address change that willcause a port conflict with another directory serverinstance.

User response: Specify an IP Address that is valid onthe computer and does not cause a port conflict withother directory server instances. To see what IPAddresses and ports are being used by anotherdirectory server instance use idsilist with the -a option.

GLPHST010E The -i option is required and was notspecified.

Explanation: The -i option was not specified and it isrequired.

User response: Specify the -i option. Use the -? optionto see the syntax for the command.

GLPGRP043E • GLPHST010E


GLPHST011W The Admin Server for the directoryserver instance is currently running andmust be restarted for the change to theIP addresses to take effect.

Explanation: The Admin Server for the directoryserver instance was running when the IP addresseswere reconfigured. Therefore, it must be restarted to beable to bind to the IP addresses.

User response: Stop the Admin Server of the directoryserver instance using the ibmdiradm -k command andthen start the Admin Server again using the ibmdiradmcommand.

GLPHST012E The IP address specified 'IP Address' isnot an existing IP Address on thecomputer.

Explanation: Tried to set an IP address that does notexist on the operating system.

User response: Specify a valid IP address that isconfigurable for this computer.

GLPICR003E The port number specified by the -aoption must be an integer greater than 0and less than or equal to 65535.

Explanation: Specified a port number that is less than0 or greater than 65535 or was not an integer.

User response: When using the -a option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPICR004E The port number specified by the -coption must be an integer greater than 0and less than or equal to 65535.


User response: When using the -c option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPICR005E The port number specified by the -poption must be an integer greater than 0and less than or equal to 65535.


User response: When using the -p option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPICR006E The port number specified by the -soption must be an integer greater than 0and less than or equal to 65535.


User response: When using the -s option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPICR007E The -I option is required and is used tospecify the instance name.



GLPICR008E The directory server instance namespecified, 'instance name', is not a validname and violates the directory serverinstance name naming rules.

Explanation: The program failed because an incorrectdirectory server instance name was specified.

User response: Specify a directory server instancename that adheres to the following rules: The directoryserver instance name must contain 1 to 8 characters.The name cannot be 'USERS', 'ADMINS', 'GUESTS','PUBLIC', or 'LOCAL'. The name cannot begin with'IBM', 'SQL', or 'SYS'. The name cannot includeaccented characters. The name can only include thefollowing characters: A-Z, a-z, _(underscore) and 0-9.The name must begin with one of the followingcharacters: A-Z or a-z. The name cannot be 'ROOT'.

GLPICR009E The DB2 instance name specified,'database name', is not a valid name andviolates the DB2 instance name namingrules.

Explanation: The program failed because an incorrectDB2 instance name was specified.

User response: Specify a DB2 instance name thatadheres to the following rules: The DB2 instance namemust contain 1 to 8 characters. The name cannot be'USERS', 'ADMINS', 'GUESTS', 'PUBLIC', or 'LOCAL'.The name cannot begin with 'IBM', 'SQL', or 'SYS'. Thename cannot include accented characters. The name canonly include the following characters: A-Z, a-z, and 0-9.The name must begin with one of the followingcharacters: A-Z or a-z.

GLPICR010E The DB2 instance name specified, 'db2instance', must match an existing user IDon the operating system.

Explanation: The DB2 instance owner ID with the

GLPHST011W • GLPICR010E


same name as the specified DB2 instance name doesnot exist on the system.

User response: Specify an existing user ID on thesystem for the DB2 instance name.

GLPICR011E The directory server instance namespecified, 'instance name', must match anexisting user ID on the operatingsystem. If a user is to be created, thenthe -G and -w options must bespecified.

Explanation: The directory instance owner ID with thesame name as that specified for directory serverinstance name does not exist on the system. If the useris to be created, then the -G and -w options must bespecified.

User response: Specify an existing user ID on thesystem for the directory server instance name, orspecify the -G and -w options and retry the operation.

GLPICR012E The -t option cannot be specified if theRDBM component of the server has notbeen installed on the operating system.

Explanation: The program cannot detect that theRDBM server component was installed. If the RDBMcomponent is not installed, it is not possible for theprogram to use DB2 functionality.

User response: Install the RDBM component or usethe command without the -t option.

GLPICR018E The -e option is required.

Explanation: The -e option is required to specify theencryption seed for the directory server instance.

User response: Specify the -e option or do not run thecommand in no-prompt mode to avoid this error. Usethe -? option to see the syntax for the command.

GLPICR022E The directory server instance 'instancename' already exists.

Explanation: Tried to create a directory server instancethat already exists.

User response: If a new directory server instance isneeded, specify a directory server instance name thatdoes not exist. The idsilist command can be used to geta list of directory server instances on the computer.

GLPICR023E An internal error occurred whilecreating the directory server instance.

Explanation: An internal error occurred while creatingthe directory server instance. This might have beencaused because the program ran out of memory.

User response: See IBM Security Directory Server

Product Overview for information about hardware andsoftware requirements. If all requirements are met,attempt to run the command again. If the problempersists, contact IBM Software Support.

GLPICR024W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.


User response: Review the earlier error messages forinformation about the exact error.

GLPICR027E Failed to register directory serverinstance: 'instance name'.

Explanation: The program failed to register thedirectory server instance.


GLPICR030E Failed to create directory server instance:'instance name'.

Explanation: The program failed to create thedirectory server instance.


GLPICR033E Failed to add database instance 'DB2instance' to directory server instance:'instance name'.

Explanation: The program failed to add the DB2instance to the directory server instance.


GLPICR011E • GLPICR033E


GLPICR036E Failed to create schema files fordirectory server instance: 'instance name'.

Explanation: The program failed to create the schemafiles for the directory server instance.


GLPICR039E Failed to create log files for directoryserver instance: 'instance name'.

Explanation: The program failed to create the log filesfor the directory server instance.


GLPICR042E Failed to create configuration file fordirectory server instance: 'instance name'.

Explanation: The program failed to create the newconfiguration file for the directory server instance.


GLPICR045E Failed to create key stash files fordirectory server instance: 'instance name'.

Explanation: The program failed to create the new keystash files for the directory server instance.


GLPICR048E Failed to create profile scripts fordirectory server instance: 'instance name'.

Explanation: The program failed to create the profilescripts for the directory server instance.

User response: Review earlier error messages

generated from the program to determine how torespond to this error. If no previous error messagesoccurred, look in the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPICR051E Failed to create directories for directoryserver instance: 'instance name'.

Explanation: The program failed to create thedirectories for the directory server instance.


GLPICR054E Failed to create DB2 instance link fordirectory server instance: 'instance name'.

Explanation: The program failed to create the DB2instance link for the directory server instance.


GLPICR055E The -l option is required and is used tospecify the location to create thedirectory server instance.

Explanation: The -l option was not specified and it isrequired.

User response: Specify the -l option. Use the -? optionto see the syntax for the command.

GLPICR056E Failed to retrieve the home directory forthe following user: 'user name'.

Explanation: The program tried to retrieve the homedirectory of the specified user. This user matches thename of the directory server instance name specified.

User response: Verify that the specified user exists onthe computer and has a home directory defined. Inaddition, you can try to specify a specific location usingthe -l option.

GLPICR058E The specified directory, 'filename', is nota valid directory, does not exist, or is notwritable.

Explanation: The directory specified to create the



directory server instance in a location that is not valid,is not writable, or is not accessible.

User response: Verify that the location where theinstance is going to be created is a valid location on thesystem and that you have access to write to thatlocation. The directory must exist.

GLPICR059E The specified directory server instancelocation 'location' is not a drive.

Explanation: The location chosen to configure adirectory server instance was not a drive. On theWindows operating system, the location must be a filesystem drive and not a directory.

User response: Verify that the location specified exists,that you have access to write to that location, and thatthe location has the necessary free space. Or chooseanother location that meets the criteria.

GLPICR060E The database instance specified 'DB2instance' is already being used byanother directory server instance.

Explanation: Tried to create a directory server instancewith a DB2 database instance that is used by anotherdirectory server instance.

User response: Specify a DB2 instance name that isnot already being used by another directory serverinstance.

GLPICR063E Failed to create Windows service for theadministration server for directoryinstance: 'instance name'.

Explanation: The admin server cannot be installed asa Windows service.

User response: If any previous error messagesoccurred, look at those messages to see how to respondto the error. Otherwise, you must be part of theAdministrators group to create the Windows service. Ifyou are part of the Administrators group, look in theIBM Security Directory Server Troubleshooting Guidefor information about debugging the program andcontacting IBM Software Support.

GLPICR064W The Windows service for theadministration server for directoryinstance 'instance name' already exists.

Explanation: The admin server service was alreadyinstalled and must have resided on the computer whencreating the directory server instance.

User response: This is only a warning. If there areissues when starting the administration server for thedirectory instance as a service, then the directory serverinstance must be removed and added again. If thiswarning message continues to occur, contact IBMSoftware Support.

GLPICR067E Failed to create Windows service fordirectory server instance: 'instance name'.

Explanation: The directory server instance cannot beinstalled as a Windows service.

User response: If any previous error messagesoccurred, look at those messages to see how to respondto the error. Otherwise, you must be part of theAdministrators group to create the Windows service. Ifyou are part of the Administrators group, look in theIBM Security Directory Server Troubleshooting Guidefor information about debugging the program andcontacting IBM Software Support.

GLPICR068W The Windows service for directoryserver instance 'instance name' alreadyexists.

Explanation: The directory server instance service wasalready installed and must have resided on thecomputer when creating the directory server instance.

User response: This is only a warning. If there areissues when starting the directory server instance as aservice, then the directory server instance must beremoved and added again. If this warning messagecontinues to occur, contact IBM Software Support.

GLPICR071E Failed to add entry to /etc/inittab for theadministration server for directoryinstance: 'instance name'.

Explanation: The admin server cannot be registered in/etc/inittab.

User response: You must be the root user on thecomputer to update the /etc/inittab file. If you are theroot user, look in the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPICR072W The entry in /etc/inittab for theadministration server for directoryinstance 'instance name' already exists.

Explanation: The admin server was already installedin /etc/inittab and must have resided on the computerwhen creating the directory server instance.

User response: This is only a warning. If there areissues when starting the administration server for thedirectory instance when the computer starts, then thedirectory server instance must be removed and addedagain. If this warning message continues to occur,contact IBM Software Support.

GLPICR059E • GLPICR072W


GLPICR075E Failed to configure ports and IPaddresses for directory server instance:'instance name'.

Explanation: The directory server instance ports andIP addresses cannot be configured in the ibmslapd.conffile. This is most likely an internal error.


GLPICR076E The directory server instance 'instancename' already exists.

Explanation: Tried to create a directory server instancethat already exists.

User response: Specify a directory server instancename that does not exist.

GLPICR079E Failed to configure key stash files fordirectory server instance: 'instance name'.

Explanation: The program failed to configure the newkey stash files for the directory server instance.


GLPICR080E The specified directory, 'filename', doesnot have enough free space. Specify anexisting location that is writable with atleast 30 MB of free space.

Explanation: The directory specified to create thedirectory server instance in does not have enough freespace. The location must have at least 30 MB of freespace.

User response: Verify that the location where theinstance is going to be created is a valid location on thesystem and that you have access to write to thatlocation. The directory must exist and must have 30MB of free space.

GLPICR083E Failed to configure database instance'DB2 instance' for directory serverinstance: 'DB2 instance'.

Explanation: An internal error occurred while tryingto configure the database instance in the directoryserver instance configuration file.

User response: Look in the IBM Security DirectoryServer Troubleshooting Guide for information about

debugging the program and contacting IBM SoftwareSupport.

GLPICR087E Failed to configure schema files fordirectory server instance: 'instance name'.

Explanation: The program failed to configure theschema files for the directory server instance.


GLPICR090E Failed to configure log files for directoryserver instance: 'instance name'.

Explanation: The program failed to configure the logfiles for the directory server instance.


GLPICR091E A database instance is alreadyconfigured in directory server instance'instance name'.

Explanation: Tried to configure a database instance fora directory server instance and one was alreadyconfigured.

User response: Unconfigure the current databaseinstance from the directory server instance if a newdatabase instance needs to be configured.

GLPICR092E The encryption seed must only containprintable ISO-8859-1 ASCII characterswith values in the range of 33 to 126inclusive, and must be a minimum of 12and a maximum of 1016 characters inlength.

Explanation: The program failed because an incorrectencryption seed was specified.


GLPICR093E The IP address specified 'IP Address' isnot an existing IP address on thecomputer.

Explanation: Tried to create a directory server instance



with an IP address that does not exist on the operatingsystem.

User response: Specify a valid IP address that isconfigurable for this computer.

GLPICR094E The ports numbers specified by the -a,-c, -p or -s options must not match eachother and must not cause a conflictbetween any ports in the configurationfile of the directory server instance.

Explanation: Ports were specified that will conflict inthe configuration file of the directory server instance.

User response: Specify unique ports numbers that donot match each other.

GLPICR095E Port 'port number' is already being usedby another directory server instance.

Explanation: Specified a port that is being used byanother directory server instance

User response: Specify a port that is not being used inany other directory server instance.

GLPICR096E The primary group, 'group name', of theuser , 'user name', is not a valid nameand violates the name naming rules.

Explanation: The program failed because the primarygroup of the directory server instance owner that wasto be created is not valid.

User response: Specify a user that has a primarygroup that adheres to the following rules: The primarygroup name must contain 1 to 8 characters. The namecannot be 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC', or'LOCAL'. The name cannot begin with 'IBM', 'SQL', or'SYS'. The name cannot include accented characters.The name can only include the following characters:A-Z, a-z, and 0-9. The name must begin with one of thefollowing characters: A-Z or a-z. Or, change theprimary group of the user specified to follow thenaming rules.

GLPICR097E Unable to determine the primary groupof the user 'user name'. The primarygroup of the directory server instanceowner must be validated before adirectory server instance can be created.

Explanation: Unable to validate the primary group ofthe directory server instance owner. This is most likelyan internal error.

User response: Validate that the user name exists onthe computer and has a primary group assigned to theuser. If the user name and primary group are valid,contact IBM Software Support.

GLPICR098E The primary group, 'group name', of theuser , 'user name', is not a valid nameand violates the name naming rules.

Explanation: The program failed because the primarygroup of the database instance owner that was to becreated is not valid.

User response: Specify a user that has a primarygroup that adheres to the following rules: The primarygroup name must contain 1 to 8 characters. The namecannot be 'USERS', 'ADMINS', 'GUESTS', 'PUBLIC', or'LOCAL'. The name cannot begin with 'IBM', 'SQL', or'SYS'. The name cannot include accented characters.The name can only include the following characters:A-Z, a-z, and 0-9. The name must begin with one of thefollowing characters: A-Z or a-z. Or, change theprimary group of the user specified to follow thenaming rules.

GLPICR099E Unable to determine the primary groupof the user 'user name'. The primarygroup of the DB2 database instanceowner must be valid before a directoryserver instance can be created.

Explanation: Unable to validate the primary group ofthe DB2 database instance owner. This is most likely aninternal error.

User response: Validate that the user name exists onthe computer and has a primary group assigned to theuser. If the user name and primary group are valid,contact IBM Software Support.

GLPICR100E The directory server instance owner,'user name', must be a member of theprimary group, 'group name', of thedatabase instance owner, 'user name'.

Explanation: The directory server instance ownermust be a member of the primary group of thedatabase instance owner. They need not be in the sameprimary group but the directory server instance ownermust be in that primary group.

User response: Add the directory server instanceowner user name to the primary group of the directoryserver instance owner, or retry the operation byspecifying the -G and -w options.

GLPICR101E The directory server instance owner,'user name', must be a member of thegroup 'idsldap'.

Explanation: The directory server instance ownermust be a member of the idsldap group.

User response: Add the directory server instanceowner user name to the idsldap group, or retry theoperation by specifying the -G and -w options.



GLPICR102E 'root' must be a member of the primarygroup, 'group name', of the databaseinstance owner, 'user name'.

Explanation: The database instance that is createdwhile creating a directory server instance failed becauseroot is not a member of the database instance owner'sprimary group.

User response: Add root to the database instanceowner's primary group, or retry the operation byspecifying the -G and -w options.

GLPICR105E Failed to add instance information tothe .profile file for directory serverinstance: 'instance name'.

Explanation: The program failed to add the instanceinformation to the .profile file for the directory serverinstance. The .profile file is located in the homedirectory of the directory server instance owner.

User response: Verify that the .profile file for thedirectory server instance owner exists and is writable.Review earlier error messages generated from theprogram to determine how to respond to this error. Ifno previous error messages occurred, look in the IBMSecurity Directory Server Troubleshooting Guide forinformation about debugging the program andcontacting IBM Software Support.

GLPICR108E Failed to add environment variables fordirectory server instance: 'instance name'.

Explanation: The program failed to add directoryserver instance environment variables to theenvironment of the directory server instance owner.


GLPICR111E Failed to create ibmslapdService.cmdfile for directory server instance:'instance name'.

Explanation: The program failed to create theibmslapdService.cmd file for the directory serverinstance. The file is needed to run the directory serverinstance as a Windows Service.


GLPICR114E Failed to create ibmdiradmService.cmdfile for directory server instance:'instance name'.

Explanation: The program failed to create theibmdiradmService.cmd file for the directory serverinstance. The file is needed to run the administrationserver for the directory instance as a Windows Service.


GLPICR115E Cannot configure database instancebecause the directory server instance'instance name' does not exist.

Explanation: Specified to configure a databaseinstance for a directory server instance does not exist.

User response: Specify a directory server instance thatexist and does not already have a database instanceconfigured.

GLPICR116E The -C option cannot be specified if theRDBM component of the server has notbeen installed on the operating system.

Explanation: The program cannot detect that theRDBM server component was installed. If the RDBMcomponent is not installed, it is not possible for theprogram to use DB2 functionality.

User response: Install the RDBM component or usethe command without the -C option.

GLPICR117E A database instance is alreadyconfigured for directory server instance'instance name'.

Explanation: A database instance is already configuredfor the directory server instance specified.

User response: Unconfigure the database instance ifanother database instance needs to be configured.Otherwise, no further action is necessary.

GLPICR120E Failed to create runtime executable fordirectory server instance: 'instance name'.

Explanation: The program failed to create the runtimeexecutable for the directory server instance. Theexecutable is called by the administration server to startthe directory server for the instance.

User response: Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, look in the IBM Security Directory Server



Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPICR121E The directory server instance owner,'user name', must be a member of thegroup 'Administrators'.

Explanation: The directory server instance ownermust be a member of the Windows Administratorsgroup.

User response: Add the directory server instanceowner user name to the Windows Administratorsgroup or choose another user name that is already inthe Administrators group.

GLPICR122E The specified directory, 'directory', doesnot have read, write, and executepermissions for the directory serverinstance owner 'username'.

Explanation: The directory specified did not haveread, write, and execute permissions for the specifieddirectory server instance owner. These permissions arerequired for the directory server instance owner to beable to start the server instance and run othercommand line utilities.

User response: Verify that the location where thedirectory server instance is going to be created is avalid location on the system and that the directoryserver instance owner has write access to that location.The directory server instance owner might not be ableto start the directory server instance and run othercommand line utilities, if the permissions on thelocation are not set correctly.

GLPICR123E Unable to determine the ownership andpermissions on the directory 'filename'.

Explanation: The command was unable to determinethe ownership and permissions of the directory wherethe directory server instance was going to be created.

User response: Verify that the location where thedirectory server instance is going to be created is avalid location on the system and the directory serverinstance owner has write access to that location.

GLPICR124E The location of directory server instance'instance name' cannot be found.

Explanation: Directory server instance location couldnot be retrieved from the Server Instance Repositoryfile. The location is required to configure the databaseinstance for the specified directory server instance.

User response: Try to run the command again. If theproblem continues look in the directory server instancerepository to verify the location is registered. If thelocation is not registered, register it by manuallyupdating the entry in the directory server instance

repository. If the command still fails after this, contactIBM Software Support.

GLPICR125E The directory server instance 'instancename' is a proxy server instance forwhich a database instance cannot beconfigured.

Explanation: A directory server instance that isconfigured as a proxy cannot have a DB2 databaseinstance configured for it.

User response: Reconfigure the directory serverinstance to not be a proxy and try to run the commandagain.

GLPICR126E A directory server instance with a DB2database instance cannot be createdbecause the necessary libraries are notloaded.

Explanation: A directory server instance with a DB2database instance requires access to certain librariesthat cannot be found on the system.

User response: Install the necessary files, or specifythe -x option to create a proxy directory server instance.

GLPICR128E The encryption salt must contain onlyprintable ISO-8859-1 ASCII characterswith values in the range of 33 to 126inclusive, and must be exactly 12characters in length.

Explanation: The program failed because an incorrectsalt value was specified.


GLPICR129E Error on running the idsadduserprogram.

Explanation: An error occurred while invoking orrunning idsadduser.

User response: Correct the problem and retry theoperation.

GLPICR131E The -G option must be specified inconjunction with -w and vice-versa.

Explanation: User has specified either the -G optionwithout specifying -w or vice-versa.

User response: Specify both the options and retry theoperation.



GLPICR132E The directory server instance owner,'user name', must be a member of thegroup 'db2group'.

Explanation: The directory server instance must be amember of the DB2 extended security group.

User response: Add the directory server instanceowner user name to the Windows DB2 extendedsecurity group or choose another user name that isalready member of DB2 extended security group.

GLPICR135E Failed to set the DB2 registry fordatabase instance 'DB2 instance' to allowDB2 SELECTIVITY.

Explanation: The command db2setDB2_SELECTIVITY=YES has failed for this databaseinstance..

User response: Set the environment variableIBMSLAPD_USE_SELECTIVITY to 'NO' and rerun thecommand to create the instance.

GLPICR136W The DB2 registry for databaseinstance 'DB2 instance' could not be setto allow DB2 SELECTIVITY but'IBMSLAPD_USE_SELECTIVITY' is setto 'NO'.

Explanation: The command db2setDB2_SELECTIVITY=YES has failed for this databaseinstance. The environment variable'IBMSLAPD_USE_SELECTIVITY' is set to 'NO', so thefailure will be ignored and instance creation willcontinue.

User response: Manually set the DB2_SELECTIVITYfor the new database instance to YES using the db2setcommand and unset the environment variableIBMSLAPD_USE_SELECTIVITY or start the directoryserver with the environment variableIBMSLAPD_USE_SELECTIVITY to 'NO'.

GLPIDL002E The LDAP URL for the source directoryserver instance, the -sU option, must beprovided.

Explanation: The LDAP URL that will be used tocontact the source directory server instance must bespecified.

User response: Provide the -sU option to thecommand and specify the LDAP URL for the sourcedirectory server instance.

GLPIDL003E The administrator DN for the sourcedirectory server instance, the -sD option,must be provided.

Explanation: The administrator DN that will be usedto connect to the source directory server instance mustbe specified.

User response: Provide the -sD option to thecommand and specify the administrator DN for thesource directory server instance.

GLPIDL004E The administrator DN for the newdirectory server instance, the -D option,must be provided.

Explanation: The administrator DN that will beconfigured for the new directory server instance mustbe specified.

User response: Provide the -D option to the commandand specify the administrator DN for the new directoryserver instance.

GLPIDL005E The directory path for the backup of theDB2 database, the -L option, must beprovided.

Explanation: The path that will be used for thebackup and restore of the DB2 database must bespecified.

User response: Provide the -L option to the commandand specify the directory path to be used for thebackup and restore.

GLPIDL006E The -x and -r options cannot be usedtogether.

Explanation: The replication environment setuprequires a database, which is not part of a proxy serverconfiguration.

User response: Specify either the -x or the -r option,but not both.

GLPIDL007E The -x and -p options cannot be usedtogether.

Explanation: The restore option requires a database,which is not part of a proxy server configuration.

User response: Specify either the -x or the -p option,but not both.

GLPIDL008E The -L option is required with the -roption. Include a directory path for thedatabase backup and restore.

Explanation: The replication environment optionrequires that the source directory server instance's databe backed up and the new directory server instancedata be populated. The directory path for the backupand restore must be supplied.

User response: If the -r option is used, the -L optionmust also be given. Either do not include the -r option,or provide the -L option.

GLPICR132E • GLPIDL008E


GLPIDL009E The -w option is required.

Explanation: The -w option is required to specify thepassword of the directory server administrator.

User response: Specify the -w option or do not runthe command in no-prompt mode to avoid this error.Use the -? option to see the syntax for the command

GLPIDL010E The LDAP URL given for the sourcedirectory server instance, the -sU option,is not a valid LDAP URL.

Explanation: The URL given is not a valid LDAPURL.

User response: Provide a valid LDAP URL: eitherldap://hostname:port or ldaps://hostname:port.

GLPIDL012E The -sw option is required.

Explanation: The -sw option is required to specify thepassword of the source directory server administrator.

User response: Specify the -sw option or do not runthe command in no-prompt mode to avoid this error.Use the -? option to see the syntax for the command

GLPIDL014E The -a option is required.

Explanation: The -a option is required to specify thepassword of the database administrator.

User response: Specify the -a option or do not run thecommand in no-prompt mode to avoid this error. Usethe -? option to see the syntax for the command

GLPIDL016E Unable to determine what mode thesource directory server is running in.

Explanation: The utility could not determine whetherthe source directory server instance was running inconfiguration only mode or not.

User response: Verify that the source directory serveris running and accessible from the target system.

GLPIDL017E The source directory server is runningin configuration only mode.

Explanation: The source directory server is notrunning in a mode suitable for the utility. It should notbe running in configuration only mode for this utilityto run.

User response: Verify that the source directory serveris running, is accessible from the target system, and isnot running in configuration only mode.

GLPIDL018E The source directory server isconfigured as a proxy server.

Explanation: The source directory server is configuredas a proxy server; therefore, the target directory servermust also be a proxy server.

User response: Include the -x option to the command,or specify a source directory server that is notconfigured as a proxy server.

GLPIDL019E The source directory server isconfigured as an RDBM server.

Explanation: The source directory server is configuredas an RDBM server; therefore, the target directoryserver must also be an RDBM server.

User response: Do not include the -x option to thecommand, or specify a source directory server that isnot configured as an RDBM server.

GLPIDL021E The encryption seed specified does notmatch the encryption seed for the sourcedirectory server instance.

Explanation: The encryption seed supplied must bethe same as the one that was used when the sourcedirectory server instance was created.

User response: Ensure that the correct encryption seedis specified with the -e option.

GLPIDL022E The encryption seed or encryption saltvalue could not be retrieved from thesource directory server instance.

Explanation: These was an error obtaining theinformation from the source directory server instance.

User response: Ensure that the source directory serverinstance is running and accessible.

GLPIDL024E The source directory server is notrunning IBM Security Directory ServerVersion 6.3.1.

Explanation: The source directory server is notrunning a version of IBM Security Directory Serversupported by this utility.

User response: Specify a source directory server thatis running IBM Security Directory Server Version 6.3.1.

GLPIDL025E The source directory server type couldnot be determined.

Explanation: The source directory server type couldnot be retrieved.


GLPIDL009E • GLPIDL025E


GLPIDL027E The directory server instance 'instancename' does not exist.

Explanation: Cannot restore database to an instancethat does not yet exist.

User response: If the wrong name was specified,specify a directory server instance name that exists.Otherwise, no action is required.

GLPIDL028E The specified directory, 'directory', is nota valid directory, does not exist, or is notaccessible. Cannot restore database.

Explanation: The directory specified for restoring thedatabase is a location that is not valid or is notaccessible.

User response: Verify that the location specified forthe backup files is a valid location on the system andthat you have access to that location. The directorymust exist.

GLPIDL029E The -x and -L options cannot be usedtogether.

Explanation: The backup option requires a database,which is not part of a proxy server configuration.

User response: Specify either the -x or the -L option,but not both.

GLPIDL030W The online backup of the sourcedirectory server instance database wasnot successful. Data will not be restoredto the new directory server instance.

Explanation: The extended operation on the sourcedirectory server instance to perform the online backupof the database was not successful.

User response: Ensure that the database on the sourcedirectory server instance is configured correctly toallow for online backups and that the directory pathgiven for the backup images exists on the sourcesystem.

GLPIDL031E Cannot establish a connection with thesource directory server instance usingthe LDAP URL provided: 'ldapurl'.

Explanation: Either the server is not running or theLDAP URL specified is not valid.

User response: Correct the LDAP URL and ensurethat the server is running.

GLPIDL032E Unable to retrieve the operating systeminformation for the target and sourceserver systems.

Explanation: The utility was unable to retrieve

information about the operating systems of the targetand source systems.

User response: Ensure that the source server isrunning and accessible.

GLPIDL034W The configuration information fromthe source server for 'configType' couldnot be copied.

Explanation: The configuration information for thegiven function could not be copied from the sourcedirectory server instance.

User response: Ensure that the database on the sourcedirectory server instance is running and accessible.

GLPIDL035W The information for SSLconfiguration from the source directoryserver has been copied. Ensure that allnecessary files are in place beforestarting the directory server instance. Ifdesired, set ibm-slapdSslPKCS11Enabled to true.

Explanation: Verify the SSL configuration informationbefore starting the new directory server instance.

User response: Verify that all the SSL information isaccurate and applicable to the system.

GLPIDL036W Unable to transfer one or both of thekey database and key stash files for SSLconfiguration from the source server.

Explanation: The key database file or the key stashfile or both could not be transferred from the sourcesystem.

User response: Verify that the files exist on the sourcesystem and are accessible.

GLPIDL037W An SSL connection has not beenestablished with the source directoryserver instance; therefore, informationabout the SSL configuration of thatserver will not be copied to the newdirectory server instance.

Explanation: The utility will not copy SSL relatedinformation if an SSL connection is not made with thesource server.

User response: If the SSL information from the sourceserver is required, establish an SSL connection with thesource server through the utility.

GLPIDL027E • GLPIDL037W


GLPIDL038W The Kerberos configurationinformation from the source directoryserver instance has been copied to thetarget instance, but Kerberos is notcurrently enabled for the instance.Verify that the information is accurateand applicable to this system andmodify the ibm-slapdKrbEnableattribute to be TRUE.

Explanation: The ibm-slapdKrbEnable attribute wasset to FALSE after all the information was set becauseverification of the configuration is necessary beforeenabling Kerberos for the server instance.

User response: Verify that the Kerberos settings areaccurate and applicable to the target system, and thenenable Kerberos for the server instance.

GLPIDL039W Kerberos is configured for the sourcedirectory server instance, but the targetsystem does not support Kerberos. Theconfiguration information will not becopied to the target system.

Explanation: Only AIX system supports Kerberosauthentication for the directory server instance.

User response: If Kerberos authentication is requiredfor the directory server instance, use a system thatsupports Kerberos.

GLPIDL040W The restore of the DB2 databaseassociated with the directory serverinstance was not successful. Data for thesource directory server instance will notbe loaded.

Explanation: The DB2 restore was not successful.

User response: Use other provided utilities to load thedata on the target directory server instance.

GLPIDL041W Any additional plugins defined onthe source directory server instance willnot be copied to the target directoryserver instance configuration file. Ifnecessary, plugins must be madeavailable to the target system and addedto the configuration file before use.

Explanation: The utility will not preserve any pluginsthat have been added to the source directory serverinstance's configuration.

User response: The libraries for the plugins must bemade available to the target directory server instancesystem and added to the configuration.

GLPIDL051W The replication configuration was notsuccessful. The online backup of thesource server will not be performed.

Explanation: Unable to configure replication.


GLPIDL053W The restore of the database was notsuccessful or was not attempted due to aprevious error. For replication to befully configured, the data must beloaded on the target directory serverinstance.

Explanation: Unable to restore database.

User response: Load the data on the target directoryserver instance.

GLPIDL055W Unable to set the server ID.Replication could not be configured.

Explanation: Unable to configure replication becausethe server ID could not be set.

User response: Check the logs for error messages.

GLPIDL060W Replication could not be configuredbecause the source directory server isnot currently configured as a masterserver.

Explanation: Unable to configure replication becausethe source server is not set up as a master server in areplication topology.

User response: Ensure that replication is configuredcorrectly or specify an alternate source directory server,or both.

GLPIDL061W Replication could not be configuredbecause the source directory server iscurrently configured as a gateway serverin the replication topology.

Explanation: Unable to configure replication becausethe source server is set up as a gateway server in areplication topology.

User response: Specify an alternate source directoryserver that is not configured as a gateway server.

GLPIDL063W The DB2 backup and restoreoperations are not permitted betweenthe target operating system, 'targetOS',and the source operating system,'sourceOS'.

Explanation: DB2 does not support backup andrestore between the operating systems shown.

GLPIDL038W • GLPIDL063W


User response: Either specify target and sourceoperating systems that support backup and restore, ormove the DB2 data in some other way.

GLPIDL065E The database instance owner's password(-a option) cannot be specified when aproxy server is being cloned (-x option).

Explanation: A proxy server does not have databaseinstance, and specifying a database instance owner'spassword is not valid when cloning a proxy server.Starting with the IBM Tivoli Directory Server 6.2 releasethis message is deprecated.

User response: Do not specify both the -a and -xoptions.

GLPIDL066E The bind dn and pw to connect to thesource server must be the admin DNand PW.

Explanation: The admin DN and PW is required tobind to the source server.

User response: Provide the admin dn and pw.

GLPIDL067W The 'dn' entry cannot be copied to thetarget server. This entry must be createdmanually.

Explanation: The 'dn' entry is not copied to the targetserver. This tool only supports replication configured touse simple binds.

User response: Create the required entry manually forreplication to work properly.

GLPIDL068E The directory server instance namespecified, 'instance name', must match anexisting user ID on the operatingsystem. If a user is to be created, thenthe -G and -a options must be specified.

Explanation: The directory instance owner ID with thesame name as that specified for directory serverinstance name does not exist on the system. If a user isto be created, then the -G and -a options must bespecified.

User response: Specify an existing user ID on thesystem for the directory server instance name, orspecify the -G and -a options and retry the operation.

GLPIDL069E The -G option must be specified inconjunction with -a and vice-versa whendeploying a proxy instance.

Explanation: While deploying a proxy instance, userhas specified either the -G option without specifying -aor vice-versa.

User response: Specify both the options and retry theoperation.

GLPIDL070E Restore is not pending for the directoryserver instance 'instance name'.

Explanation: The directory server instance is not inrestore pending state. Hence restore is denied.

User response: Make sure that restore is pending forthe directory server instance and run the commandagain.

GLPIDP004E Failed to delete directory serverinstance: 'instance name'.

Explanation: The program failed to delete thedirectory server instance.


GLPIDP007E Failed to remove the DB2 databaseinstance from directory server instance:'instance name'.

Explanation: The program failed to remove the DB2instance from the directory server instance.


GLPIDP010E Failed to delete schema files fordirectory server instance: 'instance name'.

Explanation: The program failed to delete the schemafiles for the directory server instance.


GLPIDP013E Failed to delete log files for directoryserver instance: 'instance name'.

Explanation: The program failed to delete the log filesfor the directory server instance.

User response: Review earlier error messagesgenerated from the program to determine how torespond to this error. If no previous error messagesoccurred, look in the IBM Security Directory Server

GLPIDL065E • GLPIDP013E


Troubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPIDP016E Failed to delete configuration file fordirectory server instance: 'instance name'.

Explanation: The program failed to delete theconfiguration file for the directory server instance.


GLPIDP019E Failed to delete key stash files fordirectory server instance: 'instance name'.

Explanation: The program failed to delete the keystash files for the directory server instance.


GLPIDP022E Failed to delete profile scripts fordirectory server instance: 'instance name'.

Explanation: The program failed to delete the profilescripts for the directory server instance.


GLPIDP025E Failed to delete directories for directoryserver instance: 'instance name'.

Explanation: The program failed to delete thedirectories for the directory server instance.


GLPIDP028E Failed to delete DB2 instance link fordirectory server instance: 'instance name'.

Explanation: The program failed to delete the DB2instance link for the directory server instance.


GLPIDP031W Failed to delete Windows service forthe admin server for directory serverinstance 'instance name'.

Explanation: The program failed to delete theWindows service for the admin server.

User response: Verify that the Windows service for theadmin server still exists. If it does not exist, no furtheraction is required. If the Windows service does exist,attempt to recreate the problem using the samedirectory server instance. If the problem persists,contact IBM Software Support.

GLPIDP034W Failed to delete Windows service fordirectory server instance: 'instance name'.

Explanation: The program failed to delete theWindows service for the directory server instance.

User response: Verify that the Windows service for thedirectory server instance still exists. If it does not exist,no further action is required. If the Windows servicedoes exist, attempt to recreate the problem using thesame directory server instance. If the problem persists,contact IBM Software Support.

GLPIDP037W Failed to remove entry from/etc/inittab for the admin server fordirectory server instance 'instance name'.

Explanation: The program failed to delete the adminserver entry from the /etc/inittab file.

User response: Verify that the /etc/inittab entry stillexists in the /etc/inittab file. If the entry is not gone,then remove it manually. You must be the root user tosuccessfully remove the entry from the /etc/inittab file.

GLPIDP038E The directory server instance 'instancename' does not exist.

Explanation: Tried to delete a directory server instancethat does not exist.

User response: Specify a directory server instancename that does exist if the wrong name was specified.Otherwise, no action is required.

GLPIDP016E • GLPIDP038E


GLPIDP041E Failed to unregister directory serverinstance: 'instance name'.

Explanation: The program failed to unregister thedirectory server instance.


GLPIDP042E The -I option is required and is used tospecify the instance name.





User response: Specify a directory server instancename that exists if the wrong name was specified.Otherwise, no action is required.

GLPIDP049E An internal error occurred whiledeleting the directory server instance.

Explanation: An internal error occurred while deletingthe directory server instance. This might have beencaused because the program ran out of memory.

User response: Attempt to run the command again. Ifthe problem persists, contact IBM Software Support.

GLPIDP050W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.





User response: Specify a directory server instancename that exists if the wrong name was specified.Otherwise, no action is required.

GLPIDP052E The location of directory server instance'instance name' cannot be found.

Explanation: Tried to delete a directory server andcannot find the location of the directory server instance.

User response: Try to run the command again. If theproblem continues look in the directory server instancerepository to verify the location is registered. If thelocation is not registered, register it by manuallyupdating the entry in the directory server instancerepository. If the command still fails, contact IBMSoftware Support.

GLPIDP055E Failed to unconfigure database instance'DB2 instance' for directory serverinstance: 'DB2 instance'.

Explanation: An internal error occurred while tryingto unconfigure the database instance in the directoryserver instance configuration file.


GLPIDP056E A database instance is not configuredfor directory server instance 'instancename'.

Explanation: Tried to delete a database instance for adirectory server instance and a database instance is notconfigured.

User response: Only try to drop the database instancefor a directory server instance if a database instancealready exists.

GLPIDP059E Failed to remove instance informationfrom the .profile file for directory serverinstance: 'instance name'.

Explanation: The program failed to remove theinstance information from the .profile file for thedirectory server instance. The .profile file is located inthe home directory of the directory server instanceowner.

User response: Verify that the .profile file for thedirectory server instance owner exists and is writable.Review earlier error messages generated from theprogram to determine how to respond to this error. Ifno previous error messages occurred, look in the IBMSecurity Directory Server Troubleshooting Guide forinformation about debugging the program andcontacting IBM Software Support.

GLPIDP041E • GLPIDP059E


GLPIDP062E Failed to remove environment variablesfor directory server instance: 'instancename'.

Explanation: The program failed to remove directoryserver instance environment variables from theenvironment of the directory server instance owner.


GLPIDP065E Failed to delete theibmslapdService.cmd file for directoryserver instance: 'instance name'.

Explanation: The program failed to delete theibmslapdService.cmd file for the directory serverinstance.


GLPIDP068E Failed to delete theibmdiradmService.cmd file for directoryserver instance: 'instance name'.

Explanation: The program failed to delete theibmdiradmService.cmd file for the directory serverinstance.


GLPIDP069E The -r option cannot be specified if theRDBM component of the server has notbeen installed on the operating system.

Explanation: The program cannot detect that theRDBM server component was installed. If the RDBMcomponent is not installed, the program cannot useDB2 function.

User response: Install the RDBM component or usethe command without the -r option.

GLPIDP070E A database instance is not configuredfor directory server instance 'instancename'.

Explanation: Tried to delete a database instance for adirectory server instance and one is not configured.

User response: None. Only try to drop the databaseinstance for a directory server instance if one alreadyexists.

GLPIDP074E Failed to delete the runtime executablefor directory server instance: 'instancename'.

Explanation: The program failed to delete the runtimeexecutable for the directory server instance.


GLPIDP076E Failed to delete the ldapdb.propertiesfile for directory server instance:'instance name'.

Explanation: The program failed to delete theldapdb.properties file for the directory server instance.


GLPIDP080E Failed to remove backup files fordirectory server instance: 'instance name'from 'backup path'.

Explanation: The program failed to delete the backupfor the directory server instance.

User response: Use the appropriate operating systemcommand to remove the backup manually.

GLPIDP081W The backup location for directoryserver instance 'instance name' was notconfigured.

Explanation: No backup files exist to be removed.

User response: No additional information is availablefor this message.

GLPIDP062E • GLPIDP081W


GLPIDP082W The backup location 'backup path' fordirectory server instance 'instance name'does not exist.

Explanation: No backup files were found at theconfigured backup location.

User response: No additional information is availablefor this message.

GLPILT002E An internal error occurred whilerunning the idsilist command.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. Aninternal error occurred while running idsilist command.This might have been caused because the program ranout of memory.

User response: See IBM Security Directory ServerProduct Overview for information about hardware andsoftware requirements. If all requirements are met,attempt to run the command again. If the problempersists, look in the IBM Security Directory ServerTroubleshooting Guide for information aboutdebugging the program and contacting IBM SoftwareSupport.

GLPILT003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPILT018E The -a and -r options cannot bespecified at the same time.

Explanation: The -a and -r options were specified atthe same time. This is not allowed.

User response: Specify either the -a or the -r option.Use the -? option to see the syntax for the command.

GLPISA004E You must be the root user to run thiscommand.

Explanation: The link command cannot run becausethe user is not root.

User response: Log in as the root user and run thelink command again.

GLPISA006E Not a supported operating system: OS

Explanation: This link command can only be run onLinux, AIX, Solaris and HP-UX operating systems.

User response: Check your operating system type byrunning this command: uname.

GLPISA007E Unexpected program name: program name

Explanation: Program name must be idslink oridsrmlink.

User response: Rename the program to idslink oridsrmlink and try again.

GLPISA010E Wrong version of program name. Thecorrect version must be: Version Dir

Explanation: A different version of this link commandexists on your system.

User response: Find the correct version and try again.

GLPISA013W Target file not found: Target File

Explanation: This link command tried to set asymbolic link to the target file and failed.

User response: If this link is required, verify the targetfile path and create the link manually.

GLPISA016E Bitmode=BITMODE is not a supportedbit mode.

Explanation: Client library files are provided with 32bits or 64 bits only.

User response: Provide the correct bit mode to theclient libraries option, and try again.

GLPISA017E Failed to run: command to execute

Explanation: Failed to run the specified command.

User response: See the program log file for detailsabout the failure.

GLPISA018W Not setting this link: link to set

Explanation: An existing link or file or directory wasfound, but it was not replaced.

User response: To override the existing link or file ordirectory with new link, rerun with the force option.

GLPISA019E Cannot set and remove link in onecommand.

Explanation: The options for setting links andremoving links are mutually exclusive.

User response: Rerun, using the option for settinglinks and the option for removing links on separatecommands.

GLPISA020E Option was not correctly specified.

Explanation: Specified an option incorrectly.

User response: Try again, specifying all the optionscorrectly.

GLPIDP082W • GLPISA020E


GLPISA021E Invalid argument=option argument

Explanation: See the usage description for details.

User response: Provide a correct argument option,and try again.

GLPISA023W Overriding conflict of set description isnot allowed because a version of IBMSecurity Directory Server that is before6.0 exists.

Explanation: A version of Directory Server beforeversion 6.0 exists on the system.

User response: Uninstall the older version ofDirectory Server, and try again.

GLPISA025W Conflicts found. Cannot set links forset description.

Explanation: Conflicts exist.

User response: Rerun the command with the forceoption.

GLPISA035E Lists to copy are empty or corrupted.

Explanation: This is an internal error. Global staticlink lists to copy are corrupted or empty.

User response: Check the script if the global lists arenot corrupted or empty.

GLPISA036E From and to lists to copy haveunmatched number of elements

Explanation: This is an internal error. Global staticlink lists do not have the same number of elements.

User response: Check the script if the global from listsand to lists have the same number of elements.

GLPISA037W Not a valid IDSWebApp.war file.

Explanation: There is no IDSWebApp.war file foundat the specified location.

User response: Check to see that IDSWebApp.war fileexists at the specified location; specify the correct path.

GLPISA042E The specified profile already exists.Specify another name.

Explanation: The specified profile already exists at thelocation where you are trying to create a new profile.

User response: Specify a different profile name.

GLPISA045E The command line parameter, parameter,is not valid. Use -usage to see theavailable command line options.

Explanation: An incorrect parameter has beenspecified.

User response: Check to see that all the parametersspecified are correct and valid. For more informationuse -usage option.

GLPISA046E The IDSWebApp.war uninstallationfailed. Upgrade cannot continue.

Explanation: Uninstallation of the IDSWebApp.warfile has failed.

User response: The previous version of EmbeddedWAS might not have IDSWebApp.war deployed. Makesure that the IDSWebApp.war file is deployed.

GLPISA047E The Embedded WAS PreUpgrade failed.Upgrade cannot continue.

Explanation: Embedded WAS PreUpgrade has failed.

User response: An error occurred while running thePreUpgrade command. Contact the systemadministrator.

GLPISA048E The Embedded WAS PostUpgradefailed. Upgrade cannot continue.

Explanation: Embedded WAS PostUpgrade has failed.

User response: An error occurred while running thePostUpgrade command. Contact the systemadministrator.

GLPISA049E Error copying the IDSWebApp.war file.Upgrade cannot continue.

Explanation: Cannot copy IDSWebApp.war file.

User response: The IDSWebApp.war file might notexist at the source location.

GLPISA050E Error running wsadmin command.Upgrade cannot continue.

Explanation: Cannot install the new WAR file into thenew WAS product.

User response: An error occurred while running thewsadmin command. Contact the system administrator.

GLPISA052E The specified profile already exists.Specify another name.

Explanation: The specified profile already exists at thelocation where you are trying to create a new profile.

User response: Specify a different profile name.

GLPISA021E • GLPISA052E


GLPISA053E The current Embedded WebSphereApplication Server directory contains adeployed IBM Security Directory ServerWeb Administration Tool. Upgradecannot continue.

Explanation: Embedded WAS already contains adeployed Web Administration Tool.

User response: Uninstall the current WebAdministration Tool and try again. If the problempersists, contact the system administrator.

GLPISA054E The current IBM Security Directory WebAdministration tool must be installed.

Explanation: The Web Administration tool is notinstalled.

User response: Install the Web Administration Tooland try again. If the problem persists, contact thesystem administrator.

GLPISA055E Cannot back up previous IDSWebAppconfiguration. Upgrade cannot continue.

Explanation: An error occurred while copying WebAdministration Tool files from the previous release.

User response: Make sure the source and destinationdirectories exist.

GLPISA056E Cannot restore previous IDSWebAppconfiguration. Backed up files stored at:RESTORE

Explanation: An error occurred while restoring theWeb Administration Tool configuration savedpreviously.

User response: Make sure the source and destinationdirectories exist.

GLPJBP006E Error occurred while connecting toserver: error details.

Explanation: Unable to connect to the directory server.Check to be sure that the server is running andreachable through the network.

User response: The error might have occurred for oneof the following reasons: The server might be down.Start or restart the server. The configuration settingsrequired for directory server access might be incorrector might not exist. Verify that the configuration settingsare correct. There might be a problem in the network.Check the network settings and check that the pingcommand to the server returns Success.

GLPJBP007E Exception occurred while initializingserver server name for SSL. Requiredparameters are missing. Requiredparameters: TrustStore, TrustStorePwd,TrustStoreType, KeyStore, KeyStorePwd,KeyStoreType.

Explanation: The required parameters for initializing aserver for SSL are TrustStore, TrustStorePwd,TrustStoreType, KeyStore, KeyStorePwd, KeyStoreType.An exception occurred while initializing the server forSSL. At least one of the required parameters is missing.

User response: Contact the directory serveradministrator.

Administrator response: Specify all the requiredparameters for initializing the server for SSL.

GLPJBP011E Tool is unable to start.

Explanation: The error might have occurred for one ofthe following reasons: The base DN of the consumerserver might be null. The base DN of the supplierserver might be null. The encryption settings of theconsumer and the supplier do not match.

User response: Verify that the base DN of the supplierand consumer servers are not null and that theencryption settings for the servers match.

GLPJBP013E Exception: exception text

Explanation: An exception occurred while performingthe requested task. The displayed message gives moreinformation about the exception.

User response: View the displayed message for moreinformation about the exception.

GLPJBP015E Failed to determine the server versionfor one of the servers.

Explanation: The directory server is not an LDAPserver supported by the tool. The IBM Tivoli DirectoryServer version might be before 5.1.

User response: Use the tool with a supported versionof IBM Tivoli Directory Server.

GLPJBP016W Password policy is not enabled on oneof the servers. Password policyattributes on entries will be ignoredduring comparisons.

Explanation: See message.

User response:

GLPISA053E • GLPJBP016W


GLPJBP017E Cannot open the specified file for LDIFoutput generation.LDIF file will not becreated.

Explanation: An error occurred while opening orcreating the specified file. The file path might beincorrect or the user might not have enoughpermissions to access the file.

User response: Verify that the file path is correct. Ifthe user does not have enough permissions to accessthe file, contact the system administrator.

GLPJBP018E Exception occurred while closing theLDIF file: exception details

Explanation: An exception might have occurredclosing the LDIF file for one of the following reasons:The file is already closed. The file does not exist at thespecified location. The file reference is not valid. Theuser does not have enough permissions to access thefile.

User response: Verify that the file exists at thespecified location and check the access permissions.

GLPJBP019E Missing arguments: Value not specifiedfor argument name.

Explanation: The following arguments are required forthe successful completion of the requested operation:ldaphost bindDn password keyStore keyStorePwdkeyStoreType trustStore trustStorePwd trustStoreTypeSASL bind mechanism type search base LDIF file namecount for number of entries to process At least one ofthe required arguments is either null or not specified.

User response: Specify all the required parameters.

GLPJBP020W The supplier and consumer servershave different encryption seed or saltvalues. The operation will take longer.

Explanation: The operation is faster if the supplierand consumer servers have the same encryption seedand salt values.

User response: Allow more time for the ldapdiffoperation to complete.

GLPJBP021E Missing required argument; refer to theusage description for valid syntax.

Explanation: The following arguments are required forthe successful completion of the requested operation:hostnames of the servers Administrator DN andpassword Search base At least one of the requiredarguments is either null or not specified.

User response: Specify all the required parameters.

GLPJBP022E Exception occurred while adding DN toLDIF file: exception details

Explanation: An exception occurred while writing theDNs that are to be added to the server to the LDIF file.The user might not have enough permissions to writeto the file or the file might not exist.

User response: Verify that the user has enoughpermissions to write to the file.

GLPJBP023E Exception occurred while deleting DNfrom LDIF file: exception details

Explanation: An exception occurred while writing theDNs that are to be deleted from the server to the LDIFfile. The user might not have enough permissions towrite to the file or the file might not exist.


GLPJBP024E Exception occurred while modifying DNin LDIF file: exception details

Explanation: An exception occurred while writing theDNs that are to be modified at the server to the LDIFfile. The user might not have enough permissions towrite to the file or the file might not exist.


GLPJBP025E Unable to search RootDSE: DirContextis Null.

Explanation: An error might have occurred for one ofthe following reasons: Logged-in user does not havepermission to look up LDAP data. A problem occurredwhile modifying the LDAP data. The LDAP data beingaccessed has incorrect data or incorrect namingattributes or entries. The specified directory server doesnot support the requested directory operation.Synchronization and serialization issues caused aproblem.


GLPJBP026E No RootDSE attributes were returned.

Explanation: A root directory server entry (rootDSE)search on the directory server returned no attributes.


GLPJBP027E Error occurred during enumeration ofattributes from entry name.

Explanation: An error occurred while extracting theroot directory server entry (rootDSE) search attributesas an enumeration.

GLPJBP017E • GLPJBP027E


User response: Retry the operation again. If the errorpersists, contact the directory server administrator.

GLPJBP028E Error occurred while reading rootDSEattributes: error details

Explanation: An error occurred reading the rootdirectory server entry (rootDSE) attributes whileiterating through the attribute list.


GLPJBP029E No naming contexts were found in therootDSE for this server.

Explanation: There are no naming contexts defined inthe directory server.

User response: Define a naming context for thedirectory server and then retry the operation.

GLPJBP030E No subschemasubentry found inrootDSE.

Explanation: The attribute containing the DN for theschema location is missing from the root directoryserver entry.

User response: Define a subschemasubentry for thedirectory server and then retry the operation.

GLPJBP031E An exception occurred during search:exception details.

Explanation: An error occurred while performing asearch operation on the directory server.

User response: The error might have occurred for oneof the following reasons: The directory server is notrunning or unreachable. The logged-in user does nothave authorization to access the search query results.The specified entries are incorrect or have incorrectsyntax. There is another error performing a searchoperation. Contact the directory server administrator.

GLPJBP032E Error occurred while processing searchresults for server: error details.

Explanation: An error occurred while iteratingthrough the search results on the given server.

User response: Retry the operation. If the errorpersists, contact the directory server administrator.

GLPJBP033E Error occurred while settingenvironment variables: error details.

Explanation: An error occurred while initializing theenvironment for a connection with the directory server.The user might not have enough permissions to set theenvironment settings or the system property settings.

User response: Verify that the user has enoughpermissions for setting the properties.

GLPJBP034E Unable to continue. IBM TivoliDirectory Server version 5.1 or higher isrequired.

Explanation: The IBM Tivoli Directory Server versionis less than 5.1. The tool cannot be used with a versionof IBM Tivoli Directory Server that is before version 5.1.

User response: Use the tool with IBM Tivoli DirectoryServer version 5.1 or higher.

GLPJBP039W The supplier and consumer servershave different encryption settings. Theoperation may take longer.

Explanation: The operation is faster if the supplierand consumer servers have the same encryptionsettings.

User response: Allow more time for the ldapdiffoperation.

GLPJBP040E Error while retrieving attributes of baseDN.

Explanation: An error occurred while retrieving theattributes of the base DN.

User response: Retry the operation. If the errorpersists, contact the directory server administrator.

GLPJBP041E Exception occurred while processingDN.

Explanation: Error in parsing the string DN.

User response: Check to be sure that the DN is corrector contact the directory administrator.

GLPJBP042E Exception occurred while fetchingattributes from server.

Explanation: An error occurred while fetching theattributes from the server.


GLPJBP043E Exception occurred.

Explanation: An error might have occurred for one ofthe following reasons: There is a problem performing asearch operation on the directory server. Verify that thesearch request controls are valid. There is a problemtraversing the search results entries of the directoryserver. There is a problem writing to an LDIF file. Theuser does not have enough permissions to modify thefile. There is another error traversing the directoryserver entries.




GLPJBP044E Exception occurred while writing binarydata to LDIF file.

Explanation: An error occurred while writing thebinary data to the LDIF file. The user might not haveenough permissions to modify the file or there mightbe no space left on the disk.

User response: Verify that the user has enoughpermissions to modify the file; otherwise, contact thedirectory server administrator.

GLPJBP045E Invalid entry format for: count or port.

Explanation: The specified number of entries toprocess or the directory server port number is eitherless than zero or not in a proper numeric format.

User response: Specify a valid number greater thanzero.

GLPJBP046E Missing JSSE package for SSLconnection.

Explanation: Either the Java secure socket extension(JSSE) package is not present in the installed version ofJava, or the JSSE settings are not correct.

User response: Check the installed Java for the JSSEjar file.

GLPJBP047E Specified SASL mechanism is notavailable for server server name.

Explanation: An exception occurred because thedirectory server does not support the SASLauthentication mechanism.


GLPJBP048E Unable to fix entry

Explanation: An error might have occurred whilefixing an entry for one of the following reasons: Theuser does not have permissions to modify the entry.The user does not have enough permissions to create anew entry on the directory server. The user does nothave enough permissions to create a new environmentproperty.


GLPJBP049E Error occurred while retrieving filterACL support of the server.

Explanation: An error occurred while retrieving rootdirectory server entry (rootDSE) attributes from thedirectory server.


GLPJBP050E Error occurred while quiescing theserver.

Explanation: The cascading control replicationextended operation to quiesce the specified subtree DNfailed.

User response: The error might have occurred for oneof the following reasons: The subtree is already inquiesced state. The user does not have permission toquiesce the subtree. There is another error running thecascading control replication extended operation on theserver. Contact the directory administrator.

GLPJBP051E Error occurred while unquiescing theserver.

Explanation: The cascading control replicationextended operation to unquiesce the specified subtreeDN failed.

User response: The error might have occurred for oneof the following reasons: The subtree is already inunquiesced state. The user does not have permission tounquiesce the subtree. There is another error runningthe cascading control replication extended operation onthe server. Contact the directory administrator.

GLPJBP052E Error occurred while retrieving type ofthe server.

Explanation: An error occurred while retrieving theserver type information, which indicates whether theserver is a master, from the directory server.


GLPJBP054E Error occurred while setting thereplication controls.

Explanation: An error occurred while setting thereplication request controls. Either the request controlscontain incorrect values or the directory server does notsupport the control.


GLPJBP055E Supplier and consumer servers cannotbe the same.

Explanation: The tool requires that the two servers bedifferent. The tool will exit.

User response: Specify two different servers assupplier and consumer.



GLPJBP056E Internal error occurred.

Explanation: An error occurred while removingcontrols from the previous request.


GLPKEY002E The -s option is required and is usedto specify the salt value.



GLPKEY003E The -l option is required and is usedto specify the location to create thedirectory key stash file.

Explanation: The -l option was not specified and it isrequired.

User response: Specify the -l option. Use the -? optionto see the syntax for the command.

GLPKEY004E The specified directory, 'location', isnot a valid directory, does not exist, or isnot writable.

Explanation: The directory specified to create thedirectory key stash file in a location that is not valid, isnot writable, or is not accessible.

User response: Verify that the location where the keystash file is going to be created is a valid location onthe system and that you have access to write to thatlocation. The directory must exist.

GLPKEY005E The -e option is required.

Explanation: The -e option is required to specify theencryption seed for the directory key stash file.

User response: Specify the -e option or do not run thecommand in no-prompt mode to avoid this error. Usethe -? option to see the syntax for the command.

GLPKEY007E The encryption seed must containonly printable ISO-8859-1 ASCIIcharacters with values in the range of 33to 126 inclusive, and must be aminimum of 12 and a maximum of 1016characters in length.

Explanation: The program failed because anencryption seed that is not valid was specified.


GLPKEY008E The encryption salt must contain onlyprintable ISO-8859-1 ASCII characterswith values in the range of 33 to 126inclusive, and must be exactly 12characters in length.

Explanation: The program failed because anencryption salt value that is not valid was specified.


GLPKEY010E The directory key stash file file namecannot be created or was not writable.

Explanation: The program was unable to open orwrite to the file that will hold all of the backupinformation.


GLPKEY013E Failed to create directory key stashfile: 'filename'.

Explanation: The program failed to create the newdirectory key stash file.


GLPKEY014E An internal error occurred whilecreating the directory key stash file.

Explanation: An internal error occurred while creatingthe directory key stash file. This might have beencaused because the program ran out of memory.


GLPKEY015W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.


User response: Review the earlier error messages forinformation about the exact error.

GLPJBP056E • GLPKEY015W


GLPL2D002E ldif2db: entry ending on line linenumber in LDIF file filename does nothave a valid separator. The entry isignored.

Explanation: The entries in the LDIF file must beseparated by a blank line. The entry that ends at thespecified line number does not have a blank line as theseparator.

User response: Correct the error in the entry andreload the entries affected by this error in the LDIF file.

GLPL2D004E ldif2db: Cannot authenticate DN andpassword.

Explanation: The credentials entered were not valid.There was an error verifying the DN and password.


GLPL2D005E ldif2db failed on file_operation to file:file.

Explanation: The ldif2db utility failed on theoperation specified to the file indicated.

User response: Check the file indicated for theoperation which failed and correct the problem.

GLPL2D006E ldif2db cannot connect to the directorydatabase at this time.

Explanation: The ldif2db utility cannot be run whenother applications are attached to the directory instancedatabase.

User response: Make sure that IBM Security DirectoryServer is not running for this directory instance andthat there are no other applications attached to thedirectory database. Stop the IBM Security DirectoryServer for this instance and disconnect any otherapplications from the directory database and restartldif2db.

GLPL2D007E Database is set to read-only in theIBM Security Directory Serverconfiguration file. No entries can beloaded.

Explanation: The utility cannot add any entries to thedirectory database because the database is configuredto allow only reads, not updates.

User response: Change the LDAP server configurationto allow updates if there are entries to be loaded.

GLPL2D008E The attribute attribute name on line linenumber is not preceded by a dn.

Explanation: The LDIF file has an entry that does notbegin with a distinguished name (DN).

User response: Verify the name and format of thespecified LDIF file.

GLPL2D009E Importing the entry dn is notsupported by ldif2db.

Explanation: The specified DN is not in a name spaceto which entries can be imported. ldif2db only supportsimporting to RDBM-type backends.

User response: Specify a different DN under adifferent suffix that supports import.

GLPL2D010E Importing the entry dn is notsupported by ldif2db.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. Thespecified DN is not in a name space to which entriescan be imported. ldif2db only supports importing toRDBM-type backends.

User response: Specify a different DN under adifferent suffix that supports import.

GLPL2D011E The -i option is required.

Explanation: The -i option must be specified whenusing the ldif2db command. The -i option specifies theinput file.

User response: Specify the -i option. Use the -? optionto see the usage for the ldif2db command.

GLPL2D012E The -r option value must be 'yes' or'no'.

Explanation: An incorrect parameter was specified forthe -r option.

User response: Specify 'yes' or 'no' with the -r option.Use the -? option to see the usage for the ldif2dbcommand.

GLPL2D013E The -W option requires a file name tobe specified.

Explanation: The -W option was specified without afile name.

User response: Specify a filename with the -W option.Use the -? option to see the usage for the ldif2dbcommand.

GLPL2D014E Suffix entry has not been created forentry DN of entry.

Explanation: The entry cannot be added to thedirectory because there is no defined suffix for it. Toadd the entry, there must be a suffix defined that eithermatches the entry or is an ancestor of it.

User response: Correct the DN of the entry to be

GLPL2D002E • GLPL2D014E


imported or define an appropriate suffix and retry theldif2db request.

GLPL2D015E Cannot find input file filename.

Explanation: The running program cannot find thespecified input LDIF file.

User response: Verify the name of the input file andtry again.

GLPL2D016E An error occurred during RDBMbackend initialization, rc = error code.

Explanation: ldif2db or db2ldif encountered an errorwhile initializing the RDBM database backend.

User response: Make sure that a DB2 database hasbeen properly configured. If the problem cannot beresolved, contact IBM support.

GLPL2D017E ldif2db unable to run because ofinitialization error.

Explanation: ldif2db is unable to start because of aninitialization error.

User response: View earlier error message to see whyldif2db did not run. If no previous error message wasprinted, contact IBM support.

GLPL2D018E Input file contains incorrect data atline line number.

Explanation: The LDIF file has an entry that containsan incorrect line.

User response: Verify the name and format of thespecified LDIF file and try the request again.

GLPLMT002E Could not archive file file1 to file2 :file permissions.

Explanation: Archiving failed because the instanceowner does not have proper permissions to either thefile to be archived or the archive location.

User response: Set the proper permissions and restartthe log management tool.

GLPLMT003E Could not archive file file1 to file2 :not enough space.

Explanation: Archiving failed because of insufficientdisk space.

User response: Free some disk space and restart thelog management tool.

GLPLMT005E Value of attribute is invalid

Explanation: Value of the specified configurationattribute is not in the proper format.

User response: Correct the format and retry theoperation.

GLPLMT007E file will not be archived. attribute isnot set

Explanation: The file will not be archived becausevalue of the specified attribute is not set.

User response: Specify the value of the attribute.

GLPLMT013E Cannot contact CARS server hostnameat port

Explanation: The CARS server running at specifiedhostname and the port cannot be contacted.

User response: Check the status of the CARS server.

GLPLMT014E Error sending data to CARS serverhostname at port

Explanation: There is a problem in sending the data tothe CARS server running at specified hostname and theport.

User response: Check the status of the CARS server.

GLPLMT016E Invalid command line options. The -Ioption cannot be specified with -t -a and-p.

Explanation: -I option has been specified with one ormore of -t, -a and -p options.

User response: If log management capability is to bestarted for a server instance, then specify instance nameas the value for -I option and do not specify any otheroption. If the log management capability is alreadystarted and needs to be stopped, then specify -k optionalong with -I option. If log management capability foradmin tool's log file (idsadm.log) and log managementtool's log file (idslogmgmt.log) is to be started, thenspecify one or more of -t, -a and -p, but do not specifyany of -I and -k options.

GLPLMT017E The instance instancename specifieddoes not exist.

Explanation: The directory server instance for whichlog management capability is to be started or stoppeddoes not exist.

User response: Specify the correct name of directoryserver instance and retry the operation.

GLPL2D015E • GLPLMT017E


GLPLMT018E The instance instancename specifieddoes not match with the OS userrunning the Log Management tool.

Explanation: The OS user who is starting the logmanagement tool should match with the TDS instancename for which the log management is being started.

User response: Log in with the correct credentials andretry the operation.

GLPLMT019E Only root user can perform thisoperation.

Explanation: A non-root user is attempting to start thelog management for admin tool's log (idsadm.log) andlog management tool's log (idslogmgmt.log).

User response: Log in with the credentials of root userand retry the operation.

GLPLMT020E Invalid command line options. The -koption cannot be specified with -t -a and-p.

Explanation: -k option has been specified with one ormore of -t, -a and -p options.

User response: If the log management capability is tobe stopped for a directory server instance, then specify-k option along with -I option, and do not specify anyof the -t, -a and -p options. If log managementcapability for admin tool's log file (idsadm.log) and logmanagement tool's log file (idslogmgmt.log) is to bestarted, then specify one or more of -t, -a and -p, butdo not specify any of -I and -k options.

GLPLMT021E Unable to obtain port number forTDI server: Max retries exceeded.

Explanation: The log management tool is not able togenerate a port number for the TDI server.

User response: Retry running the tool. If the problempersists, contact IBM support.

GLPLMT022E Log Management capability for thisserver instance is already enabled.

Explanation: Attempted to start log managementcapability for a directory server instance, but the logmanagement capability is already started.

User response: No action is needed by the operator.

GLPLMT023E Log Management capability for thisserver instance is already disabled.

Explanation: Attempted to stop log managementcapability for a directory server instance, but the logmanagement capability is already stopped.

User response: No action is needed by the operator.

GLPLMT024E Unable to get TDI server's portnumber.

Explanation: Unable to get the TDI server's portnumber from solution.properties file.

User response: Retry the operation. If the problempersists, contact IBM support.

GLPLMT025E File file does not exist. Unable to getTDI server's port number.

Explanation: Unable to get the TDI server's portnumber because the solution.properties file does notexist.

User response: Retry the operation. If the problempersists, contact IBM support.

GLPLMT027E Invalid command line options. The -koption can be used only in conjunctionwith -I.

Explanation: -k option has been specified withoutspecifying -I option.

User response: For stopping the log managementcapability for a directory server instance, specify both -Iand -k options and retry the operation.

GLPMIG003E Specified a backup directory,'directory', that does not exist or is notaccessible.

Explanation: A backup directory that is not valid wasspecified for migrating an older directory serverinstance.

User response: Specify a directory that exists andcontains configuration and schema files that can bemigrated.

GLPMIG004E Cannot read V3.modifiedschema filein the 'directory' directory.

Explanation: The V3.modifiedschema file in the givendirectory cannot be read.

User response: Ensure that the V3.modifiedschema fileexists in the backup directory because the migrationutility will copy the file from that location.

GLPMIG005E Unable to modify V3.modifiedschemafile with information in 'filename' file.

Explanation: The V3.modifiedschema file cannot bemodified to have the OIDs listed in the given fileremoved.

User response: Ensure that the installation is completeand all files have been installed.

GLPLMT018E • GLPMIG005E


GLPMIG006E Unable to copy file 'filename1' to'filename2'.

Explanation: File cannot be copied.

User response: Ensure that the source file exists and isaccessible. Ensure that the target directory exists and isaccessible.

GLPMIG007E Unable to create file, 'filename'.

Explanation: File cannot be created.

User response: Ensure that the target directory existsand is accessible.

GLPMIG009E Unable to read file, 'file', in directory,'directory'.

Explanation: File cannot be read.

User response: Ensure that the target file exists and isreadable.

GLPMIG010E Unable to copy file 'filename1' to'filename2' file.

Explanation: File cannot be copied.

User response: Ensure that the source file exists and isaccessible. Ensure that the target directory exists and isaccessible.

GLPMIG011E Unable to read file, 'filename'.

Explanation: File cannot be read.

User response: Ensure that the target file exists and isreadable.

GLPMIG012E Unable to delete file, 'filename'.

Explanation: File cannot be deleted.

User response: Manual removal of the file might benecessary.

GLPMIG013E Unable to write file, 'filename', todirectory, 'directory'.

Explanation: File cannot be written.

User response: Ensure that the target directory existsand is accessible.

GLPMIG014E Unable to read schema files fromdirectory, 'directory'.

Explanation: Cannot read necessary schema files fromthe specified directory. Migration cannot continue.

User response: Ensure that the schema files are in thespecified directory.

GLPMIG015E Unable to write schema files todirectory, 'directory'.

Explanation: Schema files cannot be written to thespecified directory. Migration cannot continue.

User response: Ensure that the directory exists andcan be written to.

GLPMIG016E The location for the directory serverinstance 'instance name' cannot be found.

Explanation: Tried to migrate into a directory serverinstance, but cannot find the location for the directoryserver instance.

User response: Ensure that the directory serverinstance exists or has been successfully created duringmigration.

GLPMIG017E Unable to migrate the schema filesfrom version 'starting version' to version'ending version'.

Explanation: Tried to migrate a directory serverinstance and was unable to migrate the schema files tothe new version.

User response: Ensure that the backup files arepresent and the current version is correctly installed.

GLPMIG019E Files in backup directory, 'directory',are determined to be of version, 'version'.This is an unsupported migration path.

Explanation: Unable to migrate from the IBMDirectory Server version specified.

User response: Ensure that the correct version of thefiles are in the specified backup directory. Otherwise,this is not a supported migration path. Refer to theIBM Security Directory Server Installation andConfiguration Guide for supported migration paths.

GLPMIG020E Unable to locate file, 'filename', indirectory, 'directory'.

Explanation: A file necessary for migration cannot belocated in the backup directory.

User response: Ensure that all files are backed up andtry migration again. Refer to the IBM Security DirectoryServer Installation and Configuration Guide forinformation about the files needed for migration.

GLPMIG022E All necessary files for directory serverinstance, 'instance name', cannot be foundin directory, 'directory'.

Explanation: One or more of the base schema andconfiguration files for the directory server instancecannot be found in the location for that instance.

GLPMIG006E • GLPMIG022E


User response: Ensure that the directory serverinstance is successfully created. Refer to the IBMSecurity Directory Server Troubleshooting Guide forassistance with errors from the directory server instancecreation.

GLPMIG023W Migration has checked theV3.modifiedschema file against the baseschema files for any definitioncollisions. If any collisions are reported,these will be automatically resolved.

Explanation: If there are any schema definitions in theV3.modifiedschema file that collide with definitions inother included schema files, there will be errors atserver startup. These collisions will be automaticallyresolved by removing the conflicting schema definitionsfrom the other included schema files.

User response: If any collisions were reported duringmigration, no manual intervention is required to fixthem.

GLPMIG024E Unable to migrate the configurationfile from version 'starting version' toversion 'ending version'.

Explanation: Tried to migrate a directory serverinstance and was unable to migrate the configurationfile to the new version.

User response: Ensure that the configuration file fromthe previous version has been backed up and that thebacked up file is from a valid IBM Security DirectoryServer configuration. Verify that the current IBMSecurity Directory Server installation is complete.

GLPMIG026E Unable to read in configuration file,'filename'.

Explanation: Cannot read a required configurationfile. Migration cannot continue.

User response: Ensure that the given file exists and isreadable.

GLPMIG030W The files in the backup directory,'directory name', are determined to befrom version 3.2.2. Due to databasecompatibility issues, any databaseinformation contained in theconfiguration file will not be migrated.

Explanation: Compatibility issues exist betweenversion 3.2.2 databases and later versions. Databaseinformation and configuration from version 3.2.2cannot be preserved. This is detailed in the IBMSecurity Directory Server Installation and ConfigurationGuide.

User response: Refer to the IBM Security DirectoryServer Installation and Configuration Guide formigration steps from version 3.2.2.

GLPMIG034E The -u option must be specified forthe backup directory.

Explanation: The -u option was not specified and it isrequired.

User response: Specify the -u option. Use the -? optionto see the syntax for the command.

GLPMIG036W The log file name and pathinformation from the backed upconfiguration file will not be preservedby migration. Log file names and pathswill be updated to be specific for adirectory server instance.

Explanation: Because multiple directory serverinstances are supported on a system, the log files havebeen relocated to the log directory for a particulardirectory server instance. In some cases, the log filenames have also been changed.

User response: The path and name changes must benoted and reflected in any applications that mightdepend on them.

GLPMIG040E The DB2 database instance listed inthe backed up configuration file cannotbe found on the system.

Explanation: A DB2 database instance is listed in thebacked up configuration file, but cannot be found onthe system. The user cannot be prompted because thecommand was run in no-prompt mode, and processinghas stopped.

User response: Run the command without the -noption, or edit the backed up configuration file,removing the database information, and try again.

GLPMIG041E The database name listed in thebacked up configuration file cannot befound on the system.

Explanation: A database name is listed in the backedup configuration file, but cannot be found on thesystem. The user could not be prompted because thecommand was run in no-prompt mode, and processinghas stopped.

User response: Run the command without the -noption, or edit the backed up configuration file,removing the database information, and try again.

GLPMIG042E The changelog database name listedin the backed up configuration filecannot be found on the system.

Explanation: A changelog database name is listed inthe backed up configuration file, but cannot be foundon the system. The user cannot be prompted becausethe command was run in no-prompt mode, andprocessing has stopped.

GLPMIG023W • GLPMIG042E


User response: Run the command without the -noption, or edit the backed up configuration file, removethe database information, and try again.

GLPMIG043W Not all of the schema files includedin the configuration file have beenfound in the backup directory. Checkthe file names and paths for theincluded schema files before starting theserver.

Explanation: Not all of the schema files included inthe configuration file have been found in the backupdirectory. Check the file names and paths for theincluded schema files to ensure that they can be found.The server will not start successfully if all the filesspecified cannot be found on the system.

User response: Verify that the paths and names forthe included schema files are correct in theconfiguration file and that the files exist on the system.

GLPMIG044W The file, 'file name', is included in theconfiguration file but could not befound in the given backup directory,'directory'.

Explanation: The listed file is included in theconfiguration file, but was not found in the givenbackup directory. The configuration file must be editedto contain the correct path to the file. The server willnot start correctly if it cannot find all included schemafiles.

User response: Update the configuration file tocontain the correct path to the schema file.

GLPMIG046E The DB2 database instance, 'instancename', from the backed up configurationfile was found on the system. However,a matching user ID does not exist on theoperating system.

Explanation: The DB2 instance owner ID with thesame name as the specified DB2 instance name in thebacked up configuration file does not exist on thesystem.

User response: Create a user with the same name asthe specified DB2 instance name or remove the DB2instance information from the backed up configurationfile.

GLPMIG047W The database instance name ,'database instance name', is beingoverridden by the database instanceinformation from the backed upconfiguration file. The database instancename, 'database instance name', will beused instead.

Explanation: There was database instance information

in the backed up configuration file that will be usedinstead of the database instance name specified by theidsimigr command.

User response: If a database instance other than theone currently configured with the directory serverinstance is needed, unconfigure the current databaseinstance and reconfigure with the desired databaseinstance.

GLPMIG048W The schema files were not migratedand must be migrated manually.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. There wasa problem migrating the schema files, or schema filemigration is not supported. The schema files must bemigrated manually for migration to complete.

User response: Refer to the IBM Security DirectoryServer Installation and Configuration Guide forinstructions for manual schema file migration.

GLPMIG049E The backup directory must not bespecified for this migration scenario.

Explanation: A backup directory must not be specifiedwhile migrating from TDS 6.0 or higher versions tohigher versions for an existing TDS instance. Theschema and backup files will be taken from thestandard instance location.

User response: Correct and rerun the command.

GLPMIG051E Encryption key or encryption saltvalue must not be specified for thismigration scenario.

Explanation: An encryption key or encryption saltvalue must not be specified while migrating from TDS6.0 or higher versions to higher versions for an existingTDS instance. The existing keystash files will be takenfrom the standard instance location.

User response: Correct and rerun the command.

GLPMIG053E DB2 version specified in the file'prop_file_name' is not valid.

Explanation: An Invalid or NULL string was specifiedfor the DB2 version in the ldapdb.properties file. Avalid DB2 version string is of the form n1.n2.n3 wheren1, n2 and n3 are natural numbers.

User response: Correct the DB2 version string andrerun the command.

GLPMIG054E An error occurred while migratingschema and configuration files. Thefiles were successfully restored to theiroriginal state.

Explanation: If migration encounters an internal error

GLPMIG043W • GLPMIG054E


while migrating schema and configuration files, thefiles are restored to their original state before exiting.

User response: See the earlier error messages fordetails regarding the failure. Rectify the error andre-run migration.

GLPMIG055E An error occurred while migratingschema and configuration files. Thefiles could not be restored to theiroriginal state.

Explanation: Migration encountered an internal errorwhile migrating schema and configuration files andwas unable to restore the files to their original state.

User response: See the earlier error messages fordetails regarding the failure. Rectify the error andre-run migration.

GLPMIG057E Error while allocating memory.

Explanation: The migration code path is unable toallocate the necessary storage to continue processing.


GLPMIG058E Unable to migrate a RDBM instanceinto a PROXY only installationenvironment.

Explanation: Since a proxy only installationenvironment does not have necessary files to support aRDBM instance, this scenario is not allowed.

User response: Make sure you have installed theRDBM component of the TDS server to carry outmigaration of a backed-up RDBM instance.

GLPMIG059W Unable to start the task of DB2instance and database migration becauseof insufficient information.

Explanation: The name of the associated DB2 instanceand database should be available in the backed-upconfiguration file and these should also be presentphysically on the system where migration is beingattempted. In case any of the above information ismissing or could not be retrieved, the DB2 migrationtask is not attempted.

User response: Make sure the necessary information isavailable for the tool to proceed with the required task.

GLPMIG068E Unable to retrieve DB2 informationfrom the ldapdb.properties file.

Explanation: Either the ldapdb.properties file is notexisting, or is not accessible, or does not contain DB2installation path or DB2 version or both.

User response: Check that the file is existing and isaccessible. Also check if it has all the required DB2information.

GLPMIG074E Remote migration is detected on thesystem when the server instance alreadyexists.

Explanation: Remote migration is detected on thesystem when the server instance already exists. This isan invalid scenario because remote migration can beperformed only when server instance and the databaseinstance do not exist on the system.

User response: If remote migration is to be performed,delete the server instance and retry the command with-I, -u and -l options. Refer to the command referenceguide for details about these options.

GLPPFT001E Error while extracting information fromthe server configuration file fileName.

Explanation: A problem occurred in reading the serverconfiguration file for the specified instance.

User response: If a path to the server configurationfile was specified, verify that the correct path to a validconfiguration file was given. If no path was specified,verify that the indicated directory instance has a validconfiguration file.

GLPPFT002E Unable to find input configuration filefileName.

Explanation: The specified input property file was notfound.

User response: Provide the correct path and name ofthe tuning input property file.

GLPPFT004E Unable to find the status file fileName.

User response: The perftune_stat.log file must beavailable in the instance specific logs directory to runthe performance tool.

GLPPFT006E Incorrect combination of command lineoptions. Monitor switches can either beenabled or disabled.

User response: Rerun the command specifying onlyone of the options: -m to turn on the monitor switchesor -o to turn off the monitor switches.

GLPMIG055E • GLPPFT006E


GLPPFT018E The database instance name was notfound in the server configuration file.

Explanation: The database instance name(ibm-slapdDbInstance) was not found in the serverconfiguration file.

User response: A database must be configured for thedirectory instance prior to running the idsperftuneutility. Verify that a database instance is specified in theserver configuration file and retry the command.

GLPPFT019E An error result was returned from DB2.Reason: error details

User response: Correct the error condition specified asthe reason in the error message.

GLPPFT020E Syntax error found in the property filepfile line number: lineno

User response: Correct the error in the property filespecified in the error message.

GLPPFT021E Unable to bind to server.

User response: Provide the correct hostname and portnumber of the server.

GLPPFT022E Incorrect command line optionspecified.

User response: Refer to the command usage to getmore information.

GLPPFT023E Incorrect filtercache size specified.

User response: Enter a positive integer value for thefilter cache and then retry the operation.

GLPPFT025E Out of memory.

User response: Verify that the system has sufficientmemory.

GLPPFT026E An internal error occurred whilerunning the idsperftune command.

User response: Retry the operation. If the problempersists, contact IBM Software Support.

GLPPFT027E Value specified for DB2 parameterdbparam 'dbval' should be less than dbval .

GLPPFT029W Not enough data available to performthe advanced tuning operation.

Explanation: Advanced tuning is effective only afterthe directory has been used for some minimal period oftime.

User response: Retry the command without theadvanced tuning option or run the command with theadvanced tuning option after the directory has beenused for a longer period of time.

GLPPRT002E An internal error occurred whilerunning the idssetport command.

Explanation: An internal error occurred while runningidssetport command. This might have been causedbecause the program ran out of memory.


GLPPRT003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPPRT010E Failed to set port to 'port number' fordirectory server instance: 'instance name'.

Explanation: An internal error occurred while tryingto change the directory server port.


GLPPRT013E Failed to set secure port to 'portnumber' for directory server instance:'instance name'.

Explanation: An internal error occurred while tryingto change the directory server secure port.


GLPPRT016E Failed to set admin server port to 'portnumber' for directory server instance:'instance name'.

Explanation: An internal error occurred while tryingto change the admin server port.


GLPPFT018E • GLPPRT016E


GLPPRT019E Failed to set admin server secure portto 'port number' for directory serverinstance: 'instance name'.

Explanation: An internal error occurred while tryingto change the admin server secure port.


GLPPRT020E The port number specified by the -aoption must be an integer greater than 0and less than or equal to 65535.


User response: When using the -a option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPPRT021E The port number specified by the -coption must be an integer greater than 0and less than or equal to 65535.


User response: When using the -c option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPPRT022E The port number specified by the -poption must be an integer greater than 0and less than or equal to 65535.

Explanation: Specified a port number that is less than0 or greater than 65535 or was not a integer.

User response: When using the -p option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPPRT023E The port number specified by the -soption must be an integer greater than 0and less than or equal to 65535.


User response: When using the -s option, specify portnumbers that are greater than 0 and less than or equalto 65535.

GLPPRT024E The port numbers specified by the -a,-c, -p, and -s options must not matcheach other and must not cause a conflictbetween any ports in the configurationfile of the directory server instance.

Explanation: Specified ports that will conflict for thedirectory server instance.

User response: Specify unique port numbers.

GLPPRT025E Port 'port number' is already beingused by another directory serverinstance.

Explanation: Specified a port that is being used byanother directory server instance.

User response: Specify a port that is not being usedby any other directory server instance.

GLPPRT026E The -a, -c, -p, or -s option is requiredto specify a port to configure.

Explanation: The -a, -c, -p, or -s option was notspecified and it is required.

User response: Specify the -a, -c, -p, or -s option. Usethe -? option to see the syntax for the command.

GLPPRT027W The admin server for the directoryserver instance is currently running andmust be restarted for the change to theport to take effect.

Explanation: The admin server for the directory serverinstance was running when the port was reconfigured.Therefore, the admin server must be restarted in orderto bind to the new port.

User response: Stop the admin server of the directoryserver instance using the ibmdirctl command and thenstart the admin server again using the ibmdiradmcommand.

GLPPRT028W The admin server for the directoryserver instance is currently running andmust be restarted for the change to thesecure port to take effect.

Explanation: The admin server for the directory serverinstance was running when the secure port wasreconfigured. Therefore, the admin server must berestarted in order to bind to the new secure port.

User response: Stop the admin server of the directoryserver instance using the ibmdirctl command and thenstart the admin server again using the ibmdiradmcommand.

GLPPXY001E Unable to connect to back-end serverhost name on port port number. Verify thatthe back-end server is started.

Explanation: The proxy server was unable to connectto the specified back-end server for proxying data. Theprogram continues. Proxying to the specified servercannot continue.

GLPPRT019E • GLPPXY001E


User response: Verify that the back-end server isstarted, or contact the operator to start the back-endserver. Verify that the back-end server information iscorrect in the configuration file.

GLPPXY002E The URL ldap:// qualified URL isinvalid.

Explanation: The proxy server was unable to parsethe URL in the configuration file.

User response: Verify that the URL is typed correctly.Fix any errors.

GLPPXY004E Connection to back-end server hostname:port number is down.

Explanation: The LDAP Proxy Server's connectionwith the associated back-end server has beendisconnected. This message is printed for everyconnection opened to the back-end server.

User response: Verify that the network between theproxy server and back-end server is up. Verify that theback-end server is running, and also verify that anadministrator can bind to the back-end server.Connection cleanup enabled on a back-end server canalso cause connections from the proxy server to bedropped.

GLPPXY005E The bind method bind method specifiedunder config DN section is invalid.Reverting to SIMPLE bind.

Explanation: The specified bind method is not valid.

User response: The bind method specified in theconfiguration file must be one of KERBEROS, DIGESTor SIMPLE. Verify that the configuration file matchesone of these values.

GLPPXY006E The specified proxy connection poolsize number of connections in sectionconfig file DN is invalid.

Explanation: The specified pool size is not valid.

User response: Verify that the connection pool size inthe configuration file is greater than zero.

GLPPXY007E The specified server host name cannotbe contacted after attempts attempts.Server will be unavailable.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. Thespecified back-end server is not able to be contactedafter a certain number of attempts. No further attemptswill be made to contact it.

User response: Verify that the server is working.

GLPPXY008E The server host name:port does notsupport the required control OID.

Explanation: The specified back-end server does notsupport the control shown. This occurs if the server isrunning either an older version of IBM SecurityDirectory Server that does not support this control, orthe control has been disabled on the system.

User response: Verify that the configuration file pointsto a valid, running IBM Security Directory Server thatsupports this control and the control is enabled.

GLPPXY009E The server host name:port does notsupport the required capability OID.

Explanation: The specified back-end server does notsupport the capability shown. This occurs if the serveris running either an older version of IBM SecurityDirectory Server that does not support this capability,or the capability has been disabled on the system.

User response: Verify that the configuration file pointsto a valid, running IBM Security Directory Server thatsupports this capability and the capability is enabled.

GLPPXY010E The configuration file does notcontain any entries for back-end servers.No data will be available.

Explanation: No servers were defined in theconfiguration file for the proxy server to use. Withoutvalid server definitions, the proxy server cannot beused.

User response: Define your distributed topologycorrectly in the configuration file so that the proxyserver can function properly. See the IBM SecurityDirectory Server Administration Guide for moreinformation.

GLPPXY011E Proxy server is unable to bind to hosthost name using the credentials bind DNused.

Explanation: The credentials supplied for binding tothe back-end server are not valid.

User response: Verify that the credentials supplied forthe back-end server are valid, and that the credentialsspecify either the primary administrator, localadministrative group member, or global administrator.

GLPPXY012E The credentials bind DN used suppliedfor host host name are not administrative.

Explanation: The credentials supplied for binding tothe back-end server are not a local administrativegroup member, a global administrator, or the primaryadministrator.

User response: Verify that the credentials supplied forthe back-end server are valid, and that the credentials

GLPPXY002E • GLPPXY012E


specify the primary administrator, a localadministrative group member, or a globaladministrator.

GLPPXY013E There are no data partitions definedin the configuration file. No data willbe available.

Explanation: No data partitions were defined. As aresult, the proxy server cannot route any requests.

User response: Add data partitions that are valid.Refer to the IBM Security Directory ServerAdministration Guide for more information aboutsetting up a distributed topology.

GLPPXY014E The specified DN object DN is notheld in any of the proxied contexts.

Explanation: The DN of the referenced object is notheld in any namespace the proxy server has knowledgeof. The topology is probably defined improperly in theconfiguration file.

User response: Verify that the configuration filecontains a complete distributed topology, and that itmatches the expected deployment. See the IBM SecurityDirectory Server Administration Guide for moreinformation.

GLPPXY015E A referral was returned whileperforming an operation on object DN.

Explanation: While attempting to perform anoperation on the specified object, an LDAP referral wasreturned. This indicates that the topology settings inthe proxy server are incorrect.

User response: Verify that the configuration of theproxy server matches the distributed topology. Refer tothe IBM Security Directory Server AdministrationGuide for information about setting up a distributeddirectory.

GLPPXY016E The back-end server server ID is down.

Explanation: The specified back-end server iscurrently down, and is unable to be reached via thenetwork. Until the server is brought back online, norequests can be routed to that host.

User response: Verify that the back-end server isrunning and is reachable from the proxy server'snetwork.

GLPPXY017E Error error string occurred for back-endserver 'server ID': GSSAPI bind failedusing principal name 'dn'.

Explanation: The proxy server was trying to use theprincipal name to perform a GSSAPI bind with theback-end server, but failed.

User response: Verify that the proxy server is correctlyconfigured to accept Kerberos connections. Also verifythat the proxy server's principal name is in the globaladministration group.

GLPPXY018E The DN original entry DN cannot bemodified to new object DN.

Explanation: The DN specified cannot be changed tothe new DN because a move across back-end serverswould be required.

User response: Consider a different modrdn change,or delete and then add the entry back with the newDN.

GLPPXY019E Entry DN of entry specified on binddoes not exist.

Explanation: The bind failed because the DN specifieddid not correspond to an existing entry in the directory.The password cannot be verified if the entry is notfound.

User response: Correct the DN in the bind requestand try again.

GLPPXY020E Entry DN of entry specified oncompare does not exist.

Explanation: The compare failed because the DNspecified did not correspond to an existing entry in thedirectory. Attribute values cannot be compared if theentry is not found.

User response: Correct the DN in the compare requestand try again.

GLPPXY021E Entry DN of entry to be deleted doesnot exist.

Explanation: The delete failed because the DNspecified did not correspond to an existing entry in thedirectory.

User response: Correct the DN in the delete requestand try again.

GLPPXY022E Entry DN of entry to be modified doesnot exist.

Explanation: The modify failed because the DNspecified did not correspond to an existing entry in thedirectory.

User response: Correct the DN in the modify requestand try again.



GLPPXY023E Entry DN of entry to be renamed ormoved does not exist.

Explanation: The modifyDN failed because the DNspecified did not correspond to an existing entry in thedirectory.

User response: Correct the DN in the modifyDNrequest and try again.

GLPPXY024E The entry object DN already exists.

Explanation: The specified entry cannot be added tothe DIT because it already exists.

User response: Check the entry DN to ensure that it iscorrect, and retry.

GLPPXY025E The server server ID is down. Failingover to server server ID.

Explanation: The first specified server is no longerreachable via the network. As a result the proxy serveris retrying on the second server.

User response: Restart the server that is down. Verifythat connectivity has been established. If auto failbackis disabled, perform the resume role extendedoperation to restore the server.

GLPPXY026E The value of ibm-slapdProxyNumPartitions in entry configfile entry DN must be greater than zero.

Explanation: You attempted to create a distributedcontainer with 0 or less partitions.

User response: Modify the parameter to contain morethan 0 partitions.

GLPPXY027E The DN config entry DN specified forattribute attribute name in entry configentry DN is not valid.

Explanation: You attempted to place a DN that is notvalid as a value for an attribute in the configurationfile.

User response: Fill in a valid DN value for theattribute wherever it is found in the configuration file.

GLPPXY028E The DN back-end Server config entry DNis not located anywhere in theconfiguration file.

Explanation: You attempted to place a DN that is notvalid in the configuration file for referencing aback-end server section.

User response: Fill in a valid DN value for theibm-slapdProxybackendServerDn attribute wherever itis found in the configuration file.

GLPPXY029E The value of ibm-slapdProxyPartitionIndex in entry configfile entry DN must be greater than zero.

Explanation: You attempted to create a partition witha value less than one.

User response: Modify the parameter to contain anindex greater than zero.

GLPPXY030E The server host name:port does notsupport the required extension OID.

Explanation: The specified back-end server does notsupport the extended operation shown. This occurs ifthe server is running either an older release of IBMSecurity Directory Server that does not support thisextended operation, or the extended operation isdisabled.

User response: Verify that the configuration file pointsto a running version of IBM Security Directory Serverthat supports this extension and the extension isenabled.

GLPPXY031E All back-end servers in server groupDN are down.

Explanation: All back-end servers in the group arecurrently down, and are unable to be reached via thenetwork. If the -n option was not specified, the proxyserver will be started in configuration only mode.

User response: Verify that the back-end servers arerunning and are reachable from the proxy server'snetwork.

GLPPXY033E Internal transaction Tran Id againstback-end server ldap url was stopped.

Explanation: The specified transaction against thegiven back-end server was stopped. This is caused byan error either in the transaction or on the back-endserver. Note that the transaction ID printed out is notthe same as viewed by the client.

User response: View the corresponding back-endserver's logs.

GLPPXY036E All writable back-end servers withinthe partition name partition areunavailable. All write operations willfail until a writable back-end server isback online.

Explanation: All back-end servers that can acceptupdates are unavailable. The proxy is unable to processupdate requests for the partition.

User response: Ensure that all back-end servers areavailable. After back-end servers are available, requesta resume role extended operation, if auto failback isdisabled.



GLPPXY037E The primary write server host name:portfor the partition name partition is down.Failing over to server: host name:port.

Explanation: The primary write server is unavailable.


GLPPXY038E All back-end servers within thepartition name partition are unavailable.

Explanation: All back-end servers are unavailable. Theproxy server is unable to process any requests.


GLPPXY039E A partition number number that is notvalid is returned by the DN partitioningplugin for DN.

Explanation: A partition number that is not valid isreturned by the DN partition plugin.

User response: Ensure that the DN partition functionreturns a partition number that is greater than 0 butnot greater than the number of partitions passed to theDN partition plugin.

GLPPXY044E The back-end server server ID isunresponsive.

Explanation: The specified back-end server did notrespond to the health check within the configured timelimit. Until the server is responsive and restored to itsconfigured role, no requests can be routed to that host.

User response: Verify that the back-end server isrunning and responding. If this message is printed andthe back-end server is still performing at an acceptablelevel, consider changing the health check configuration.See the IBM Security Directory Server AdministrationGuide for more information.

GLPPXY046E The back-end server server ID isstarted in configuration only mode.

Explanation: The specified back-end server iscurrently running in configuration only mode. If the -noption was not specified and server groups are notdefined, the proxy server will be started inconfiguration only mode. If the specified back-endserver is a member of a server group and anotherserver in the group is up, the proxy server will startnormally. However if the specified back-end server isrestarted, the proxy server will treat that server as aread only server. This message is printed at start up.

User response: Verify that the back-end server isrunning correctly.

GLPPXY047E Unable to retrieve the server ID forthe back-end server server ID.

Explanation: Unable to retrieve the server ID for thespecified back-end server. If the -n option was notspecified, the proxy server will be started inconfiguration only mode.


GLPPXY048E The back-end server server ID iscurrently running in configuration onlymode.

Explanation: The specified back-end server iscurrently running in configuration only mode. As longas it is running in configuration only mode, no requestscan be routed to that host. This message is printedwhen health check detects that a back-end server isrunning in configuration only mode.

User response: Restart the back-end server in fullmode. If auto failback is disabled, issue a resume rolerequest to restore the back-end server.

GLPPXY049E There was an error while parsingrequired information from the back-endserver server ID.

Explanation: Unable to retrieve required informationfrom the specified back-end server. If the -n option wasnot specified, the proxy server will be started inconfiguration only mode.


GLPPXY050E Transaction request to back-end serverserver host name and port failed becausetoo many connections are currently inuse by transactions.

Explanation: Unable to send the transaction request tothe back-end server because too many connections arecurrently in use by transactions. The proxy server willalways reserve one back-end connection fornon-transactional operations.

User response: Decrease the number of allowedconcurrent transactions, or increase the number ofconnections to the back-end server and restart theproxy server.

GLPPXY051E Request to back-end server server hostname and port failed because all theconnections are currently in use bytransactions.



Explanation: Unable to send the request to theback-end server because all the connections arecurrently in use by transactions.

User response: Decrease the number of allowedconcurrent transactions, or increase the number ofconnections to the back-end server and restart theproxy server.

GLPPXY052W More than one attribute: attribute typedefined in the entry: entry DN. Only thefirst attribute value attribute value will beused.

Explanation: The configuration file contains more thanone attribute value for the attribute. The proxy serverwill only honor the first attribute value.

User response: Remove the additional attribute valuesand verify the configuration.

GLPPXY053E Failed to add back-end server storedin entry: entry DN.

Explanation: While processing the configuration file,there was an error with the entry specified in themessage. The back-end server defined in that entrycannot be used until the error is corrected.

User response: Check the entry in the configurationfile and correct any errors.

GLPPXY064W All writable back-end servers withintier previous tier number of partitionpartition name are unavailable. Failingover to tier next tier number.

Explanation: All back-end servers that can acceptupdates are unavailable in the current tier. The proxyserver will failover to the next tier with available writeservers.

User response: Ensure that all back-end servers areavailable within the given tier. After back-end serversare available, request a resume role extended operationmanually if auto failback is disabled. Otherwise, theproxy server will do an auto failback.

GLPPXY067E The specified proxy status intervalstatus interval in section config file dn isinvalid.

Explanation: The specified proxy status interval is notvalid.

User response: Verify that the proxy status interval inthe configuration file is not negative. A value of zero isallowed to disable health check.

GLPPXY074E Unsupported scope specified onibm-allMembers search. Only base levelibm-allMembers searches are allowed.

Explanation: As ibm-allMembers search involves a lotof processing it is only supported for base scope ondistributed directory.

User response: Try ibm-allMembers search with basescope.

GLPPXY077E The proxy server configuration ismissing the required split container forcn=ibmpolicies.

Explanation: Split container for cn=ibmpolicies ismandatory for proxy server to start.

User response: Add split container and splits forcn=ibmpolicies.

GLPPXY080E Unsupported scope specified onibm-allGroups search. Only base levelibm-allGroups searches are allowed.

Explanation: As ibm-allGroups search involves a lot ofprocessing it is only supported for base scope ondistributed directory.

User response: Try ibm-allGroups search with basescope.

GLPPXY081E Unsupported NULL based subtreesearch requested.

Explanation: NULL based subtree searches are notsupported in a distributed directory.

User response: Modify the search request to specify abase.

GLPPXY082E Unsupported attribute attribute type oncompare request.

Explanation: Compare requests on some attributes arenot supported in a distributed directory.

User response: Modify the compare request to specifya different attribute.

GLPPXY083E Update operations are not allowed onthe split point entry entry DN.

Explanation: Update operations including add,modify, delete, and rename on the split point entry arenot supported in a distributed directory.

User response: The update request should beperformed directly on the back-end server.

GLPPXY052W • GLPPXY083E


GLPPXY084W The local administrator entry DN hasrequested the schema updates. Theupdates will not be propagated to thebackend servers.

Explanation: The updates are performed only in theschema files of the proxy server and are not propagatedto the backend servers if requested by a localadministrator.

User response: If schema updates are to bepropagated to the backend servers, use the GlobalAdministrative Group Member credentials to performthem.

GLPRDB001E Error code error_code from function:SQL function error message .

Explanation: The LDAP server received an error whenperforming DB2 operations. The request failed. Theremight be an additional message with information aboutSQL return codes.

User response: See the file named as the attributevalue for the ibm-slapdCLIErrors attribute in thedirectory server instance configuration for details aboutthe error and corrective actions.

GLPRDB002W utility program name: number addedentries have been successfully addedout of number attempted attempted.

Explanation: The utility successfully added thespecified number of entries to the directory.

User response: See the file named as the attributevalue for the ibm-slapdErrors attribute in the serverconfiguration for details about the errors if the numberadded is less than the number to be added.

GLPRDB003E database name parameter is missingfrom LDAP directory configuration file.

Explanation: The directory server configuration file ismissing the database name.

User response: Run one of the configuration utilitiesto configure the directory server instance and try again.

GLPRDB004E The directory server is unable toconnect to the database.

Explanation: The directory server cannot connect tothe database used to store the directory data.

User response: Make sure the database instance anddatabase named in the directory server configurationfile exist and that the database instance can be started.Verify that the user ID and password in theconfiguration are correct.

GLPRDB005E DN does not have permission to allparts of the filter or the RDN. Thesearch operation cannot return anyresults.

Explanation: The LDAP server cannot return therequested data because the requester is not permittedto read all of the data requested.

User response: Modify the request and try again. Ifaccess to the data is needed, contact the directoryserver administrator.

GLPRDB006E Only one attribute-value pair can becompared at a time.

Explanation: The LDAP server cannot complete therequest because more than one attribute-value pair isbeing compared in the request.

User response: Modify the request and try again.

GLPRDB007E When adding the ownerPropagatefield, the entryOwner field must also beadded.

Explanation: The LDAP server cannot complete therequest because the request is attempting to add theownerPropagate flag without also adding theentryOwner field.


GLPRDB008E When adding the aclPropagate field,the aclEntry field must also be added.

Explanation: The LDAP server cannot complete therequest because the request is attempting to add theaclPropagate flag without also adding the aclEntryfield.


GLPRDB009E An explicit ACL must be set in orderto change or delete this attribute value.

Explanation: The LDAP server cannot complete therequest because an explicit ACL does not exist.


GLPRDB010E An explicit owner must be set inorder to change or delete this attributevalue.

Explanation: The LDAP server cannot complete therequest because an explicit owner does not exist.


GLPPXY084W • GLPRDB010E


GLPRDB011E Cannot delete and change the sameattribute.

Explanation: The LDAP server cannot complete therequest because the request is attempting to both deleteand modify the same attribute.


GLPRDB012E Starting with the IBM TivoliDirectory Server 6.1 release this messageis deprecated.

Explanation: The LDAP server cannot complete therequest because the permissions specified for the objectare not correct.

GLPRDB013E The DnType type value specified inthe aclentry is not valid. Valid valuesare: 'access-id', 'group', and 'role'.

Explanation: The LDAP server cannot complete therequest because the DnType specified is not correct.

User response: Correct the request and try again.

GLPRDB014E The prefix prefix value specified for apermission set is not valid. Validprefixes are: 'normal', 'critical','sensitive', 'system', 'restricted' and'object'.

Explanation: The LDAP server cannot complete therequest because the prefix specified for the permissionsis not correct.

User response: Correct the request and try again.

GLPRDB015E DB2 codepage cannot be determined.

Explanation: The directory server instance cannotdetermine the codepage used by the DB2 database.Database access will not be available.

User response: 1. Check the db2cli.log file and correctany reported errors. 2. If there are no reported errors,issue the following DB2 command: db2 get db cfg for<database name>. 3. Look for the database code pagevalue in the output and set the value to theenvironment variable DB2CP. 4. Restart the ibmslapdserver.

GLPRDB016E DB2 codepage codepage number is notsupported by the LDAP server.

Explanation: The LDAP server cannot support thecodepage used by the DB2 database. Database accesswill not be available.

User response: Use the idscfgdb or idsxcfg tools tocreate the database. You can specify either UTF-8 orlocal codepage at database creation time. UTF-8database supports a wide range of characters and

provides better performance.

GLPRDB017E XPG4 codepage codepage numbercannot be opened by LDAP server: errormessage.

Explanation: There is no mapping between thecodepage used by the DB2 database and the XPG4library for translation. Database access will not beavailable.

User response: Use the idscfgdb or idsxcfg tools tocreate the database. You can specify either UTF-8 orlocal codepage at database creation time. UTF-8database supports a wide range of characters andprovides better performance.

GLPRDB018E Incoming data cannot be fullytranslated to DB2 codepage: codepagenumber.

Explanation: There is no mapping from the client datato the DB2 database codepage. The client data must beUTF-8 encoded when sent. If the database is using alocal codepage, it is possible that valid UTF-8characters cannot be properly translated into the localcodepage.

User response: 1. Identify and correct the clientapplication that issued the request if the data is notproperly encoded in UTF-8. 2. Create the databaseusing UTF-8 database if wider-range character supportis desired.

GLPRDB019E Entry entry DN cannot be modified.

Explanation: The LDAP server cannot complete therequest because the original entry contains an objectclass that indicates that it contains Enterprise IdentityMapping (EIM) information. When an entry containsEIM information, the EIM object classes cannot beentirely removed from the entry.

User response: Modify the request so that not all EIMobject classes are being removed from the entry and trythe request again.

GLPRDB020E Entry entry DN cannot be modified.

Explanation: The LDAP server cannot complete therequest because the original entry does not use anobject class that indicates that it contains EnterpriseIdentity Mapping (EIM) information. However, anobject class that indicates that the entry will containEIM information was specified on the modify request.If an entry originally does not specify an EIM objectclass, an EIM object class cannot be added to the entryat a later time.

User response: Modify the request so that no EIMobject classes are being added to the entry and try therequest again.

GLPRDB011E • GLPRDB020E


GLPRDB021E The length length specified forattribute attribute exceeds the maximumschema length.

Explanation: The length specified for the givenattribute exceeds the maximum schema length.

User response: Specify a smaller length for the givenattribute. The maximum version 3 schema length is32768.

GLPRDB022E Specified DB2 column length lengthfor attribute attribute must match thelength defined for the attribute syntax.

Explanation: The DB2 column length defined for anattribute must match the length defined for theattribute syntax.

User response: Ensure that the DB2 column lengthdefined for the attribute matches the length defined forthe attribute syntax.

GLPRDB023W The server is not caching attributesfor search filter resolution because notenough memory was configured forattribute caching.

Explanation: Not enough memory has beenconfigured for caching any attributes. All caching ofattributes has been removed. Searches will continue tooperate correctly, but their performance might not be asfast as it would be if attribute caches were used.

User response: Reconfigure the server to increase theamount of memory for attribute caching.

GLPRDB024E The server cannot load attributecaching because an internal erroroccurred.

Explanation: The server cannot load attribute cachingbecause of an internal error. Searches will continue tooperate correctly, but their performance might not be asfast as it would be if attribute caches were used.

User response: Restart the server. If the errorcontinues, contact IBM Software Support.

GLPRDB025E The server cannot cache theobjectclass attribute when theenvironment variable OC_ALIAS is setto Yes.


GLPRDB026E The server cannot cache attributeattribute name for search filter resolutionbecause it is not a supported attribute.

Explanation: The reported attribute cannot be cached

for filter resolution because it is an operational attributeor an attribute not supported to be cached, or theattribute does not exist in the schema. Searches willcontinue to operate correctly.

User response: To avoid this error message in thefuture, reconfigure the server to so that this attribute isnot configured as a cached attribute.

GLPRDB027E The server cannot load all configuredattribute caches for search filterresolution because not enough memorywas configured to hold all configuredattribute caches.

Explanation: Caches were not created for all attributesconfigured because not enough memory wasconfigured to hold the caches. Loading of the attributecaches has stopped. Searches will continue to operatecorrectly, but their performance might be degradeduntil the server is reconfigured to increase the amountof memory for attribute caching.

User response: To see which attributes have beencached, view the monitor information. If additionalattribute caches are desired, reconfigure the server toincrease the amount of memory for attribute caching.

GLPRDB028E The server deleted the cache forattribute attribute_name for search filterresolution because not enough memorywas configured to hold all attributecaches configured.

Explanation: The cache for the specified attribute forfilter resolution was deleted because not enoughmemory has been configured to hold all the attributecaches. Searches will continue to operate correctly, buttheir performance might not be as fast as it would be ifattribute caches existed as configured.

User response: Reconfigure the server to increase theamount of memory for attribute caching.

GLPRDB029E The server deleted the cache forattribute attribute_name for search filterresolution because an error occurred thatwould have caused the cache to becomecorrupted.

Explanation: The cache for the listed attribute or filterresolution was deleted because an error occurred thatwould have caused the corruption of the cache.Searches will continue to operate correctly, but theirperformance might not be as fast as it would be ifattribute caches existed as configured.

User response: Restart the server or reconfigure theattribute cache values. The attribute cache values canbe reconfigured using the IBM Security DirectoryServer Web Administration Tool.



GLPRDB030E Migration of the REF attribute tablefailed.

Explanation: Failed to change the column length ofthe REF column in the REF attribute table. This can bedue to failure of any number of DB2 operations. Checkthe server and db2cli error logs. Searches shouldcontinue to operate correctly, but if an attempt is madeto add, delete, modify, or modrdn a ref attribute, thebehavior is undefined.

Administrator response: Contact IBM SoftwareSupport for assistance.

GLPRDB031E Failed to drop the unique constraintfor attribute attribute_name.

Explanation: The server failed to drop the uniqueconstraint for the attribute. This problem might be dueto the constraint not being defined or might be causedby an internal error.

User response: Do not try to remove the attributefrom the list of attributes with unique values.

GLPRDB032E Failed to add the unique constraintfor attribute attribute_name.

Explanation: Failed to add the unique constraint forthe reported attribute. This problem is caused byduplicate attribute values or by an internal error.

User response: Do not try to add the reportedattribute to the list of attributes with unique values. Ifunique values are desired for this attribute, you mustfirst remove the duplicate values from the existingentries and then add this attribute to the list ofattributes that must have unique values.

GLPRDB033E The server cannot support languagetags for attribute attribute_name.

Explanation: The server cannot add the language tagsto the internal table for the attribute because the tablewill become too large. This entry will not be added ormodified until the language tags are removed from theoperation for the attribute.

Programmer response: Remove the language tagsfrom the attribute and try the request again.

GLPRDB034E Because attribute attribute name is notdefined in the schema, the uniqueattributes feature cannot be supportedfor this attribute.

Explanation: The attribute does not exist in theschema and therefore cannot be defined as unique.

User response: Remove this attribute from the list ofattributes requiring unique values or add this attributeto the schema and restart the server.

GLPRDB035E Because attribute attribute name isdefined to allow language tags, theunique attributes feature cannot besupported for this attribute.

Explanation: Attributes cannot be defined as uniqueand use language tags.

User response: Remove this attribute from the list ofattributes requiring unique values.

GLPRDB036E The unique attributes feature doesnot support attribute attribute_name. Thelist of attributes the unique attributesfeature does not support includes, but isnot limited to, the following:operational attributes, configurationattributes, binary attributes, and the cnand objectclass attributes.

Explanation: Specified to make an attribute uniquethat is not supported as a unique attribute.


GLPRDB037E The unique attributes feature doesnot support attribute attribute_name. Thelist of attributes the unique attributesfeature does not support includes, but isnot limited to, the following:operational attributes, configurationattributes, binary attributes, and theobjectclass attribute.

Explanation: Specified to make an attribute uniquethat is not supported as a unique attribute.


GLPRDB038E utility_program_name is unable toconnect to the database.

Explanation: The named program cannot connect tothe database used to store the directory data.

User response: Make sure the database instance anddatabase named in the LDAP server configuration fileexist and that the database instance can be started.Verify that the user ID and password in theconfiguration are correct.

GLPRDB039E database_userid parameter is missingfrom LDAP directory configuration file.

Explanation: The LDAP directory configuration file ismissing the database user ID.

User response: Run the idscfgdb or idsxcfg commandagain to properly reconfigure a database for the givendirectory server instance.



GLPRDB040E database_user_password parameter ismissing from LDAP directoryconfiguration file.

Explanation: The LDAP directory configuration file ismissing the password for the database user ID.

User response: Run the idscfgdb or idsxcfg commandagain to properly reconfigure a database for the givendirectory server instance.

GLPRDB041E When adding the ownerPropagatefield, the entryOwner field must also beadded.

Explanation: The LDAP server cannot complete therequest because the request is attempting to add theownerPropagate flag without also adding theentryOwner field.


GLPRDB042E When deleting the entryOwner field,the ownerPropagate field must also bedeleted.

Explanation: The LDAP server cannot complete therequest because the request is attempting to delete theentryOwner flag without also deleting theownerPropagate field.


GLPRDB043E When adding the aclPropagate field,the aclEntry field must also be added.

Explanation: The LDAP server cannot complete therequest because the request is attempting to add theaclPropagate flag without also adding the aclEntryfield.


GLPRDB044E When deleting the aclEntry field, theaclPropagate field must also be deleted.

Explanation: The LDAP server cannot complete therequest because the request is attempting to delete theaclEntry flag without also deleting the aclPropagatefield.


GLPRDB045E Unable to connect to database;program terminating.

Explanation: All database connections have beenterminated. The directory server must be shut down.

User response: Make sure that database connectionsare not being terminated by other applications or users.Restart the directory server.

GLPRDB046E Unable to connect to database;program terminating.

Explanation: All database connections have beenterminated. The directory server must be shut down.

User response: Make sure that database connectionsare not being terminated by other applications or users.Restart the directory server.

GLPRDB047E Moving entry 'entry DN' to suffixsuffix is not allowed.

Explanation: Moving an entry to the specified suffixusing the modify DN operation is not allowed by theserver.

User response: Specify a different suffix to move theentry under.

GLPRDB048E Moving entry 'entry DN' is notallowed.

Explanation: This entry has special meaning to theserver and is not allowed to be renamed using themodify DN operation.

User response: Specify a different entry to move.

GLPRDB049E Moving entry to 'new entry DN' is notallowed.

Explanation: This entry has special meaning to theserver and is not allowed to be the result of a modifyDN operation.

User response: Specify a different DN to rename theentry to.

GLPRDB050E Attribute attribute name was not foundin the schema definition.

Explanation: The specified attribute was not found inthe schema definitions.

User response: Add the definition of the attribute tothe schema and retry the operation, or correct theattribute name in the request and retry.

GLPRDB051E Entry DN of entry already exists.

Explanation: The request to add an entry failedbecause an entry already exists in the directory withthe specified distinguished name.

User response: Choose a unique name for the entryand retry the operation.



GLPRDB052E Entry DN of entry already exists.

Explanation: The request to rename an entry failedbecause an entry already exists in the directory withthe specified distinguished name.

User response: Choose a unique name for the entryand retry the operation.

GLPRDB053E Entry DN of entry violates the schemadefinition.

Explanation: The add failed because the new entryviolates the rules defined in the directory schema.Verify that the object class(es) and attributes includedin the new entry are appropriate based on the currentlydefined directory schema.

User response: Either change the directory schemadefinitions to allow the desired new entry, or changethe request to fit the schema. Then try adding the entryagain.

GLPRDB054E Entry DN of entry violates the schemadefinition.

Explanation: The modify failed because the new entrywould violate the rules defined in the directoryschema. Verify that the object class(es) and attributesincluded in the modified entry are appropriate basedon the currently defined directory schema.

User response: Either change the directory schemadefinitions to allow the desired new entry content, orchange the request to fit the schema. Then trymodifying the entry again.

GLPRDB055E Parent entry does not exist for entryDN of entry.

Explanation: Moving an entry failed because thespecified parent entry does not exist.

User response: Correct the new parent name specifiedin the moddn operation, or add an appropriate parententry, and then retry.


Explanation: ACL checking failed for the operationbecause the parent of the specified entry does not exist.

User response: Correct the name of the entryspecified, or add an appropriate parent entry, and thenretry.


Explanation: Adding an entry failed because thespecified parent entry does not exist.

User response: Correct the name of the entry to beadded, or add an appropriate parent entry, and thenretry.

GLPRDB058E Entry size size is greater than themaximum size supported (max size).

Explanation: The requested operation cannot completebecause it would result in an entry that exceeds themaximum supported size.

User response: Reduce the size of the data included inthe entry.

GLPRDB059E An SQL call failed: SQL routine name.

Explanation: An unexpected exception occurredduring SQL processing.

User response: View the db2cli.log file to look forcorresponding DB2 error messages. Ensure that DB2 isoperating correctly.

GLPRDB060E Entry DN of entry specified on binddoes not exist.

Explanation: The bind failed because the DN specifieddid not correspond to an existing entry in the directory.The password cannot be verified if the entry is notfound.

User response: Correct the DN in the bind requestand try again.

GLPRDB061E Entry DN of entry specified oncompare does not exist.

Explanation: The compare failed because the DNspecified did not correspond to an existing entry in thedirectory. Attribute values cannot be compared if theentry is not found.

User response: Correct the DN in the compare requestand try again.

GLPRDB062E Entry DN of entry to be deleted doesnot exist.

Explanation: The delete failed because the DNspecified did not correspond to an existing entry in thedirectory.

User response: Correct the DN in the delete requestand try again.

GLPRDB063E Entry DN of entry to be modified doesnot exist.

Explanation: The modify failed because the DNspecified did not correspond to an existing entry in thedirectory.



User response: Correct the DN in the modify requestand try again.

GLPRDB064E Entry DN of entry to be renamed ormoved does not exist.

Explanation: The modifyDN failed because the DNspecified did not correspond to an existing entry in thedirectory.

User response: Correct the DN in the modifyDNrequest and try again.

GLPRDB065E The new superior DN DN of entry thatthe entry was to be moved to does notexist.

Explanation: The modifyDN failed because the DNspecified as the new parent entry did not correspond toan existing entry in the directory, and there is no suffixto match the new entry DN.

User response: Correct the DN in the modifyDNrequest and try again. If the intent was to move theentry to a new suffix, the suffix must be added to theserver configuration before the entry can be movedthere.

GLPRDB066E The attribute attribute name with valueattribute value already exists.

Explanation: The specified value cannot be added tothe attribute because it already exists.

User response: Check the entry content to ensure thatit is correct, and if so, ignore this error. Otherwise,correct the modify request and try again.

GLPRDB067E Entry DN of entry does not containattribute attribute name.

Explanation: The attribute to be deleted was notfound in the specified entry.


GLPRDB068E Entry DN of entry does not containattribute attribute name with valueattribute value.

Explanation: The attribute value to be deleted was notfound in the specified entry.


GLPRDB069E Attribute attribute name has amaximum value length of max length.Current attribute value is of lengthcurrent length.

Explanation: The attribute value to be added has alength greater than the maximum length defined in theschema.

User response: Retry the operation with a shortervalue.

GLPRDB070E DB2CLI error, SQL data is: nativereturn code=DB2 rc, SQL state=DB2 SQLstate, SQL message=message text.

Explanation: The directory server received an errorwhile performing DB2 operations. The information inthe messages is the data available from DB2 at the timeof the error.

User response: Check the db2cli.log file for relatederror messages. Evaluate and resolve the DB2 problemwith the information provided. If the problem cannotbe resolved, contact IBM Software Support.

GLPRDB071E An error occurred during backendidentifier backend initialization, rc =return code.

Explanation: The directory server encountered anerror while initializing a backend.

User response: If the error refers to a databasebackend, make sure that a DB2 database has beenproperly configured. If the problem cannot be resolved,contact IBM Software Support.

GLPRDB072E Distinguished name DN might havepartial access.

Explanation: The directory server encountered anerror when obtaining the group memberships for thespecified distinguished name. The access granted mightbe incomplete.

User response: Examine the ACL and group entriesfor the specified DN and correct any malformedentries.

GLPRDB073E Starting with the IBM TivoliDirectory Server 6.1 release this messageis deprecated.

Explanation: The LDAP server cannot complete therequest because the access class permissions specifiedare not correct.



GLPRDB074E Replication conflict adding DNoccurred. The entry was replaced.

Explanation: An entry was added to this server thathad been added previously by another master server.The entry on this server was older; therefore, the entrywas overwritten by the new entry.

User response: The contents of the directory were notthe same on all servers. Check that no updates havebeen lost by comparing the contents of the servers inthe replication topology.

GLPRDB075E Replication conflict: an add of entryDN was rejected because it had an oldertimestamp.

Explanation: An attempt was made to add an entry tothis server that had been added previously. The entryon this server was more recent; therefore, the entry wasnot overwritten by the new entry.

User response: The contents of the directory were notthe same on all servers. Check that no updates havebeen lost by comparing the contents of the servers inthe replication topology.

GLPRDB076E Specified attribute length attributelength for attribute attribute name mustnot be less than the length currentlydefined for the attribute.

Explanation: Reducing the attribute size is notsupported.

User response: Retry the operation with a value thatis greater than the attribute length currently defined inthe schema.

GLPRDB077E Modifying attribute table name,column name, or syntax is not allowedwhen the attribute attribute name alreadycontains data.

Explanation: Attribute table name, column name, orsyntax can be changed only when the attribute table isempty or has not been created.

User response: Export the directory data into an LDIFfile, unconfigure the database, modify the attribute sizeinformation in the schema file, configure the database,and import the data into the database. Otherwise, nofurther action can be taken.

GLPRDB078E Specified attribute length attributelength for attribute attribute name causesthe total size of columns to exceed themaximum record size.

Explanation: Altering the column cannot cause thetotal byte count of all columns to exceed the maximumrecord size.

User response: Retry the operation with a value thatwill not cause the total byte count of all columns toexceed the maximum record size.

GLPRDB079W Attribute table name attribute name islonger than 16 characters. The currenttable name current table name for thisattribute is being renamed to table name.

Explanation: In previous releases, if an attribute tablename was longer than 16 bytes, the table name wastruncated to 16 bytes. Starting with IBM TivoliDirectory Server 6.0, longer attribute table names up to128 bytes are supported. When the IBM TivoliDirectory Server 6.0 or later server is started for thefirst time, any attribute table whose name wastruncated to 16 bytes will be renamed to the longertable name.

User response: No further action is required.

GLPRDB080E To increase the maximum length ofattribute attribute name, its data typemust be either VARCHAR,VARGRAPHIC or LONG VARCHAR.

Explanation: To increase the size of an attribute, theattribute data type must be either VARCHAR,VARGRAPHIC, or LONG VARCHAR. These are theonly data types of a column that can be increased usingDB2.

User response: Export the directory data into an LDIFfile, unconfigure the database, modify the attribute sizeinformation in the schema file, configure the database,and import the data into the database. Otherwise, nofurther action can be taken.

GLPRDB081E Transaction log is either full orrunning out of disk space. The currentdatabase operation will be rolled backto the last committed state.


GLPRDB082E The request to increase the size ofattribute attribute name was notcompleted successfully due to failedDB2 operation(s). A partial change(creation of the temporary tabletemporary table name) has been committedin the database. Issue the modifyrequest again or remove the temporarytable temporary table name from yourdatabase.

Explanation: During the creation of a new attributetable with increased attribute size, if any of theoperations after creating the temporary table fails, thedatabase will be rolled back to the last committed state.



However, the temporary table must be removedmanually.

User response: Issue the command again. Otherwise,remove the temporary table manually to recover thestate of the database.

GLPRDB083E The server cannot be started becausea newer version of the IBM SecurityDirectory Server is already installed andconfigured on the system.

Explanation: Before starting the internal datamigration process at server startup, it has beendetermined that a newer version of server is alreadyinstalled and configured on the system; therefore, theserver cannot be started.

User response: Contact IBM Software Support.

GLPRDB084E Failed to complete the internal datamigration.

Explanation: The directory server instance cannot bestarted because problems were encountered during theinternal data migration process at server startup.

User response: Check the log files for errors, resolvethe issues, and restart the server. The migration processwill be resumed when the server is being started.

GLPRDB085E Failed to complete the internal datamigration for long table names.

Explanation: The server cannot be started becauseproblems were encountered during the migrationprocess for renaming attribute tables to have longernames.


GLPRDB086E Failed to rename the attribute tabletable name to new table name.

Explanation: The server cannot be started becauseproblems were encountered during the migrationprocess for renaming attribute tables to have longernames.


GLPRDB087E Failed to rename the attribute indexindex name to new index name.

Explanation: The server cannot be started becauseproblems were encountered during the migrationprocess for renaming attribute indexes.

User response: Check the log files for errors, resolve

the issues, and restart the server. The migration processwill be resumed when the server is being started.

GLPRDB088E Entry DN of entry contains anincorrect ACL definition.

Explanation: The request to add or update the entryfailed because the request contained an ACL definitionthat violated the ACL syntax.

User response: Correct the ACL definition in the entryand retry the operation.

GLPRDB089E The directory server is unable to logon as the database administrator.

Explanation: The directory server cannot log on as thedatabase administrator defined in the directory serverconfiguration file.

User response: Make sure the database instance in thedirectory server configuration file exists. Verify that theuser ID and password in the configuration are correct.

GLPRDB090E Failed to complete the internal datamigration for objectclass index.


GLPRDB091W Attribute attribute name is notindexed but is used in searches numbertimes.

Explanation: Attributes used in search filters or searchsort keys generally must be indexed to improveperformance.

User response: Determine whether the attribute isfrequently used in searches. If it is, create an index onthe attribute.

GLPRDB092E Modifications to object classibm-pwdGroupAndIndividualPolicies orattribute ibm-pwdGroupAndIndividualEnabled areallowed only for the global passwordpolicy entry.

Explanation: Object class ibm-pwdGroupAndIndividualPolicies and attributeibm-pwdGroupAndIndividaulEnabled can be modifiedonly for the global password policy entry.

User response: Make sure the modification of theobjectclass or attribute is for the global password policyentry (cn=pwdPolicy,cn=IBMpolicies).



GLPRDB093E The specified access class access classpermission, invalid permission, is notvalid. Valid permissions are validpermissions.

Explanation: The LDAP server cannot complete therequest because the access class permissions specifiedare not correct.

User response: Correct the permissions in the requestand try again.

GLPRDB098E Data conversion for encryptedattribute attribute name failed.

Explanation: If the attribute specified to be converteddoes not exist in the schema, is not specified to beencrypted in the schema, or is specified to be encryptedin a format that is not supported, the conversion willfail. The conversion will also fail if an internal erroroccurred in the server.

User response: If the attribute does not exist in theschema, is not specified to be encrypted in the schema,or is specified to be encrypted in a format that is notsupported, modify the schema as required to fix theproblem and restart the server. Check the log files forany additional errors.

GLPRDB101W Encrypted attribute attribute_namecannot be made unique.

Explanation: The unique attribute feature does notsupport encrypted attributes.


GLPRDB102W Unique attribute attribute_namecannot be encrypted.

Explanation: The encrypted attribute feature does notsupport unique attributes.

User response: Remove the attribute from the list ofunique attributes or do not define this attribute to beencrypted.

GLPRDB103E The password policy entry DN ofentry referenced by entry DN of entry isnot valid.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. The DNof the password policy entry specified for the user orgroup entry is not valid.

User response: The DN of the password policy entrymust be specified in accordance with DN grammar.

GLPRDB104E The DN of the password policy entryDN of entry referenced by entry DN ofentry cannot be found.

Explanation: The DN of the password policy entryspecified for the user or group entry does not exist.

User response: The password policy entry specifiedfor the user or group entry must be created first.

GLPRDB105E The password policy entry DN ofentry is in use and cannot be renamed ordeleted.

Explanation: The password policy entry is referencedby other entries as either an individual password policyor a group passsword policy and, therefore, cannot berenamed or deleted.

User response: Make sure the password policy entryto be deleted or renamed is not referenced by any otherentries.

GLPRDB106W The ibm-pwdPolicy attribute inpassword policy entry DN of entry is setto TRUE, but the ibm-pwdPolicyattribute in the global password policyis set to FALSE. No password policywill be evaluated or enforced.

Explanation: The global password policy is not turnedon. No effective password policy will be evaluated.

User response: Make sure the global password policyas well as the individual or group password policiesare set to TRUE for correct effective password policyevaluation.

GLPRDB108E The creation of a suffix entry DN ofsuffix failed.

Explanation: The creation of the suffix entry failed.The server will not try adding it again until anotherattempt is made to create a child under this entry.

User response: The suffix entry must be manuallycreated.

GLPRDB109E The server does not supportautomatic creation of a suffix entryusing this RDN DN of suffix . Anadministrator must create the entrybefore entries can be added under thissuffix.

Explanation: The server does not have a rule to createa suffix entry with the given relative distinguishedname. The server does support automatic creation ofsuffix entries using the following naming attributes: o,ou, c, dc, cn.

User response: The suffix entry must be manuallycreated.



GLPRDB110E Attribute ibm-pwdPolicyStartTime inentry DN of entry cannot be set to afuture time. The value of the attribute isvalue.

Explanation: The server does not allow a passwordpolicy start time to be set to a future date.

User response: Do one of the following: Turn onpassword policy and let the server generate a passwordpolicy start time for the password policy. Specify a timevalue for attribute ibm-pwdPolicyStartTime that isearlier than the current time.

GLPRDB111E The server is unable to use theusername and password combination forthe DB2 instance owner in theconfiguration file to establish aconnection to the database.

Explanation: When attempting to connect to thedatabase instance with the user name and passwordspecified in the configuration file for the directoryserver instance, the directory server instance receivedan error due to the user/password combination.

User response: Ensure that the password given isvalid for the user id on the system and that the accountis not locked or otherwise unable to login. Thepassword given in the configuration file for thedirectory server instance may need to be updated toreflect the current password on the system.

GLPRDB112E An attempt to delete entry entry namefailed. The return code from creating atombstone is LDAP return code.

Explanation: An internal error occurred. The deleteoperation cannot proceed.

User response: If the error refers to a databasebackend, make sure that a DB2 database has beenproperly configured. If the error refers to LDAPconfiguration, make sure that the tombstone subtree isproperly created. If the problem cannot be resolved,contact IBM Software Support.

GLPRDB113E An attempt to delete entry entry namefailed. The return code from the deleteoperation is LDAP return code.

Explanation: An internal error occurred. The deleteoperation cannot proceed.

User response: If the error refers to a databasebackend, make sure that a DB2 database has beenproperly configured. If the error refers to LDAPconfiguration, make sure that the tombstone subtree isproperly created. If the problem cannot be resolved,contact IBM Software Support.

GLPRDB114W The deleted entry entry name hasbeen restored, but the entry's groupmembership is not restored.

Explanation: The entry that has been deleted isrestored.

User response: The deleted entry has been restored,but the entry's group membership is not restored.

GLPRDB118E Failed to update the databaseconfiguration for LOGARCHMETH1 fordatabase database to method archivemethod.

Explanation: The update to the database configurationto enable or disable online backup has failed.

User response: Check the db2cli.log file and correctany reported errors.

GLPRDB121W All members of group 'group DN'have been replaced.

Explanation: A modify operation was performed onthe group to replace all the members oruniquemembers. In a multi-master replicationenvironment this may cause the group entry to go outof sync.

User response: If multi-master replication is setupthen the administrator should verify the content of thegroup on all replicas and manually synchronize thegroup if necessary.

GLPRDB122E The environment variablesLDAP_MAXCARD andIBMSLAPD_USE_SELECTIVITY cannotboth be set to YES.

Explanation: The environment variableLDAP_MAXCARD causes the directory server toperiodically set the cardinality of selected tables to themaximum value. This causes better performance forsome types of searches. The environment variableIBMSLAPD_USE_SELECTIVITY can also be set to YESto improve performance for some searches. Bothvariables cannot be set to YES.

User response: Unset either LDAP_MAXCARD orIBMSLAPD_USE_SELECTIVITY in the environmentbefore starting the server.

GLPRDB131E Failed to update DB2 statistics fortable 'table name' for instance 'instancename' with SQLCODE DB2 sqlcode.

Explanation: Table statistics are refreshed beforedetermining which entries in the directory should beused with DB2 selectivity in subtree searches as thedirectory seraver starts. Since the statistics could not beupdated,due to this failure, DB2 selectivity will not beused.



User response: Check for additional messages in thedb2cli.log file that may indicate the cause of the failureand make any corrections called for.

GLPRDB132E Reading the database for the eid entryid returned null data.

Explanation: Possibly the eid is not present in theentry cache or its a busy entry.

User response: Either retry or specify the correct entryid.

GLPRDB133E The attribute attr type contains alanguage tag, but language tags are notenabled.

Explanation: Language tags need to be enabled for theattributes that contain a language tag.

User response: Enable language tags.

GLPRDB134E The maximum filter limit that is setin IDS_MAX_SEARCH_FILTER_LEVEL=max filter exceeded for the assertioncontrol on the host, host, with conn id,conn id and is bound with dn, dn

Explanation: The maximum limit of the search filterlevel exceeds for assertion control.

User response: Ensure that the search filter level is inthe specified limits for assertion control.

GLPRDB145E Invalid replication filter attribute valuespecified in entry ' entry dn'.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.2 release this message is deprecated. Thismessage is replaced by the message having tagGLPRPL145E. The replication filter value specified isnot valid.

User response: The replication filter value must bespecified as per filter grammar.

GLPRDB146E Replication filter value is notspecified.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.2 release this message is deprecated. Thereplication filter value is not specified.


GLPRDB147W Attribute attribut name is not foundin schema.

Explanation: The attribute to be deleted is not foundin the server schema.

User response: Check the name of the attribute to be

deleted and retry the operation.

GLPRPL001E Unable to connect to replica host nameon port port number. Verify that thereplica is started.

Explanation: The LDAP Server was unable to connectto the specified server to perform replication. Theprogram continues. Replication to the specified servercannot continue.

User response: Verify that the replica server is started,or contact the operator to start the replica server. Verifythat the replica server information is correct.

GLPRPL003W The DN of the credential entry entryname defined for the replicationagreement entry name cannot be found.

Explanation: The DN of the entry that contains thecredentials used by the server to authenticate to theassociated replica cannot be found.

User response: Make sure the DN of the credentialentry defined in the replication agreement is correctand the credential entry exists.

GLPRPL004E The credential entry entry namedefined for the replication agreemententry name is not valid.

Explanation: The object class of the credential entrydefined for the replication agreement entry is not valid.

User response: Make sure the object class defined forthe credential entry is valid. For example, for a simplebind, the objectclass can be ibm-replicationCredentialSimple.

GLPRPL005E The credential entry entry name is inuse and cannot be deleted.

Explanation: This object cannot be deleted becausesome other object is referencing this object.

User response: Make sure that no other object, such asa replication agreement object, is referencing this objectbefore deleting this object.

GLPRPL006E For the replica group entry entry name,the parent entry must be anibm-replicationContext entry.

Explanation: An ibm-replicaGroup entry must becreated directly beneath an ibm-replicationContextentry.

User response: Take the correct actions to ensure thatthe parent entry of an ibm-replicaGroup entry is anibm-replicationContext entry.

GLPRDB132E • GLPRPL006E


GLPRPL007E For the replica subentry entry entryname, the parent entry must be anibm-replicaGroup entry.

Explanation: An ibm-replicaSubentry entry must becreated directly beneath an ibm-replicaGroup entry.

User response: Take the correct actions to ensure thatthe parent entry of an ibm-replicaSubentry entry is anibm-replicaGroup entry.

GLPRPL008E For the replication agreement entryDN of entry, the parent entry must be anibm-replicaSubentry entry.

Explanation: An ibm-replicationAgreement entry mustbe created directly beneath an ibm-replicaSubentryentry.

User response: Take the correct actions to ensure thatthe parent entry of an ibm-replicationAgreement entryis an ibm-replicaSubentry entry.

GLPRPL009E Master DN and Admin DN cannot bethe same.

Explanation: The value of the ibm-slapdAdminDnattribute and the value of the ibm-slapdMasterDnattribute cannot be the same in the configuration file.

User response: Change the value of theibm-slapdAdminDn attribute or the value of theibm-slapdMasterDn attribute so that they do not havethe same value.

GLPRPL010E The consumer URL defined inreplication agreement entry entry name isa duplicate.

Explanation: For a given subtree, the supplier hasalready had a replication agreement entry that containsthe same consumer URL. To avoid establishing morethan one connection to the consumer, the consumerURL specified in a replication agreement entry must beunique for that supplier.

User response: Make sure the consumer URL specifiedin a replication agreement is correct.

GLPRPL011E Initial server startup has not beendone.

Explanation: The requested operation cannot continuebecause the server has not completed migration.

User response: Start the server to complete migrationand try the request again.

GLPRPL012W Server migration in progress; wait formigration to complete. Server migrationmight take several minutes.

Explanation: This message indicates that the migrationcould take a long time if there is a lot to migrate.

User response: Wait for the migration process tocomplete.

GLPRPL013E The value of the ibm-slapdMigrationInfo attribute mustcontain a valid version number andserver type.

Explanation: There is no value specified for theibm-slapdMigrationInfo attribute.

User response: Specify a valid version number or avalid server type as the value of theibm-slapdMigrationInfo attribute.

GLPRPL014E The schedule DN object entry namecannot be found.

Explanation: The DN of the entry that contains theweekly schedule for the supplier to contact a consumercould not be found.

User response: Make sure the DN of the scheduleentry defined in the replication agreement is correctand the schedule entry exists.

GLPRPL015W Invalid port port type specified: portnumber. Port number must be numeric,in the range 1 - 65535. Server starting inconfiguration only mode on port typeport port number.

Explanation: Invalid port number specified. Serverstarting in configuration only mode with the portnumber specified in the configuration file.

User response: Specify a valid port number.

GLPRPL016E Internal processing error in server;replication thread cannot start.

Explanation: The data passed to create a replicationthread is in error and the replication thread cannot bestarted.

User response: This is an internal processing error. Ifthe problem persists, contact IBM Software Support.

GLPRPL019E Unable to create schedule for replica'entry name'; all changes will bereplicated immediately.

Explanation: Tried to construct schedule by retrievingthe schedule entry defined for this replicationagreement entry, but failed. All changes will bereplicated immediately.

GLPRPL007E • GLPRPL019E


User response: Make sure the value ofibm-replicaScheduleDn is defined correctly for thisreplication agreement entry. Make sure the definedschedule entry exists.

GLPRPL020E Unable to locate schedule entry withDN 'entry name'.

Explanation: The schedule entry referenced by somereplication agreement entries does not exist.

User response: Make sure the schedule entry exists inthe database. Make sure the value ofibm-replicScheduleDn is defined correctly forreplication agreement entries.

GLPRPL021E Error on schedule entry with DN'entry name' attribute attribute name value'attribute value'. Value ignored.

Explanation: The time format defined in the scheduleentry is in error. The value is ignored.

User response: Make sure the time format specified inthe schedule entry is correct.

GLPRPL022W Replica 'entry name' missing scheduleDN; all changes will be replicatedimmediately.

Explanation: The replica is missing a replicationschedule. The server defaults to replicate all changesimmediately.

User response: If the replica should not receivechanges immediately, add a replication schedule to thespecified replica.

GLPRPL023E Error retrieving pending changes forreplica 'entry name'. Will try again.

Explanation: Problem occurred while retrievingpending changes from the database for this replica.

User response: There might be some problem with thedatabase. If the problem persists, contact IBM SoftwareSupport.

GLPRPL024E Error retrieving data for replica 'entryname' change ID change id entry 'entryname' return code 'return code'. Will tryagain.

Explanation: Problem occurred while retrieving datafrom the replication change table for the entry.


GLPRPL025E Error while removing status entry forreplica 'entry name'.

Explanation: Problem occurred while deleting thereplication agreement entry from the replication statustable.

User response: Check the DB2 error log file andcorrect any problems. If the problem persists, contactIBM Software Support.

GLPRPL026E Error while updating status for replica'entry name' to last change ID change id.

Explanation: Problem occurred while updating thestatus for the replication agreement entry in thereplication status table.

User response: Check the DB2 error log file andcorrect any problems. If the problem persists, contactIBM Software Support.

GLPRPL027W Error while parsing data for changeID change id for replica 'entry name'. Willtry again.

Explanation: Problem occurred while parsing theLDIF data obtained from the replication change table.

User response: Review the errors and contact IBMSoftware Support if problem persists.

GLPRPL032E Error error string occurred for replica'entry name': add failed for entry 'entryname' change ID change id.

Explanation: During the replication from this supplierto the consumer defined in the replication agreement,an add operation failed. The error string shows thereason why the operation failed. The change ID is theID the server uses to record the change in the server'sinternal database.

User response: Depending on the error, take theproper actions to correct the error on either the supplieror the consumer.

GLPRPL033E Error error string occurred for replica'entry name': modify failed for entry'entry name' change ID change id.

Explanation: During the replication from this supplierto the consumer defined in the replication agreement, amodify operation failed. The error string shows thereason why the operation failed. The change ID is theID the server uses to record the change in the server'sinternal database.




GLPRPL034E Error error string occurred for replica'entry name': rename failed for entry'entry name' change ID change id.

Explanation: During the replication from this supplierto the consumer defined in the replication agreement, arename operation failed. The error string shows thereason why the operation failed. The change ID is theID the server uses to record the change in the server'sinternal database.


GLPRPL035E Error error string occurred for replica'entry name': delete failed for entry 'entryname' change ID change id.

Explanation: During the replication from this supplierto the consumer defined in the replication agreement, adelete operation failed. The error string shows thereason why the operation failed. The change ID is theID the server uses to record the change in the server'sinternal database.


GLPRPL036E Error 'error string' occurred for replica'entry name': bind failed using masterDn'DN'.

Explanation: The supplier failed to use the masterDnto perform a simple bind with the consumer

User response: Check the credential object defined inthe replication agreement and make sure the DN usedto bind is correct. In addition, make sure the consumerhas the proper master DN defined in the configurationfile.

GLPRPL037E Error error string occurred for replica'entry name': GSSAPI bind failed usingprincipal name 'DN'.

Explanation: The supplier failed to bind with theconsumer using a SASL bind with mechanism GSSAPI.

User response: Verify that an SASL bind withmechanism GSSAPI can be performed with theconsumer using a command line utility (ldapsearch). Ifthis succeeds, check the credential object defined in thereplication agreement and confirm that the DN used tobind is correct. In addition, make sure the consumerhas the proper master DN defined in the server'sconfiguration file.

GLPRPL038E Error error string occurred for replica'entry name': EXTERNAL bind failed.

Explanation: The supplier failed to bind using theEXTERNAL bind mechanism.

User response: Verify that an SASL bind withmechanism EXTERNAL can be performed with theconsumer using a command line utility (ldapsearch). Ifthis succeeds, check the credential object defined in thereplication agreement and confirm that the DN used tobind is correct. In addition, make sure the consumerhas the proper master DN defined in the server'sconfiguration file.

GLPRPL039W Replication agreement 'entry name'has consumer server ID 'server id', butconnected to server with ID 'server id'.

Explanation: The ID of the consumer defined in thereplication agreement is different from the ID of theconsumer that the server actually connects to.

User response: To establish a replication session, makesure the value of the ibm-replicaConsumerId attributedefined in a replication agreement entry is the same asthe value of the ibm-slapdServerId attribute defined inthe consumer's configuration file.

GLPRPL040W Replication for replica 'replicationagreement DN' will continue to retry thesame update after receiving an error.

Explanation: Updates that fail on the replica willblock replication of later updates until the cause of theproblem is resolved and the update is successful.

User response: Ensure that replication errors arecorrected quickly to avoid a backlog of updates.

GLPRPL041W Replication for replica 'replicationagreement DN' will continue to the nextupdate after receiving an error.

Explanation: Updates that fail on the replica will notblock replication. The failing updates will be logged inthe replication error log and replication will continue tothe next update.

User response: Ensure that the supplier and consumerservers stay synchronized by periodically checking forreplication errors in the log. Run the ldapdiff commandto re-synchronize data if there are errors.

GLPRPL042W Replication continuing for replica'replication agreement DN' after loggingupdate type for entry 'update entry DN'ignoring error: LDAP return code LDAPerror description additional error message.

Explanation: This update failed on the replica for thereason specified, but replication is set to continue afterlogging the error.

GLPRPL034E • GLPRPL042W


User response: The supplier and consumer servers'data might no longer be synchronized. Other updatesmay also fail due to this error. Compare the databetween the supplier and consumer to ensure that thedata is synchronized. Additional actions might berequired to prevent future errors.

GLPRPL043W Replication continuing for replica'replication agreement DN' after skippingupdate type for entry 'update entry DN'because of error: LDAP return code LDAPerror description additional error message.

Explanation: The specified update on the replica hasalready been completed successfully. This update willbe skipped and replication will continue.

User response: Compare the DN entries on thesupplier and consumer to ensure that they match.

GLPRPL044E Server failed to acquire Kerberoscredential for the replica 'replicationagreement DN'.

Explanation: The LDAP server failed to acquireKerberos credentials for a replica.

User response: Make sure the replica's LDAP serverservice principal name is created correctly in the KDCand the keytab file name is specified correctly. Also,check that the master has the correct credentials for thereplica.

GLPRPL045E Unable to connect to replica host nameon port port number. Verify that thereplica is started.

Explanation: The LDAP Server was unable to bind tothe specified server to perform replication.

User response: Verify that the bind informationdefined for the supplier to contact the consumer iscorrect.

GLPRPL046W The DN of the credential entrycredential entry name defined for thereplication agreement agreement entryname cannot be found.

Explanation: The DN of the entry that contains thecredentials used by the server to authenticate to theassociated replica server cannot be found.

User response: Make sure the DN of the credentialentry is correct and the credential entry exists.

GLPRPL047E The DN of the credential entrycredential entry name defined for thereplication agreement agreement entryname cannot be found.

Explanation: There is an internal search error. The DN

of the entry that contains the credentials used by theserver to authenticate to the associated replica servercannot be found.

User response: Make sure the DN of the credentialobject is correct and the credential object exists. If theproblem persists, contact IBM Software Support.

GLPRPL048E The consumer URL defined inreplicaAgreement entry name is aduplicate.

Explanation: Problem occurred while adding theconsumer URL to the replication status table. For agiven subtree, the supplier might have already had areplication agreement entry that contains the sameconsumer URL. To avoid establishing more than oneconnection to the consumer, the consumer URLspecified in a replication agreement entry must beunique for that supplier.

User response: Make sure the consumer URL specifiedin a replication agreement is correct.

GLPRPL049E The value of the ibm-slapdMigrationInfo attribute mustcontain a valid version number.

Explanation: The value specified foribm-slapdMigrationInfo attribute is not a valid versionnumber.

User response: Specify a valid version number, suchas 4.1, as the value of ibm-slapdMigrationInfo attribute.

GLPRPL051E Error error string occurred for replica'entry name': delete failed for entry 'entryname' change ID change id.

Explanation: During the replication from this supplierto the consumer defined in the replication agreement, adelete subtree operation failed. The error string showsthe reason why the operation failed. The change ID isthe ID the server uses to record the change in theserver's internal database.


GLPRPL053E Error retrieving pending change countfor replica 'entry name'.

Explanation: Problem occurred while retrievingpending change count from the database for thisreplica.


GLPRPL043W • GLPRPL053E


GLPRPL054E Error while removing status entry forreplica 'entry name'.

Explanation: Problem occurred while deleting theconsumer associated with the replication agreemententry from the replication consumer status table.



Explanation: The DN of the entry that contains theweekly schedule for a supplier to contact a consumercould not be found.



Explanation: There is an internal search error. The DNof the entry that contains the weekly schedule for asupplier to contact a consumer could not be found.

User response: Make sure the DN of the scheduleentry defined in the replication agreement is correctand the schedule entry exists. If the problem persists,contact IBM Software Support.


Explanation: The entry that contains the dailyschedule for a supplier to contact a consumer could notbe found.



Explanation: The entry that contains the dailyschedule for a supplier to contact a consumer could notbe found.



Explanation: There is an internal search error. The DNof the entry that contains the daily schedule for asupplier to contact a consumer could not be found.

User response: Make sure the DN of the scheduleentry defined in the replication agreement is correctand the schedule entry exists. If the problem persists,contact IBM Software Support.

GLPRPL060E Error while updating status for replica'entry name' to last change ID change id.

Explanation: Problem occurred while updating thestatus for the replication agreement entry in thereplication status table.


GLPRPL061E Invalid port type port specified: portnumber. Port number must be numeric,in the range 1 - 65535. Server starting inconfiguration only mode with port typeport port number.

Explanation: Invalid port number specified. Serverstarting in configuration only mode with the SSL portnumber specified in the configuration file.

User response: Specify a valid SSL port number.

GLPRPL062E Transaction time limit of time limitexceeded.

Explanation: The transaction timed out. Thetransaction time limit was exceeded for thesereplication operations.

User response: Decrease the number of operationswithin the transaction, ensure network performance isadequate, or increase the transaction timeout value andrestart the server.

GLPRPL063E Cannot move 'entry DN' from onereplication context to another.

Explanation: An entry cannot be moved into or out ofa replication context using the modify DN operation.

User response: Move the entry within a singlereplication context, or delete the entry and then add itin the desired replication context.

GLPRPL064E The replication configuration couldnot be read.

Explanation: A problem was encountered during theconfiguration of replication.

User response: Make sure the server configuration fileis correct and the replication configuration entry exists.



GLPRPL065E The replication configuration DNobject entry name cannot be found.

Explanation: The DN of the entry that is used toconfigure replication cannot be found.

User response: Make sure the server configuration fileis correct and the replication configuration entry exists.

GLPRPL066E Error on configuration entry with DN'entry name'; required attribute attributename is missing.

Explanation: The missing attribute is required.

User response: Make sure the data in the replicationconfiguration entry is correct.

GLPRPL067E Error on configuration entry with DN'entry name' attribute attribute name value'attribute value'. Value ignored.

Explanation: The value is in error and will be ignored.

User response: Make sure the data in the replicationconfiguration entry is correct.

GLPRPL068E Error initializing the log used forreplication errors.

Explanation: The server was unable to initialize thereplication error log in the database. The server willrun in configuration mode.

User response: This is an internal processing error. Ifthe problem persists, contact IBM Software Support

GLPRPL070E Propagation of replication topologyentries to host hostname port port numberfailed with error code rc.

Explanation: Propagation of replication topologyentries to the target server is in error.

User response: Correct the error on the target serverand retry the operation.

GLPRPL074W Replication conflict: a modify of'entry name' was rejected because it hadan older timestamp.

Explanation: An attempt was made by a replicationsupplier to modify an entry on this server. The latestupdate to the entry on this server was more recent;therefore, the supplier's update to the entry wasignored.

User response: Check that no updates have been lostby comparing the contents of this entry on all theservers in the replication topology.

GLPRPL075W Replication conflict: a conflict isdetected on a modify operation of DN'entry name'. The reason for this conflictis because the entry has been modifiedon this server before the entry wasmodified on the supplier.

Explanation: A replication conflict has been detected.The entry on this server was modified before the entrywas modified on the supplier. To resolve this conflict,the server requests the supplier to re-add the entry,replacing the current entry contents.

User response: If the entry is not synchronized amongservers in a replication environment, you mustmanually update the entry on the servers to bring thedata into a synchronized state.

GLPRPL076W Replication conflict: a conflict isdetected on a modify operation of DN'entry name'. An earlier update on thesupplier has not yet been applied to thisserver.

Explanation: A replication conflict has occurred. Toresolve this conflict, the server requests the supplier tore-add the entry, replacing the current entry contents.


GLPRPL078W The extended operation cannotreplicate to target server host port portnumber because the target server doesnot support replication topology entries.

Explanation: The target server is an earlier releaseserver that cannot handle replication topology entries.The Replication Topology extended operation will notreplicate entries to the target server.

User response: Either upgrade the target server to amore recent release or exclude the target server as atarget of this operation.

GLPRPL079E The extended operation cannotreplicate entries to the target serverhostname port port number because thetarget server does not have the suffixsuffix.

Explanation: The extended operation failed toreplicate entries to the target server because the targetserver does not have a proper suffix and does notsupport dynamic suffix creation by a supplier server.

User response: Manually add a proper suffix to thetarget server's configuration file to accommodate theentries to be sent by the supplier.



GLPRPL083W Replication conflict: re-add of DN'entry name' to host hostname port portnumber failed.

Explanation: The re-add of an entry to the targetserver to resolve a replication conflict failed. The serverwill not try to add the entry again.


GLPRPL084E Replication conflict: re-add of DN'entry name' to resolve a conflict will notcontinue because the entry is too large.

Explanation: A replication conflict has occurred on atarget server. To resolve this conflict, this server isrequested to re-add the entry. However, the size of theentry exceeds the maximum re-add entry size definedin the configuration file. The entry will not be re-addedto the target server.

User response: If the entry on the target server is notsynchronized with the other servers in a replicationenvironment, the user must manually update the entryon the servers to bring the data into a synchronizedstate.

GLPRPL085E Unable to format a string requiringnumber of bytes bytes in onlynumberAvailable bytes.

Explanation: The server failed to format a string inthe available space.

User response: Report this problem to IBM SoftwareSupport.

GLPRPL086E Attribute 'attribute name' is missingfrom entry 'entry DN'.

Explanation: In order to create a replication contextbased on an entry that is not a suffix, ACL's must bedefined explicitly in that entry. The add of the entryhas failed.

User response: Add the specified attribute to the entryand retry the add operation.

GLPRPL087E The Replication Topology extendedoperation failed to quiesce the contextentry name on host hostname port portnumber. The operation will not continuewith this server.

Explanation: The Replication Topology extendedoperation cannot quiesce the specified context on thetarget server.

User response: Make sure the context entry on thetarget server is in the proper state. For example, cannot

quiesce an already quiesced context.

GLPRPL089E The Replication Topology extendedoperation failed to unquiesce the contextentry name on host hostname port portnumber. The operation will not continuewith this server.

Explanation: The Replication Topology extendedoperation cannot unquiesce the specified context on thetarget server.

User response: Make sure the context entry on thetarget server is in the proper state. For example, cannotunquiesce a context that is not quiesced.

GLPRPL091E The Replication Topology extendedoperation failed to add a suffix entryname to the configuration file of targethost hostname port port number. Theoperation will not continue with thisserver.

Explanation: Adding an ibm-slapdSuffix attribute withthe replication context DN as the value to the entry'cn=Directory, cn=RDBM Backends, cn=IBM Directory,cn=Schemas, cn=Configuration' in the target server'sconfiguration file has failed. This suffix is needed onthe target server for the Replication Topology extendedoperation to send entries to the target server.

User response: The suffix can be added manually onthe target server before re-trying the extendedoperation.

GLPRPL093E The Replication Topology extendedoperation failed to purge the queue thatis associated with the replicationagreement entry name on host hostnameport port number.

Explanation: A replication agreement entry is about tobe modified on the target server by the extendedoperation. Before modifying, the extended operationattempts to purge the replication queue associated withthe entry. However, the purge operation failed.

User response: Try to manually purge the replicationqueue or delete the replication agreement on the targetserver before re-issuing the extended operation to thesupplier.

GLPRPL095E The supplier of the ReplicationTopology extended operation failed tocontact target host hostname port portnumber using replication agreement entryname.

Explanation: The supplier of the extended operationcannot connect to the target server defined in thereplication agreement.



User response: Check to make sure that the targetserver is up and running.

GLPRPL097E Error initializing or writing to the logused for replication conflict resolution.

Explanation: Error occurred when writing to theLostAndFound file used for replication conflictresolution.

User response: Make sure the log file is configuredcorrectly.

GLPRPL098E The Replication Topology extendedoperation timed out.

Explanation: The Replication Topology extendedoperation cannot continue because the time limit hasbeen exceeded.

User response: Change the timeout option to makesure that enough time is given to run the extendedoperation.

GLPRPL100E The update logged as a failure witherror ID error ID for replicationagreement DN 'replication agreement'failed on attempt attempt number withLDAP return code LDAP error text.

Explanation: The update was retried and failed again.

User response: The error remains in the replicationerror log and can be attempted again or removed.

GLPRPL103E Unable to log failure in replicationerror log for replication agreement DN'replication agreement for entry withchange ID change id.

Explanation: The change was not replicated and couldnot be logged as a failure.

User response: Check the DB2 error log for possiblecauses such as disk full or some other resourceproblem. Use the ldapdiff utility to synchronize thereplicated subtree for the supplier and consumerservers.

GLPRPL104W Reached or exceeded the limit maxreplication errors for the replication errorlog for replication agreement DN'replication agreement'.

Explanation: The configured limit for the number ofreplication errors to be logged has been reached orexceeded for this replication agreement.

User response: Clear one or more errors in thereplication error log by successfully retrying them or byremoving them. Increase the maximum limit forreplication errors in the configuration.

GLPRPL105W Approaching the limit max replicationerrors for the replication error log forreplication agreement DN 'replicationagreement'. The current number oflogged failures is replication error count.

Explanation: Replication for this agreement will blockif the number of failures to be logged is greater thanthe limit in the server configuration.

User response: Clear one or more errors in thereplication error log by successfully retrying them or byremoving them. Increase the maximum limit forreplication errors in the configuration.

GLPRPL110E Replication for DN 'replicationagreement' terminated because of anunsupported replication method. method.

Explanation: The method for this replication is notvalid.

User response: Update the replication agreement entryto correct the replication method.

GLPRPL111W Replication for DN 'replicationagreement' set to use the limit of maxconnections for consumer connections.

Explanation: The number of connections in thereplication agreement entry exceeds the limit.

User response: Update the replication agreement entryto correct the number of consumer connections.

GLPRPL112W Replication for DN 'replicationagreement' set to use the default numberdefault connections for consumerconnections.

Explanation: The number of connections was notspecified in the replication agreement entry.

User response: Update the replication agreement entryto set the number of consumer connections.

GLPRPL113E Unable to create replication agent onconnection connection ID for DN'replication agreement', replicationterminating.

Explanation: Failed to create the threads required tosend updates and process results.

User response: Check system resource limits thatimpact the number of threads a process can have or theamount of memory available.



GLPRPL115W Replication for DN 'replicationagreement' encountered a gap in thechange IDs: current change ID followedlast change ID.


GLPRPL116E Replication for DN 'replicationagreement' encountered a gap in thechange IDs: current change ID followedlast change ID after trying one more timebut is continuing.


GLPRPL117E Unable to log additional replicationfailures in replication error log forreplication agreement DN 'replicationagreement because the number of loggedentries exceeds the limit; replication iswaiting for the log to be cleared.

Explanation: Replication for this agreement is waitingbecause the number of logged failures is greater thanthe limit in the server configuration.

User response: Clear one or more errors in thereplication error log by successfully retrying them or byremoving them. Increase the maximum for replicationerrors in the configuration.

GLPRPL118E Replication for replica 'repl_agmt_dn'will continue to retry the same failedupdate with change ID change id until itis successful.

Explanation: This failed update is blocking replicationof later updates until the cause of the problem isresolved and the update is successful.

User response: Correct the problem causing thisupdate to fail or skip this update using the extendedoperation to control the replication queue. Ensure thatreplication errors are corrected quickly to avoid abacklog of updates.

GLPRPL119W Replica 'entry name' will usesingle-threaded, synchronousreplication, instead of the method in thereplication agreement.

Explanation: The indicated replication agreementspecifies an asynchronous replication method. Theglobal data under cn=IBMPolicies is restricted tosingle-threaded, synchronous replication.

User response: To eliminate the warning, change theindicated replication agreement to specify thereplication method supported for global data.

GLPRPL120E Error occurred processing the replicaURL for replication agreement'repl_agmt_dn'.

Explanation: The replica URL contained in theibm-replicaURL attribute of the replication agreementdirectory entry is empty or cannot be parsed correctly.

User response: Use the Directory Server WebAdministration Tool to edit the replication agreementand verify that the replica hostname and port arecorrect.

GLPRPL121E The operation being performed onDN 'dn' is not allowed in a transaction.

Explanation: Changes to the replication topology arenot allowed in a transaction.

Programmer response: Do not change the replicationtopology in a transaction.

GLPRPL124W Change cannot be replicated becauseit contains attributes that require asecure connection.

Explanation: The change contains one or moreattributes that have been defined as requiring a secureconnection, but the replication agreement is not using asecure connection. Other messages identify the failingchange and the associated replication agreement.

Programmer response: Change the replicationagreement to use a secure connection.

GLPRPL125E Cannot replicate to consumer becauseit does not support encrypted attributes.Replica: 'replication agreement'.

Explanation: The schema contains one or moreencrypted attributes. Encrypted attributes cannot bereplicated to this consumer because it does not supportencrypted attributes. Replication to the consumer willnot be started.

Programmer response: Change the attributedefinitions in the schema so that attributes are notencrypted.

GLPRPL126E Cannot replicate to consumer becauseit does not support the current passwordencryption setting. Replica: 'replicationagreement'.

Explanation: Password encryption has beenconfigured to use an encryption method not supportedby the consumer server. Replication to the consumerwill not be started.

Programmer response: Change the passwordencryption setting to a value supported by allconsumer servers. Any passwords that have been setwith the current password encryption setting must be



reset to be usable on the consumer server.

GLPRPL127W Change cannot be replicated becauseconsumer does not support encryptedattributes.

Explanation: The change contains one or moreattributes that are defined as encrypted, but theconsumer server does not support attribute encryption.Other messages identify the failing change and theassociated replication agreement.

Programmer response: Do not use encryptedattributes. After changing the schema, repair anyentries containing the encrypted attributes.

GLPRPL129E Creation of surrogate entry 'entry name'on partial replica hostname port portnumber failed.

Explanation: This master server was attempting tocreate a new entry on the specified partial replica andthe parent entry was missing probably because thereplication filter eliminated it completely. The serverattempted to create a surrogate entry to take the placeof the missing parent, but this operation failed.

User response: If the entry is not present on the targetserver and is still required for child entries, you mustmanually create the entry on the servers to proceed.

GLPRPL131W The replication filter entry filter entryname defined for the replicationagreement agreement entry name cannotbe found.

Explanation: The entry specified to contain thereplication filter used by the server to filter out selectedattributes from entries during replication cannot befound.

User response: Make sure the DN of the filter entry iscorrect and the entry exists.

GLPRPL132E The replication filter entry filter entryname defined for the replicationagreement agreement entry name cannotbe found.

Explanation: There is an internal search error. Theentry specified to contain the replication filter used bythe server to filter out selected attributes from entriescannot be found.

User response: Make sure the DN of the replicationfilter object is correct and the filter entry exists. If theproblem persists, contact IBM Software Support.

GLPRPL133W The operational attribute op attr namespecified as part of the replication filterinclusion/exclusion list is not allowed.

Explanation: Operational attributes cannot bespecified as part of the filter inclusion/exclusion list. Ifspecified, these will not be considered for filtering ofattributes from entries during replication.

User response: Only specify non-operational attributesas part of the inclusion/exclusion list in a replicationfilter.

GLPRPL138W Consumer server on host host name,port port number, does not support therequested password encryption format.

Explanation: An administrator attempted to changethe password encryption setting to a value that is notsupported by all consumer servers. The change is notallowed because replicated passwords would not beusable on the consumer servers.

User response: Use a password encryption setting thatis supported by all servers, or upgrade the consumerserver to a version that supports the desired passwordencryption.

GLPRPL139E The filter entry entry name is in useand cannot be deleted.

Explanation: This object cannot be deleted becausesome other object is referencing this object.

User response: Make sure that no other object, such asa replication agreement object, is referencing this objectbefore deleting this object.

GLPRPL141W Consumer server on host host name,port port number, does not support therequested attribute encryption format.

Explanation: An administrator attempted to encryptan attribute, but attribute encryption is not supportedby all consumer servers. The change is not allowedbecause the schema would not be usable on theconsumer servers.

User response: Use an attribute encryption setting thatis supported by all servers, or upgrade the consumerserver to a version that supports encrypted attributes.

GLPRPL142W Internal search for the parent entrydn failed.

Explanation: An internal error occurred while tryingto locate the entry in the server. This entry is requiredto be created as a missing parent entry on theconsumer for replication to continue.

User response: Verify that the entry exists on themaster server.

GLPRPL127W • GLPRPL142W


GLPRPL143E The attribute attribute name specifiedin the replication filter is not found inthe schema.

Explanation: The specified attribute was not found inthe schema.

User response: Make sure that only attributes definedin the schema are specified in the replication filter.

GLPRPL144E The objectclass objectclass namespecified in the replication filter is notfound in the schema.

Explanation: The specified objectclass was not foundin the schema.

User response: Make sure that only objectclassesdefined in the schema are specified in the replicationfilter.

GLPRPL145E Invalid replication filter 'attribute value'specified in entry ' entry dn'.

Explanation: The replication filter value specified isnot valid.


GLPRPL146W Replication conflict: modification to'entry name' was rejected because it hasmodification timestamp equal to thetarget entry timestamp.

Explanation: Replicated entry timestamp will be equalto the target entry timestamp only if the replicatedentry is updated on the consumer server and result isnot acknowledged by the supplier due tocommunication failure and the entry is resent by thesupplier.

User response: Check that no updates have been lostby comparing the contents of this entry on all theservers in the replication topology.

GLPRPL147E Cannot replicate to consumer becauseit does not support SHA2 and SaltedSHA2 algorithm families. Replica:'replication agreement'.

Explanation: The schema contains one or moreencrypted attributes with SHA224, SHA256, SHA384,SHA512, SSHA224, SSHA256, SSHA384, or SSHA512.Encrypted attributes cannot be replicated to thisconsumer because it does not support these encryptionschemes. Replication to the consumer will not bestarted.

Programmer response: Change the attributedefinitions in the schema so that attributes are notencrypted or encrypted using the schemes supportedby consumer.

GLPRPL50E The value of the ibm-slapdMigrationInfo attribute mustcontain a valid server type.

Explanation: The value specified foribm-slapdMigrationInfo attribute is not a valid servertype.

User response: Specify a valid server type, such asMaster, as the value of ibm-slapdMigrationInfoattribute.

GLPRUN002E The idsrunstats tool is unable to runbecause of initialization error.

Explanation: The idsrunstats tool is unable to startbecause of an initialization error.

User response: View earlier error message to see whyidsrunstats did not run. Run the idsrunstats tool againafter fixing the problem. If no previous error messagewas printed, contact IBM Software Support.

GLPRUN004E Failed to retrieve the list of tables toupdate index statistics.

Explanation: The idsrunstats tool is unable get the listof tables to update statistics.

User response: View earlier error message to see whyidsrunstats did not run. Run the idsrunstats tool againafter fixing the problem. If the problem persists, contactIBM Software Support.

GLPRUN007W Index statistics on table 'tabname'could not be updated at this time.

Explanation: The idsrunstats tool is unable to updateindex statistics for the table.

User response: Run the idsrunstats tool in debugmode to get detail messages. Run the idsrunstats toolagain after fixing the problem. If the problem persists,contact IBM Software Support.

GLPSCH001E Data source: file name: line line number:expected Object ID, but could not find itat or before variable.

Explanation: Numeric Object ID was expected.

User response: Make sure a numeric Object ID isdefined for the object.

GLPSCH002E Data source: file name: line line number:expected one of the following: variables,but could not find it at or beforevariable.

Explanation: Expected Object ID, left parenthesis,right parenthesis, or $ symbol.

User response: Make sure an Object ID or one of the

GLPRPL143E • GLPSCH002E


missing symbols is provided.

GLPSCH003E Data source: file name: line line number:expected digit after '.', but could notfind it at or before variable.

Explanation: Expected a digit after the '.' character innumeric object ID.

User response: Make sure only digits follow the '.'character.

GLPSCH004E Data source: file name: line line number:expected non-empty quoted string, butcould not find it at or before variable.

Explanation: Encountered an empty quoted string.

User response: Make sure the quoted string is notempty.

GLPSCH005E Data source: file name: line line number:expected number after brace, but couldnot find it at or before variable.

Explanation: Expected a number following the openbrace character.

User response: Make sure a number follows the openbrace character.

GLPSCH006E Data source: file name: line line number:expected '}' after '{ <number>', but couldnot find it at or before variable.

Explanation: Expected a closing brace after a number.

User response: Make sure a closing brace alwaysfollows a number.

GLPSCH007E Data source: file name: line line number:expected a quoted string, but could notfind it at or before variable.

Explanation: Expected a quoted string.

User response: Make sure the DESC field of theattribute is followed with a quoted string.

GLPSCH008E Data source: file name: line line number:expected a quoted string or openparenthesis, but could not find it at orbefore variable.

Explanation: The server was expecting a quoted stringor an open parenthesis after the NAME field.

User response: Make sure the NAME field is followedby a quoted string or an open parenthesis.

GLPSCH009E Data source: file name: line line number:expected an LDAP description string,but could not find it at or beforevariable.

Explanation: The server is expecting a descriptionfollowing the DESC field.

User response: Make sure a description follows theDESC field in an attribute definition.

GLPSCH010E Data source: file name: line line number:expected a quoted LDAP descriptionstring, but could not find it at or beforevariable.

Explanation: The server was expecting a quoteddescription following the DESC field.

User response: Make sure a quoted descriptionfollows the DESC field in an attribute definition.

GLPSCH011E Data source: file name: line line number:expected a quoted LDAP descriptionstring or open parenthesis, but could notfind it at or before variable.

Explanation: The server was expecting a quoted stringor an open parenthesis following the DESC field in anattribute definition.

User response: Make sure a quoted description or anopen parenthesis follows the DESC field in an attributedefinition.

GLPSCH012E Data source: file name: line line number:encountered non-terminated quotedstring at or before variable.

Explanation: The server encountered a non-terminatedquoted string.

User response: Make sure all quoted strings areterminated.

GLPSCH013E Data source: file name: line line number:encountered unexpected end of input.

Explanation: Unexpected end of file encountered bythe server.

User response: Make sure the last attribute or classdefinition in the schema file is terminated with aclosing parenthesis.

GLPSCH014E Data source: file name: line line number:input not valid at or before variable.

Explanation: The server encountered an invalid inputstring in the schema file.

User response: Make sure all schema definitionscomply with RFC2252.

GLPSCH003E • GLPSCH014E


GLPSCH015E Data source: file name: line line number:expected usage specification, but couldnot find it at or before variable.

Explanation: The server was expecting 'USAGE'directive, but did not find it.


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 beforevariable.

Explanation: The server was expecting one or twoquoted strings specifying the database table and/orcolumn names. But the server did not find any.

User response: Make sure the database table nameand/or column name follow the DBNAME directive.

GLPSCH017E Data source: file name: line line number:expected ACCESS-CLASS specification,but could not find it at or beforevariable.

Explanation: The server is expecting ACCESS-CLASSspecification for the attribute, but did not find thisspecification.

User response: Make sure all attribute definitionscontain ACCESS-CLASS specification.

GLPSCH018E Data source: file name: line line number:variable variable has already been defined.

Explanation: Multiple definition of an attribute.

User response: Make sure attributes are only definedonce.

GLPSCH019E Data source: file name: line line number:found duplicated definition for variablevariable.

Explanation: Duplicate definition of object class,matching rules, or syntax.

User response: Make sure object classes, matchingrules, or syntaxes are defined only once.

GLPSCH020E Data source: file name: line line number:attribute type variable already has anIBM extended definition.

Explanation: Multiple IBM extended definition for anattribute.

User response: Make sure each attribute definition hasonly one IBM extended definition.

GLPSCH021E Data source: file name: line line number:all alternate definitions of same variablemust be in a single file. variable is alsodefined in variable.

Explanation: All alternate definitions of an attributemust be in the same file.

User response: Make sure alternate definitions of anattribute are not split into more than one file.

GLPSCH022E Data source: file name: line line number:inconsistent variable, variable and variable(with object ID variable).

Explanation: Alternate definitions of an attribute areconsistent.

User response: Make sure alternate definitions ofattributes are consistent except with respect to 'NAME'.

GLPSCH023E Data source: file name: line line number:variable variable does not have a syntaxdefinition.

Explanation: Attribute definition does not include'SYNTAX' directive.


GLPSCH024E Operation not valid. Expected one ofthe following operations: variable.

Explanation: A modify operation that is not valid isspecified.

User response: You can only use the change types(add, delete, and replace) with the modify operation.

GLPSCH025E variable variable not found whenprocessing variable variable.

Explanation: Definition of SUP, matching rule, orsyntax for an attribute or object class is not found.

User response: Make sure definitions of all syntaxes,matching rules, and SUPs are available.

GLPSCH026E variable variable does not exist; deleteoperation failed.

Explanation: Attempted to remove an attribute, amatching rule, or a syntax that is not defined.


GLPSCH027E variable variable does not exist; replaceoperation failed.

Explanation: Attempted to replace an attribute that isnot defined.




GLPSCH028E variable variable does not have a syntaxdefinition.

Explanation: Attribute does not have a syntaxdefinition.


GLPSCH029E Attempt to delete variable failed. Thespecified object ID object ID and namename do not refer to the same variable.

Explanation: Object ID and name do not refer to thesame object.

User response: The name and object ID must refer tothe same object.

GLPSCH030E Attempt to replace variable failed. Thespecified object ID object ID and namename do not refer to the same variable.

Explanation: Object ID and name do not refer to thesame object.

User response: The name and object ID must refer tothe same object.

GLPSCH031E variable variable already exists; addoperation failed.

Explanation: Attempted to add an object that alreadyexists.


GLPSCH032E variable variable cannot be deleted. It isstill being used.

Explanation: Attempted to delete an object that is inuse.


GLPSCH033E Missing LDAP V3 specification forvariable attribute.

Explanation: LDAP V3 specification for an attribute ismissing.

User response: Make sure the schema files arecomplete and installed by the server.

GLPSCH034E attribute variable and its supertypesuper have different usages.

Explanation: An attribute and its superior type havedifferent usage directives.


GLPSCH035E Cycle, attribute, detected in supertypespecification.

Explanation: Circular dependency in an attributedefinition and its supertype is detected.


GLPSCH036E Cycle, class, detected in superclassspecification.

Explanation: Circular dependency in a class definitionand its supertype is detected.


GLPSCH037E entity variable was not provided. Mustbe provided as quoted string.

Explanation: Entity value is missing.

User response: Make sure entity value is provided asa quoted string.

GLPSCH038E entity string must be provided asstring, but was provided as string.

Explanation: Incorrect entity value.

User response: Make sure the entity value is of theproper type.

GLPSCH039E string quoted string must be providedas string with inherited properties orIBM extensions string, but was providedas string with inherited properties orIBM extensions string.

Explanation: Entity value does not match theinherited property.


GLPSCH040E The IBM extension for string quotedstring must be provided as string, butwas provided as string.

Explanation: Entity value does not match the IBMextended definition .


GLPSCH041E Data source: file name: line line number:expected ENCRYPT specification, butcould not find it at or before variable.

Explanation: The server was expecting 'ENCRYPT'directive, but did not find it.




GLPSCH042E Data source: file name: line line number:expected RETURN-VALUE specification,but could not find it at or beforevariable.

Explanation: The server was expecting'RETURN-VALUE' directive, but did not find it.


GLPSCH043E Attribute attribute name cannot beencrypted. The server does not supportencryption for syntax syntax name.

Explanation: The server supports encryption for thesesyntaxes: Binary, Directory String, IA5 String andTelephone Number.

User response: Change the IBMAttributeType to use asupported syntax or do not encrypt this attribute.

GLPSCH044E Attribute attribute name cannot beencrypted.

Explanation: The server does not allow operationalattributes and other special attributes to be encrypted.

User response: Do not encrypt this attribute.

GLPSCH046W matching rule type Matching Rulematching rule name for attribute attributename is not compatible with its syntaxsyntax name

Explanation: The specified matching rule is notcompatible with the other matching rules or the syntaxof the attribute. This matching rule is ignored.

User response: Change the attribute definition so thatall matching rules are compatible with the syntax of theattribute.

GLPSCH047E Password attribute attribute namecannot be encrypted in the schema.

Explanation: Password encryption is controlled by theserver password encryption policy.

User response: Do not define this attribute asencrypted using the schema; use the server passwordencryption policy.

GLPSCH049W matching rule type Matching Rulematching rule name for attribute attributename is not consistent with othermatching rules defined for this attributein terms of case-sensitivity handling.

Explanation: The specified matching rule is not

consistent with other matching rules of the attribute interms of case-sensitivity. This attribute will be treatedas case-sensitive for all EQUALITY, SUBSRING andORDERING matches.

User response: Change the attribute definition so thatall matching rules are consistent for case-sensitivity ofthe attribute.

GLPSCH050E Length attribute length for attributeattribute name is less than the minimumlength of 32 for an AES-encrypted value.

Explanation: The specified attribute is defined to useAES encryption, but the attribute length is too short tohold an AES encrypted value.

User response: Change the attribute definition to usea length of at least 32, or do not encrypt the attribute.

GLPSCH052W Invalid value 'value' set for attributeencryption. Assuming AES256encryption format.

Explanation: Attribute level encryption accepts onlyone of following values: AES-128 AES-192, AES-256,SSHA, SHA-224, SHA2-56, SHA3-84, SHA-512,SSHA-224, SSHA-256, SSHA-384, or SSHA-512 If SHA-2feature is not enabled then SHA-224, SHA-256,SHA-384, SHA-512, SSHA-224, SSHA-256, SSHA-384,and SSHA-512 are not allowed.

User response: If SHA-2 feature needs to be enabled,ibm-slapdUseNonFIPSCrypt should be set to true incn=configuration entry, otherwise set appropriateencryption method.

GLPSRV005E Server was unable to decode inputdata from the client (connection ID:connid, IP address: )ip_addr, Port: port)while processing operation: operation.

Explanation: The server is unable to process therequested operation because of a failure wheninterpreting the request.

User response: Make sure that clients BER encodeLDAP messages correctly.

GLPSRV006E Unable to open file 'file'. Tryspecifying the full path name.

Explanation: The server is unable to open thespecified configuration file.

User response: Correct the file name and restart theserver, or contact the administrator.

GLPSCH042E • GLPSRV006E


GLPSRV007E Error while trying to allocate memory.

Explanation: The server is unable to allocate thenecessary storage to continue processing.

User response: Increase the storage for the server andrestart the server.

GLPSRV008E Unable to create necessary thread.

Explanation: The server is unable to obtain thenecessary resources to create a required thread. If thefailure occurs during startup of the server, the programwill end.

User response: Verify that the system is notoverloaded and is configured correctly.

GLPSRV010E Server unable to start due to attributedependency check failure.

Explanation: The server is unable to start due toattribute dependency check failure.

User response: For additional information seeMessage ID GLPSRV011E and GLPRPL009E.

GLPSRV011E Server cannot use port port for bothSSL and non-SSL.

Explanation: The server cannot listen on the specifiedport for both secure and nonsecure requests.

User response: Make sure different ports are specifiedfor SSL and non-SSL ports.

GLPSRV012E A primary administrator DN andadministrator PW must be specified inthe server configuration.

Explanation: The server encountered either a blankadminDN or adminPW parameter in the configurationfile.

User response: Ensure that both adminDN andadminPW are specified in the configuration file.

GLPSRV013E Attempt to initialize administrativeconnection failed, error value (errorstring).


User response: Remove the socket file associated withthe AF_UNIX domain and restart the server.

GLPSRV014E An attempt to set a TCP/IP parameterhas failed. The operating systemreturned error error value (error string).

Explanation: The server received an error while

attempting to set options for the TCP/IP socket option:TCP_NODELAY.


GLPSRV022E Failed to initialize secure connectionfrom client (connection ID: connid, IPaddress: ip_addr, Port: port).

Explanation: The server determined that a client sentnon-encrypted data to the secure port. The requestfrom the client is ended.

User response: If a command utility such asldapsearch is called by the client and securecommunications is intended, make sure the -Z (usesecure communications) parameter is specified. If theclient does not intend to use secure communications,then specify the non-secure port.

GLPSRV027E Server failed to acquire Kerberoscredential.

Explanation: The server failed to acquire Kerberoscredentials for the server principal.

User response: Make sure the server service principalname is created correctly in the KDC and the keytabfile name is specified correctly in the configuration.

GLPSRV028E Mapping from Kerberos principal toLDAP DN failed because more than onekrbPrincipalName is found.

Explanation: The mapping from Kerberos principal toLDAP DN failed because more than onekrbPrincipalName is found in the database.

User response: Make sure there is only one LDAP DNthat can be mapped from the Kerberos principal.

GLPSRV029E SASL GSSAPI bind request fromclient failed due to a token that is notvalid.

Explanation: SASL GSSAPI bind request from thespecified client failed because of a token that is notvalid.

User response: Make sure that there is a valid tokenfor the Kerberos principal being used.

GLPSRV030E Maximum operations per transactionmaximum operations exceeded.

Explanation: The maximum number of operations pertransaction specified in the server configuration hasbeen exceeded.

User response: Reduce the number of operations inthe transaction and try again or change the serverconfiguration.

GLPSRV007E • GLPSRV030E


GLPSRV031E Maximum number of transactionsmaximum transactions exceeded.

Explanation: The maximum number of concurrenttransactions requests specified in the serverconfiguration has been exceeded.

User response: Reduce the number of concurrenttransaction requests or change the server configuration.

GLPSRV032E Time limit of time limit for atransaction was exceeded and all of theoperations in the transaction were rolledback.

Explanation: The transaction time limit was exceededfor the operations in a transaction.

User response: Increase the transaction time limit inthe server configuration.

GLPSRV036E Errors were encountered whilestarting the server; started inconfiguration only mode.

Explanation: Errors prevented the server from startingnormally. A server in configuration mode will allowchanges to the configuration to correct any errors.

User response: Check the server log for errors. Afterthese error conditions have been corrected, attempt tostart the server again.

GLPSRV037E Failed to change file to file name.

Explanation: An error occurred while attempting toopen the file specified as the audit output file or thelog file for the server, DB2 or bulkload. The specifiedfile is not a valid location or the user issuing thecommand does not have the necessary permissions towrite to the file.

User response: Verify that the file name and path arevalid and that the permissions allow writing to the file.

GLPSRV038W Using default file file name.

Explanation: The file specified in the configurationcould not be opened so the default file will be usedinstead.

User response: If using the default file isunacceptable, verify that the file specified in theconfiguration is valid and can be written to.

GLPSRV039E Configuration entry: entry DNcontains an line that is not valid: entryattribute : attribute value

Explanation: The configuration entry shown was notvalid.

User response: Check the configuration entry shown

and make sure that it is valid.

GLPSRV040E Server starting in configuration onlymode due to errors.

Explanation: A previous error caused the directoryserver instance to start in configuration only mode.

User response: Review the server log to find the errorthat caused the server to start in configuration onlymode. Correct the error condition and restart the server.

GLPSRV042W Server responding to a large backlogof requested client operations. There arenumber of pending requests pendingrequests.


GLPSRV043W Server response to the backlog ofrequested client operations hascompleted. number of completed requestsrequests completed.


GLPSRV044W Client connection from IP addressbound as bind DN closed by server.

Explanation: The server has closed the specified clientconnection, either as a result of reaping connections oras a result of an unbind LDAP extended operation.

User response: Verify that the reaping parameters inthe server configuration are acceptable.

GLPSRV045W Automatically closed number ofconnections idle client connections.

Explanation: The current number of connectionsexceeded the limit specified in the server configurationso the server closed the specified number of idle clientconnections.

User response: Verify the reaping parameters areacceptable. See the IBM Security Directory ServerAdministration Guide for more information.

GLPSRV046W No anonymous binds will beallowed.

Explanation: The administrator has configured theserver to reject anonymous binds.

User response: Verify that no client applicationsrequire anonymous access to the server.(ibm-SlapdAllowAnon == False).

GLPSRV031E • GLPSRV046W


GLPSRV047W Anonymous binds will be allowed.

Explanation: The administrator has configured theserver to accept anonymous binds.

User response: Verify that anonymous access to theserver should be allowed.

GLPSRV051W Anonymous binds will no longer beaccepted. Closed number of connectionsexisting anonymous client connections;number of connections will be closed assoon as possible.

Explanation: As a result of a server configurationupdate, all anonymous connections bound to the serverhave been closed.

User response: Verify that the server configurationupdate was expected and that the new behavior isacceptable.

GLPSRV052W Processing unbind request from thedirectory administrator. Closed number ofconnections client connections; anothernumber of connections client connectionswill be closed as soon as possible.

Explanation: The server has accepted an unbindLDAP extended operation request and the specifiednumber of client connections have been closed.

User response: Verify that the request to unbind theseconnections was expected.

GLPSRV053E Server unable to respond to the largebacklog of client requests.


GLPSRV054E Unable to enable tracing dynamically.

Explanation: The server was unable to start tracing asrequested.

User response: Ensure that the IBM LDAP TraceFacility is on. For example, run 'ldtrc on' or use theldaptrace command.

GLPSRV056E Server unable to disable tracingdynamically.

Explanation: The server was unable to turn off tracingas requested.

User response: Turn the IBM LDAP Trace Facility offor restart the directory server instance with tracingturned off. For example, run 'ldtrc off' or use theldaptrace command.

GLPSRV058E Unable to set debug level for serverdebugging.

Explanation: The server was unable to change thedebug level dynamically. The debug level is used tocontrol the type of information output to the debugoutput file.

User response: Make sure the requested debug level isvalid. For example, 65535 or a sum of the values shownby 'ibmslapd -h ?' that are less than 65535. The debuglevel 65535 or 0xFFFF will turn on all debug messages.

GLPSRV059W Debug level set to debug_output_level.

Explanation: The server was able to change the debuglevel dynamically. The debug level is used to controlthe type of information that is output to the debugoutput file.

User response: Make sure the requested debug level isthe value desired. Try 'ibmslapd -h ?' to see all values.The debug level 65535 or 0xFFFF will turn on all debugmessages.

GLPSRV060E Unable to set debug output file namefor the server.

Explanation: The server was unable to change thedebug output filename dynamically.

User response: Make sure the path name and the filename are valid and that the file permissions are correct.

GLPSRV062E Attribute attribute name in entry entryname specified the Kerberos ID for anadministrator incorrectly.

Explanation: The syntax of the Kerberos ID definedfor the administrative user is not valid. The KerberosID must start with 'ibm-kn=' or 'ibm-kerberosName='.

User response: Make sure that the Kerberos ID hasthe proper prefix.

GLPSRV063E Unable to complete registration of allsupported features.

Explanation: The server was unable to register all thesupported features.

User response: Make sure sufficient memory isavailable to run the server.

GLPSRV064E Failed to initialize plugin name.

Explanation: The server was unable to initialize thespecified object. The object might be an external serverplug-in, or an internal server feature.

User response: Verify that the server is properlyconfigured.

GLPSRV047W • GLPSRV064E


GLPSRV065E Values for the attribute attribute nameare not unique. The attribute attributename was removed from the uniqueattribute entry: entry name.

Explanation: The unique attribute specified in thedatabase does not contain valid unique constraints. Theattribute has been removed from the unique attributelist.

User response: This is most likely caused after abulkload of new data. Remove all of the duplicatevalues for this attribute, and then re-add the attributeto the unique list.

GLPSRV066E DIGEST-MD5 bind attempt failedbecause the value for the component namecomponent in the response was notvalid.

Explanation: The DIGEST-MD5 bind request violatedthe protocol. The specified component's value wasincorrect.

User response: Ensure that the client is using thecorrect protocol.

GLPSRV067E DIGEST-MD5 bind attempt forusername was unsuccessful because theusername did not match an entry.

Explanation: The username supplied on aDIGEST-MD5 bind request must match a single entryin the directory that has a userpassword attribute.

User response: Ensure that the username is correctand that it matches a single entry in the directory thathas a userpassword attribute.

GLPSRV068E DIGEST-MD5 bind attempt forusername was unsuccessful because theusername matched more than one entry.

Explanation: The username supplied on aDIGEST-MD5 bind request must match a single entryin the directory that has a userpassword attribute.

User response: Ensure that the username is correctand that it matches a single entry in the directory thathas a userpassword attribute.

GLPSRV069E DIGEST-MD5 bind attempt wasunsuccessful because the response fromthe client was improperly formatted.

Explanation: The DIGEST-MD5 bind request violatedthe protocol.

User response: Ensure that the client is using thecorrect protocol.

GLPSRV070E DIGEST-MD5 bind attempt forusername was unsuccessful because thepassword was incorrect.

Explanation: A user attempted to bind withDIGEST-MD5 but supplied the wrong password.

User response: Ensure that the client supplies thecorrect password.

GLPSRV071E DIGEST-MD5 bind attempt forusername was unsuccessful because theuser did not have proxy authority.

Explanation: A user attempted to bind withDIGEST-MD5 using an authorization ID but the userdid not have proxy authority.

User response: Bind with a user that has proxyauthority or do not use an authorization ID.

GLPSRV072E Mapping from Kerberos principal toLDAP DN failed because more than onealtSecurityIdentities exists.

Explanation: The mapping from Kerberos principal toLDAP DN failed because more than onealtSecurityIdentities exists in the database.

User response: Make sure there is only one LDAP DNthat can be mapped from the altSecurityIdentities.


Explanation: The syntax of the Kerberos ID definedfor the administrative user is not valid. A Kerberos IDmust start with 'ibm-kn=' or 'ibm-kerberosName'.

User response: Make sure that the Kerberos ID hasthe proper syntax.


Explanation: The syntax of the Kerberos ID definedfor an administrator is not valid. A Kerberos ID muststart with 'ibm-kn=' or 'ibm-kerberosName='.

User response: Make sure that the Kerberos ID hasthe proper syntax.

GLPSRV075E Bad Administrator Kerberos IDdefined in attribute attribute name inentry entry name. The Kerberos ID muststart with 'ibm-kn=' or'ibm-kerberosName='.

Explanation: The syntax of the Kerberos ID definedfor a member of the administrative group is not valid.



A Kerberos ID must start with 'ibm-kn=' or'ibm-kerberosName='.

User response: Make sure that the Kerberos ID hasthe proper prefix.

GLPSRV076E Transaction time limit of time limitexceeded. No future operationsrequested in this transaction areallowed. Transaction rolled back.

Explanation: The transaction timed out. Thetransaction time limit was exceeded for theseoperations.

User response: Increase the amount of time neededfor this transaction or decrease the number ofoperations for this transaction.

GLPSRV077E Unable to enable tracing at startup.

Explanation: The server was unable to initializetracing at server startup.

User response: Ensure that the IBM LDAP TraceFacility is on. To accomplish this, run the command'ldtrc on' or use the ldaptrace command.

GLPSRV078W Server trace enabled.

Explanation: The server was able to initialize tracingat server startup.

User response: Because of the performance impact ofcollecting trace and debug data from the server, makesure that the data is being collected to resolve aproblem.

GLPSRV079E Unable to set the server debug levelat startup.

Explanation: The server was unable to set the debuglevel at server startup. The debug level is used tocontrol the type of information output to the debugoutput file.

User response: Make sure the requested debug level isa valid. For example, 65535 or a sum of the valuesshown by 'ibmslapd -h ?' that are less than 65535. Thedebug level 65535 or 0xFFFF will turn on all debugmessages.

GLPSRV080W Server debug level set todebug_output_level.

Explanation: The server was able to set the debuglevel at server startup. The debug level is used tocontrol the type of information output to the debugoutput file.

User response: Make sure the requested debug level isthe value desired. Try 'ibmslapd -h ?' to see all values.

The debug level 65535 or 0xFFFF will turn on all debugmessages.

GLPSRV081E Unable to set the server debug outputfile name at startup.

Explanation: The server was unable to set the debugoutput filename at server startup.

User response: Make sure the path name and the filename are valid and that the file permissions are correct.

GLPSRV083E Unable to enable server tracing asrequested on the command line.

Explanation: The server was unable to initializetracing at server startup as requested on the commandline.

User response: Ensure that the IBM LDAP TraceFacility is on and restart the server with the samecommand line option. For example, run the command'ldtrc on' or use the ldaptrace command.

GLPSRV084W Trace enabled from command line.

Explanation: The server was able to initialize tracingat server startup as requested on the command line.

User response: Because of the performance impact ofcollecting trace and debug data from the server, makesure that the data is being collected to resolve aproblem.

GLPSRV085E An attempt to set the TCP/IP keepalive option has failed. The operatingsystem returned error error value (errorstring).

Explanation: The server received the error whileattempting to set the socket option for keep alive.


GLPSRV087E The -a and -n options cannot be usedtogether.

Explanation: A command was issued to start theserver in configuration only mode and not inconfiguration only mode at the same time.

User response: Specify only the -a or -n option,depending on the desired server state.

GLPSRV088E The server is unable to run because ofinitialization error.

Explanation: The server is unable to run because of aninitialization error.

User response: View earlier error messages to see whythe program did not run. Check for proper system



requirements to be met and all environment variablesto be set correctly (for example, the ulimit command onAIX, Linux, Solaris, and HP-UX systems). Clues to thisproblem might also be found in the ibmslapd.log file. Ifno previous error messages were printed, contact IBMSoftware Support. Make sure you have all log filesavailable to send to IBM Software Support if they arerequired.

GLPSRV089E Server unable to start because theserver could not write to the slapd.pidfile.

Explanation: The server is unable to write the processID to the directory server instance's slapd.pid file.

User response: Verify that the location where the PIDfile is going to be created is writable and accessible byyour user ID. This file should be created in the localtmp directory of the directory server instance (theibmslapd-instancename\tmp directory).

GLPSRV090E Maximum number of operations pertransaction, maximum operations,exceeded.

Explanation: The maximum number of operations pertransaction has been exceeded.

User response: Reduce the number of operations inthe transaction and try again.

GLPSRV091E Null based one level search is notsupported.

Explanation: The requested NULL based one levelsearch is not supported.

User response: Modify the client request so that itdoes not specify a one level search.

GLPSRV092E No values for type attribute name.

Explanation: An attribute without a value wasspecified on an add operation.

User response: Make sure each attribute has at leastone value on the add operation.

GLPSRV093E version number is an unsupportedLDAP version.

Explanation: The bind operation requires the client tospecify the version of LDAP protocol. Only version 2and version 3 are supported.

User response: Make sure the client application isusing LDAP version 2 or 3.

GLPSRV094E The value attribute value is not a validvalue for attribute ibm-slapdServerBackend. The attribute takeseither RDBM or PROXY as its values.

Explanation: The server encountered a value that isnot valid in the configuration file.

User response: Ensure that the value ofibm-slapdServerType is set to either 'PROXY' or'RDBM', depending on whether you want a proxy orstandard directory server.

GLPSRV095E Plugin type plugin type with pathplugin path is not supported. Plugin notloaded.

Explanation: A plug-in type that is not supported wasencountered in the server configuration.

User response: Make sure only supported plug-intypes are specified.

GLPSRV096E Bind attempt by DN DN and sourceIP address IP Address was unsuccessful.

Explanation: Due to authentication problems, a bindattempt from a client was not successful.

User response: Make sure the client uses the correctcredentials.

GLPSRV097E Internal processing error in the server;return code return code from pthreadlibrary.

Explanation: One of the pthread library functionsfailed.

User response: Make sure the operating system isproperly configured.

GLPSRV099E Unable to open audit log file'filename'.

Explanation: The server is unable to open the auditlog file.

User response: Make sure the server instance ownerhas the appropriate access to the directories in the filename path and to the file itself.

GLPSRV100E Audit log file 'filename' is full, unableto log any more records.

Explanation: The audit log is full. The server can nolonger add audit messages to the log.

User response: Clear the audit log file, move it to adifferent filesystem (or drive) that has more space.



GLPSRV101E Problems retrieving entry 'entry DN'in the server configuration.

Explanation: The server could not retrieve an entryfrom the server configuration file.

User response: Verify that the DN and data for theentry are correct.

GLPSRV103E Found an unknown attribute 'attributename' in entry 'entry DN'.

Explanation: An unknown attribute was encounteredin one of the configuration file's entries.

User response: Make sure correct attributes arespecified for all entries.

GLPSRV106E Communications error: error string.

Explanation: Critical communication error occurred.

User response: Make sure the TCP/IP protocol stackis configured correctly.

GLPSRV114E Server failed to start normally withSSL; starting in configuration onlymode without SSL.

Explanation: The server failed to start in normal modewith SSL so it is starting in configuration only mode toallow configuration changes to address the problem.

User response: Make sure two different ports for SSLand non-SSL are specified. Verify all SSL serverconfiguration settings.

GLPSRV115E The operator is not in the sameprimary group as the directory serverinstance owner 'instance name'. Onlyusers in the same primary group as thedirectory server instance owner can starta directory server instance.

Explanation: The program failed to start because theuser does not have the same primary group as thedirectory server instance owner.

User response: Validate the primary group of thedirectory server instance owner. If the user does nothave the same primary group as the owner, the user isnot authorized to start the directory server instance.

GLPSRV119E Failed to create Windows service fordirectory server instance: 'instance name'.

Explanation: The directory server instance could notbe installed as a Windows service.


GLPSRV122E Failed to stop directory serverinstance: 'instance name'.

Explanation: The program failed to stop the directoryserver instance. The error might have occurred becausethe directory server instance was already stopped.

User response: Verify that directory server instanceexists and is running. If necessary, stop the directoryserver instance manually using the kill command onAIX, Linux, Solaris, and HP-UX systems or through theWindows Services panel on Windows systems.

GLPSRV123E Unable to stop directory serverinstance 'instance name' because the stateof the server cannot be determined.

Explanation: An attempt was made to stop thedirectory server instance and its state could not bedetermined.

User response: This error most likely occurredbecause the user does not have sufficient access tocheck the status of the directory server instance. Verifythat the directory server slapd.pid file can be read bythe user.

GLPSRV126E Failed to delete Windows service fordirectory server instance: 'instance name'.

Explanation: The program failed to delete theWindows service for the directory server instance.

User response: Verify that the Windows service for thedirectory server instance still exists. If it does not exist,no further action is required. If the Windows servicedoes exist, attempt to recreate the problem using thesame directory server instance.

GLPSRV127E The -k and -i options cannot be usedtogether.

Explanation: A command was issued to stop thedirectory server instance and register the directoryserver instance as a Windows service at the same time.

User response: Specify only the -k or -i option.

GLPSRV128E The -k and -u options cannot be usedtogether.

Explanation: A command was issued to stop thedirectory server instance and unregister the directoryserver instance as a Windows service at the same time.

User response: Specify only the -k or -u option.

GLPSRV129E The -i and -u options cannot be usedtogether.

Explanation: A command was issued to register andunregister the directory server instance as a Windowsservice at the same time.



User response: Specify only the -i or -u option.

GLPSRV131E The -k and -c options cannot be usedtogether.

Explanation: A command was issued to stop thedirectory server instance and start the directory serverinstance in console mode at the same time.

User response: Specify only the -k or -c option.

GLPSRV132E The -k and -a options cannot be usedtogether.

Explanation: A command was issued to stop thedirectory server instance and start the directory serverinstance in configuration only mode at the same time.

User response: Specify only the -k or -a option.

GLPSRV133E The -k and -n options cannot be usedtogether.

Explanation: A command was issued to stop thedirectory server instance and start the directory serverinstance at the same time.

User response: Specify only the -k or -n option.

GLPSRV135E A problem was encountered whileretrieving server configuration entriesfor subtree 'subtree DN'.

Explanation: The server could not retrieve the entriesunder the specified DN from the server configuration.

User response: Verify that the specified subtree existsin the server configuration file. If it does not, considercopying the subtree from the installed serverconfiguration template file.

GLPSRV136E text

Explanation: This message reserved for use by IBMSoftware Support.

GLPSRV137E The Administrative Password Policysettings in the server configuration arenot valid.

Explanation: One or more Administrative PasswordPolicy settings in the server configuration are not valid.

User response: Make sure that AdministrativePassword Policy values are valid.

GLPSRV138W A client connection from IP addressbound as bind DN closed by the server.

Explanation: The server has closed the specified clientconnection as a result of an unbind extended operation.

User response: See the IBM Security Directory Server

Administration Guide for more information.

GLPSRV139W A client connection from IP addressbound as bind DN closed by the server.

Explanation: The server has closed the specified clientconnection as a result of reaping (connections that metadministrative criteria).

User response: Verify that the reaping parameters areacceptable. See the IBM Security Directory ServerAdministration Guide for more information.

GLPSRV140E An unsupported operation wasrequested within a transaction.Transaction transaction ID rolled back.

Explanation: A client sent an unsupported operationwithin a transaction.

User response: Verify that the client requesting thetransaction only requests update operations.

GLPSRV141E An unsupported operation wasrequested within a transaction after aprepare transaction extended operationrequest. Transaction transaction ID rolledback.

Explanation: A client sent an unsupported operationwithin a transaction after a prepare transactionextended operation request. Only a commit or roll backrequest is allowed following a prepare transactionextended operation.

User response: Verify that the client requesting thetransaction only sends a roll back or commit requestfollowing a prepare transaction extended operation.

GLPSRV142E An unsupported extended operationwas requested within a transaction aftera prepare transaction extended operationrequest. Transaction transaction ID rolledback.

Explanation: A client sent an unsupported extendedoperation within a transaction after a preparetransaction extended operation request. Only a commitor roll back request is allowed following a preparetransaction extended operation.

User response: Verify that the client requesting thetransaction only sends a roll back or commit requestfollowing a prepare transaction extended operation.

GLPSRV143E Transaction time limit betweenprepare and commit or roll backexceeded. Transaction transaction IDrolled back.

Explanation: The time between the prepare extendedoperation and the commit or roll back extended



operation was greater than the configured limit. Thetransaction will be rolled back to free up resources.

User response: Decrease the amount of time betweenthe prepare transaction extended operation and thecommit or rollback extended operations.

GLPSRV144E Extended operation OID failed, optiondecimal option is not valid for thisrequest.

Explanation: The option is not valid for the specifiedextended operation.

User response: Make sure the correct option is usedwith the extended operation request.

GLPSRV145E The modify request failed becauseproxy split name is not unique.

Explanation: The modify request failed because theibm-slapdProxySplitName specified was not uniquewithin the configuration file.

User response: Specify a unique ibm-slapdProxySplitName and retry the modify request.

GLPSRV146E The add request failed because proxysplit name is not unique.

Explanation: The add request failed because theibm-slapdProxySplitName specified was not uniquewithin the configuration file.

User response: Specify a unique ibm-slapdProxySplitName and retry the add request.

GLPSRV147W Connection write time limitexceeded. Connection from IP addressbound as bind DN will be closed.

Explanation: The server has tried to write messages tothe client at the specified IP address. The writeoperation has timed out. The server is going to shutdown the connection to the client.

User response: Identify the client application andensure that the application receives messages from theserver in a timely manner.

GLPSRV148W Transaction with ID transaction IDsubmitted by bind DN will be rolledback due to an error (LDAP error) in anoperation.

Explanation: The server has encountered an error inthe processing of the transaction and is rolling back anyupdates made as a part of the transaction.

User response: The client application also receives areturn code and message, so no action from thedirectory administrator is required.

GLPSRV149E Ulimit entry entry DN is not presentin the server configuration.

Explanation: The ulimit entry in the serverconfiguration identifies the prescribed system limits forthe server process.

User response: Copy the entry from the installedserver configuration template file and add it to theserver configuration file for the failing server instance.

GLPSRV150E Input not valid for option ulimitoption.

Explanation: The value for the specified ulimit optionin the server configuration is not valid.

User response: Correct the value for the specifiedulimit option in the server configuration and restart theserver.

GLPSRV151E Prescribed soft limit is out of range orgreater than hard limit value for optionulimit option.

Explanation: The value for the specified ulimit optionin the server configuration is too large or too small.

User response: Correct the value for the specifiedulimit option in the server configuration and restart theserver.

GLPSRV153W The server was not able to accept arequested client connection. Themaximum capacity of message has beenreached. This error has occurred messagetimes.

Explanation: This is a limit imposed the operatingsystem.

User response: Check for idle connections that can bedropped. Modify the server configuration parametersfor reaping idle connections.

GLPSRV154E A new persistent search request couldnot be handled by the server.

Explanation: The server limit for maximum number ofconcurrent persistent searches was exceeded.

User response: Unbind some existing persistentsearches, increase the maximum number of concurrentpersistent searches allowed, or wait until somepersistent searches have completed and retry theoperation.

GLPSRV161W There are no AdministrativePassword Policy settings in the serverconfiguration.

Explanation: There are no Administrative PasswordPolicy settings in the server configuration file. The



server will start without Administrative PasswordPolicy enabled.

User response: Verify that the AdministrativePassword Policy entry is in the server configurationfile.

GLPSRV162W Referral 'referral' not valid.

Explanation: The referral specified in the serverconfiguration file is not in the supported format.

User response: Verify the referral in the configurationfile.

GLPSRV163E Pass-through bind failed on 'URL' forentry 'bind DN'.

Explanation: Pass-through authentication bind failedfor specified entry using the given host and port.

User response: Verify the following: The pass-throughdirectory server is running on the specified hostnameand port number. If attribute mapping is configured,then the password of the mapped DN on thepass-through directory matches the password supplied.If the entry contains ibm-ptaLinkAttribute, it does nothave the value _DISABLE_. If attribute mapping isconfigured as 'ibm-slapdPtaAttMapping: attr1 $ attr2 ',the entry contains attribute 'attr1'. If attribute mappingis configured, the mapped entry must be present on thepass-through directory.

GLPSRV164E Pass-through bind failed because theattribute 'attribute name' has multiplevalues in entry 'EntryDN'.

Explanation: The pass-through authentication bindfailed because attribute mapping is configured and theentry contains multiple values for the attributeconfigured in attribute mapping.

User response: The attribute configured in theattribute mapping must have a single value in theentry. If there are multiple values, pass-throughauthentication does not work.

GLPSRV165E Pass-through authentication faileddue to a timeout.

Explanation: The pass-through directory did notrespond within the specified time limit.

User response: Try one of the following: Check to seeif the pass-through directory is running. Increase thetime limit and restart the directory server instance.Check for network failures.

GLPSRV166E The pass-through search to getmapped DN for the bind DN 'bind DN',returned more than one entry.

Explanation: The error occurred because pass-throughauthentication is configured with attribute mappingand the search for the bind DN on the pass-throughdirectory returned more then one entry.

User response: Set the attribute mapping so that thevalue of the attribute is unique in the pass-throughdirectory.

GLPSRV167E Nested subtrees '1st subtree DN' and'2nd subtree DN' found in pass-throughauthentication configuration.

Explanation: Nested subtrees are not allowed inpass-through authentication configuration

User response: Nested subtrees are not allowed inpass-through authentication. Modify the configurationto remove nested subtrees.

GLPSRV168E Attribute mapping is configured forattribute 'attribute name', which is notpresent in the schema.

Explanation: If attribute mapping is configured as'ibm-ptaAttMapping: attr1 $ attr2 ', the attribute 'attr1'MUST be present in schema.

User response: Add the attribute in the schema orselect some other attribute for attribute mapping.

GLPSRV169W Attribute mapping is configured forattribute 'attribute name', which is notpresent in the schema for pass-throughdirectory server 'URL'.

Explanation: The attribute mapping is configured as'ibm-ptaAttMapping: attr1 $ attr2', and attribute 'attr2'is not present in the pass-through directory schema.

User response: Pass-through bind might fail becausethe attribute is not present in the pass-throughdirectory schema. Add this attribute.

GLPSRV170E Attribute name 'attribute name' that isnot valid specified in attribute mapping.

Explanation: The specified attribute name is not valid.

User response: Specify a valid attribute name andretry.

GLPSRV171E Specified attribute mapping 'attributemap' is not valid.

Explanation: Attribute mapping should be in the formattr1 $ attr2, where attr1 and attr2 are both validattribute names and attr1 MUST be present in the localschema.

GLPSRV162W • GLPSRV171E


User response: Specify a valid attribute mapping andretry.

GLPSRV172E Pass-through attribute mapping isconfigured for bind DN 'bind DN' butthe entry is missing.

Explanation: Entry must be present on the IBMSecurity Directory Server to perform pass-throughauthentication if attribute mapping is configured.

User response: Check to see if the entry is missing.Add the appropriate entry.

GLPSRV173E Value for attribute 'attribute name' notvalid in entry 'entry DN'.

Explanation: Specified attribute does not have a validvalue.

User response: Specify the correct value for theattribute in the entry shown.

GLPSRV174E Pass-through subtree 'subtree DN'conflicts with restricted subtree 'restrictedsubtree DN'.

Explanation: The pass-through subtree shown conflictswith the restricted list of subtrees.

User response: Specify a pass-through subtree thatdoes not conflict with any of the restricted subtrees.

GLPSRV175W Unable to check schema ofpass-through directory 'URL' forattribute 'attribute name', received returncode LDAP return code.

Explanation: An error occurred while verifying thepass-through directory schema for existence of theattribute.

User response: Take appropriate action based on thereturn code.

GLPSRV177W Directory server instance unable toshut down; exiting now.

Explanation: The server was unable to shutdowngracefully as requested within the maximum allowedtime.

GLPSRV178E Internal error while processing plugintype plugin type with path plugin path.

Explanation: A plug-in specified in the serverconfiguration could not be processed.

User response: Make sure the plug-in is valid and thetype supported.

GLPSRV179E The pass-through URL 'URL' is notvalid.

Explanation: The format used to configure the URLidentifying the pass-through directory server isincorrect.

User response: Ensure that the URL identifying thepass-through directory server is in LDAP URL format.

GLPSRV181E The pass-through authentication bindfailed during attribute mapping withrc=rc.

Explanation: The server must bind to thepass-through directory server for pass-throughauthentication to work and the bind failed.

User response: Check the return code. Verify thatpass-through directory is running. Verify that bind DNand password given in configured for attributemapping is correct.

GLPSRV182E Failed to connect to pass-throughdirectory 'URL'.

Explanation: The server must connect to thepass-through directory server for pass-throughauthentication to work and this connection could notbe established.

User response: Verify that Pass-through directory isrunning. Check for a network failure. If SSL isconfigured verify that the key file and password arecorrect. Contact IBM Software Support if problempersists.

GLPSRV183E Unable to modify log path to 'path' forthe 'entry DN'. The file already exists onthe system.

Explanation: The modify request of the log path to thespecified value is not allowed. A file already exists onthe system with that path.

User response: Verify the requested value. Delete theexisting file on the system or request a new location.

GLPSRV184E Unable to modify log path to 'path' forthe 'entry DN'. The 'entry DN' entry isalready configured with that log filepath.

Explanation: The modify request of the log path to thespecified value is not allowed. A different log file isalready configured to use that path.

User response: Request a different location.



GLPSRV185E Unable to modify log path to 'path' forthe 'entry DN'. The file cannot bewritten to.

Explanation: The modify request of the log path to thespecified value is not allowed. The system is unable tocreate a file in the location.

User response: Request a different location.

GLPSRV186W The proxy server has temporarilysuspended reading client requests fromthe network.

Explanation: The proxy server has temporarilysuspended reading client requests from the networkbecause there are no free back-end connections for theproxy server to process additional requests.

User response: No immediate action is required. Theproxy server will start reading client request from thenetwork as soon as a free back-end connection becomesavailable. If the problem persists consider increasingthe number of back-end connections in the serverconfiguration.

GLPSRV188E Sort control missing in virtual listview search request.

Explanation: A sort control is a pre-requisite forprocessing a VLV search request.

User response: Re-send the virtual list view searchrequest with appropriate sort control.

GLPSRV191E Terminating server because ofinitialization errors.

Explanation: The server is unable to run because ofinitialization errors.

User response: View earlier error messages to see whythe program did not run. Check for proper systemrequirements to be met and all environment variablesto be set correctly (for example, the ulimit command onAIX, Linux, Solaris, and HP-UX systems). Check ifthere are any DB2 licensing or database connectionissues. Clues to this problem might also be found in theibmslapd.log file. If no previous error messages wereprinted, contact IBM Software Support. Make sure youhave all log files available to send to IBM SoftwareSupport if they are required.

GLPSRV192E Server is unable to start because theserver could not write to theslapd.properties file.

Explanation: The server is unable to write the startupdetails to the properties file of the directory serverinstance.

User response: Verify that the location where theslapd.properties file is going to be created is writable

and accessible by your user ID. This file should becreated in the local tmp directory of the directoryserver instance (the ibmslapd-instancename\tmpdirectory).

GLPSRV203W The server has temporarilysuspended reading client requests fromthe network. There are number ofwritewaiters of number of total workersworker threads attempting to writeresults.

Explanation: The server has temporarily suspendedreading client requests from the network because thereare no free worker threads for the server to processadditional requests. The number of databaseconnections may be too small for the current workload.

User response: The server will start reading clientrequest from the network as soon as a worker threadbecomes available. Increase the number of workerthreads in the server configuration by increasing thenumber of database connections.

GLPSRV204W The server has temporarilysuspended reading client requests fromthe network number of times times. Thereare number of writewaiters of number oftotal workers worker threads attemptingto write results.

Explanation: The server has temporarily suspendedreading client requests from the network because thereare no free worker threads for the server to processadditional requests. The number of databaseconnections may be too small for the current workload.This message will only be logged one time in any fiveminute interval.

User response: The server will start reading clientrequest from the network as soon as a worker threadbecomes available. Increase the number of workerthreads in the server configuration by increasing thenumber of database connections.

GLPSRV208W Persistent search is not supported onsubtree dn.

Explanation: A persistent search cannot be run withthe given subtree.

User response: Remove the -c option or specifyanother subtree for the search.

GLPSRV209W Message for support team: additionaltext.

Explanation: An error has occurred, as detailed in theadditional text. This information will be used be IBMSupport to further diagnos the issue.

User response: Contact IBM Support with theadditional information.



GLPSRV217W Invalid value 'value' set foribm-slapdPwEncryption attribute.Assuming AES256 encryption format.

Explanation: Attribute ibm-slapdPwEncryptionaccepts only one of following values: none, aes128aes192, aes256, crypt, sha, ssha, md5, sha224, sha256,sha384, sha512, ssha224, ssha256, ssha384, or ssha512 IfSHA-2 feature is not enabled then sha224, sha256,sha384, sha512, ssha224, ssha256, ssha384, and ssha512are not allowed.

User response: If SHA-2 feature needs to be enabled,ibm-slapdUseNonFIPSCrypt should be set to true incn=configuration entry, otherwise set appropriateencryption method.

GLPSRV218E User provided encrypted string isbadly formatted.

Explanation: User has provided pre-encrypted stringin the operation. This string is not properly formattedand can not be decrypted. Such an addition is notallowed.

User response: Supply correct string in operation.Alternatively clear text string should be provided withserver side encryption configuration. Server will thenencrypt it before storing in database.

GLPSRV224E No entry matching the search criterion'value' was found.

Explanation: User attempted to bind with the value ofthe configured unique attribute. However, no entry thatcontains the attribute value was found on the server.

User response: Ensure that the value of the uniqueattribute is correct, and run the operation again.

GLPSRV225E Too many entries matching the searchcriterion 'value' were found.

Explanation: User attempted to bind with the value ofthe configured unique attribute. However, multipleentries that contain the attribute value were found onthe server.

User response: For a bind operation with an attributeto be successful, the value of the configured attributemust be unique. Ensure to configure an attribute thatcontains a unique value for bind operations.

GLPSRV226E The maximum filter limit that is setin IDS_MAX_SEARCH_FILTER_LEVEL,max filter exceeded for the search on thehost, host with conn id, conn id and isbound with dn=dn

Explanation: The maximum limit of the search filterlevel exceeds in the search.

User response: Ensure that the search filter level is in

the specified limits for search.

GLPSRV2286E A search on pass-through server'host', port 'port', url 'url' failed.

Explanation: The search operation on a pass-throughserver failed.

User response: Ensure that the pass-through servercontains valid credentials for authentication.

GLPSSL002E File I/O error on opening SSL keydatabase file key database filename.

Explanation: The SSL key database used by the LDAPdirectory and administration servers cannot be read.

User response: Ensure that the file permissions on theSSL key database file are correct.

GLPSSL003E Open of SSL key database file keydatabase filename failed.

Explanation: The SSL key database used by the LDAPdirectory and administration servers cannot be opened

User response: Ensure that the file permissions on theSSL key database file are correct.

GLPSSL004E SSL key database file key databasefilename is in an unknown format.

Explanation: The file configured as the SSL keydatabase to be used by the LDAP directory andadministration servers is not a CMS key database file.

User response: Ensure that the file configured to beused as the SSL key database is a CMS key databasefile.

GLPSSL005E The password supplied for key databasefile key database filename is not correct.

Explanation: The SSL key database used by the LDAPdirectory and administration servers cannot be openedusing the password supplied in the configuration.

User response: Correct the password for the SSL keydatabase and try to restart.

GLPSSL006E A memory allocation error occurredprocessing SSL key database file keydatabase filename.

Explanation: There is not enough memory available toprocess the SSL key database file.

User response: Increase the amount of memoryavailable and try to restart.

GLPSRV217W • GLPSSL006E


GLPSSL007E SSL socket initialization failed due to aproblem with creating the key pair.

Explanation: Secure socket initialization failed due toa problem with creating the key pair during the SSLhandshake.


GLPSSL008E An incorrect label was specified for SSLkey database key database filename.

Explanation: The supplied key label is a duplicate.

User response: Supply a label that is not already inthe SSL key database.

GLPSSL009E An incorrect value of cipher spec wasgiven for the SSL cipher specification.

Explanation: The specified SSL cipher is not valid.

User response: Correct the cipher specification in theconfiguration and restart the server.

GLPSSL010E No SSL ciphers were specified.

Explanation: No SSL ciphers were specified in theconfiguration.

User response: Correct the configuration to specify atleast one cipher and restart the server.

GLPSSL011E The certificate in the SSL key databasefile key database filename has expired.

Explanation: The certificate to be used by the LDAPdirectory or administration server has expired in SSLkey database file.

User response: Specify the label of an unexpiredcertificate in the SSL key database file in theconfiguration and restart the server.

GLPSSL012E The certificate certificate label in the SSLkey database file is not valid.

Explanation: The certificate to be used by the LDAPdirectory or administration server in the SSL keydatabase file is not valid.

User response: Specify the label of a valid certificatein the SSL key database file in the configuration andrestart the server.

GLPSSL013E The certificate is of an unsupported typein the SSL key database file key databasefilename.

Explanation: The certificate from the SSL key databasefile is of an unsupported type.

User response: Specify the label of a supported type

of certificate in the SSL key database file in theconfiguration and restart the server.

GLPSSL014E No certificate exists in SSL key databasefile filename.

Explanation: No certificate exists in the SSL keydatabase file.

User response: Obtain a valid certificate for the serverand add it to the SSL key database file beforeattempting to restart the server.

GLPSSL015E The underlying secure socket wasclosed.

Explanation: The SSL handshake did not completesuccessfully.

User response: Ensure that the client supplied thenecessary information to complete the SSL handshake.

GLPSSL016E An SSL error of error code wasencountered contacting consumer serverhost name, port port number.

Explanation: The supplier server could not contact theconsumer server using SSL.

User response: Ensure that the consumer server canbe contacted using SSL with the information availablefrom the supplier's SSL key database. In particular,check that the supplier server has a signer certificatefor the consumer.

GLPSSL017E The required SSL shared libraries couldnot be loaded.

Explanation: The shared libraries required for SSL areloaded dynamically. A problem was encounteredloading these libraries.

User response: Ensure that the correct GSKit versionis installed properly and restart the server.

GLPSSL018E The required SSL shared librariesencountered an internal load error.

Explanation: The shared libraries required for SSL areloaded dynamically. A problem was encounteredloading these libraries.

User response: Ensure that the correct GSKit versionis installed properly and restart the server.

GLPSSL019E The SSL layer has reported anunidentified internal error, SSLextended error code:error code.

Explanation: An SSL library function used by theLDAP directory or administration server failed forsome unspecified reason.

GLPSSL007E • GLPSSL019E



GLPSSL020E The SSL layer has reported a badparameter.

Explanation: An SSL library function used by theLDAP directory or administration server has reportedthat it was supplied a bad parameter.


GLPSSL021E An attempt has been made to use adomestic key database with an exportversion of the SSL library.

Explanation: No distinctions are made presentlybetween domestic and export versions of SSL, so thismessage should not appear. It is included here forcompleteness.


GLPSSL022E Secure socket client authentication erroroccurred.

Explanation: Secure socket client authentication erroroccurred.

User response: Verify that the SSL Client is valid.

GLPSSL023W Attempted to configure server for SSLin a non-SSL version of the product.

Explanation: The server that is running is a non-SSLversion of the product; SSL cannot be configured onthis version of the server.

User response: Get an SSL version of the server if youwant to configure the server for SSL.

GLPSSL024E Failed to start with SSL. Starting inconfiguration only mode without SSL.

Explanation: The server was unable to start using SSL.It is starting in configuration mode only without SSL.

User response: Check that the SSL port being used isvalid and is not the same as the non-SSL port. Aftercorrecting any problems, restart the server.

GLPSSL026E SSL socket initialization failed due to aproblem with creating a handle.

Explanation: Secure socket initialization failed due toa problem with creating the required handle duringSSL handshake.


GLPSSL027E SSL socket initialization failed due to aproblem with initializing a handle.

Explanation: Secure socket initialization failed due toa problem with initializing the required handle duringSSL handshake.


GLPSSL031W The server is operating in FIPS modefor the SSL layer but not the underlyingcryptographic layer.

Explanation: An error occurred during initialization ofGSKit in FIPS mode. The server starts in configurationmode.

GLPSSL033E Unable to load the specified PKCS#11library library.

Explanation: Attempt to load the specified libraryfailed. The server starts in configuration mode.

User response: Specify the correct path and file namefor the PKCS#11 library to be used for cryptographicoperations.

GLPSSL034E A PKCS#11 token token is not present inthe slot.

Explanation: Unable to find the PKCS#11 token namein the PKCS#11 crypto hardware slot.

User response: Verify that the name of the tokenspecified in the server configuration file for SSL iscorrect. The PKCS#11 token name specified must bepresent on the slot created on the PKCS#11 cryptohardware used for cryptographic operations.

GLPSSL035E The password/pin to access the PKCS#11token is not valid.

Explanation: The PKCS#11 hardware passwordsupplied in the directory server configuration is notcorrect.

User response: Correct the PKCS#11 token passwordin the configuration and restart the server.

GLPSSL036E A PKCS#11 token label token label is notvalid.

Explanation: The SSL certificate label specified in theconfiguraion file is invalid.

User response: Specify the correct certificate labelpresent in the PKCS#11 crypto hardware slot used bythe directory server for cryptographic operations andrestart the server.

GLPSSL020E • GLPSSL036E


GLPSSL038W Unable to start the server in FIPSMode. Turning off the FIPS Support.

Explanation: An error occurred during initialization ofGSKit in FIPS mode. The server starts in configurationmode.

GLPSSL040E An incorrect value of protocol was givenfor the security protocol specification.

Explanation: The specified protocol is not valid.

User response: Correct the protocol specification inthe configuration and restart the server.

GLPSSL041E An incorrect value of mode was given forthe Suite B specification.

Explanation: The specified Suite B mode is not valid.

User response: Correct the Suite B specification in theconfiguration and restart the server.

GLPSSL042E An incorrect value of sigalg was givenfor the signature algorithm specification.

Explanation: The specified signature algorithm is notvalid.

User response: Correct the signature algorithmspecification in the configuration and restart the server.

GLPUCH004E Failed to remove change log fromdirectory server instance: 'instance name'.

Explanation: The program failed to remove thechange log from the directory server instance.


GLPUCH007E Failed to unconfigure change logdatabase 'database name' for directoryserver instance: 'DB2 instance'.

Explanation: An internal error occurred while tryingto unconfigure the change log database in the directoryserver instance configuration file.


GLPUCH008E A change log database is notconfigured for directory server instance'instance name'.

Explanation: Tried to delete a change log databasewhich is not configured.

User response: Drop the change log database for adirectory server instance only if change log database isconfigured.

GLPUCH009E A database instance is not configuredfor directory server instance 'instancename'.

Explanation: An attempt to delete a change logdatabase failed because no database instance isconfigured for the directory server instance.

User response: Drop the change log database for adirectory server instance only if the database instanceand database are configured. Check the contents of theibmslapd.conf file of the directory server instance andverify that it has the correct database informationconfigured.

GLPUCH010E Unable to unconfigure the changelog. No change log is configured fordirectory server instance 'instance name'.

Explanation: A change log database can only beunconfigured if a change log is already configured.


GLPUCH012E An internal error occurred whilerunning the idsucfgchglg command.

Explanation: An internal error occurred while runningidsucfgchglg command. This might have been causedbecause the program ran out of memory.


GLPUCH013W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPSSL038W • GLPUCH013W


GLPUDB004E Failed to remove the DB2 databasefrom directory server instance: 'instancename'.

Explanation: The program failed to remove the DB2database from the directory server instance.


GLPUDB007E Failed to unconfigure database'database name' for directory serverinstance: 'DB2 instance'.

Explanation: An internal error occurred while tryingto unconfigure the database in the directory serverinstance configuration file.


GLPUDB008E A database is not configured fordirectory server instance 'instance name'.

Explanation: Tried to delete a database for a directoryserver instance and no database is configured.

User response: Only try to drop the database for adirectory server instance if a database already exists.

GLPUDB009E Failed to unconfigure local loopbackfor directory server instance: 'instancename'.

Explanation: The program failed to unconfigure localloopback for the directory server instance.

User response: Check the directory server instanceibmslapd.conf file and see if the local loopback aliasattribute still exists. If it does, remove the attributefrom the ibmslapd.conf file.

GLPUDB010E A database is not configured fordirectory server instance 'instance name'.

Explanation: Starting with the IBM Tivoli DirectoryServer 6.1 release this message is deprecated. Tried todelete a database for a directory server instance and nodatabase is configured.

User response: Only try to drop the database for adirectory server instance if a database already exists.

GLPUDB011E A database instance is not configuredfor directory server instance 'instancename'.

Explanation: Tried to delete a database and nodatabase instance is configured for the directory serverinstance.

User response: Only try to drop the database for adirectory server instance if the database instance anddatabase instance are configured. Check the contents ofthe ibmslapd.conf file of the directory server instanceand verify that it has the correct database informationconfigured.

GLPUDB012E An internal error occurred whilerunning the idsucfgdb command.

Explanation: An internal error occurred while runningthe idsucfgdb command. This might have been causedbecause the program ran out of memory.


GLPUDB013W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPUDB014E Unable to unconfigure database. Nodatabase is configured for directoryserver instance 'instance name'.

Explanation: A database can only be unconfigured if adatabase is already configured.


GLPUDB024E Inactive logs for directory serverinstance 'instance name' could not beremoved from location 'inactive log path'.

Explanation: An error occurred while trying toremove the directory which contains the inactive logfiles for the database that was dropped.

User response: The path containing the inactive logfiles should be removed by the system administratorusing the appropriate operating system commands.

GLPUDB004E • GLPUDB024E


GLPUDB025E The database backup file fordirectory server instance 'instance name'named 'backup file name' could not beremoved.

Explanation: An error occurred while trying toremove the backup file for the database that wasdropped.

User response: The database backup file should beremoved by the system administrator using theappropriate operating system commands.

GLPUSC002E An internal error occurred whilerunning the idsucfgsch command.

Explanation: An internal error occurred while runningidsucfgsch command. This might have been causedbecause the program ran out of memory.


GLPUSC003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPUSC006E Failed to remove schema file:'schemafile'.

Explanation: An error occurred while trying toremove the schema file from the configuration file ofthe directory server instance.


GLPUSC008E The schema file 'schemafile' does notexist in the configuration file of thedirectory server instance.

Explanation: The schema file cannot be removed fromthe configuration file of the directory server instancebecause it does not exist in the configuration file.

User response: Use idsxcfg to determine whichschema files exist in the configuration file of thedirectory server instance.

GLPUSC009E Deletion of a system defined schemafile 'schemafile' is not allowed.

Explanation: The schema file cannot be removed fromthe configuration file of the directory server instancebecause it is a system defined schema file. The serverwill not be able to start properly if the file is deleted.

User response: Use idsxcfg to determine whichschema files exist in the configuration file of thedirectory server instance. If a schema file needs to bedeleted, choose one that is not a system defined schemafile.

GLPUSC010E The -s option is required and is usedto specify the name of the schema file toremove.



GLPUSF002E An internal error occurred whilerunning the idsucfgsuf command.

Explanation: An internal error occurred while runningidsucfgsuf command. This might have been causedbecause the program ran out of memory.


GLPUSF003W The program did not completesuccessfully. View earlier error messagesfor information about the exact error.



GLPUSF006E Failed to remove suffix: 'suffix'.

Explanation: An error occurred while trying toremove the suffix file from the configuration file of thedirectory server instance.


GLPUDB025E • GLPUSF006E


GLPUSF008E The suffix 'suffix' does not exist in theconfiguration file of the directory serverinstance.

Explanation: The suffix cannot be removed from theconfiguration file of the directory server instancebecause it does not exist in the configuration file.

User response: Use idsxcfg to determine whichsuffixes exist in the configuration file of the directoryserver instance.

GLPUSF009E Deletion of the system defined suffix'suffix' is not allowed.

Explanation: A system-defined suffix can not beremoved from the configuration file of a directoryserver instance.

User response: Specify a suffix that is not asystem-defined suffix. A list of system-defined suffixescan be found in the IBM Security Directory ServerAdministration Guide.

GLPUSF010E The -s option is required and is usedto specify the name of the suffix toremove.



GLPWCO002E Select an entry.

Explanation: An entry must be selected for the currentoperation. No entry was selected.

User response: Select an entry for the requestedoperation to be successful.

GLPWCO003E Cannot connect to the server.

Explanation: Unable to connect to the directory serveror administration server. Check to be sure that theserver is running and reachable through the network.

User response: The error might have occurred for oneof the following reasons: The server might be down.Start or restart the server. There might be a problem inthe network. Check the network settings and check thatthe ping command to the server returns Success.

GLPWCO005E Select a row.

Explanation: An entry must be selected for the currentrequested operation to succeed. No entry was selected.

User response: Select a row from the table for therequested operation to succeed.

GLPWCO006E The server is running inconfiguration only mode. This taskcannot be initialized.

Explanation: The directory server is running inconfiguration only mode. In this mode, not all of theWeb Administration Tool tasks are available.

User response: If an error caused the directory serverto start in configuration only mode, correct the errorand start the directory server in normal mode; thenretry the task.

GLPWCO008E A server with the same hostnameand port already exists.

Explanation: The server with the specified hostnameand port is already registered with the WebAdministration Tool.

User response: Either change the hostname to one thatis not already registered, or change the port for thehostname so that the hostname and port combinationdoes not exist in the registered server list.

GLPWCO009E The administration port specified isalready in use.

Explanation: A server with the specified hostnameand administration port is already registered with theWeb Administration Tool. The specified administrationport is in use, either as the administration port or thenormal port of an existing server with same hostname.

User response: Either change the hostname to one thatis not already registered, or change the administrationport for the hostname so that the hostname andadministration port combination does not exist in theregistered server list.

GLPWCO010E Authentication error: Either the username or password (or both) is incorrect,or the password has expired.

Explanation: The login failed because the specifieduser name or password is incorrect, or the passwordmight have expired.

User response: Attempt to log in again by specifyingthe correct user name and password. If you still receivean error, then contact the directory server administrator.

GLPWCO011E Communications error: Unable toconnect to the specified LDAP server.

Explanation: The login failed because the connectionto the specified LDAP server could not be established.

User response: Check to be sure that the specifiedLDAP server is reachable through the network and thatthe LDAP server or its administration server isrunning.

GLPUSF008E • GLPWCO011E


GLPWCO012E Login failed: The server is currentlyunwilling to accept the bind. Thespecified account might be locked.

Explanation: The login failed because the specifieduser account is locked.

User response: Contact the directory serveradministrator to unlock the account.

GLPWCO013E LDAP server error: Unable toconnect to the specified LDAP serverusing the existing connection settings.

Explanation: The user login failed because of internalJNDI exceptions.

User response: Try using the tool again; if the errorpersists, contact the directory server administrator.

GLPWCO014E Internal error: An internal erroroccurred while trying to authenticate theuser.

Explanation: An internal error might have occurredfor one of the following reasons: A problem occurredwhile performing file operations. An internal objectreturned an unexpected result.

User response: Try using the tool again; if the errorpersists, contact the directory server administrator.

GLPWCO015E Parameter error: Either the user nameor the password or both were notspecified.

Explanation: User name and password are requiredfor a login to be successful.

User response: Type a valid user name and passwordand then try to log in.

GLPWCO016E Unknown error: Attempted to accessthis page without all requiredparameters.

Explanation: An attempt was made to access this pagewithout the required parameters.

User response: Do not open this page directly. Openthe page through the Web Administration Tool.

GLPWCO017E The current user does not haveaccess to this page. Current sessionmight have timed out.

Explanation: An attempt was made to access a pagefor which the current logged-in user does not haveaccess permission.

User response: Contact the directory serveradministrator to grant access to this page.

GLPWCO018E Error: Current password incorrect.

Explanation: The password provided does not matchthe existing password of the console administrator.

User response: Type a valid password for the consoleadministrator in the Current password field.

GLPWCO019E Error: Confirmation passwordincorrect.

Explanation: The values typed in the New passwordand Confirm new password fields must be exactly thesame. These fields are case-sensitive. The valuesspecified in the two fields do not match.

User response: Type the same value in the Newpassword and Confirm new password fields.

GLPWCO020W Are you sure you want to delete theselected server?

Explanation: Continuing with this operation willdelete the selected server from the list of registeredservers for the Web Administration Tool.

User response: Click OK to delete the selected serveror Cancel to cancel the delete operation.

GLPWCO021E Unauthorized access. The user is nota console administrator.

Explanation: The logged-in user does not haveauthorization to access this panel. Only consoleadministration users are allowed to access this panel.

User response: Log in as a console administrationuser to access this panel.

GLPWCO022W The password must be changedbefore access can be granted to theLDAP data.

Explanation: Password policy is enabled on thedirectory server. Password for the logged-in user mustbe changed before any action can be performed on thedirectory server.

User response: Change the password using theChange password panel under the User propertiessection and then try again to access the LDAP data.

GLPWCO023W The account is locked.

Explanation: The maximum number of login failureswas reached and the account was locked by the server.

User response: Contact the directory serveradministrator to unlock the account.

GLPWCO012E • GLPWCO023W


GLPWCO024W The password was reset and mustbe changed now.

Explanation: Password policy is enabled on thedirectory server. An administrator or another user withthe correct authority has reset the password. Thepassword must be set before the user can access thedirectory data.

User response: Change the user password.

GLPWCO025W The password cannot be changed.The user does not have the authority tomodify the password.

Explanation: Password policy is enabled on thedirectory server. The current user does not have accessrights to change the password.

User response: Contact the directory serveradministrator to change the password.

GLPWCO026W The current password was notsupplied or is not correct.

Explanation: Password policy is enabled on thedirectory server. The current password is required forthis operation to run. Either the password was notsupplied or an incorrect password was supplied.

User response: Provide the correct current passwordfor the account and request the operation again.

GLPWCO027W Incorrect password syntax.

Explanation: Password policy is enabled on thedirectory server. The syntax of the password isincorrect. Check for the following errors: The passwordis too short. The password does not contain theminimum number of required alphabetic characters.The password does not contain the minimum numberof required numeric and special characters. Thepassword has a character repeated more times than themaximum allowed. The new password does not haveenough characters that are different from those in thecurrent password.

User response: Type a valid password that meets allrequirements.

GLPWCO028W The password is too short.

Explanation: Password policy is enabled on thedirectory server. The password policy for the systemrequires that the password contain a minimum numberof characters; the password is too short.

User response: Type a password that contains at leastthe minimum number of characters required.

GLPWCO029W The current password is not oldenough and cannot be changed at thistime.

Explanation: Password policy is enabled on thedirectory server. The age of the password is less thanthe minimum time required between passwordchanges. The password cannot be changed at this time.

User response: Try changing the password at somelater point of time.

GLPWCO030W The password specified is incorrect.The password has already been used.

Explanation: Password policy is enabled on thedirectory server. This password was used earlier.Provide a new password.

User response: Type a new password that has neverbeen used.

GLPWCO031W number of binds LDAP binds remainbefore the account will be locked.

Explanation: Password policy is enabled on thedirectory server. Some number of grace logins isavailable before the user account is locked. The numberof grace logins remaining is shown in the message.

User response: Change the password from the Changepassword panel under User properties to prevent theaccount from being locked.

GLPWCO032W Password will expire after number ofseconds seconds.

Explanation: Password policy is enabled on thedirectory server. The account will expire after thespecified number of seconds.

User response: Change the password from the Changepassword panel under User properties to prevent theaccount from being locked.

GLPWCO033E Connected to administration server.This task cannot be initialized.

Explanation: The directory server is not running. TheWeb Administration Tool is connected to theadministration server. In this mode, not all of the WebAdministration Tool tasks are available.

User response: Start the directory server in normalmode; then retry the task.

GLPWCO034E Server with the same server namealready exists.

Explanation: The server with the specified servername is already registered with the WebAdministration Tool.

GLPWCO024W • GLPWCO034E


User response: Change the server name to a namethat is not already registered and does not exist in theregistered server list.

GLPWCO035W Connected to administration server.Not all operations are available.

Explanation: The directory server is not running. TheWeb Administration Tool is connected to theadministration server. In this mode, not all of the WebAdministration Tool operations are available.

User response: Start the directory server in normalmode to view all the values on the panel.

GLPWCO036E Incorrect port in Server entry.

Explanation: The error might have occurred for one ofthe following reasons: The port number must be innumeric format. The error occurred as the specifiedport number cannot be converted to a numeric type.The port number must be a positive number. The erroroccured as the specified port number is either anegative number or zero.

User response: Type the port number in numericformat such that it is greater than zero..

GLPWCO037E Incorrect server entry. Provide theserver entry in the following format'hostname:port'.

Explanation: The server entry must be specified in theformat 'hostname:port. The error occurred because thespecified server entry is not in the required format.

User response: Specify the server entry in the format'hostname:port'.

GLPWCO038W Changes made to the schema are notpropagated to the back-end servers. Forchanging the schema of the back-endservers, changes must be made on theback-end servers.

Explanation: When logged in to a proxy server,changes made to the schema are not propagated toback-end servers. All schema changes to be made on aback-end server must be made when logged in to theback-end server.

User response: Log in to the back-end directory serverto change the schema.

GLPWCO039E Key database password does notmatch.

Explanation: The password provided for key databasedoes not match with the password in the passwordconfirmation field.

User response: Ensure that passwords in the key

database password field and password confirmationfield are the same.

GLPWCO040E Trust database password does notmatch.

Explanation: The password provided for trustdatabase does not match with the password in thepassword confirmation field.

User response: Ensure that passwords in the trustdatabase password field and password confirmationfield are the same.

GLPWCO041E Insufficient access rights.

Explanation: The loggedin user does not havesufficient access rights to perform the operation.

User response: Contact directory server administrator.

GLPWCO042E Password is required if an ssl keydatabase path is specified.

Explanation: Specify a password for an ssl keydatabase file.

User response: Ensure that a password is specified forssl key database if an ssl key database path is provided.

GLPWCO043E SSL key database path is required ifthe password for an ssl key databasefile is specified.

Explanation: Specify a key database path and filename of an ssl key database file.

User response: Ensure that a key database path andfile name is specified if the password for an ssl keydatabase file is provided.

GLPWCO044E SSL key database file name is notvalid.

Explanation: Specify a valid file name of an ssl keydatabase file.

User response: Ensure that a valid file name isprovided.

GLPWCO045E Password is required if an trustdatabase path is specified.

Explanation: Specify a password for an trust databasefile.

User response: Ensure that a password is specified fortrust database if an trust database path is provided.

GLPWCO035W • GLPWCO045E


GLPWCO046E Trust database path is required if thepassword for an trust database file isspecified.

Explanation: Specify a trust database path and filename of an trust database file.

User response: Ensure that a trust database path andfile name is specified if the password for an trustdatabase file is provided.

GLPWCO047E Trust database file name is not valid.

Explanation: Specify a valid file name of an trustdatabase file.

User response: Ensure that a valid file name isprovided.

GLPWDM001E An error occurred connecting toserver server name: error.

Explanation: An error might have occurred for one ofthe following reasons: Logged-in user does not havepermission to look up LDAP data. A problem occurredwhile modifying the LDAP data. The LDAP data beingaccessed has incorrect data or incorrect namingattributes or entries. A problem occurred while creatingthe initial context. A problem occurred while chasing areferral. The specified directory server does not supportthe requested directory operation. Synchronization andserialization issues caused a problem.

User response: Try to perform the operation again. Ifthe error persists, contact the directory serveradministrator.

GLPWDM002E An error occurred whiledisconnecting from the server servername: error.

Explanation: The server connection is not closedbecause an error occurred while closing the connection.If the program expects the server connection to beclosed, unexpected results might occur.

User response: If the server is behaving normally youcan safely ignore this message. If the WebAdministration Tool displays unexpected results,contact the directory server administrator.

GLPWDM003E An error occurred while addingentry entry DN : error.

Explanation: An error might have occurred for one ofthe following reasons: The DN being added wouldmodify a read-only tree. The DN being added isincorrect. The logged-in user does not have permissionto add an entry at the specified location. The parententry of the specified DN does not exist.Synchronization and serialization issues caused aproblem. Refer to the Java exception for moreinformation.


GLPWDM004E An error occurred while deleting theentry DN. The logged in user cannotdelete that user's own entry.

Explanation: Same as above

User response: Contact the directory serveradministrator to remove the account.

GLPWDM005E An error occurred while deletingentry entry DN: error.

Explanation: An error might have occurred for one ofthe following reasons: The DN being added wouldmodify a read-only tree. The logged-in user does nothave permission to add an entry at the specifiedlocation. The parent entry of the specified DN does notexist. Synchronization and serialization issues caused aproblem. The LDAP data specified for deletion doesnot conform to the naming syntax. Refer to the Javaexception for more information.

User response: Try to perform the operation again. Ifthe error persists, contact the directory serveradministrator.

GLPWDM006E The language tag already exists: tag.

Explanation: The specified language tag is alreadyadded to the directory server.

User response: Specify a new language tag that doesnot exist in the directory server.

GLPWDM007E Entry already exists: entry DN.

Explanation: The specified entry already exists.

User response: Specify a new value that is not presentin the directory server.

GLPWDM008E The user already exists: user DN.

Explanation: The specified user is already a memberof the group.

User response: Type a valid user name, which is notpart of the group already, from the realm.

GLPWDM009E The group already exists: user DN.

Explanation: The user is already a member of thespecified group.

User response: Type a valid group name, of which theuser is not a member, from the corresponding realm.

GLPWCO046E • GLPWDM009E


GLPWDM010E Cannot delete non-leaf node entryentry DN.

Explanation: An attempt was made to remove anentry that has entries below it in the tree that are in useby some other operation.

User response: Try again later, when the child nodesare not in use by another operation and can be deleted.If the problem persists, try deleting all the child nodesfirst, and then delete the current node.

GLPWDM011E Missing required attributes on entryentry DN: error.

Explanation: All required attributes must be presentwhen updating an entry in the directory server. Theerror occurred because some of the required attributesdid not have any value.

User response: Specify values for all requiredattributes and then try saving the modifications.

GLPWDM012E Error: Entry entry DN does not exist.

Explanation: The deletion operation failed because theentry to be deleted does not exist in the directoryserver.

User response: The entry might be absent for one ofthe following reasons: The specified entry was deletedearlier by some other operation and the current pagedisplays old data. Refresh the page to view the latestdata. The user might have specified an incorrect entry.Type the entry to be deleted again.

GLPWDM013E The current operation cannotcontinue.

Explanation: The current operation cannot continue.The operation reached a state where the initialnamespace has changed, and the operation must beterminated.

User response: Contact the directory serveradministrator for more information.

GLPWDM014E An error occurred opening thecontext for server server name: error.

Explanation: An error might have occurred for one ofthe following reasons: The logged-in user does nothave permission to look up LDAP data. The specifieddirectory server is not running or is unreachable. Thespecified directory server does not support therequested directory operation. Synchronization andserialization issues caused a problem. There is anotherproblem creating the initial context. Contact thedirectory server administrator.


GLPWDM015E An error occurred while retrievingattributes for entry : error.

Explanation: An error occurred while retrieving theattributes from the directory server. One of thefollowing might have occurred: The logged-in userdoes not have permission to look up LDAP data. TheDN whose attributes are being retrieved is incorrect orhas incorrect syntax or attribute values. The directoryserver is down or unreachable. Synchronization andserialization issues caused a problem.


GLPWDM016E An error occurred setting attributesfor entry : error.

Explanation: An error occurred while modifying thedirectory server data for one of the following reasons:The logged-in user does not have authorization tomodify the data. There is a problem such as networkconnectivity to the server, incorrect attribute values, orincorrect DN, while modifying the data.

User response: Specify valid values and then try tosave the modified data in the directory server. If theerror persists, contact the directory serveradministrator.

GLPWDM017E Editing RDN entry entry DN failed.

Explanation: The new RDN specified might beincorrect. See the IBM Tivoli Directory ServerAdministration Guide for information about valid DNsyntax.

User response: Specify a valid RDN.

GLPWDM018E An error occurred renaming entryentry DN: error.

Explanation: An error might have occurred for one ofthe following reasons: The DN being added wouldmodify a read-only tree. The logged-in user does nothave permission to modify an entry at the specifiedlocation. Synchronization and serialization issuescaused a problem.


GLPWDM019E The context was null on entry entryDN.

Explanation: The context, required for performingdirectory server operations, is null. No further directoryoperations can be carried out.

User response: Try the operation again. If the errorpersists, log in to the Web Administration Tool again. Ifthe problem still persists, contact the directory serveradministrator.

GLPWDM010E • GLPWDM019E


GLPWDM020E An error occurred while performinga search operation on the directoryserver.

Explanation: The error might have occurred for one ofthe following reasons: The directory context is null orthe server is not running or unreachable. The logged-inuser does not have authorization to access the searchquery results. The specified entries are incorrect or haveincorrect syntax. An unknown problem occurred.Contact the directory server administrator for moreinformation.


GLPWDM022E An error occurred while retrievingattributes for the rootDSE search onserver server name: error

Explanation: An error occurred while retrieving therootDSE attributes from the directory server. The servermight be down.

User response: If the server is not running, start theserver. If the error persists, contact the directory serveradministrator.

Administrator response: Contact IBM SoftwareSupport.

GLPWDM023E Unable to read any naming contextfrom the directory server.

Explanation: An error occurred while retrieving thenaming contexts from the directory server.


GLPWDM024E Unable to read anysubschemaSubentry from the directoryserver.

Explanation: The schema is published as part of thedirectory information, and is available in theSubschema entry. An error occurred while retrievingthe entry from the directory server.


Administrator response: Set the subschemaSubentryvalue in the rootDSE of the directory server.

GLPWDM026E An error occurred searching serverserver name: error.

Explanation: The error might have occurred for one ofthe following reasons: The search filter specified is notsupported or not understood by the directory server.The search controls contain incorrect settings. Thespecified entries to search are incorrect or have

incorrect syntax. The LDAP data being accessed hasincorrect data, incorrect naming attributes, or incorrectentries. Synchronization and serialization issues causeda problem.


GLPWDM027E An error occurred while browsingsearch results for server server name:error.

Explanation: This error occurs when a methodproduces a result that exceeds a size-related limit. Thiscan happen, for example, if the result contains moreobjects than the user requested, or when the size of theresult exceeds an implementation-specific limit. See theJava exception for more details.


GLPWDM028W An error occurred while retrievingentries. The server does not supportpaging, sorting, or both. Displaying thefirst number entries: error.

Explanation: The server does not support paging orsorting or both. The first entries are being displayed.


GLPWDM029E The search base DN entry DN doesnot exist.

Explanation: The search base DN does not exist in thedirectory server.

User response: If the user specified a nonexistentsearch base, specify a valid existing search base.Otherwise, contact the directory server administrator.

GLPWDM030E Encountered unknown attribute:attribute ID.

Explanation: An unknown attribute was encountered.The attribute is not part of the directory server schema.


GLPWDM032E Incorrect input ACL DN.

Explanation: The specified Subject DN and Subjecttype combination might be incorrect.

User response: Type a valid Subject DN and Subjecttype.



GLPWDM033E Error: incorrect input ACL DN details.

Explanation: A Subject DN was specified that doesnot conform to standards. See the IBM Tivoli DirectoryServer Administration Guide for information aboutvalid DN syntax.

User response: Specify valid ACL DN details.

GLPWDM035W Are you sure you want to delete theentry : entry?

Explanation: Continuing with this operation willdelete the selected entry.

User response: Click OK to delete the selected entryor Cancel to cancel the delete operation.

GLPWDM036W Are you sure you want to delete theselected static group DN?

Explanation: Continuing with this operation willdelete the selected static group DN under the selectedsuffix.

User response: Click OK to delete the selected staticgroup DN or Cancel to cancel the delete operation.

GLPWDM037W Are you sure you want to delete theselected member?

Explanation: Continuing with this operation willdelete the selected member from the group.

User response: Click OK to delete the selectedmember or Cancel to cancel the delete operation.

GLPWDM038W Are you sure you want to delete theselected entry : Entry DN ?

Explanation: Continuing with this operation willdelete the selected entry from the directory server.

User response: Click OK to delete the selected entryor Cancel to cancel the delete operation.

GLPWDM039W Are you sure you want to delete theselected non-leaf node and all itschildren : Entry DN ?

Explanation: Continuing with this operation willdelete the selected non-leaf node and all its childrenfrom the directory.

User response: Click OK to delete the selectednon-leaf node and all its children or Cancel to cancelthe delete operation.

GLPWDM041E A leaf node cannot be expanded.

Explanation: The selected entry is a leaf node. Onlynon-leaf nodes can be expanded.

User response: Select a non-leaf node to expand anddisplay the child nodes.

GLPWDM042E Incorrect group name.

Explanation: The specified group does not exist in therealm corresponding to the current user.

User response: Specify a valid group name that existsin the realm corresponding to the current user.

GLPWDM043E Select an attribute from theAvailable attributes list to add to theSelected required attributes list.

Explanation: An entry must be selected from theAvailable attributes list for the add operation. No entrywas selected.

User response: Select an entry from the Availableattributes list for the add operation to be successful.

GLPWDM044E Select an attribute to be removedfrom the Selected required attributeslist.

Explanation: An entry must be selected from theSelected required attributes list for the removeoperation. No entry was selected.

User response: Select an entry from the Selectedrequired attributes list for the remove operation to besuccessful.

GLPWDM045E Select an attribute from the Selectedrequired attributes list to move it to theSelected optional attributes list.

Explanation: An entry must be selected from theSelected required attributes list for the move operation.No entry was selected.

User response: Select an entry from the Selectedrequired attributes list for the move operation to besuccessful.

GLPWDM046E Select an attribute from theAvailable attributes list to add to theSelected optional attributes list.

Explanation: An entry must be selected from theAvailable attributes list for the add operation. No entrywas selected.

User response: Select an entry from the Availableattributes list for the add operation to be successful.



GLPWDM047E Select an attribute to be removedfrom the Selected optional attributeslist.

Explanation: An entry must be selected from theoptional attributes list for the remove operation. Noentry was selected.

User response: Select an entry from the optionalattributes list for the remove operation to be successful.

GLPWDM048E Select an attribute from the Selectedoptional attributes list to move it to theSelected required attributes list.

Explanation: An entry must be selected from theSelected optional attributes list for the move operation.No entry was selected.

User response: Select an entry from the Selectedoptional attributes list for the move operation to besuccessful.

GLPWDM049E Collapse operation cannot occur.The top-level entries are alreadydisplayed.

Explanation: The panel already displays the top-levelentries and cannot display a higher level.

User response: Collapse operation is not valid.

GLPWDM050E No auxiliary object classes areavailable to be deleted.

Explanation: The current selected entry does not haveany auxiliary object classes associated with it. Thedelete auxiliary objectclass operation failed.

User response: A delete auxiliary objectclass operationcannot be performed on an entry with no auxiliaryobjectclass.

GLPWDM051E Not a valid user.

Explanation: The specified user does not exist in therealm corresponding to the current group.

User response: Specify a valid user name that exists inthe realm corresponding to the current group.

GLPWDM052W Are you sure you want to delete theselected auxiliary object classes ?

Explanation: Continuing with this operation willdelete the selected auxiliary object classes from thedirectory server.

User response: Click OK to delete the selectedauxiliary object classes or Cancel to cancel the deleteoperation.

GLPWDM053E Cannot read all ACL information.Contact the directory serveradministrator to check the ACLs for thisentry.

Explanation: The logged-in user does not have readand search permission for ACL information.


GLPWDM054E Cannot read all Owner information.Contact the directory serveradministrator to check the owners onthis entry.

Explanation: The logged-in user does not have readand search permission for owner information.


GLPWDM055E The syntax of the language tag isincorrect.

Explanation: The language tag must start with lang-(for example, lang-en-US) and must be less than 240characters in length. The language tag cannot contain adigit between two hyphens.

User response: Specify a valid language tag.

GLPWDM056E Enter a search condition.

Explanation: The search filter field for the manualsearch is empty.

User response: Type a valid search filter in the fieldbeside manual search.

GLPWDM057E Enter a search condition.

Explanation: No search filters were specified for theadvanced search. The search filter table beside theAdvanced search option is empty.

User response: Click the Add button at the top of thesearch filter table and add a filter before attempting tosearch the directory server entries.

GLPWDM058E This value already exists. Add adifferent value.

Explanation: The entry already exists. Provide adifferent entry.

User response: Provide a different entry, which doesnot exist already, to add.



GLPWDM059E No value was specified for theValue field.

Explanation: The Value field on the Add filter panel isempty.

User response: Specify a valid value for the Valuefield on the Add filter panel.

GLPWDM060E No value is specified for the SubjectDN field on the Owners panel.

Explanation: The Subject DN field of the Owner panelis empty.

User response: Specify a valid value for the SubjectDN field on the Owners panel.

GLPWDM061E No value is specified for the GroupDN field on the Static membershipspanel.

Explanation: The Group DN field of the Staticmemberships panel is empty.

User response: Specify a valid value for the GroupDN field on the Static memberships panel.

GLPWDM062E No value is specified for theattribute to be added on the Entermultiple values panel.

Explanation: The value to be added for the givenattribute is empty.

User response: Specify a valid value to add for theattribute.

GLPWDM063E No value is specified for the givenattribute in the Value field on theLanguage tag values panel.

Explanation: The language tag value to be added forthe given attribute is empty in the Value field.

User response: Specify a valid language tag value toadd for the given attribute.

GLPWDM064E No value is specified for the Nestedgroup DN field on the Nested groupspanel.

Explanation: The Nested group DN field of theNested groups panel is empty.

User response: Specify a valid value for the Nestedgroup DN field.

GLPWDM065E No value is specified for themember field of Static group memberspanel.

Explanation: The member field on the Static groupmembers panel must be specified.

User response: Specify a valid value for the memberfield.

GLPWDM066E No value is specified for theuniqueMember field on the Static groupmembers panel.

Explanation: The uniqueMember field on the Staticgroup members panel is not specified.

User response: Specify a valid value for theuniqueMember field.

GLPWDM067E All fields on the Required attributespage are required.

Explanation: All attributes on the Required attributespage must be specified. Some of the required attributeshad no value.

User response: Specify values for all attributes on theRequired attributes page and then save the changes.

GLPWDM068E The RDN must be provided.

Explanation: The Relative DN field on the Editattributes panel must be specified.

User response: Specify a valid value for the RelativeDN field.

GLPWDM069E Select at least one auxiliary objectclass for deletion.

Explanation: An auxiliary objectclass must be selectedfor the delete operation to be successful. No auxiliaryobjectclass was selected.

User response: Select an auxiliary objectclass for thedelete operation.

GLPWDM070E All the users under the realm arealready members of the selected group.No more users can be added to thisgroup.

Explanation: Same as above.

User response: All the users under the realm arealready added to the selected group. To add a differentuser to the group, add that user to the associated realmand then to the group.



GLPWDM071E ACLs cannot be edited for entriesunder cn=configuration

Explanation: ACLs are not defined and cannot beedited for entries under cn=configuration.

User response: You cannot edit ACLs for entriesunder cn=configuration.

GLPWDM072E The DN Subject DN is not valid forthe type Subject Type.

Explanation: The following combinations of SubjectDN and Subject type for owners are not valid. SubjectDN cn=this and Subject type group. Subject DNcn=anybody and Subject type access-id. Subject DNcn=authenticated and Subject type access-id. TheSubject DN cn=this is valid for the Subject typeaccess-id and role. The Subject DNs cn=anybody andcn=authenticated are valid for the Subject type groupand role.

User response: Enter a valid combination of SubjectDN and Subject type.

GLPWDM073E The current server data will beloaded. However, there are pendingchanges that are not yet saved in thecurrent group memberships table of theStatic memberships panel. Do you wantto make these changes?

Explanation: Changes to the current groupmemberships table of Static memberships panel havenot been saved in the directory server. Continuing withthis operation will display the current directory serverdata along with the entries still pending to be saved tothe directory server. Canceling the operation will onlydisplay the current server data; the unsaved data in thetable will be lost.

User response: Click OK to display the current serverdata along with the unsaved entries in the membertable, or click Cancel to load only the current serverdata.

GLPWDM074E The current server data will beloaded. However, there are pendingchanges that are not yet saved in thestatic group members table of the Staticgroup members panel. Do you want toretain these changes?

Explanation: Changes to the static group memberstable of the Static group members panel have not yetbeen saved in the directory server. If you continue withthis operation, the current directory server data, alongwith the entries still pending to be saved to thedirectory server, will be displayed. If you cancel theoperation, the current server data will be displayed andthe unsaved data in the table will be lost.

User response: Click OK to display the current server

data along with the unsaved entries in the membertable, or click Cancel to load only the current serverdata.

GLPWDM075E The current server data will beloaded. However, there are pendingchanges that are not yet saved in theunique members table of Static groupmembers panel. Do you want to retainthese changes?

Explanation: Changes to the unique members table ofthe Static group members panel have not yet beensaved in the directory server. If you continue with thisoperation, the current directory server data, along withthe entries still pending to be saved to the directoryserver, will be displayed. If you cancel the operation,the current server data will be displayed and theunsaved data in the table will be lost.

User response: Click OK to display the current serverdata along with the unsaved entries in the membertable, or click Cancel to load only the current serverdata.

GLPWDM076E The selected entry is not a group.This option is not valid. Select a groupentry or make this entry a group byadding appropriate auxiliary classes.

Explanation: The Manage Members option is validonly for group entries. The selected entry is not agroup.

User response: Select a group entry or make this entrya group by adding appropriate auxiliary classes.

GLPWDM077E Incorrect DN entry. Specify a validDN.

Explanation: The specified DN entry is incorrect. Anerror occurred while parsing the specified DN in thedirectory server.

User response: Specify a valid DN entry.

GLPWDM078W The directory server entries havenot been loaded into the table. Only theuser changes will be removed from thetable. Are you sure you want to removeall the entries in the table?

Explanation: Continuing with this operation willremove all the entries in the table.

User response: Click OK to remove all the entries inthe table.

GLPWDM071E • GLPWDM078W


GLPWDM079E Cannot remove a MUST attribute:attribute name

Explanation: The specified attribute is a MUSTattribute and cannot be empty.

User response: The specified attribute cannot beremoved.

GLPWDM080E Are you sure you want to remove allthe table entries?

Explanation: Continuing with this operation willremove all the entries from the table.

User response: Click OK to remove all the tableentries or Cancel to cancel the remove operation.

GLPWDM081E Possible duplicate value(s) exist forattribute name attribute on the server:server name

Explanation: One or more of the attribute values to beadded to the directory server attribute already exist inthe server. Cannot add an already existing attributevalue.

User response: Remove the duplicate attribute valuefrom the table and then save the data into the directoryserver.

GLPWDM082E One or more of the entries selectedin the table already exist and will beignored.

Explanation: Some of the entries selected in the tablealready exist. Duplicate entries are not allowed. Theseentries will not be added.

User response:

GLPWDM083E The value entered is not a validstatic group DN. Specify a valid staticgroup entry.

Explanation: The specified Group DN value is not avalid static group entry.

User response: Specify a valid static group entry.

GLPWDM084E An error occurred in the Referralpanel while retrieving the list ofattributes from the directory server.

Explanation: An error occurred while retrieving theattributes from the directory server. One of thefollowing errors might have occurred: The logged-inuser does not have permission to look up LDAP data.The DN whose attributes are to be retrieved areincorrect or have incorrect syntax or attribute values.The directory server is down or unreachable.Synchronization and serialization issues caused anerror.


GLPWDM085E Incorrect Base DN.

Explanation: The Base DN value is incorrect. See theIBM Tivoli Directory Server Administration Guide forinformation about valid DN syntax.

User response: Type a valid Base DN.

GLPWDM086E Malformed referral URL.

Explanation: A well-formed referral URL consists ofhost, port, DN, attributes, scope and filter. A validreferral URL starts with either ldap or ldaps followedby ://. It is followed by a valid hostname and portnumber. The parameters DN, attributes, scope and filterare optional. A valid referral URL isldap://server1.com:389/ou=austin,o=ibm,c=us?cn,sn,description?base?objectclass=*

User response: Specify valid referral URL components.

GLPWDM087E Date format is incorrect. Provide thedate value in date format format forcolumn ''column''.

Explanation: The specified date is not in a validformat. The date must be in the format shown.

User response: Specify the date value in the formatshown.

GLPWDM088W Are you sure you want to delete theselected binary data entry?

Explanation: Continuing with this operation willdelete the selected binary data entry.

User response: Click OK to delete the selected binarydata entry or Cancel to cancel the delete operation.

GLPWDM089E File cannot be uploaded on Webserver or file not found.

Explanation: The file cannot be uploaded on the Webserver. The file path might be incorrect, or there mightbe a problem uploading the specified file because ofsize restrictions or a network problem.

User response: Verify that the file path is valid andthat the Web server is reachable through network, andthen click Submit.

GLPWDM091E Select a binary data entry to delete.

Explanation: Binary data entry is required to beselected for deletion operation.

User response: Select a binary data entry.



GLPWDM092E Select only one binary data entry toexport.

Explanation: Binary data entry is required to beselected for export operation.

User response: Select a binary data entry.

GLPWDM096W Are you sure you want to removeall the encrypted attributes?

Explanation: Continuing with this operation willremove all the encrypted attributes.

User response: Click OK to remove all the encryptedattributes or Cancel to cancel the remove operation.

GLPWDM097E Not a valid realm location. TheParent DN field value is not allowed.

Explanation: An error might have occurred for one ofthe following reasons: The following DNs are notallowed as realm locations: cn=changelogcn=configuration cn=localhost cn=pwdpolicycn=schema The Parent DN field might have one of thelisted DNs as its value. The specified Parent DN mightnot exist in the directory server.

User response: While adding a realm, specify a validrealm location. If the error messages occurred whileperforming some other operation on an existing realm,contact the directory server administrator.

GLPWDM099E Not a valid template location. TheParent DN field value is not allowed.

Explanation: An error might have occurred for one ofthe following reasons: The following DNs are notallowed as template locations: cn=changelogcn=configuration cn=localhost cn=pwdpolicycn=schema The Parent DN field might have one of thelisted DNs as its value. The specified Parent DN mightnot exist in the directory server.

User response: While adding a template, specify avalid template location. If the error messages occurredwhile performing some other operation on an existingtemplate, contact the directory server administrator.

GLPWDM100E A template or entry with the samename already exists in the specifiedlocation.

Explanation: The specified template name was alreadyadded to the directory server at the specified location.

User response: Specify a new template name, whichdoes not exist at the specified location.

GLPWDM101E Incorrect administrator groupcontainer location.

Explanation: An error might have occurred for one ofthe following reasons: The following DNs are notallowed as administrator group container locations:cn=changelog cn=configuration cn=localhostcn=pwdpolicy cn=schema The Administrator groupfield might have one of the listed DNs as its value. Thespecified container DN for administrative groups doesnot exist in the directory server.

User response: Specify a valid administrator groupcontainer location.

GLPWDM102E Incorrect user container location.

Explanation: An error might have occurred for one ofthe following reasons: The following DNs are notallowed as user container locations: cn=changelogcn=configuration cn=localhost cn=pwdpolicycn=schema The User container field might have one ofthe listed DNs as its value. The specified User containerfield value might not exist in the directory server.

User response: Specify a valid user container location.

GLPWDM103E Not a valid group container location.

Explanation: An error might have occurred for one ofthe following reasons: The following DNs are notallowed as group container locations: cn=changelogcn=configuration cn=localhost cn=pwdpolicycn=schema The Group container field might have oneof the listed DNs as its value. The specified Groupcontainer field value might not exist in the directoryserver.

User response: Specify a valid group containerlocation.

GLPWDM104E This template is in use by one ormore realms and cannot be deleted.

Explanation: The selected template cannot be deleted.A template being referred by one or more realms in thedirectory server cannot be deleted.

User response: Delete the realms that refer to theselected template or disassociate the referring realmsfrom the selected template, so that no existing realmrefers to the selected template any more. Then attemptto delete the selected template again.

GLPWDM105E The specified administrator group isnot a group.

Explanation: A group must have at least one of thefollowing attributes: member, memberurl,uniquemember, or ibm-membergroup. The specifiedadministrator group is not a group because it does notcontain any of the required attributes.



User response: Specify a valid group name as a valuefor the administrator group.

GLPWDM106E The selected tab name tab cannot bemoved.

Explanation: The specified tab cannot be movedbecause this tab will not be displayed to the user. Thistab contains attributes that will not be displayed to theuser.

User response: This tab cannot be moved. To displaythe attributes of this tab, move the attributes of the tabto some other tab.

GLPWDM107E The selected tab cannot be moveddown because the tab is already at thebottom of the list.

Explanation: The selected tab cannot be moved down.The tab is already at the bottom of the list. The [Notdisplayed] tab cannot be moved.

User response: The selected tab cannot be moveddown.

GLPWDM108E A tab with this name already exists.

Explanation: The specified tab name is already addedto the template.

User response: Specify a new tab name, which doesnot exist in the template.

GLPWDM109E The tab name cannot be renamed. Atab with this name already exists.

Explanation: The specified tab name already exists inthe template.

User response: Specify a new tab name, which doesnot exist in the template.

GLPWDM110W Are you sure you want to delete theselected tab?

Explanation: Continuing with this operation willdelete the selected tab.

User response: Click OK to delete the selected tab orCancel to cancel the delete operation.

GLPWDM111E The tabs NOT_DISPLAYED andREQUIRED cannot be deleted.

Explanation: The tabs [NOT_DISPLAYED] andREQUIRED are required tabs. These tabs cannot bedeleted.

User response: You cannot delete theNOT_DISPLAYED and REQUIRED tabs.

GLPWDM112E All required attributes must be on adisplayed tab.

Explanation: Some of the required attributes are notdisplayed on any of the displayed tabs. The displayedtabs are all tabs except the [Not displayed] tab.

User response: View the required attributes in the[Not displayed] tab that are not on any of thedisplayed tabs. Move these attributes to any of thedisplayed tabs or create a new tab to display them.

GLPWDM113E No naming attribute was found inthe selected object classes. Select objectclasses with at least one namingattribute.

Explanation: A naming attribute is an attribute thathas one of the following syntaxes: Directory Stringsyntax IA5 String Integer syntax - integral numberThere must be at least one naming attribute in theselected objectclasses.

User response: Select objectclasses with namingattributes.

GLPWDM114E There is no template associated withthis realm

Explanation: A realm must have templates for thecreation of users. A group can be created without atemplate, but it cannot have any users.

User response: Add a template to the associated realmbefore managing the users and groups.

GLPWDM115E An error occurred while adding theuser to the group.

Explanation: An error occurred while adding the useras the member of the group.


GLPWDM116E An error occurred while removingthe user from the group.

Explanation: An error occurred while removing theuser from membership of the group.


GLPWDM117E No realms were found. Add a realmand then access the selected panel.

Explanation: The selected panel will be displayed, ifthere is at least one realm in the directory server.

User response: Add a realm before displaying theselected panel.



GLPWDM119E Some of the changes could not besaved.

Explanation: Some of the changes were not saved. Anerror might have occurred for one of the followingreasons: There might be a problem connecting to theserver. The input value specified might be incorrect.There is another error performing the requestedoperation. View log files for more information aboutthe error. For assistance, contact IBM Software Support.

User response: Verify that you are connected to theserver and that the input value is correct. For moreassistance, contact IBM Software Support.

GLPWDM120W The entry entry DN has beensuccessfully added. Would you like toadd a similar entry?

Explanation: Continuing with this operation willallow you to add one more entry.

User response: Click Yes to add one more entry or Noto return to the panel.

GLPWDM121E Select an object class.

Explanation: At least one object class must be selectedbefore navigating to the next panel. An error occurredbecause an object class was not selected.

User response: Select an object class and then clickNext.

GLPWDM122E No value was specified for theValue field.

Explanation: The Value field on the multiple values isempty.

User response: Specify a valid value for the Valuefield.

GLPWDM124E Select a role for the administrativegroup member.

Explanation: At least one role must be selected for theadministrative group member. A role was not definedfor the administrative group member.

User response: Select a role for the administrativegroup member or clear the administrative role checkbox to create an administrative group member with nospecial authority.

GLPWDM125E Member member does not exist inthe Directory Information Tree (DIT).

Explanation: A non-existing entry is added as amember of a group.

User response: Verify that an entry with the given DNexists in the DIT.

GLPWDM126W Not all values are fetched for thisentry. Displaying number of values fetchedof total number of values total values.

Explanation: A limit is set in the Web AdministrationTool for the maximum number of attribute values to befetched for an attribute and for an entry. As a result ofthe limit, all the attribute values of the selected entryare not fetched.

User response: Remove the limit on the maximumnumber of attribute values to be fetched for an attributeand for an entry, to view all the attribute values of theentry. The limiting value can be modified through theManage properties for webadmin searches panel ofConsole administration login.

GLPWDM127E Incorrect search filter filter for usersin the realm realm name : error message.

Explanation: An incorrect filter was specified for therealm.

User response: Specify a valid filter for the realm. e.g.(cn=user*)

GLPWDM128E Illegal combination for the attribute.

Explanation: The combination being for the attributeis illegal. e.g. An attribute which is not encryptedcannot return encrypted values.

User response: Try a valid combination of settings.

GLPWDM129E Are you sure you want to deleteselected ACL objects ?

Explanation: Continuing with this operation willdelete the selected ACL objects.

User response: Click OK to delete the selected ACLobjects or click Cancel to cancel the deletion operation.

GLPWRM001E Select a node in the tree.

Explanation: A node must be selected to perform therequested operation.

User response: Select a node and then retry theoperation.

GLPWRM002E Failed to suspend replication forselected replication agreement.

Explanation: The extended operation on the server tochange the replication queue to the suspended statefailed.

User response: The error might have occurred for oneof the following reasons: The server might be down.Check to be sure that the server is running andreachable through the network. There is an error with

GLPWDM119E • GLPWRM002E


the control replication extended operation. Contact IBMSoftware Support.

GLPWRM003E Failed to resume replication forselected replication agreement.

Explanation: The extended operation on the server tochange the replication queue to the resumed statefailed.

User response: The error might have occurred for oneof the following reasons: The server might be down.Check to be sure that the server is running andreachable through the network. There is an error withthe control replication extended operation. Contact IBMSoftware Support.

GLPWRM004E Failed to force replication forselected replication agreement.

Explanation: The extended operation on the server toforce replication for the selected replication queuefailed.

User response: The error might have occurred for oneof the following reasons: The server might be down.Check to be sure that the server is running andreachable through the network. There is an error withthe control replication extended operation. Contact IBMSoftware Support.

GLPWRM005E Failed to skip the blockingunreplicated change for the selectedreplication agreement.

Explanation: The extended operation on the server toskip the blocking unreplicated change for the selectedreplication agreement failed.

User response: The error might have occurred for oneof the following reasons: The server might be down.Check to be sure that the server is running andreachable through the network. There is an error withthe control replication queue extended operation.Contact IBM Software Support.

GLPWRM006E Failed to skip all unreplicatedchanges for selected replicationagreement.

Explanation: The extended operation on the server toskip all unreplicated changes for the selectedreplication agreement failed.

User response: The error might have occurred for oneof the following reasons: The server might be down.Check to be sure that the server is running andreachable through the network. There is an error withthe control replication queue extended operation.Contact IBM Software Support.

GLPWRM008E Failed to configure subtree as areplication context.

Explanation: Unable to add the ibm-replicationContext auxiliary object class to the subtree.This subtree was not configured as a replicationcontext.

User response: The error might have occurred for oneof the following reasons: The subtree is alreadyconfigured for replication. The subtree entry specifieddoes not exist in the DIT. Check whether the subtreeentry exists in the DIT. There is another error addingthe objectclass to the given subtree entry. Contact IBMSoftware Support.

GLPWRM009E Failed to modify the selectedreplication context.

Explanation: Unable to add or edit theibm-replicareferralurl attribute for the selected subtree.

User response: The error might have occurred for oneof the following reasons: The subtree entry does nothave permission for the user to add or modify attributeibm-replicareferralurl. Check whether the subtree entryhas permission for the user to edit this attribute. Thereis another error editing this subtree entry. Contact IBMSoftware Support.

GLPWRM010E Unable to add the default groupunder the replicated subtree.

Explanation: Unable to add the entryibm-replicaGroup=default with objectclassibm-replicagroup under the selected subtree.

User response: The error might have occurred for oneof the following reasons: The entry already exists in theDIT. The user does not have permission to add thisentry. Check whether the subtree entry has permissionfor the user to add this entry. There is another erroradding entry ibm-replicaGroup=default under thesubtree. Contact IBM Software Support.

GLPWRM011E Connected to administration server.Replication management cannotfunction in this mode.

Explanation: The Directory Server is not running. TheWeb Administration tool is connected to theadministration server. In this mode, no replicationmanagement functions are available.

User response: Start the Directory Server in normalmode; then retry the replication management function.

GLPWRM012E Unable to add the subentry: subentry.

Explanation: Unable to add the entry with objectclassibm-replicasubentry under the selected subtree. This isrequired to create a master server or forwarder serverin the topology.

GLPWRM003E • GLPWRM012E


User response: The error might have occurred for oneof the following reasons: The entry already exists in theDIT. The user does not have permission to add thisentry. Check whether the subtree entry has permissionfor the user to add this entry. There is another erroradding the entry with objectclass ibm-replicasubentryunder the subtree. Contact IBM Software Support.

GLPWRM013E Unable to delete the subentry:subentry.

Explanation: Unable to delete the entry withobjectclass ibm-replicasubentry under the selectedsubtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to delete this entry. Check whether thesubtree entry has permission for the user to delete thisentry. The subtree to which this entry belongs to maybe quiesced. Unquiesce the subtree and try again. Thereis another error deleting the entry with objectclassibm-replicasubentry under the subtree. Contact IBMSoftware Support.

GLPWRM014E Unable to add the agreement:agreement name.

Explanation: Unable to add the entry with objectclassibm-replicationAgreement under the selected subtree.This is required to create a replica server in thetopology.

User response: The error might have occurred for oneof the following reasons: The entry already exists in theDIT. The user does not have permission to add thisentry. Check whether the subtree entry has permissionfor the user to add this entry. There is another erroradding the entry with objectclass ibm-replicationAgreement under the subtree. Contact IBMSoftware Support.

GLPWRM015E Unable to edit the agreement:agreement name.

Explanation: Unable to edit the entry with objectclassibm-replicationAgreement under the selected subtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to edit this entry. Check whether the subtreeentry has permission for the user to edit this entry.There is another error editing attributes of the entrywith the objectclass ibm-replicasubentry under thesubtree. Contact IBM Software Support.

GLPWRM016E Unable to delete the agreement:agreement name.

Explanation: Unable to delete the entry withobjectclass ibm-replicationAgreement under the selectedsubtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to delete this entry. Check whether thesubtree entry has permission for the user to delete thisentry. There is another error deleting the entry withobjectclass ibm-replicasubentry under the subtree.Contact IBM Software Support.

GLPWRM017E Unable to add the daily schedule:schedule name.

Explanation: Unable to add the entry with objectclassibm-replicationdailyschedule under the selectedsubtree.

User response: The error might have occurred for oneof the following reasons: The entry already exists in theDIT. The user does not have permission to add thisentry. Check whether the subtree entry has permissionfor the user to add this entry. There is another erroradding the entry with objectclass ibm-replicationdailyschedule under the subtree. ContactIBM Software Support.

GLPWRM018E Unable to edit the daily schedule:schedule name.

Explanation: Unable to edit the entry with theobjectclass ibm-replicationdailyschedule under theselected subtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to edit this entry. Check whether the subtreeentry has permission for the user to edit this entry.There is another error editing the attributes of the entrywith objectclass ibm-replicationdailyschedule under thesubtree. Contact IBM Software Support.

GLPWRM019E Unable to copy the daily schedule:schedule name.

Explanation: Unable to add the entry with objectclassibm-replicationdailyschedule under the destinationsubtree.

User response: The error might have occurred for oneof the following reasons: The entry already exists in thedestination subtree. The user does not have permissionto add this entry. Check whether the destinationsubtree entry has permission for the user to add thisentry. There is another error adding the entry withobjectclass ibm-replicationdailyschedule under thedestination subtree. Contact IBM Software Support.

GLPWRM020E Server is running in configurationonly mode. Replication managementcannot function in this mode.

Explanation: The directory server is running inconfiguration only mode. In this mode, replicationmanagement tasks are not available.



User response: If an error caused the directory serverto start in configuration only mode, correct the errorand start the directory server in normal mode; thenretry replication management functions.

GLPWRM021E Unable to add the weekly schedule:schedule name.

Explanation: Unable to add the entry with theobjectclass ibm-replicationweeklyschedule under theselected subtree.

User response: The error might have occurred for oneof the following reasons: The entry already exists in theDIT. The user does not have permission to add thisentry. Check whether the subtree entry has permissionfor the user to add this entry. There is another erroradding the entry with objectclass ibm-replicationweeklyschedule under the subtree. ContactIBM Software Support.

GLPWRM022E Unable to edit the weekly schedule:schedule name.

Explanation: Unable to edit the entry with objectclassibm-replicationweeklyschedule under the selectedsubtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to edit this entry. Check whether the subtreeentry has permission for the user to edit this entry.There is another error editing the attributes of the entrywith objectclass ibm-replicationweeklyschedule underthe subtree. Contact IBM Software Support.

GLPWRM023E Unable to delete the replicationfilter object.

Explanation: Unable to delete the selected replicationfilter object for the selected subtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to delete this entry. Check whether thesubtree entry has permission for the user to delete thisentry. There is another error deleting the replicationfilter object under the subtree. Contact IBM SoftwareSupport.

GLPWRM024E Unable to edit the replication filterobject.

Explanation: Unable to edit the selected replicationfilter object for the selected subtree.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to edit this entry. Check whether the subtreeentry has permission for the user to edit this entry.There is another error modifying the replication filterobject under the subtree. Contact IBM SoftwareSupport.

GLPWRM025E Unable to retrieve the suffixes fromthe server.

Explanation: The search operation to retrieve the listof suffixes from server failed.

User response: The error might have occurred for oneof the following reasons: Root DSE search is notworking on server. Root DSE of the server is notshowing naming contexts. There is another errorretrieving suffixes. Contact IBM Software Support.

GLPWRM026E Unable to get the list of availabledaily schedules from the server.

Explanation: The search operation to get the list ofdaily schedule objects from the server failed.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to search daily schedule objects. The serveris not reachable or is running in configuration onlymode. There is another error searching for dailyschedule objects. Contact IBM Software Support.

GLPWRM027E Unable to retrieve the list ofavailable weekly schedules from theserver.

Explanation: The search operation to retrieve the listof weekly schedule objects from the server failed.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to search weekly schedule objects. Theserver is not reachable or is running in configurationonly mode. There is another error searching for weeklyschedule objects. Contact IBM Software Support.

GLPWRM028E Unable to get the list of availablecredentials from the server.

Explanation: The search operation to retrieve the listof credential objects from the server failed.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to search credential objects. The server isnot reachable or is running in configuration only mode.There is another error searching for credential objects.Contact IBM Software Support.

GLPWRM029E Unable to get the server ID of theserver you are connected to.

Explanation: Failed to get the server ID for thedirectory server to which the Web Administration Toolis connected.

User response: The error might have occurred for oneof the following reasons: The server might have gonedown during the operation. The server is not reachable



by the Web Administration Tool. Contact the directoryadministrator.

GLPWRM030E Unable to get the server ID of thereplica server.

Explanation: Failed to get the server ID for thedirectory server, which is defined as a replica in thetopology.

User response: The error might have occurred for oneof the following reasons: The replica server is down.The replica server is not reachable by the WebAdministration Tool. Check to be sure that the replicaserver is running and reachable through network bythe Web Administration Tool.

GLPWRM031E Unable to get server ID of themaster server. A valid server ID must beprovided for a peer master topology towork.

Explanation: Failed to get the server ID for thedirectory server, which is being defined as a masterserver. A valid server ID is required for the server youare defining as a master server in the topology.

User response: The error might have occurred for oneof the following reasons: The master server is down.The master server is not reachable by the WebAdministration Tool. Check to be sure that the server isrunning and reachable through the network by the WebAdministration Tool.

GLPWRM032E Unable to get the hostname of theserver.

Explanation: Failed to get the hostname from thereplica subentry object.

User response: The hostname is either not present ornot correctly defined in the master server entry of theDIT. Check the entry in the DIT for the server.

GLPWRM033E Unable to add theibm-slapdSupplier credential object.

Explanation: Failed to add supplier credential objectfor the subtree in the configuration file.

User response: The user does not have access to addthe supplier credentials for the subtree or there isanother error performing this operation. Contact thedirectory administrator.

GLPWRM034E Unable to modify theibm-slapdSupplier credential object.

Explanation: Failed to modify supplier credentialobject for the subtree in the configuration file.

User response: The user does not have access tomodify the supplier credentials for the subtree or there

is another error performing this operation. Contact thedirectory administrator.

GLPWRM035E Unable to delete theibm-slapdSupplier credential object.

Explanation: Failed to delete the supplier credentialobject for the subtree in the configuration file.

User response: The user does not have access todelete the supplier credentials for the subtree or there isanother error performing this operation. Contact thedirectory administrator.

GLPWRM036E Unable to add theibm-slapdReplication credential object.

Explanation: Failed to add the default suppliercredential object in the configuration file.

User response: The user does not have access to adddefault supplier credentials or there is another errorperforming this operation. Contact the directoryadministrator.

GLPWRM037E Unable to modify theibm-slapdReplication credential object.

Explanation: Failed to modify the default suppliercredential object in the configuration file.

User response: The user does not have access tomodify default supplier credentials or there is anothererror performing this operation. Contact the directoryadministrator.

GLPWRM038E Unable to delete theibm-slapdReplication credential object.

Explanation: Failed to delete the default suppliercredential object in the configuration file.

User response: The user does not have access todelete default supplier credentials or there is anothererror performing this operation. Contact the directoryadministrator.

GLPWRM039E Unable to add the simple credential.

Explanation: Failed to add the simple credential objectentry with objectclass ibm-replicationCredentialsSimplein the selected container.

User response: The error might have occurred for oneof the following reasons: The credential object alreadyexists in the selected container. The user does not havepermission to create the entry in the specified container.There is another error adding the credential object.Contact the directory administrator.



GLPWRM040E Unable to add the replication filterobject.

Explanation: Failed to add the filter object entry withobjectclass ibm-replicationFilter in the selectedcontainer.

User response: The error might have occurred for oneof the following reasons: The filter object already existsin the selected container. The user does not havepermission to create the entry in the specified container.There is another error adding the filter object. Contactthe directory administrator.

GLPWRM041E Unable to modify the simplecredential.

Explanation: Failed to modify the simple credentialobject entry with objectclass ibm-replicationCredentialsSimple in the selected container.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to modify the entry in the specifiedcontainer. There is another error modifying thecredential object. Contact the directory administrator.

GLPWRM042E Unable to add the Kerberoscredential.

Explanation: Failed to add the Kerberos credentialobject entry with objectclass ibm-replicationCredentialsKerberos in the selected container.

User response: The error might have occurred for oneof the following reasons: The credential object alreadyexists in the selected container. The user does not havepermission to create the entry in the specified container.There is another error adding the credential object.Contact the directory administrator.

GLPWRM043E Unable to modify the Kerberoscredential.

Explanation: Failed to modify the Kerberos credentialobject entry with objectclass ibm-replicationCredentialsKerberos in the selected container.


GLPWRM044E Unable to add the SSL credential.

Explanation: Failed to add the SSL credential objectentry with objectclass ibm-replicationCredentialsExternal in the selected container.

User response: The error might have occurred for oneof the following reasons: The credential object alreadyexists in the selected container. The user does not have

permission to create the entry in the specified container.There is another error adding the credential object.Contact the directory administrator.

GLPWRM045E Unable to modify the SSL credential.

Explanation: Failed to modify the SSL credentialobject entry with objectclass ibm-replicationCredentialsExternal in the selected container.


GLPWRM046E Unable to delete the credentialobject.

Explanation: Failed to delete the credential objectentry from the selected container.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to delete the entry in the specifiedcontainer. There is another error deleting the credentialobject. Contact the directory administrator.

GLPWRM047E Unable to add the container objectunder localhost.

Explanation: Failed to add the container entrycn=replication, cn=localhost, which holds thereplication related credentials, schedule and filterobjects.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to add an entry under cn=localhost. There isanother error adding the container entry. Contact thedirectory administrator.

GLPWRM048E Unable to quiesce the subtree.

Explanation: The cascading replication extendedoperation to quiesce the subtree failed.

User response: The error might have occurred for oneof the following reasons: The subtree is already inquiesced state. The user does not have permission toquiesce the subtree. There is another error running thecascading control extended operation on the server.Contact the directory administrator.

GLPWRM049E Unable to unquiesce the subtree.

Explanation: The cascading replication extendedoperation to unquiesce the subtree failed.

User response: The error might have occurred for oneof the following reasons: The subtree is already innormal state. The user does not have permission tounquiesce the subtree. There is another error running



the cascading control replication extended operation onserver. Contact the directory administrator.

GLPWRM050E Unable to get the credential objectfrom the server.

Explanation: Failed to retrieve the replicationcredential object from the specified container.

User response: The error might have occurred for oneof the following reasons: The credential object is notpresent or was deleted from the specified container.The user does not have permission to search for thecredential object. There is another error retrievinginformation about credential object. Contact thedirectory administrator.

GLPWRM051E Error in retrieving the enabledcapabilities from the root DSE.

Explanation: Failed to get the value for theibm-enabledCapabilities attribute from the rootDSE ofthe given server.

User response: Check to be sure that the server isrunning and reachable through network.

GLPWRM052E Unable to get the values fromcn=replication, cn=configuration.

Explanation: Failed to read the attributes for entrycn=replication, cn=configuration.

User response: The error might have occurred for oneof the following reasons: The server is not running ornot reachable through the network. Entrycn=replication, cn=configuration does not exist. There isanother error reading the server's configuration file forthis entry. Contact the directory administrator.

GLPWRM053E Unable to set the values incn=replication, cn=configuration.

Explanation: Failed to set attributes for entrycn=replication, cn=configuration.

User response: The error might have occurred for oneof the following reasons: The server is not running ornot reachable through network. The user does not havepermission to set values under cn=replication,cn=configuration. There is another error settingattributes in the configuration file. Contact the directoryadministrator.

GLPWRM054E Unable to search for the replicationcontainer object under localhost.

Explanation: Failed to search for the cn=replicationcontainer under cn=localhost.

User response: Check to be sure that the server isrunning and the user has permission to search entriesunder cn=localhost.

GLPWRM055E Unable to search for the defaultgroup under the replicated subtree.

Explanation: Failed to search for entryibm-replicaGroup=default under the replicated subtree.

User response: Check to be sure that the server isrunning and the user has permission to search entriesunder the replicated subtree.

GLPWRM056E Unable to search for the replicatedsubtrees under the suffixes.

Explanation: Unable to get the list of definedreplication contexts under the given suffix entry.

User response: Check to be sure that the server isrunning and the user has permission to search entriesunder the given suffix.

GLPWRM057E Unable to convert the string toname.

Explanation: Failed to parse the string DN to JNDIName.

User response: Check to be sure that the DN is corrector contact the directory administrator.

GLPWRM058E Unable to search for the mastercredential object.

Explanation: Unable to search for master credentialobjects in cn=configuration.

User response: Check to be sure that the server isrunning and the user has permission to search entriesunder cn=configuration.

GLPWRM059E Unable to search for the suppliercredential objects.

Explanation: Unable to search for supplier credentialobjects in cn=configuration.

User response: Check to be sure that the server isrunning and the user has permission to search entriesunder cn=configuration.

GLPWRM060E Unable to search the directory.

Explanation: Failed to search for replication topologyentries in the directory information tree.

User response: Check to be sure that the server isrunning and the user has permission to search DITentries.



GLPWRM061E Daily schedule daily schedule namehas been deleted.

Explanation: The daily schedule for which the dailyschedule details panel was launched was deleted andcould not be found.

User response: Check to see if the daily scheduleobject exists. Refresh the screen and try launching thepanel again.

GLPWRM062E The selected string is not a schedule.

Explanation: The selected row from the weeklyschedule details table does not contain a valid dailyschedule.


GLPWRM063E The cascading replication extendedoperation failed.

Explanation: The cascading control replicationextended operation, which is used to quiesce andunquiesce a subtree, failed. Wait for replication andreplicating data now is failed on the specified directoryserver.

User response: Check to see if the user has permissionto run the extended operation on the given subtree oragreement. Contact the directory administrator if theproblem persists.

GLPWRM064E Server server name reported an errorfrom server server name. The logged-inuser does not have authority to performthis operation.

Explanation: Failed to run the extended operation onthe server because the user does not have the authorityto perform the operation.

User response: Check the user permissions and try theoperation again. Contact the directory administrator ifthe problem persists.

GLPWRM065E error message replica details agreementDN details

Explanation: The cascase replication extendedoperation did not complete in the required time. Thereplication topology might be incorrectly configured orone of the servers might not be running.

User response: Verify that the supplier and consumerreplicas are correctly configured and running; thenretry the operation.

GLPWRM066E Replication context is already in therequested state.

Explanation: The quiesce or unquiesce replicatedsubtree operation failed because the specified subtree isalready in the requested state.

User response: Change the state of the subtree and trythe operation again. Contact the directory administratorif the problem persists.

GLPWRM067E The specified change is not the nextchange to replicate. The server mightalready have replicated this change.

Explanation: The change to skip from the replicationchange table is not the next change in the queue. Failedto skip the change.

User response: Check to see if the change is alreadyreplicated or deleted from the replication change table.Refresh the panel and try again. Contact the directoryadministrator if the problem persists.

GLPWRM068E Server server name reported an errorfrom server server name. Operation didnot complete within the specified time.

Explanation: Failed to get the response for theextended operation from the server because the timeoutvalue specified was exceeded.

User response: Check to be sure that the server isrunning and reachable. Retry the operation. Contact thedirectory administrator if the problem persists.

GLPWRM069E Replication from supplier replicasupplier replica to consumer replicaconsumer replica did not complete.

GLPWRM070E Server server name reported an errorfrom server server name. Operation failedwith result code result code.

Explanation: Extended operation failed on server.

User response: Check the return code to look up thereason.

GLPWRM071E 'Create missing parent entries' willonly be considered when replicationfilter DN is specified.

Explanation: A filter DN must be specified if the'Create missing parent entries' check box is selected.

User response: Either specify a filter DN or clear the'Create missing parent entries' check box.



GLPWRM072E Error occurred on the agreement toserver server name.

Explanation: Error occurred while running theextended operation on the server for the specifiedconsumer agreement.


GLPWRM073E Unable to add the container objectunder IBMpolicies.

Explanation: Failed to add the container entrycn=replication, cn=IBMpolicies, which holds thereplication-related credentials, schedule, and filterobjects.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to add an entry under cn=IBMpolicies.There is another error adding the container entry.Contact the directory administrator.

GLPWRM074E Unable to search for the replicationcontainer object under IBMpolicies.

Explanation: Failed to search for the cn=replicationcontainer under cn=IBMpolicies.

User response: Check to be sure that the server isrunning and the user has permission to search entriesunder cn=IBMpolicies.

GLPWRM075E Entry already exists in the list.

Explanation: The server entry already exists in the list.

User response: Select a different entry to add to theserver list.

GLPWRM076E Error occurred setting the gatewayand master servers.

Explanation: Failed to add or remove auxiliary objectclass ibm-replicationGateway to subentries.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to add or remove an auxiliary objectclassfor the subentry. The objectclass is already present forthe entry where it is being added or not present in theentry from which it is being removed. There is anothererror during the operation. Contact the directoryadministrator.

GLPWRM078E Master DN cannot be the same asthe administrator DN.

Explanation: Failed to add supplier credentialsbecause the DN for credentials cannot be the same asthe administrative DN for the directory server.

User response: Use a different DN and try theoperation again.

GLPWRM079E Replication error control extendedoperation failed.

Explanation: Failed to run the replication error controlextended operation.

User response: The error might have occurred for oneof the following reasons: Error retrying or deleting oneor all errors from the replication error table. The userdoes not have the authority to perform the operation.The error being viewed, retried, or deleted does notexist in the replication error table. There is anothererror during the operation. Refresh the page. If theproblem persists, contact the directory administrator.

GLPWRM080E Schedule does not exist or wasdeleted.

Explanation: Failed to edit, copy, or delete theschedule because it was either deleted from the DIT ormoved to a different location.

User response: Refresh the panel and perform theoperation again.

GLPWRM081E Failed to create topology onconsumer consumer name. Synchronizethe topology on the new server. Refer tothe IBM Tivoli Directory ServerInstallation and Configuration Guidefor instructions.

Explanation: An error occurred running thereplication topology extended operation on thesupplier. The topology information was not replicatedto the consumer server.

User response: Rerun the replication topologyextended operation from the command line on thesupplier to replicate the topology to the consumer. Ifthat does not work, manually synchronize the topologyon two servers. Refer to the IBM Tivoli Directory ServerInstallation and Configuration Guide for instructions.The error might have occurred for one of the followingreasons: The consumer server is down and notreachable by the supplier server. The supplier server isnot able to connect to the consumer server due toincorrect credentials. Error while adding replicationobjects on the consumer server. Failed to execute thecascading control replication extended operation forquiesce or unquiesce subtree on consumer server. Thereis another error during the operation. Contact thedirectory administrator.



GLPWRM082E Failed to create supplier credentialson consumer consumer name. Thesupplier credentials must be created onthe consumer for replication to work.Refer to the IBM Tivoli Directory ServerAdministration Guide for instructions.

Explanation: An error occurred while creatingsupplier credentials on the consumer server.

User response: The error might have occurred for oneof the following reasons: The consumer server is downand not reachable by the supplier server. Incorrectadministrative credentials were provided for theconsumer server. There is another error whileperforming the operation. Contact the directoryadministrator.

GLPWRM083E Failed to connect to consumer serverconsumer name.

Explanation: Failed to log in to the consumer serverwhile trying to create supplier credentials on theconsumer.

User response: The error might have occurred for oneof the following reasons: The consumer server is downand not reachable by the supplier server. Incorrectadministrative credentials provided for the consumerserver. There is another error while performing thisoperation. Contact the directory administrator.

GLPWRM084E Failed to start consumer serverconsumer name.

Explanation: Failed to start the consumer server.

User response: The error might have occurred for oneof the following reasons: The administration server isnot running on the consumer server or theadministrative port provided is not correct. Incorrectadministrative credentials provided for consumerserver. There is another error while performing thisoperation. Contact the directory administrator.

GLPWRM085E Cannot connect to administrationserver.

Explanation: Unable to connect to administrationserver of consumer server.

User response: The error might have occurred for oneof the following reasons: Administration server is notrunning on the consumer server. Administration serverport provided is not correct. Consumer server is notreachable through the network.

GLPWRM086E Failed to restart to consumer serverserver name.

Explanation: Failed to restart the consumer server.

User response: The error might have occurred for one

of the following reasons: The administration server isnot running on the consumer server or theadministrative port provided is not correct. Incorrectadministrative credentials provided for consumerserver. There is another error while performing thisoperation. Contact the directory administrator.

GLPWRM088E The server server name is a proxyserver. A proxy server cannot be addedto the replication topology

Explanation: The server specified during the addreplica or add master operation is a proxy server andcannot be added to the topology.

User response: Select a server that is not a proxyserver.

GLPWRM089E Cannot move source server becausethere are agreements associated with it.

Explanation: The master server being moved hasagreements associated with it. These must be deletedbefore the move operation can continue.

User response: Delete all the agreements under themaster server and retry the move operation.

GLPWRM090E The requested operation cannot beperformed. The server being promotedis already a master server.

Explanation: You are trying to promote a server to bea master server in the topology, but the selected serveris already a master server.

User response: A master server cannot be promoted tobe a master. Select a replica to be promoted.

GLPWRM091E The requested operation cannot beperformed. The old and new supplierscannot both be master servers.

Explanation: You are trying to move a server under amaster server, but the server being moved is a masterserver in the topology. A master server cannot bemoved under another master.

User response: Select a different server to move andretry the operation.

GLPWRM092E Cannot connect to server. Themanage topology function must connectto the server being promoted to performthis operation.

Explanation: There was an error connecting to theserver that is being promoted to be a master server.The server must be running and reachable before it canbe promoted.

User response: Check to see if the server is down.Start it and retry the operation.



GLPWRM093E The selected node cannot be deleted.

Explanation: An attempt was made to delete thereplication topology node, which does not representany server in the topology and cannot be deleted.

User response: Select a node in the tree to delete thatis a server in the replication topology.

GLPWRM094W Consumer server server name mustbe restarted for the supplier credentialto take effect. Do you want to restart theserver?

Explanation: Continuing with this operation willrestart the specified consumer server.

User response: Click OK to restart the consumerserver or Cancel to cancel the operation.

GLPWRM095E Cannot edit the ACL for thissubtree. One can only edit the ACL on aserver that is a master server for thissubtree.

Explanation: You are trying to edit an ACL for asubtree. The Web Administration Tool is not connectedto the master server for this subtree.

User response: Select a different subtree for which toedit an ACL, or connect to a server that is a masterserver in the selected replication context, and thenperform the edit ACL operation.

GLPWRM096E The selected node cannot be moved.

Explanation: You are attempting to move a node thatis not a subentry node or an agreement node.

User response: Select a node in the tree that is either asubentry node or an agreement node.

GLPWRM097E Cannot delete a node that hasagreements under it.

Explanation: You are attempting to delete a subentrynode in the topology that has agreements under it.

User response: First delete all the agreements underthe selected node, and then delete the node.

GLPWRM098E The selected node cannot be edited.

Explanation: You are attempting to edit a node in thereplication topology that is not an agreement node.

User response: Select an agreement node to edit.

GLPWRM099E Hostname or port not provided.

Explanation: The hostname or port was not providedduring the add master or add replica operation.

User response: Provide a valid hostname and port forthe server being added to the topology.

GLPWRM100E Referral LDAP URL not valid.

Explanation: The referral LDAP URL provided is notvalid. Type a valid LDAP URL.

User response: Provide a valid referral URL. It muststart with ldap:// or ldaps://.

GLPWRM101E Cannot delete this subtree. There arenon-empty ibm-replicaGroup objectsunder this replication context.

Explanation: The subtree being deleted has replicationrelated entries under it.

User response: Make sure that the subtree does nothave any agreements or subentries under it and thentry the delete operation again.

GLPWRM102E The entry does not exist or thelogged-in user does not have sufficientauthority to perform this operation.

Explanation: Failed to retrieve ACL information forsubtree while checking the ACL during the add subtreeoperation. This is done for non-suffix subtrees.

User response: The user does not have authority toretrieve the ACL information for the subtree or thesubtree does not exist.

GLPWRM103E No credential selected to edit.

Explanation: No valid credential object DN wasprovided for editing credentials. Select a credential toedit.

User response: Provide a valid credential object DNand click Edit.

GLPWRM104E No credential selected.

Explanation: No credential object was selected duringthe add replica or add master operation.

User response: A credential object must be selectedduring an add replica and add master operation foradding a new server in the topology. Select a validcredential object on the Select credential panel. If thereis no credential object defined, add one object andselect it to complete the operation.



GLPWRM105E Cannot create replicated subtree atsubtree DN. Access control is not definedproperly for this entry.

Explanation: While trying to configure a subtree forreplication, an explicit ACL must be defined if the entryis not a suffix entry.

User response: Define an explicit ACL for the subtreeand try the add subtree operation again.

GLPWRM106E Failed to promote a replica under amaster server. There is no replicasubentry corresponding to the server towhich the Web Administration Tool isconnected.

Explanation: Failed to promote a replica under amaster server because there is no replication subentryfor the server present in the replication topology towhich the Web Administration Tool is connected.

User response: Make sure that the WebAdministration Tool is connected to a master server inthe topology, and then try the move operation again.

GLPWRM107E Agreement agreement name does nothave a valid replica ID defined. First setthe replica ID in all agreementssupplying agreement name. If there aremultiple masters, it might be necessaryto change this agreement under eachmaster.

Explanation: You are trying to move a replica server,but the agreement node for the replica does not have avalid server ID defined.

User response: Edit the agreement to add a validserver ID and try the operation again.

GLPWRM108E Cannot promote server to master.The server being promoted must be aleaf replica with no subordinatereplicas.

Explanation: An attempt is being made to promote aserver to a master server, but it has subordinatespresent under it. Only a leaf node with no subordinatescan be promoted to a master server in the topology.

User response: Select a leaf node and try theoperation again.

GLPWRM109E This server cannot be promoted to amaster server.

Explanation: The server being promoted does nothave a correct server ID or enabled capabilities defined,and it cannot be made a master server.

User response: Make sure that the selected agreementto be promoted as master server has a valid server ID

and enabled capabilities defined, and then try theoperation again.

GLPWRM110E The source server and thedestination server are the same. Select adifferent destination server.

Explanation: The source and destination server are thesame during a move operation. The operation failed.

User response: A server cannot be moved under itself.Select different source and destination servers for themove operation to succeed.

GLPWRM111E Unable to delete the subtree

Explanation: Unable to delete the selected subtree. Anerror occurred while deleting the subtree, the replicadefault group, and the associated auxiliary objectclass.

User response: The error might have occurred for oneof the following reasons: The user does not havepermission to delete the selected subtree. Checkwhether the subtree entry has permission for the userto delete this entry. There is another error deleting theentry ibm-replicaGroup=default under the subtree.Contact IBM Software Support.

GLPWRM112E Unable to get ACL information.

Explanation: An error occurred while retrieving ACLinformation from the directory server and traversingthe information.

User response: The error might have occurred for oneof the following reasons: The user might not havepermission to retrieve ACL information. The server isnot reachable or is running in configuration only mode.There is another error while retrieving ACLinformation. Contact IBM Software Support.

GLPWRM113E The time selected has already beenscheduled.

Explanation: The specified time has already beenadded to the daily schedule. A duplicate entry is notallowed.

User response: Specify a new time such that the newtime does not conflict with any other time value in thecurrent daily schedule.

GLPWRM114E Select a subtree.

Explanation: A subtree must be selected to performthe operation.

User response: Select a subtree and try to perform thisoperation again.



GLPWRM115E Select an entry in the table toremove.

Explanation: A row from the table must be selected toperform the remove operation.

User response: Select a row from the table and retrythe remove operation.

GLPWRM116E Unable to add schedule. Theschedule object schedule object namealready exists.

Explanation: The specified schedule already exists. Anerror occurred trying to add a duplicate scheduleobject.

User response: Specify a different schedule to add.

GLPWRM117E Master DN cannot be the same asthe administrator DN.

Explanation: A Master DN was provided that is thesame as the administrator DN. These DNs must bedifferent.

User response: Provide a Master DN that is differentfrom the administrator DN.

GLPWRM118E Default credential has already beendeleted.


User response: Select supplier information to delete.

GLPWRM119E Passwords do not match.

Explanation: The values typed in the Replication bindpassword and Confirm password fields must be exactlythe same. These fields are case-sensitive. The valuesspecified in these two fields do not match.

User response: Provide the same value in theReplication bind password and Confirm passwordfields.

GLPWRM120E Select an entry in the list.

Explanation: A supplier information entry from thelist must be selected to perform the operation.

User response: Select a supplier information entryfrom the list and then retry the operation.

GLPWRM121E The subtree subtree DN already has asupplier object associated with it.Choose a different replicated subtree.

Explanation: The subtree is already present undercn=configuration and already has a supplier credential.A duplicate entry is not allowed.

User response: Select a different replicated subtree.

GLPWRM122E Replica bind DN is a required field.

Explanation: The replica bind DN field cannot beblank while adding a credential object.

User response: Specify a valid replica bind DN tocreate a credential object.

GLPWRM123E Bind password is a required field.

Explanation: The bind password field is a requiredfield for adding a credential object.

User response: Specify a valid bind password tocreate a credential object.

GLPWRM124E This subtree was originally createdas a non-replicated subtree. To createcredentials in this subtree, the subtreemust be initialized for replication withthis server as the master. Click OK toinitialize the subtree.

Explanation: A non-replicated subtree must beinitialized for replication as the master before creatingcredentials. Continuing with the operation willinitialize the subtree.

User response: Click OK to initialize the subtree forreplication or Cancel to cancel the credential creationoperation.

GLPWRM125E Confirm password is a requiredfield.

Explanation: The Confirm password field is a requiredfield for adding a credential object.

User response: Type the password in the Confirmpassword field to create a credential object.

GLPWRM126E Passwords do not match.

Explanation: The values typed in the Key filepassword and Confirm password fields must be exactlythe same. These fields are case-sensitive. The valuesspecified in these two fields do not match.

User response: Provide the same value in the Key filepassword and Confirm password fields.

GLPWRM127E Simple bind credential details notspecified.

Explanation: The simple bind credentials must bespecified before going to the next step.

User response: Specify the simple bind credentials,and then click Next.



GLPWRM128E Credential not selected.

Explanation: A credential must be selected to performthis operation.

User response: Select a credential and retry theoperation.

GLPWRM129E Select a replication filter.

Explanation: A replication filter for the selectedsubtree must be selected to perform this operation.

User response: Select a replication filter for theselected subtree and retry the operation.

GLPWRM130E Unable to add the credential. Thecredential object credential object namealready exists.

Explanation: The specified credential object alreadyexists at the selected subtree. An error occurred whileadding a duplicate value to the directory server.

User response: Specify a different credential object toadd the credentials.

GLPWRM131E Unable to add the replication filter.The filter object filter object name alreadyexists.

Explanation: The specified replication filter alreadyexists. An error occurred while adding a duplicatevalue to the directory server.

User response: Specify a different replication filter.

GLPWRM132E Select at least one object class orselect the check box to include all objectclasses.

Explanation: At least one objectclass must be selectedbefore proceeding.

User response: Select at least one objectclass.

GLPWRM133E Select at least one attribute or selectthe check box to include all attributes.

Explanation: At least one attribute must be selected.

User response: Select at least one objectclass and retrythe operation.

GLPWRM134W You have requested to skip allunreplicated changes for thisagreement.Click OK to continue withthis request, or click Cancel.

Explanation: Continuing with this operation willdelete all unreplicated changes from replication queue.

User response: Click OK to go ahead or click Cancelto end the operation.

GLPWRM136W Are you sure you want to delete theselected node node names from thetopology ?

Explanation: Continuing with this operation willdelete the selected node from the topology.

User response: Click OK to delete the selected nodefrom the topology or click Cancel to cancel the deleteoperation.

GLPWRM137W Warning: All the agreements underthe selected master will be deleted. Areyou sure you want to continue?

Explanation: Continuing with this operation willdelete all the agreements under the selected master.

User response: Click OK to delete all the agreementsunder the selected master from the topology or clickCancel to cancel the delete operation.

GLPWRM138W This subtree is a non-replicatedsubtree. To edit ACLs for this subtree,the subtree must be initialized forreplication with this server as themaster. Click OK to continue.

Explanation: A non-replicated subtree must beinitialized for replication as the master before editingthe ACLs. Continuing with the operation will initializethe subtree.

User response: Click OK to initialize the subtree forreplication or click Cancel to cancel the deleteoperation.

GLPWRM139W The current server to which you areconnected to will become a master forthis subtree. Are you sure you want tocontinue?

Explanation: Continuing with this operation willmake the current server the master for this subtree.

User response: Click OK to make the current serverthe master for the subtree or click Cancel to cancel theoperation.

GLPWRM140W If you cancel this request, the newserver will not be added to the topology.Are you sure you want to cancel?

Explanation: Continuing with this process will cancelthe earlier requested operation.

User response: Click OK to cancel the operation orclick Cancel to continue with the operation.

GLPWRM128E • GLPWRM140W


GLPWRM141W If you cancel this request, the moveoperation will not be completed. Areyou sure you want to cancel?

Explanation: Continuing with this process will cancelthe requested move operation.

User response: Click OK to cancel the move operationor click Cancel to continue with the operation.

GLPWRM142W Are you sure you want to quiescethe subtree subtree DN?

Explanation: Continuing with this operation willquiesce the selected subtree.

User response: Click OK to quiesce the selectedsubtree or click Cancel to cancel the quiesce operation.

GLPWRM143W Are you sure you want to delete thesubtree subtree DN?

Explanation: Continuing with this operation willdelete the selected subtree.

User response: Click OK to delete the selected subtreeor click Cancel to cancel the delete operation.

GLPWRM144W Are you sure you want to unquiescethe subtree subtree DN?

Explanation: Continuing with this operation willunquiesce the selected subtree.

User response: Click OK to unquiesce the selectedsubtree or click Cancel to cancel the unquiesceoperation.

GLPWRM145W Are you sure you want to deletethis daily schedule?

Explanation: Continuing with this operation willdelete the selected daily schedule.

User response: Click OK to delete the selected dailyschedule or click Cancel to cancel the delete operation.

GLPWRM146W Are you sure you want to deletethis weekly schedule?

Explanation: Continuing with this operation willdelete the selected weekly schedule.

User response: Click OK to delete the selected weeklyschedule or click Cancel to cancel the delete operation.

GLPWRM147W Are you sure you want to removethis entry?

Explanation: Continuing with this operation willdelete the selected supplier information.

User response: Click OK to delete the selected

supplier information or click Cancel to cancel the deleteoperation.

GLPWRM148W Are you sure you want to delete theselected credential object?

Explanation: Continuing with this operation willdelete the selected credential object.

User response: Click OK to delete the selectedcredential object or click Cancel to cancel the deletionoperation.

GLPWRM149W Are you sure you want to deletethis replication filter object?

Explanation: Continuing with this operation willdelete the selected replication filter object.

User response: Click OK to delete the selectedreplication filter object or click Cancel to cancel thedeletion operation.

GLPWRM156E The selected node is neither amaster nor a gateway. Select a master orgateway node and then click Viewserver.


User response: Select a master or gateway node andthen click View server.

GLPWRM165E The selected node is neither amaster nor a gateway. Select a master orgateway node and then click Viewschedule.


User response: Select a master or gateway node andthen click View schedule.

GLPWRM168E Incorrect DN: DN.

Explanation: The specified DN does not exist in thedirectory server.

User response: Select a valid DN by clicking on theBrowse button or type a valid DN that exists in thedirectory server.

GLPWRM904E This subtree was originally createdas a non-replicated subtree. To createreplication filters in this subtree, thesubtree must be initialized forreplication with this server as themaster. Click OK to initialize thesubtree.

Explanation: A non-replicated subtree must beinitialized for replication as the master before creating

GLPWRM141W • GLPWRM904E


replication filters. Continuing with the operation willinitialize the subtree.

User response: Click OK to initialize the subtree forreplication or Cancel to cancel the replication filtercreation operation.

GLPWRM9838W Warning: This will only delete theagreement agreement with the selectedsupplier.If this node consumes changesfrom other suppliers, you must deleteeach of those agreements separately inorder to completely remove it from thetopology.

Explanation: Continuing with this operation willdelete agreement with selected supplier.

User response: Click OK to delete the selected nodefrom the topology or click Cancel to cancel the deleteoperation.

GLPWRP001E Ran wrapper script on anunsupported operating system: OS

Explanation: The script can be run only on Linux,AIX, Solaris or HP-UX systems.

User response: Check your operating system type byrunning this command: uname. Also, verify that youhave permission to run the uname command.

GLPWRP002E The program program name is notinstalled or could not be found.

Explanation: The script could not find the programthat was going to be invoked. This most likely occurredbecause the program was removed or you do not havepermissions to run the program.

User response: Verify that you have permission to runthe program the script was going to execute. Theprogram will be in the 32 or 64 directory at a levelbelow where the script invoked is located. If theprogram is not present you might have to reinstall theIBM Security Directory Server product. Contact IBMSoftware Support if you continue to encounterproblems with the script.

GLPWRP003E The java command at location is notinstalled or could not be found.

Explanation: The script could not find the javaprogram that was going to be invoked. This most likelyoccurred because the program was removed or you donot have permissions to run the program.

User response: Verify that you have permission to runthe program the script was going to execute. If theprogram is not present you might have to reinstall theIBM Security Directory Server product. Contact IBMSoftware Support if you continue to encounterproblems with the script.

GLPWRP004W Could not remove oldest archivedcore file because write access is neededfor: filename.

Explanation: The script could not remove the oldestarchived core file. This most likely occurred becauseyou do not have the necessary permissions to removethe file or to access the directory where the file resides.

User response: Verify that you have write permissionson the file the script was going to delete. Contact thesystem administrator to remove the file if you do nothave the necessary permissions.

GLPWRP006E The DB2 property file 'filename' is notavailable.

Explanation: The script could not find theldapdb.properties file. This most likely occurredbecause you do not have the necessary permissions toread the file or the file is not available.

User response: Verify that you have a validldapdb.properties file with the necessary permissions toread the file.

GLPWRP007E The instance instance is not created orcould not be found.

Explanation: The script could not find the location ofthe instance created. This most likely occurred becauseyou have specified an invalid instance name.

User response: Verify that you have specified a validinstance name.

GLPWRP008E The instance instance is either not aTDS version version instance or it doesnot exist.

Explanation: This most likely occurred because eitherthe TDS version for the instance is different from theTDS version for this utility or instance does not exist.

User response: Verify that you are running the correctversion of the utility and using the existing instance.

GLPWRP009E The instance type (PROXY or RDBM)for instance instance was not found.

Explanation: This most likely occurred because theinstance type entry is missing or not valid in theibmslapd.conf configuration file.

User response: Verify that your ibmslapd.conf file hasa valid entry for instance type.

GLPWRP010E The executable 'progname' cannot beused on the PROXY server instance'instance'.

Explanation: This most likely occurred because an

GLPWRM9838W • GLPWRP010E


attempt was made to use this utility on a proxy serverinstance.

User response: Verify that the instance name specifiedis not a proxy server instance.

GLPWRP011E The executable progname cannot beused on the default PROXY serverinstance instance.

Explanation: This most likely occurred because anattempt was made to use this utility on the defaultserver instance which is of type proxy.

User response: Verify that the default instance in therepository is not a proxy server instance.

GLPWRP012E An invalid file name was specified.

Explanation: The file does not exist or could not beread.

User response: Verify that the file exists with properpermissions to access it.

GLPWRP013E DB2 versions prior to 9.1 are notsupported.

Explanation: This version of Security Directory Serverdoes not support DB2 versions prior to 9.1.

User response: Install the correct version of DB2 andperform the operation again.

GLPWRP014E A supported version of IBM DB2 isnot installed on the system, or theldapdb.properties file does not containinformation about the supported IBMDB2 version.

Explanation: This version of IBM Security DirectoryServer supports IBM DB2 version 9.5 or later.

User response: Install the correct version of DB2 andperform the operation again.

GLPWSA004E Some of the changes could not besaved.

Explanation: Some of the changes were not saved. Anerror might have occurred for one of the followingreasons: There might be a problem connecting to theserver. The input value specified might be incorrect.There might be a problem in the server configurationfile.

User response: Verify that you are connected to theserver and that the input value is correct.

GLPWSA005E Cannot connect to administrationserver.

Explanation: The tool could not connect to theadministration server. Verify that the administrationserver is running and that the server is reachablethrough the network. Check that the correct port forthe administration server was specified whileregistering the server in the Web Administration Tool.

User response: An error might have occurred for oneof the following reasons: The administration serverprocess might not be running. Start or restart theadministration server. There might be a problem in thenetwork. Check the network settings and verify thatthe server is reachable through the network. Be surethat the correct administration server port wasprovided while registering the server.

GLPWSA006E The confirmation password forsimple bind is incorrect.

Explanation: The values typed in the Bind passwordand Confirm password fields must be exactly the same.These fields are case-sensitive. The values specified inthese two fields do not match.

User response: Provide the same value in the Bindpassword and Confirm password fields.

GLPWSA009E Passwords do not match.

Explanation: The values typed in the password andconfirm password fields must be exactly the same.These fields are case-sensitive. The values specified inthese two fields do not match.

User response: Provide the same value in the Newpassword and Confirm password fields.

GLPWSA010E The confirmation password isincorrect on the certificate revocationpanel.

Explanation: The values typed in the Bind passwordand Confirm password fields must be exactly the same.These fields are case-sensitive. The values specified inthese two fields do not match.

User response: Provide the same value in the Bindpassword and Confirm password fields.

GLPWSA011E The Certificate revocation list DNwas not created. The input value mightbe incorrect.

Explanation: The Certificate revocation list DN wasnot created. Some of the required fields on thecertificate revocation panel might be empty or mighthave incorrect values.

User response: Provide valid values for all the fieldson the certificate revocation panel.

GLPWRP011E • GLPWSA011E


GLPWSA012E The Kerberos DN was not created.The value provided might be incorrect.

Explanation: Some of the required fields on theKerberos panel might be empty or have incorrectvalues.

User response: To create a Kerberos DN, provide validvalues for the Kerberos realm, Kerberos keytab file, andAlternate administrator ID fields on the Kerberos panel.To delete a Kerberos DN, remove the values of thesefields.

GLPWSA015E Incorrect Directory Serveradministrator DN syntax.

Explanation: An incorrect DN was specified. The fieldmust contain a well-formed distinguished name. Seethe IBM Tivoli Directory Server Administration Guidefor information about valid DN syntax.

User response: Type a valid Directory Serveradministrator DN.

GLPWSA016E Incorrect Directory Serveradministrator DN.

Explanation: The Directory Server administrator DN isincorrect.

User response: Type a valid Directory Serveradministrator DN.

GLPWSA017E Incorrect Kerberos ID.

Explanation: The Kerberos ID is incorrect. The syntaxor the prefix might be incorrect. The Kerberos ID muststart with either ibm-kn or ibm-kerberosName.

User response: Type a valid Kerberos ID.

GLPWSA018E Incorrect syntax for Kerberos ID.

Explanation: The Kerberos ID is incorrect. This IDmust consist of two tokens.

User response: Type a valid Kerberos ID that consistsof two tokens.

GLPWSA019E Incorrect prefix for Kerberos DN.

Explanation: The prefix of the Kerberos ID isincorrect. The Kerberos ID must start with eitheribm-kn or ibm-kerberosName.

User response: Type a valid Kerberos ID with a validprefix.

GLPWSA020E Passwords do not match. Somechanges were saved.

Explanation: The values typed in the Password andConfirm password fields must be exactly the same.These fields are case-sensitive. The values specified inthese two fields do not match. Some of the changeswere saved; however, not all changes were savedbecause the two password fields did not match.

User response: Provide the same value in thePassword and Confirm password fields.

GLPWSA021E PKCS#11 interface support isenabled. All fields must be completedand you must select either the keystorage or the accelerator mode optionor both. Some of the changes weresaved.

Explanation: PKCS#11 interface support is enabled.When PKCS#11 interface support is enabled, all fieldson PKCS#11 settings panel must be completed and youmust select either the key storage or the acceleratormode option or both. Some of the changes were saved.Not all changes were saved because of incorrect input.

User response: Complete all the fields and select thekey storage or the accelerator mode option or both.

GLPWSA022E Passwords do not match. Somechanges were saved and will take effectafter the server is restarted.

Explanation: The value typed in the Password andConfirm password fields must be exactly the same.These fields are case-sensitive. The values specified inthese two fields do not match. Some of the changeswere saved; however, not all changes were savedbecause the two password fields did not match. Thesaved changes will take effect only after the server isrestarted.

User response: Provide the same value in thePassword and Confirm password fields. Restart theserver for the changes that were saved to take effect.

GLPWSA023E PKCS#11 interface support isenabled. All fields must be completedand you must select either the keystorage or the accelerator mode optionor both. Some of the changes weresaved and will take effect after theserver is restarted.

Explanation: PKCS#11 interface support is enabled.When PKCS#11 interface support is enabled, all fieldsmust be completed and you must select either the keystorage or the accelerator mode option or both. Some ofthe changes were saved but will take effect only afterthe server is restarted; however, not all changes weresaved because of incorrect input. The saved changes

GLPWSA012E • GLPWSA023E


will take effect only after the server is restarted.

User response: Complete all the fields and select thekey storage or the accelerator mode option or both.Restart the server for the changes that were saved totake effect.

GLPWSA024E PKCS#11 interface support isenabled. All fields must be completedand you must select either the keystorage or the accelerator mode optionor both.

Explanation: PKCS#11 interface support is enabled.When PKCS#11 interface support is enabled, all fieldsmust be completed and you must select either the keystorage or the accelerator mode option or both.

User response: Complete all the fields and select thekey storage or the accelerator mode option or both.

GLPWSA025W Are you sure you want to delete theselected administrative group memberDN?

Explanation: Continuing with this operation willdelete the selected administrative group member DNfrom the directory.

User response: Click OK to delete the selectedadministrative group member DN or Cancel to cancelthe delete operation.

GLPWSA026W Are you sure you want to delete theselected suffix DN?

Explanation: Continuing with this operation willdelete the selected suffix from the directory.

User response: Click OK to delete the selected suffixDN or Cancel to cancel the delete operation.

GLPWSA027E Current password is incorrect.

Explanation: The Current password field value doesnot match the existing password of the specifiedDirectory Server administrator DN.

User response: Type a valid password for thespecified administrator DN in the Current passwordfield .

GLPWSA028E Secure port and unsecure port cannothave the same value.

Explanation: The same port number is specified forboth the secure and unsecure port numbers. Both ofthese port numbers must be unique.

User response: Specify unique port numbers for thesecure port and the unsecure port.

GLPWSA031E The administrator DN value alreadyexists.

Explanation: The specified administrator DN valuealready exists in the administrator group.

User response: Type a different administrator DNvalue to add to the administrator group.

GLPWSA032E The selected available attributealready exists under cn=localhost.

Explanation: The selected available attribute alreadyexists under cn=localhost.

User response: Select an attribute name in theAvailable attributes list that does not exist in thecn=localhost attribute list.

GLPWSA033E The selected available attributealready exists under cn=IBMpolicies.

Explanation: The selected available attribute alreadyexists under cn=IBMpolicies.

User response: Select an attribute name in theAvailable attributes list that does not exist in thecn=IBMpolicies list.

GLPWSA034E The selected available attributealready exists in the list of cachedattributes under database.

Explanation: The selected available attribute alreadyexists in the list of cached attributes under database.

User response: Select an attribute name in theAvailable attributes list that does not exist in the list ofcached attributes under database.

GLPWSA035E The selected available attributealready exists in the list of cachedattributes under changelog.

Explanation: The selected available attribute alreadyexists in the list of cached attributes under changelog.

User response: Select an attribute name in theAvailable attributes list that does not exist in the list ofcached attributes under changelog.

GLPWSA036E This suffix DN value already exists.

Explanation: The suffix DN provided already exists inthe server.

User response: Type a valid suffix DN that does notexist in the server and then click Add.



GLPWSA037W Are you sure you want to clear thelog file?

Explanation: Continuing with this operation will clearthe log file.

User response: Click on OK to clear the log file orCancel to cancel the clear operation.

GLPWSA038E Select at least one DN or IP addressto disconnect.

Explanation: Select at least one DN or IP address forthe disconnect operation to be successful. Disconnectwith both DN and IP being None is not a validoperation.

User response: Select at least one DN or IP and thenclick Disconnect.

GLPWSA039W Are you sure you want to disconnectall connections?

Explanation: Continuing with this operation willdisconnect all the server connections.

User response: Click OK to disconnect all the serverconnections or click Cancel to cancel the operation.

GLPWSA040E Failed to either add or edit passwordpolicy object.

Explanation: The specified input violates at least oneof the password policy rules. Password Policy Rules arefollowing: 1. pwdMinLength should be greater than orequal to pwdMinOtherChars + passwordAlphaChars 2.pwdMinLength should be greater than or equal topwdMinDiffChars 3. pwdMaxAge should be greaterthan pwdMinAge 4. pwdMaxAge should be greaterthan or equal to pwdExpireWarning 5.pwdAllowUserChange has to be TRUE, ifpwdMustChange is TRUE 6.passwordMaxRepeatedChars should be greater than orequal to passwordMaxConsecutiveRepeatedChars

User response: Specify input that does not violate thepassword policy rules.

GLPWSA041E The specified administrator DNalready exists. Specify a newadministrator DN.

Explanation: The new administrator DN must bedifferent than the earlier existing administrator DN.The specified administrator DN is exactly the same asthe earlier administrator DN.

User response: Specify a new administrator DN.

GLPWSA042E Type a valid value for the serverrealm in the Digest-MD5 panel.

Explanation: The server realm field of the Digest-MD5panel has an incorrect value. The server realm cannotbe blank or contain only spaces.

User response: Type a valid value for the server realmin the Digest-MD5 panel.

GLPWSA043E Type a valid value for the Usernameattribute in the Digest-MD5 panel.

Explanation: The Username attribute field of theDigest-MD5 panel has an incorrect value. TheUsername attribute cannot be blank or contain onlyspaces.

User response: Type a valid value for the Usernameattribute in Digest-MD5 panel.

GLPWSA044W Are you sure you want to delete theselected back-end directory servers?

Explanation: Continuing with this operation willdelete the selected directory server.

User response: Click OK to delete the selectedback-end server or click Cancel to cancel the operation.

GLPWSA045W Are you sure you want to delete allback-end directory servers?

Explanation: Continuing with this operation willdelete all back-end directory servers.

User response: Click OK to delete all the back-endservers or click Cancel to cancel the operation.

GLPWSA046E Passwords do not match.

Explanation: The values typed in the Key filepassword and Confirm password fields must be exactlythe same. These fields are case-sensitive. The valuesspecified in these two fields do not match.

User response: Provide the same value in the Key filepassword and Confirm password fields.

GLPWSA050E An error occurred while editing aback-end directory server.

Explanation: The updates to the back-end directoryserver were not saved successfully. An error might haveoccurred for one of the following reasons: Not able toconnect to server. The updated values in some of thefields might not be valid for the directory server.

User response: Check whether the server is up andrunning; if not, start the server. Check whether thereare any incorrect values in the fields, and then typevalid values.

GLPWSA037W • GLPWSA050E


GLPWSA051E An error occurred while adding theback-end directory server.

Explanation: The back-end directory server was notadded. An error might have occurred for one of thefollowing reasons: Not able to connect to server. Thevalues in some of the fields might not be valid for thedirectory server.

User response: Check whether the server is up andrunning; if not, start the server. Check whether thereare any values in the fields, and then type valid values.

GLPWSA052E An error occurred while deletingback-end directory servers.

Explanation: The selected back-end directory serverwas not deleted. An error might have occurred for oneof the following reasons: Not able to connect to server.The selected server might not be a valid back-enddirectory server.

User response: Check whether the server is up andrunning; if not, start the server. Check whether theselected server is a valid back-end directory server.

GLPWSA053E An error occurred while loadingback-end directory server information.

Explanation: An error occurred while loadinginformation to the back-end directory server. The errormight have occurred for one of the following reasons:Not able to connect to server. There might be incorrectentries or an incorrect DN.

User response: Check that the back-end directoryserver information is correct and that the servers arerunning in normal mode.

GLPWSA054E Kerberos is not enabled for the proxyserver.

Explanation: Kerberos was selected as the bindmethod, but Kerberos is not enabled. Enable Kerberosbefore selecting it as the bind method for the back-enddirectory server.

User response: Enable Kerberos and then set the bindmethod as Kerberos.

GLPWSA055E Incorrect suffix DN.

Explanation: The suffix specified in the Suffix DNfield is incorrect. A valid suffix consists of three parts.The first part is a valid naming attribute present in theschema; the second part is the symbol '='; and the thirdpart is a valid value for the first part. The syntax of thesuffix must be 'attribute=value'.

User response: Type a valid suffix DN.

GLPWSA056E Incorrect DN specified for displayingentry details.

Explanation: The entry DN specified for displayingthe entry details is incorrect. See the IBM TivoliDirectory Server Administration Guide for informationabout valid DN syntax.

User response: Type a valid entry DN.

GLPWSA057E Incorrect DN specified as partitionbase DN, while adding a split.

Explanation: The partition base DN specified foradding a split is incorrect. See the IBM Tivoli DirectoryServer Administration Guide for information aboutvalid DN syntax.

User response: Type a valid partition base DN.

GLPWSA058E Incorrect DN specified for the bindDN.

Explanation: The bind DN specified for displaying theentry details is incorrect. See the IBM Tivoli DirectoryServer Administration Guide for information aboutvalid DN syntax.

User response: Type a valid bind DN.

GLPWSA059E Select a referral entry to remove fromthe table.

Explanation: A referral entry must be selected in thetable for the remove operation to be successful.

User response: In the table, select the referral entry toremove.

GLPWSA060E Select a suffix DN entry to removefrom the table.

Explanation: A suffix DN entry must be selected inthe table for the remove operation to be successful.

User response: In the table, select the suffix DN entryto remove.

GLPWSA061E Select a suffix DN entry in the tableto edit.

Explanation: A suffix DN entry must be selected inthe table for the edit operation to be successful.

User response: In the table, select the suffix DN entryto edit.

GLPWSA062E No partition entry is selected. Selectan entry in the partition entries table todisplay the associated servers.

Explanation: Select the partition entry to display theassociated servers.



User response: Select a partition entry in the table.

GLPWSA063E No partition base DN entry isselected. Select the partition base DNentry in the table for which you want toperform the resume role operation.

Explanation: Select the partition base DN for whichyou want to perform the resume role operation.

User response: Select a partition base DN entry in thetable.

GLPWSA064E No back-end directory server entry isselected. Select the back-end directoryserver entry in the table for which youwant to perform the resume roleoperation.

Explanation: Select the back-end directory server forwhich you want to perform the resume role operation.

User response: Select a back-end directory serverentry in the table.

GLPWSA065E No partition base DN entry isselected. Select the partition base DNentry you want to delete.

Explanation: You must select the partition base DNyou want to delete.


GLPWSA066E No partition base DN entry isselected. Select the entry in the table forthe partition base DN to edit.

Explanation: Select the partition base DN to edit.


GLPWSA067E No back-end directory server entry isselected. Select the back-end directoryserver entry to delete.

Explanation: Select the back-end directory server todelete.


GLPWSA068E No back-end directory server entry isselected. Select the entry in the table forthe back-end directory server to edit.

Explanation: Select the back-end directory server toedit.


GLPWSA069E No back-end directory server entry isselected. Select a back-end directoryserver entry in the table for which youwant to view the correspondingpartition bases.

Explanation: Select the back-end directory server forwhich you want to view the corresponding partitionbases.


GLPWSA070E Suffix DN value is incorrect. Type avalid DN.

Explanation: The suffix DN value to be added isincorrect; this value cannot be blank or contain onlyspaces.

User response: Type a valid suffix DN value.

GLPWSA071W Are you sure you want to delete theselected back-end directory server splitentry?

Explanation: Continuing with this operation willdelete the selected back-end directory server split entry.

User response: Click OK to delete the selected splitentry or Cancel to cancel the delete operation.

GLPWSA072W Are you sure you want to delete theselected partition base DN entry?

Explanation: Deleting the selected partition base entryresults in deletion of all the back-end directory serversplits for the selected partition base. Confirm that youwant to delete the partition base DN and itscorresponding back-end directory server split entries.

User response: Click OK to delete the selectedpartition base DN and the corresponding back-enddirectory server split entries, or click Cancel to cancelthe delete operation.

GLPWSA073W Are you sure you want to delete allthe back-end directory server splits?

Explanation: Continuing with this operation willdelete the back-end directory server splits.

User response: Click OK to delete all the split entriesor Cancel to cancel the delete operation.

GLPWSA074E Incorrect partition index value.Partition index value is more than thenumber of partitions.

Explanation: The partition index value must be lessthan or equal to the number of partitions for thepartition base.



User response: Type a partition index value that isless than or equal to the number of partitions for thepartition base.

GLPWSA075E Incorrect number of partitions. Thereexists a partition index value greaterthan the specified number of partitions.

Explanation: A partition index value exists that isgreater than the number of partitions specified.

User response: Type a value for the number ofpartitions that is greater than all existing partitionindex values for the partition base.

GLPWSA076E The specified back-end directoryserver entry already exists.

Explanation: Attempt to create a back-end directoryserver that already exists failed.

User response: Specify a back-end directory serverthat does not already exist.

GLPWSA077E The specified partition base alreadyexists.

Explanation: Attempt to create a partition base thatalready exists failed.

User response: Type a partition base DN that is notalready present in the proxy server.

GLPWSA078E The specified suffix DN alreadyexists.

Explanation: Attempt to create a suffix DN thatalready exists failed.

User response: Type a suffix DN that is not alreadypresent in the proxy server.

GLPWSA079E An error occurred.

Explanation: This is a general error message. Checkthe error log for more details about the error.

User response: See the error log for more details orcontact the Directory Server administrator.

GLPWSA080E An error occurred while adding thepartition base.



GLPWSA081E An error occurred while editing thepartition base.



GLPWSA082E An error occurred while deleting thepartition base.



GLPWSA084E Resume role extended operationfailed because the selected back-enddirectory server does not exist.

Explanation: The resume role operation failed. Anerror might have occurred for one of the followingreasons: The selected back-end directory server doesnot exist or is not available currently. The syntax of theserver URL might be incorrect. There might be aproblem connecting to one of the selected servers. Theserver did not process the resume role request properly.

User response: Verify that the back-end directoryserver exists and is reachable through the network andthen try the resume role operation again.

GLPWSA086E The format of the split name isincorrect.

Explanation: The resume role operation failed. Anerror might have occurred for one of the followingreasons: The selected partition might not exist. Thesyntax of the split URL might be incorrect. There mightbe a problem connecting to one of the selected servers.The server did not process the resume role requestproperly.

User response: Verify that the back-end directoryserver exists and is reachable through the network andthen try the resume role operation again.

GLPWSA088E Type a valid entry DN to search.

Explanation: The entry DN provided is not valid. Asearch cannot be done on a blank entry DN or an entryDN containing only spaces.

User response: Type a valid entry DN.

GLPWSA089E You clicked 'Select a file containingmultiple DN'. Type the name of a filecontaining multiple DNs, or select a fileusing the Browse button, and then clickSubmit to submit the file on the Web



server. Then click Show entry details.

Explanation: The option 'Select a file containingmultiple DN' is selected. A file containing valid DNsmust first be submitted to the Web server. Type a validfile name or select a file using the Browse button, andthen click Submit to submit the file to the Web server.Then click Show entry details.

User response: Type a valid file name or select a fileusing the Browse button and click Submit. Then clickShow entry details.

GLPWSA090E File cannot be uploaded on Webserver or file not found.

Explanation: The specified file cannot be uploaded onthe Web server. The file path might be incorrect, orthere might be size restrictions or a network problemthat prevented the file from being uploaded.

User response: Verify that the file path is valid andthat the Web server is reachable through the network,and then click Submit.

GLPWSA093E Error retrieving information forentry: DN

Explanation: An error occurred while retrievinginformation for the entry.

User response: Verify that the specified DN has avalid syntax and exists and that there is an activeconnection to the server.

GLPWSA094E Error retrieving information for thefollowing entries: DNs

Explanation: An error occurred while retrievinginformation for the entries.

User response: Verify that the specified DNs have avalid syntax and exist and that there is an activeconnection to the server.

GLPWSA104E Select a role.

Explanation: At least one of the roles must be selectedto perform the operation.

User response: Select at least one of the roles toperform the required operation.

GLPWSA105W Connected to administration server.Not all values are available.

Explanation: At least one of the administration groupmember DNs must be selected to perform the requiredoperation. The Web Administration Tool is connected tothe administration server. As a result, not all the valuesof the panel are available.

User response: Start the directory server in normalmode to view all the values of the panel.

GLPWSA106E Select an administration groupmember DN from the table.

Explanation: At least one of the administration groupmember DN must be selected to perform the requiredoperation.

User response: Select at least one of theadministration group member DNs to perform therequired operation.

GLPWSA108E You have selected a subtree that isnot a suffix. Parent entries for thissubtree will not be available forpass-through authentication. Do youwant to continue ?

Explanation: You have selected a subtree that is not asuffix. Parent entries for this subtree will not beavailable for pass-through authentication. Do you wantto continue ?

User response: None

GLPWSA109E Incorrect port.

Explanation: The port number must be non-zero.

User response: Type a valid port number in numericformat.

GLPWSA110E Specify the Subtree DN.

Explanation: The subtree DN should not be empty.

User response: Add a valid subtree DN.

GLPWSA111E Cannot connect to Pass-throughserver.

Explanation: Unable to connect to the Pass-throughserver. Check to be sure that the server is running andreachable through the network.

User response: The error might have occurred for oneof the following reasons: The server might be down.Start or restart the server. Verify the server name andport number and ensure that the server is running.There might be a problem in the network. Check thenetwork settings and check that the ping command tothe server returns Success.

GLPWSA112E Entries under suffixes'cn=configuration', 'cn=schema','cn=pwdpolicy,cn=ibmpolicies','cn=changelog', and 'cn=localhost'cannot be configured for pass-throughauthentication.

Explanation: Entries under suffixes 'cn=configuration','cn=schema', 'cn=pwdpolicy,cn=ibmpolicies','cn=changelog', and 'cn=localhost' cannot be configuredfor pass-through authentication.



User response: Specify a different subtree DN that isnot under any of the following suffixes:'cn=configuration', 'cn=schema','cn=pwdpolicy,cn=ibmpolicies', 'cn=changelog', or'cn=localhost'.

GLPWSA113E Another subtree under this suffix isalready configured for pass-throughauthentication. Select a subtree in adifferent suffix.

Explanation: Possible errors are 1. Selected DNalready present in subtree DN list 2. Another subtreeunder this selected suffix is already configured forpass-through authentication.

User response: Select a subtree in a different suffix.

GLPWSA114E Password policy rule violated. Verifythe input given.

Explanation: The specified input violates at least oneof the password policy rules. Password Policy Rules arefollowing: 1. pwdMinLength should be greater than orequal to pwdMinOtherChars + passwordAlphaChars 2.pwdMinLength should be greater than or equal topwdMinDiffChars 3. pwdMaxAge should be greaterthan pwdMinAge 4. pwdMaxAge should be greaterthan or equal to pwdExpireWarning 5.pwdAllowUserChange has to be TRUE, ifpwdMustChange is TRUE 6.passwordMaxRepeatedChars should be greater than orequal to passwordMaxConsecutiveRepeatedChars

User response: Specify input that does not violate thepassword policy rules.

GLPWSA115E Subtree DN is not specified.

Explanation: No subtree DN is specified and anattempt is being made to add it in the subtree list.

User response: Specify the subtree DN.

GLPWSA116W Do you want to remove the selectedsubtree DN?

Explanation: Confirmation is required beforeremoving a subtree DN.

User response: Click Yes if you want to remove theselected DN from configured subtree list; otherwise,click No.

GLPWSA117W Do you want to remove theconfigured subtree?

Explanation: Confirmation is required beforeremoving a configured subtree.

User response: Click Yes if you want to remove theconfigured subtree; otherwise click No.

GLPWSA118E The number of registrations perconnection cannot be more than thetotal registrations.

Explanation: The total number of registrations for thedirectory server must be more than the number ofconnections for each connection. An error occurredbecause the above requirement is not met.

User response: Modify the number of registrationssuch that the registrations for each connection will notbe more than the total registrations.

GLPWSA119W Select only one back-end directoryserver to edit.

Explanation: Only one back-end directory server canbe edited at a time. More than one back-end directoryserver is selected.

User response: Select only one back-end directoryserver to edit.

GLPWSA120W Select only one back-end directoryserver to view partition bases.

Explanation: The partition bases can be viewed foronly one back-end directory server at a time. More thanone back-end directory server is selected.

User response: Select only one back-end directoryserver to view partition bases.

GLPWSA121E The number of database connectionsfor replication cannot exceed the totalnumber of database connections.

Explanation: The total number of databaseconnections for the directory server must be more thanthe number of database connections for replication. Anerror occurred as the above requirement is not met.

User response: Modify the number of databaseconnections such that the total database connectionswill not be more than the database connections forreplication .

GLPWSA122E Failed to enable / disable multiplepassword policy.

Explanation: An internal error occurred whileenabling or disabling the multiple password policyfeature.

User response: Try the operation again and if problempersists than contact directory administrator.

GLPWSA123E Global password policy object cannotbe deleted.

Explanation: You cannot delete the global passwordpolicy object.



User response: Select any other password policyobject to delete.

GLPWSA124E Failed to delete the password policyobject.

Explanation: An error occurred while deleting thepassword policy object.

User response: Check if the password policy object isnot in use by some user or group. Contact directoryadministrator if problem persists.

GLPWSA125E Select a role for the administrativegroup member.

Explanation: At least one role should be selected forthe administrative group member. An error occurred, asa role was not defined for the administrative groupmember.

User response: Select a role for the administrativegroup member or deselect the administrative rolecheckbox to create a administrative group member withno special authority.

GLPWSA126W Are you sure you want to delete theselected proxy server group DN entry?

Explanation: Confirm that you want to delete theproxy server group.

User response: Click OK to delete the selected proxyserver group DN, or click Cancel to cancel the deleteoperation.

GLPWSA130E Selected back-end directory serverlist is empty.

Explanation: An error occurred whileadding/modifying the proxy server group.

User response: Proxy server group must contain oneor more back-end directory servers.

GLPWSA132E Error performing operation.

Explanation: An error occurred while starting the logmanagement service.

User response: The error might have occurred for oneof the following reasons: Tivoli Directory Integrator isrequired to be properly configured for the logmanagement service to start. Check whether the TivoliDirectory Integrator is properly installed andconfigured. There is an error with the control logmanagement extended operation. Contact IBM SoftwareSupport.

GLPWSA133E Password policy object with thename policy name already exists.

Explanation: There is already a password policy objectpresent with the name given.

User response: Specify a different name for thepassword policy object you are creating.

GLPWSA134E Password policy object policy name isin use by some user or group and itcannot be deleted.

Explanation: Password policy object is being used byeither a user or group and it cannot be deleted.

User response: To delete this password policy object,modify all users and groups that are using thispassword policy object. Click View to view all usersand groups that are using this policy object.

GLPWSA135W Are you sure you want to delete theselected password policy object?

Explanation: Continuing with this operation willdelete the selected password policy object from thedirectory.

User response: Click OK to delete the selectedpassword policy object or Cancel to cancel the deleteoperation.

GLPWSA136W Are you sure you want to change thenumber of partition for the split?

Explanation: Changing the number of partitions for asplit can lead to problems if data is already loaded.Continuing with this operation will change the numberof partitions for the split and save changes to the proxyserver configuration.

User response: Click OK to save changes to the proxyserver configuration or Cancel to cancel the operation.

GLPWSA137E A parent node or a child node of thespecified suffix DN value already exists.The specified suffix DN value cannot beadded.

Explanation: The specified DN value is a child nodeor a parent node of an existing suffix DN. Hence, thespecified DN cannot be added.

User response: Type a valid suffix DN that does notexist in the server and then click Add.

GLPWSA138E The number of elements from asingle search that can be added to thesearch filter cache should not exceed thenumber of elements in a search filtercache.

Explanation: The total number of elements in a search



filter cache should not be less than the number ofelements from a single search that can be added to thesearch filter cache. An error occurred as the aboverequirement is not met.

User response: Modify the total number of elementsin the search filter cache such that it is not less than thetotal number of elements from a single search that canbe added to the search filter cache.

GLPWSA150E The backup/restore directory pathspecified is invalid.

Explanation: The backup/restore directory pathspecified is invalid. The directory specified may not bewritable.

User response: Verify if the backup/restore directoryexists on the remote system and is writable.

GLPWSA155E The backup/restore directory path isnot specified.

Explanation: The backup/restore directory path is notspecified. Click on Refresh button.

User response: Verify if the backup/restore directorypath is specified on the Configure directory serverbackup panel. Click on Refresh button. If not, specifythe backup/restore directory path.

GLPWSA156E The value of password monitoringinterval is out of range.

Explanation: The value of password monitoringinterval should be in the range of 1 through 45 days.

User response: Verify if the value of passwordmonitoring interval is not more than 45 days.

GLPWSA157W Are you sure you want to delete theselected referral/s?

Explanation: Continuing with this operation willdelete the selected referral from the directory.

User response: Click OK to delete the selected referralor Cancel to cancel the delete operation.

GLPWSA847E Failed to start the server.

Explanation: An error occurred while starting theserver. Refer to server error log for more details.

User response: Correct the error and retry theoperation.

GLPWSA848E Failed to stop the server.

Explanation: An error occurred while stopping theserver. Refer to server error log for more details.


GLPWSA849E Failed to restart the server.

Explanation: An error occurred while restarting theserver. Refer to server error log for more details.




Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law :

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

193

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to


IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 195

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.


Index

Aaccessibility x

Ccomponent identifier 1component identifiers

general information 2components, directory server

messages 5

Ddirectory server

messages 5directory server, messages

general information 1overview 1

Eeducation xiexplanation

message 3

Fformat

message 1message ID 1

IIBM

Software Support xiSupport Assistant xi

identifiersseverity 3

Mmessage

administrator response 3explanation 3operator response 3programmer response 3

message format 1message ID format 1

Oonline

publications ixterminology ix

Pproblem-determination xiproduct identifier 1publications

accessing online ixlist of for this product ix

Sseverity

identifiers 3subsystem identifier 1

Tterminology ixtraining xitroubleshooting xi

197

��

Printed in USA

GC27-2751-01

IBM Security Directory Server Version 6.3

Documents

Transcript of IBM Security Directory Server Version 6.3