Re: Problem updating schema in ADAM
- From: Steve <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 9 Mar 2007 09:55:15 -0800
So it is! I guess I missed it, or I guess didn't understand what it meant.
Anyway, thanks a lot for the help.
"Joe Kaplan" wrote:
That line is in all of the schema update LDIF files that come with ADAM..
What this modification does is tells the directory to rebuild its internal
schema settings for directory objects. You normally do this when you have
completed a batch of modifications. You wouldn't want it to do this
everytime it sees a modification to the schema because it wouldn't know if
you had other mods coming, so they give you the opportunity to tell the dir
when you are ready to update. :)
Restarting the directory service should also do this, but the mod is a much
friendlier way of accomplishing the same goal.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F7FEE50B-857E-41D5-BF59-E4350777ABEC@xxxxxxxxxxxxxxxx
It was the schemaUpdateNow that was missing.
In all the web sites and ldif files I studied to figure out how to do
this,
I never saw anything like this. Do you know where I can look to
understand
this better?
"Joe Kaplan" wrote:
Do you have the schemaUpdateNow mod in your LDIF files at the end?
dn:
changetype: modify
add: schemaUpdateNow
schemaUpdateNow: 1
Also, are you closing ADSI Edit and restarting your process after you do
the
schema update? ADSI caches the schema for the directory in memory and on
the file system. It won't update the in memory cache until the process
restarts. During the first access to a given directory, ADSI will check
to
see if the cached version on the file system is up to date based on the
update date of the schema in the directory and will attempt to rebuild
the
local cache if the directory version is newer.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AFD1651E-6F55-4064-8496-47656093AE23@xxxxxxxxxxxxxxxx
I am using LDIFDE.exe to import some new attributes and classes into the
ADAM
schema. After a lot of experimenting, I managed to get the attribute
and
class definitions in the right order so that LDIFDE did not give any
errors.
Now that I have the schema updated, both ADAM-adsiedit and my own code
get
errors when trying to create instances of my new classes.
0x8007200a The specified directory service attribute or value does not
exist.
However, if I connect to the ADAM instance with "ADAM Schema.msc",
suddenly
everything is good. Both adsiedit and my code can create the
instances.
Am I leaving something out of my schema import? Is there some post
processing of the ADAM instance I am supposed to do after the import
that
adsiedit and my code don't do but ADAM Schema does do? If so, does
anyone
know what it is?
- References:
- Re: Problem updating schema in ADAM
- From: Joe Kaplan
- Re: Problem updating schema in ADAM
- From: Joe Kaplan
- Re: Problem updating schema in ADAM
- Prev by Date: Re: Inter-site transports question(s) :)
- Next by Date: Re: local usergroups
- Previous by thread: Re: Problem updating schema in ADAM
- Next by thread: Re: Group Policy and child domain
- Index(es):
Relevant Pages
|
