| Event Id | 225 |
| Source | ESE |
| Description | %1 (%2) %3 No log files can be truncated. |
| Event Information | Explanation: This Information event is logged when the Microsoft® Exchange Extensible Storage Engine (ESE) cannot truncate transaction log files. ESE truncates log files as part of the Exchange Server backup process. ESE event 225 can occur when the following conditions are true: If ESE cannot determine whether transaction log files have been committed to the Exchange Server database. If ESE identifies that one or more transaction log files are locked. If ESE identifies that one or more transaction log files are damaged. The occurrence of ESE event 225 does not provide enough information to help you determine the root cause of this error. ESE event 225 frequently occurs together with other related Error events and Warning events that must also be investigated. If you do not resolve this problem, the quantity of transaction log files will continue to grow and the drive that hosts your transaction log files will eventually run out of disk space. When you run out of disk space on the disk that hosts your transaction log files, the Microsoft Exchange Information Store service and other Exchange Server services will stop. A computer that is running Exchange cannot process e-mail when the Microsoft Exchange Information Store service stops. User Action: To resolve this event, do one or more of the following: 1. In Event Viewer, examine the Application log and System log for related events that occur before and after this event. These related events may help identify the cause of this error. 2. Make sure that you are running the most current Exchange Server 2003 updates and service packs. |
| Reference Links | Microsoft product: Exchange Version: 6.5.7596.0 Event Source: ESE Event ID: 225 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.