#48841 Windows Sync total update fails if OU is in the 389 side.
Closed: wontfix 4 years ago by mreynolds. Opened 7 years ago by nhosoi.

My lab environment:
389-ds-base 1.3.4.8 + win 2012 r2

OU just in 389 side with users: Full sync failed, log error:

[17/May/2016:14:19:44 -0300] - Attempting to add entry cn=mais um teste,ou=teste,ou=RNP,dc=homolog,dc=rnp to AD for local entry uid=teste.teste,ou=teste,ou=RNP,dc=homolog,dc=rnp
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Received result code 32 (0000208D: NameErr: DSID-03100238, problem 2001 (NO_OBJECT), data 0, best match of:   'OU=RNP,DC=homolog,DC=rnp' ) for add operation
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): windows_process_total_add: Cannot replay add operation.
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Beginning linger on the connection
[17/May/2016:14:19:44 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): windows_tot_run: failed to obtain data to send to the consumer; LDAP error - 1
[17/May/2016:14:19:44 -0300] - Calling dirsync search request plugin
[17/May/2016:14:19:44 -0300] - Sending dirsync search request
[17/May/2016:14:19:45 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Cancelling linger on the connection
[17/May/2016:14:19:45 -0300] NSMMReplicationPlugin - windows sync - agmt="cn=AD - DF-GTI-DC01" (gti-df-dc01:636): Disconnected from the consumer
[17/May/2016:14:19:45 -0300] NSMMReplicationPlugin - windows sync - windows_inc_runs: cancelled dirsync: 7fa660001d60, rval: 1

OU just in AD side with users: Full sync ok

My production environment:
389-ds-base 1.3.2.19 + win 2008 r2

OU just in 389 side with users: Full sync ok
OU just in AD side with users: Full sync ok


Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.6 backlog

7 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: None
- Issue set to the milestone: FUTURE (was: 1.3.6 backlog)

6 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1901

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata