Re: ADAMSync

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Lee Flight (lef_at_le.ac.uk-nospam)
Date: 12/21/04 

Date: Tue, 21 Dec 2004 02:06:57 -0000

Hi

is this the first attempt to run the sync, is there any data in the ADAM
instance?

If you use ldp to search for the GUID
 39472aef2cc2384882d7275e3fad138a
below what is the corresponding object, is it the partition head
DC=ggg,DC=domain,DC=global?

It appears from the output below that the DirSync and standard LDAP
search are failing, have the Enterprise Admin permissions/rights on the
W2003
domain partition been modified from the default?

Thanks
Lee Flight

"confused" <confused@discussions.microsoft.com> wrote in message
news:A0AB389D-4FB1-4350-BE82-BD78ECD6A0C3@microsoft.com...
> I've setup my ADAMSync using an Enterprise Admin account and tested the
> query
> against the source-ad-server using ldp.exe without any problems. I do not
> have any includes or excludes and have only added the schemas that came
> with
> adamsync. However, when I attempt to synch using this config, the error I
> get
> is:
>
> C:\WINDOWS\ADAM>adamsync.exe /sync localhost:389 ADAMApplication /log -
> Establishing connection to target server localhost:389.
> Saving Configuration File on DC=ggg,DC=domain,DC=global,DC=ADAM-Users
> Saved configuration file.
> ADAMSync is querying for a writeable replica of
> dc-777-01.ggg.domain.global.
> Error: DCLocator call failed with error 1355. Attempting to bind directly
> to
> str
> ing.
> Establishing connection to source server dc-777-01.ggg.domain.global:389.
> Using file .?dam9C.tmp as a store for deferred dn-references.
> Populating the schema cache
> Populating the well known objects cache
> Starting synchronization run from dc=ggg,dc=domain,dc=global.
> Starting DirSync Search with object mode security.
>
> Processing Entry: Page 1, Frame 1, Entry 0, Count 0, USN 0
> Processing source entry <guid=39472aef2cc2384882d7275e3fad138a>
> Processing in-scope entry 39472aef2cc2384882d7275e3fad138a.
> Cannot modify object which does not exist in target. Re-reading subtree
> via
> LDAP
> .
> Previous entry took 0 seconds (16, 0) to process
>
> Processing Entry: Page 1, Frame 2, Entry 0, Count 0, USN 8245
> Processing source entry <guid=39472aef2cc2384882d7275e3fad138a>
> Processing in-scope entry 39472aef2cc2384882d7275e3fad138a.
> Unable to read necessary attributes / object via LDAP.
> Cannot process entry. Please fix the permissions in AD or in the
> configurationFi
> le and re-run the sync session.
> Saving Configuration File on DC=ggg,DC=domain,DC=global,DC=ADAM-Users
> Saved configuration file.
>
> Anybody know what's going on ?
>