[jira] (DIRSERVER-2116) ApacheDS failed to start after every reboot and throwing error ERR_250_ENTRY_ALREADY_EXISTS dc=example,dc=com already exists!

[Steve Sobol (JIRA)]

Title: Message Title

Steve Sobol commented on DIRSERVER-2116   Re: ApacheDS failed to start after every reboot and throwing error ERR_250_ENTRY_ALREADY_EXISTS dc=example,dc=com already exists! This is a deal-breaker. I'm having a similar problem after creating a new partition dc=lobosstudios,dc=com. Server running on Windows, Apache Directory Studio running on Windows (same machine, Win10 Pro). First the server complains about a context entry already existing in dc=lobosstudios,dc=com and I try removing the ads-contextentry attribute. Then I restart the server and it no longer logs that error on my new partition, but instead logs the same error on ou=system – and then I have the same issue as AADI. There IS no ads-contextentry attribute in the ldif for the system partition. What I'm seeing in the logs is that first this was going to be fix in m21, then m22, then m23 – which is what I'm trying to set up – and now it's been pushed back again. This is logged as a "major" bug - shouldn't it have been fixed already? If you guys aren't planning on permanently fixing this bug soon, can you at least tell me if there's a 2.0 milestone or nightly that doesn't have the problem? My only practical alternative is OpenLDAP, and the thought of manually configuring OpenLDAP gives me nightmares. Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)