locked
ADAMSYNC- Constraint Violation RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am working on a Multi Domain AD LDS setup.  I have it almost done, four domains out of five are sync'd.  My last domain, I have this error in my log below.  Many, Many, Many users have been sync'd succesfully before this user.  This appears to be the last user to sync in this OU, as there are roughly 30 other users already sync'd.  

    Anyone have an idea? I cant find to much out in the Internets.

    A constraint violation occured when attempting to add target object CN=Joe,OU=Associates,OU=Users,OU=People,DC=LastDomain-Com,DC=CUCM,DC=Local.

    This could be due to a schema mismatch. This must be fixed before

    synchronization can continue.

    Ldap error occured. ldap_add_sWC: Constraint Violation. 

    Extended Info: 000021C8: AtrErr: DSID-03200BF3, #1:
    0: 000021C8: DSID-03200BF3, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90290 (userPrincipalName)
    .

    Tuesday, September 27, 2016 4:52 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Thanks for your post.

    Please check if the below information is helpful to you:

    Possible Cause

    This happens due to the any of following reasons:

    • There is white space in the display name of the user account listed along with the error message.
    • There is white space in any of the values of authOrig attribute (or the attribute listed in the CONSTRAINT_ATT_TYPE) of the user account listed along with the error message. The authOrig attribute is used by Microsoft Exchange Server.

    Due to white space, a junk character or \ appears at the end of those values. You can check this using the Adsiedit snap-in or using the Ldifde tool using the command below:

    ldifde -f filename.ldf -d "DN of that user"

    You can follow any of the steps given below to fix the issue:

    • Remove the white spaces in the display name or authOrig values.
    • Put the attribute in the exclusion list in the ADAM xml configuration file.

    NOTE: If Adamsync is failing for the authOrig attribute (an attribute used by Microsoft Exchange Server) and you put authOrig in the exclusion list, Adamsync will again fail for a few more attributes with error "Target does not exist." Make sure that you put the following attributes in the exclusion list along with the authOrig attribute:

    • homeMTA     
    • homeMDB     
    • showInAddressBook     
    • altRecipient

    Best Regards,

    Alvin Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Alvwan Tuesday, October 4, 2016 1:06 AM
    • Marked as answer by Alvwan Monday, October 10, 2016 3:09 AM
    Wednesday, September 28, 2016 9:17 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Thanks for your post.

    Please check if the below information is helpful to you:

    Possible Cause

    This happens due to the any of following reasons:

    • There is white space in the display name of the user account listed along with the error message.
    • There is white space in any of the values of authOrig attribute (or the attribute listed in the CONSTRAINT_ATT_TYPE) of the user account listed along with the error message. The authOrig attribute is used by Microsoft Exchange Server.

    Due to white space, a junk character or \ appears at the end of those values. You can check this using the Adsiedit snap-in or using the Ldifde tool using the command below:

    ldifde -f filename.ldf -d "DN of that user"

    You can follow any of the steps given below to fix the issue:

    • Remove the white spaces in the display name or authOrig values.
    • Put the attribute in the exclusion list in the ADAM xml configuration file.

    NOTE: If Adamsync is failing for the authOrig attribute (an attribute used by Microsoft Exchange Server) and you put authOrig in the exclusion list, Adamsync will again fail for a few more attributes with error "Target does not exist." Make sure that you put the following attributes in the exclusion list along with the authOrig attribute:

    • homeMTA     
    • homeMDB     
    • showInAddressBook     
    • altRecipient

    Best Regards,

    Alvin Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Alvwan Tuesday, October 4, 2016 1:06 AM
    • Marked as answer by Alvwan Monday, October 10, 2016 3:09 AM
    Wednesday, September 28, 2016 9:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Alvin Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 30, 2016 10:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This looks more like a duplicate UPN.

    Find CN=Joe's UPN and search for it in your ADLDS

    Joseph M. Durnal MCM: Exchange 2010 MCITP: Enterprise Messaging Administrator, Exchange 2010 MCITP: Enterprise Messaging Administrator, MCITP: Enterprise Administrator

    Wednesday, February 7, 2018 4:36 PM