The database page read from file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem that contains this file. Please contact your hardware vendor for assistance in diagnosing the problem.
The database latency troubleshooter quarantined user %1 on database %2 due to unusual activity in the mailbox. If the problem ...
The database management scope {0} won't be applied to the management role assignment for the management role {1} because ...
The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state, with no copies configured ...
The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state. Unable to find any server ...
The database page read from file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
The database page read from file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
The database page read from file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page checksum ...
The database page read from file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page checksum ...
The database page read from file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The expected ...