Troubleshooting GALSync: mv-constraint-violation (msExchSafeSenderHash)

Troubleshooting GALSync: mv-constraint-violation (msExchSafeSenderHash)


In a Global Address List (GalSync) Synchronization process you receive a mv-constraint-violation on several objects.  You click on the mv-constraint-violation to discover that it is for the msExchSafeSenderHash.


The problem here is that the amount of data that is being pushed from the unique connector space is exceeds the size limitations to the attribute in the metaverse.


The attribute value from the connector space exceeds the length restrictions of the metaverse attribute.


The quick and easy resolution is to simply remove the attribute from Configure Attribute Flow so that the information is not synchronized across to the target forest.  
  1. In the Synchronization Manager Console, select Management Agents
  2. Select the Source GalSync Management Agent that is throwing the mv-constraint-violation error
  3. From the Actions menu, select Properties
  4. Select Configure Attribute Flow
  5. Expand User > Person
  6. locate and select the msExchSafeSenderHash (Direct) msExchSafeSenderHash
  7. Click the Delete button


  1. mv-constraintviolation error in GalSync

You can also get the mv-constraint-violation on the Info attribute.  The same resolution applies.


Current Forefront Identity Manager 2010 Resources
Current Certificate Lifecycle Manager Resources
GalSync Resource Wiki
PCNS-Password Synchronization Wiki
Leave a Comment
  • Please add 6 and 3 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Wikis - Comment List
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
  • Good Article.

  • Good Article.

  • This is all well and good, but what happens when you actually need the attribute in full? Is there a way to extend the MV constraint for an attribute?

  • MV-Constraint is where the source attribute is attempting to push an abundance of data into the metaverse where it is meeting a limitation from SQL Server.  In this particular issue the msExchSafeSenderHash contains a lot of data that doesn't fit into the msExchSafeSenderHash Metaverse Attribute.  You will need to correct the issue at the source data level and then pass the information through.  

Page 1 of 1 (4 items)