%1 (%2) %3Corruption was detected while restoring from backup logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable. For more information, click http://www.microsoft.com/contentredirect.asp.
Corrupt Message detected during MoveMailbox. Fid = %1 ; Mid = %2 ; Some or all properties of this message will not be moved ...
Corrupt Message detected. Fid = %1 ; Mid = %2 ; Some or all properties of this message will not be transferred correctly. ...
Corruption was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. Data not ...
Corruption was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. Data not ...
Corruption was detected while restoring from backup logfile %4. The failing checksum record is located at position %5. Data ...
Could not connect over LDAP to %1. This domain controller is running %2 %3. Please upgrade to Windows 2000 SP3 or later. ...
Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
Could not delete key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
Could not delete value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact ...