search for: removelingeringobjects

...ver were not replicated to the Windows machine. Further investigation show that there are 2 lingering objects that prevent replication, and it has been for quite a while. The various procedures on the Microsoft site to remove the lingering objects don't work against the Samba DC. eg. repadmin /removelingeringobjects on the objects gives following error, and no usefull information was found on Google: DsReplicaVerifyObjectsW() failed with status 1745 (0x6d1): The procedure number is out of range. I also disabled the Strict Replication Consistency on the Windows DC, so that the object would be recreated an...

...is error can be found at http://support.microsoft.com/?id=314282. If both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on the installation CD. To see which objects would be deleted without actually performing the deletion run "repadmin /removelingeringobjects <Source DC> <Destination DC DSA GUID> <NC> /ADVISORY_MODE". The eventlogs on the source DC will enumerate all lingering objects. To remove lingering objects from a source domain controller run "repadmin /removelingeringobjects <Source DC> <Destination DC DSA GU...

...Windows > machine. Further investigation show that there are 2 lingering > objects that prevent replication, and it has been for quite a while. > > The various procedures on the Microsoft site to remove the lingering > objects don't work against the Samba DC. > eg. repadmin /removelingeringobjects on the objects gives following > error, and no usefull information was found on Google: > > DsReplicaVerifyObjectsW() failed with status 1745 (0x6d1): > The procedure number is out of range. > > I also disabled the Strict Replication Consistency on the Windows DC, > so th...

...t;, line 252, in replicate schema=schema, req_level=req_level, req=req) When I first got this I ran tapicfg on a windows DC and saw a TAPI3Directory partition. I deleted it and it didn't seem to help. I've also run ldp.exe, and tried to find it that way. As well as running repadmin /removelingeringobjects thinking it might just not have been fully deleted. Is this just having to wait for the tombstone lifetime of the deleted object to pass, or is there something I can do to fix this and get the replication working for the Samba 4 server I'm trying to setup. Thanks! Liam liam(dot)k(at)weaver...

...urther investigation show that there are 2 lingering > > objects that prevent replication, and it has been for quite a while. > > > > The various procedures on the Microsoft site to remove the lingering > > objects don't work against the Samba DC. > > eg. repadmin /removelingeringobjects on the objects gives following > > error, and no usefull information was found on Google: > > > > DsReplicaVerifyObjectsW() failed with status 1745 (0x6d1): > > The procedure number is out of range. > > > > I also disabled the Strict Replication Consistency o...