Handling unmatched users
Novell Cool Solutions: Question & Answer
Reader Rating 
Q:
When migrating or editing an existing unmatched user in eDirectory
that also exists in AD, I get the "LDAP_ALREADY_EXISTS" error message and
user object association stays in a pending state. I've tried TID 10091618, which is the exact error I receive, but its fix is not applicable here.
A:
The UPN and sAMAccountName must be unique within an AD domain. It sounds like your driver is not finding a matching object and therefore tries to create a new one. When it does, there is a UPN/sAMAccountName conflict.
You'll need to modify your matching rules to find the existing users in AD.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com