Re: CommitChanges and delay?
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Apr 2007 22:49:35 -0700
It should be changing the directory synchronously. Are you absolutely
positive that you are searching to get your changes from the same DC you
made the edit on? Are you reading the GC?
The only behavior I'm aware of that could cause the write to not actually
"write" immediately is the (LDAP_SERVER_LAZY_COMMIT_OID )
1.2.840.113556.1.4.841 control, although I don't really know a ton about it
and am not sure if ADSI uses it under the hood. It isn't something you can
turn on or off if it is and isn't implemented in the .NET layer. You could
find out for sure if it is in there by sniffing the wire traffic.
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
--
"Gary Stewart" <Gary Stewart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6B79E8D2-210F-4B46-B14F-BC484C15424A@xxxxxxxxxxxxxxxx
When I add or delete a user from an AD Group using the .Net directoryentry
object, it appears that at certain times there is a delay in the change
taking place.
The problem this is causing is that I immediately turn around and attempt
to
refresh a list of objects after the operation and the data can come back
inaccurate.
Is there anyway to make CommitChanges a blocking call or to determine when
the changes actually take place?
Thanks,
Gary
.
- Prev by Date: Re: CA wont allow me to submit new requests in a text file
- Next by Date: GPO Software Deployment Path Change...
- Previous by thread: Re: CA wont allow me to submit new requests in a text file
- Next by thread: GPO Software Deployment Path Change...
- Index(es):
Relevant Pages
|
