One of the attributes for a user was too large to fit into the Lync Server database. A truncated version of the attribute ...

Lync Server 2013

One of the attributes for a user was too large to fit into the Lync Server database. A truncated version of the attribute has been put into the database.

Uri:
%1
The DN of the user User Replicator tried to synchronize is:
%2
This update came from domain:
%3
The attribute that was too large:
%4
Maximum size of attribute:
%5
Actual size of attribute:
%6
The source of the replication is %7.

Cause: This can occur because the Lync Server stores some attribute data in UTF-8 format, which, when converted from the Unicode in Active Directory, can result in massive string sizes.
Resolution:
No resolution is required. However, the offending attribute can be shortened in Active Directory if it is important that the entire attribute fit into the database.

On-premise PrimaryUserAddress is different from on-premise sip address in ProxyAddresses. TenantId: '%1', ObjectId: '%2' ... One IP address bound to the internal interface. If this network adapter is not on the same network as the Director / Front ... One IP Address bound to the ISA server external interface. Note: The reverse proxy can be behind a NAT or a port forwarding ... One IP address is bound to each internal collocated Access Edge and Web Conferencing node. If these network adapters are ... One of the attributes for a user was too large to fit into the Lync Server database. A truncated version of the attribute ... One of the underlying thread synchronization primitives failed. This may cause a deadlock, hang, or serious error in the ... One or more attributes for a user were incorrect in Active Directory domain:%1 The user with these attributes has DN:%2 These ... One or more attributes for an object were incorrect in Active Directory domain:%1 The object with these attributes has DN:%2 ... One or more components of Lync Server are still active. If you remove Lync Server, these components may stop working. Do ...