+++ This bug was initially created as a clone of Bug #676689 +++
Description of problem:
I set up windows sync (2008 R2). Initial sync went ok. I added an ntUser to the DS side - when it went to sync it crashed with an assertion abort in ldap_next_entry() in windows_search_entry_ext(). It seems that openldap ldap_next_entry(LDAP *, LDAPMessage *entry) does not like entry == NULL - it asserts and aborts, while mozldap ldap_next_entry will just return NULL in that case.
--- Additional comment from email@example.com on 2011-02-10 17:28:04 EST ---
Created attachment 478135 [details]
1) setup windows sync and a sync agreement
2) add a user to the DS side like this
dn: cn=testuser,ou=people,<your suffix>
3) verify that the user entry is created in AD
4) verify the directory server did not crash
[root@rheltest etc]# ldapadd -x -D "cn=Directory Manager" -w abc -h localhost -p 389 << EOF
> dn: cn=testuser,ou=users,ou=unix,dc=corp,dc=example,dc=com
> objectclass: person
> objectClass: inetorgperson
> objectclass: ntUser
> sn: User
> givenName: Test
> ntUserDomainId: testuser
> ntUserCreateNewAccount: TRUE
adding new entry "cn=testuser,ou=users,ou=unix,dc=corp,dc=example,dc=com"
- Entry replicated to AD and no crash found.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.