| Event Id | 446 |
| Source | ESE |
| Description | process name (process id) file nameDatabase recovery stopped abruptly while redoing logfile value (value,%6). The logs after this point may not be recognizable and will not be processed. |
| Event Information | According to Microsoft Cause: The logs after this point may not be recognizable and will not be processed. Some log files may be damaged because of size mismatching. Resolution: If performing a soft recovery, restore from backup media. If performing a hard recovery, refer to the backup set to determine the affected log files. If the corrupted log file is outside the backup set, remove the files outside the backup set and run restore again. If the corruption is contained in log files, revert to a previous backup in the backup set. Loss of data may occur. If the problem persists, contact Microsoft Product Support Services. |
| Reference Links | "Event Id:446 of Source Id:ESE " |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.