Resources For IT Professionals
Page Details
  • First published by (Microsoft)
  • When: 10 May 2012 12:53 PM
  • Last revision by (cMV)
  • When: 29 Jul 2013 11:45 PM
  • Revisions: 9
  • Comments: 4
Options

Revision #7

Wiki  >  TechNet Articles  >  Troubleshooting GALSync: mv-constraint-violation (msExchSafeSenderHash)  >  Revision #7
Troubleshooting GALSync: mv-constraint-violation (msExchSafeSenderHash)
You are currently reviewing an older revision of this page.
Go to current version
PROBLEM STATEMENT
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.


CAUSE
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.

mv-constraint-violation

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


RESOLUTION
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

ADDITIONAL INFORMATION

  1. mv-constraintviolation error in GalSync

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




SEE ALSO
Current Forefront Identity Manager 2010 Resources
Current Certificate Lifecycle Manager Resources
GalSync Resource Wiki
PCNS-Password Synchronization Wiki

Revert to this revision