Old reports in the QoE Monitoring Server database could not be purged. Server: '%1' Database: '%2' Error: '%3' Cause: A database failure was encountered while attempting to purge the database of old records. Resolution: Check the SQL error number for the cause of the failure.
Number of times during the call that the multiple endpoints quality event was raised on the client. Indicates whether two ...
Number of user updates that User Replicator has received. Includes all user updates, even those that don't result in a database ...
Number of user updates that User Replicator receives per second. Includes all user updates, even those that don't result ...
Old records in the QoE Monitoring Server database could not be completely purged within the allocated time. Purging time ...
Old reports in the QoE Monitoring Server database could not be purged. Server: '%1' Database: '%2' Error: '%3' Cause: A database ...
On-premise PrimaryUserAddress is different from on-premise sip address in ProxyAddresses. TenantId: '%1', ObjectId: '%2' ...
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 ...