Re: Importing schema from AD to ADAM
- From: "Eric Fleischman [MSFT]" <efleis@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Dec 2005 13:04:13 -0800
Oh yes, I forgot. I already wrote up how to tackle this error. :)
http://blogs.technet.com/efleis/archive/2005/09/14/410817.aspx
~Eric
--
Eric Fleischman [MSFT]
These postings are provided "AS IS" with no warranties, and confers no
rights.
"Eric Fleischman [MSFT]" <efleis@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OAMLzQoAGHA.3072@xxxxxxxxxxxxxxxxxxxxxxx
> And for your particular error:
> C:\>err 00002099
> # for hex 0x2099 / decimal 8345 :
> ERROR_DS_ILLEGAL_SUPERIOR winerror.h
> # The object cannot be added because the parent is not on the
> # list of possible superiors.
>
> Basically, you are trying to sync an object such that it is to be a child
> of an object not allowed per the schema.
> My suggested troubleshooting steps:
> - Enable logging, identify the object on which you are failing (I talk
> about logging on my blog, Lee gave you a link already :))
> - Check out the schema definition of that objct in the target ADAM
> instance, and add the appropriate possSuperiors to it such that it can be
> a child of the object you are trying to place it under in your sync
> operation.
>
> Hope that helps! Holler w/questions.
> ~Eric
>
> --
> Eric Fleischman [MSFT]
> These postings are provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> "Rainier [MCT]" <RainierMCT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:AF2E0E52-1FE1-404A-B5FF-9E5014A8C5A5@xxxxxxxxxxxxxxxx
>> Hi,
>>
>> I'm trying to export a schema and data from Active directory and get it
>> into
>> my local ADAM instance. I've been trying to do this now for days and I'm
>> not
>> getting thru.
>>
>> I've tried LDIFDE, ADAMSync and even dsde.
>>
>> LDIFDE -f outputfile.ldf -s MyADServername returns me a big ldf file.
>> When trying to import this one using
>> LDFIDE -i -f outputfile.ldf -s localhost:389 -z returns me a list of
>> errors
>> missing attributes.
>>
>> Tried importing the ad_schema.ldf and the schema_Metadata.ldf that came
>> with
>> AdamSync.
>> LDIFDE -I -s localhost:389 -c CN=Configuration, DC=X
>> #ConfigurationContext
>> -f ad_schema.ldf
>> and
>> LDIFDE -I -s localhost:389 -c CN=Configuration, DC=X
>> #ConfigurationContext
>> -f schema_Metadata.ldf
>> This loads a bunch of entries.
>>
>> I've updated the xml file to match my AD and ADAM settings
>> AdamSync /install localhost:389 c:\config.xml
>>
>> AdamSync /Sync localhost:389 ADAMApplication
>> Gives me the following error: Ldap error occured. ldap_add_sW: Naming
>> Violation.
>> Extended Info: 00002099: NameErr: DSID-03050F55, problem 2005
>> (NAMING_VIOLATION)
>> , data 0, best match of:
>> 'CN=Builtin,DC=global,DC=umusic,DC=net,DC=ADAM-users'
>>
>> I feel I'm getting closer but I'm not there yet. Can someone give me the
>> last clue ??
>>
>> Kind Regards,
>> --
>> Rainier van Slingerlandt
>> (Freelance trainer/consultant/developer)
>> www.slingerlandt.com
>
>
.
- References:
- Re: Importing schema from AD to ADAM
- From: Eric Fleischman [MSFT]
- Re: Importing schema from AD to ADAM
- Prev by Date: Re: Importing schema from AD to ADAM
- Next by Date: Re: Connecting 2 Wk3 AD servers in two different location
- Previous by thread: Re: Importing schema from AD to ADAM
- Next by thread: Re: Active Directoru died of HDU problem
- Index(es):
Relevant Pages
|
