The Account OC directly inherits from Top, the InetOrgPerson OC has an
inheriting hierarchy which is :
InetOrgPerson -> OragnizationalPerson -> Person -> Top
When defining an entry, you can't have two Structural OCs (Account and
InetOrgPerson are Structural) defined at the same time.
It's a bit like if in Java you tries to define a class extending 2
classes. It's not allowed (somehow not the perfect metaphor, but it may
You have to either select one or the other OC for you entry, or if you
need some of the AT present in both OC then define your own OC
inheriting from either Account or InetOrgPerson OC, and add the missing ATs.
Hope it helps
PS : OC = OjectClass, AT = AttriuteType (for clarity)
On 11/17/10 9:05 PM, Chris Beach wrote:
I've purchased a new server to replace my current domain
issue I'm having is migrating LDAP from my old server to the new one, I've
worked out a lot of the problems I've had, but I'm not having any luck with
this one. Please keep in mind, I am not very knowledgeable with LDAP in
general, so I may have missed things more experienced people may not have.
I had two objectClasses that were conflicting: account and inetOrgPerson,
apparently in my old LDAP version it allowed this, but the new one was
giving errors ( (65) invalid structural object class chain
(inetOrgPerson/account)), so I simply removed all of the account
objectClasses to see what it would do, this did get rid of half the errors,
and all of my users now show up in LDAP, but I find now that all of my
ou=Computers are erroring out with:
slapadd: dn="uid=STCQA01$,ou=Computers,dc=pin,dc=com" (line=10425): (65) no
structural object class provided
I can only assume this is because I've removed the account object class from
the file, but if I add it back in I get:
slapadd: dn="uid=STCQA01$,ou=Computers,dc=pin,dc=com" (line=10426): (65)
invalid structural object class chain (inetOrgPerson/account)
Any suggestions on what I'm doing wrong here?
Here is my includes in slapd.conf:
I really would appreciate any feedback, thanks!