The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a lost flush detection timestamp mismatch. The read operation will fail with error %4. If this condition persists, restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
The database management scope {0} won't be applied to the role assignment for the management role {1} because this role has ...
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 the file "%1" at offset %2 (database page %5) for %3 bytes failed verification because it contains ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a lost ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a persisted ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
The database page read from the file "%1" at offset %2 (database page %6) for %3 bytes failed verification. Bit %5 was corrupted ...
The database page read from the file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page ...