Hi Emmanuel Yes indeed. We have prepared customized configuration where there is.
dn: ads-partitionId=ims,ou=partitions,ads-directoryServiceId=default,ou=config ads-contextEntry:: ZG46IGRjPWltcyxkYz1wbGF5dGVjaCxkYz1jb3JwCm9iamVjdGNsYXNzOiBkb 21haW4Kb2JqZWN0Y2xhc3M6IHRvcApkYzogaW1zCgo= entryCSN: 20160512143435.245000Z#000000#000#000000 If I remember it right our problem started after upgrading the configuration. Is it OK to remove this entry? Best Regards Joel Arula -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Wednesday, May 18, 2016 4:09 PM To: [email protected] Subject: Re: ERR_250_ENTRY_ALREADY_EXISTS Le 18/05/16 à 13:25, Joel Arula a écrit : > Hi > > I am using embeded aopache ds version 2.0.0-M21 When setting up clean > installation every startup after first one is failing with > org.apache.directory.api.ldap.model.exception.LdapEntryAlreadyExistsEx > ception: ERR_250_ENTRY_ALREADY_EXISTS What can be done in order to avoid this > error, and what causes it ? > > Best Regards > > Joel Arula > Have you edited teh configuration with Apache Directory Studio ? If so, you may have added the contextEntry in the configuration, and it will be injected at startup. Sadly, once injected, it won't be removed from teh config, and will be added again when you start the server again... Can you check that ?
