mv-constraint-violation
The attribute value from the connector space exceeds the length restrictions of the metaverse attribute.
You can also get the mv-constraint-violation on the Info attribute. The same resolution applies.
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.
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?
Good Article.