Replica has no update vector . . . .

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This problem is due to the formatting of data in the Fedora Directory that 
does not meet the requirements for Active Directory.  The last time I set up 
Windows Sync, I avoided this by importing the data directly into AD from an 
ldif file.  Then I populated the Fedora Directory by initiating a full 
resynchronzation.

This time I wanted to see if I could populate the AD using the full 
resynchronization.  To begin, I carefully formatted the data before importing 
the ldif file into Fedora DS.  Then I started the initial full 
resynchronization.  I thought my data formatting would eliminate errors, but 
still the synchronization was interrupted whenever the AD found data it did 
not like.  Since it did not finish, I would get the "replica has no update 
vetor" message.  Also, the Replication Status window reported a "Last 
consumer init. update" message:

Total update aborted LDAP error: Operations error. Error Code: 1

By checking the contents of the Active Directory, I was able to find out 
where the initial sync stopped.  I examined the entry that caused it to stop 
and corrected the attributes that AD did not like or deleted the entry.  I 
repeated this process several times until the resync finally completed.

It would be very helpful if the Fedora Directory could be made to display the 
entry that caused the initial resync to stop.

Things that AD doesn't like:  Carriage returns in attribute values, blank 
attribute values including no password.  Also, AD requires all entries to 
have certain attributes, including:

objectclass: ntuser
ntUserDomainID: yourADuserID
ntusercreatenewaccount: true


---------- Original Message -----------
From: "Glenn" <glenn at mail.txwes.edu>
To: "Fedora DS List" <fedora-directory-users at redhat.com>
Sent: Mon, 9 Apr 2007 16:20:09 -0500
Subject: Replica has no update vector . . . .

> When I get Windows Sync running between Fedora Directory Server 
> 1.0.3 and Active Directory on a Windows 2003 server, it logs an 
> error message every four seconds:  "Replica has no update vector. It 
> has never been initialized."  I've tried restarting the directory 
> server and the admin server, and I've tried initiating a full 
> resyncronization, but the error messages continue.
> 
> Also, in case it is related, I've noticed that out of 600 or so 
> users in the Fedora directory, only five have replicated to the AD server.
> 
> Hoping someone can tell me how to get this working.  Thanks.   -G.
> 
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
------- End of Original Message -------




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux