Log truncation for database '{0}' could not be coordinated between the active copy on '{1}' and the passive copy on '{2}' because the passive copy is not recognized by the server hosting the active copy. This state can be the result of Active Directory replication latency or issues. Hresult: 0x{3:x}.
Log sequence numbers for this instance have almost been completely consumed. The current log generation is %1 which is approaching ...
Log sequence numbers for this instance have almost been completely consumed. The current log generation is %4 which is approaching ...
Log Threads Waiting is the number of threads waiting for their data to be written to the log in order to complete an update ...
Log truncation failed because not all log files required for recovery were successfully copied. For more information, click ...
Log truncation for database '{0}' could not be coordinated between the active copy on '{1}' and the passive copy on '{2}' ...
Log Writes/sec is the number of times the log buffers are written to the log file(s) per second. If this number approaches ...
LogCopyNotKeepingUp is 1 when log copy and inspection is falling behind and not able to keep up with new logs being generated ...
LogExport Web App won't function correctly if you disable Integrated Windows authentication on the EWS virtual directory ...
Logical and physical disk performance counters on server {2} are disabled. It will not be possible to monitor disk performance ...