Old records in the QoE Monitoring Server database could not be completely purged within the allocated time. Purging time (in minutes): '%1' Cause: The old database records were only partially purged. This may happen if the number of days to retain reports has been reduced by a large number. Resolution: If the problem persists over several consecutive daily purges, report this problem to Customer Support Services.
Number of times during the call that the acoustic feedback quality event was raised on the client. Indicates whether two ...
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 ...