Event ID 225 — Application Recovery

Event ID 225 — Application Recovery

Updated: January 27, 2011

Applies To: Windows Server 2008

You can use the wbadmin start recovery command or the Recovery Wizard in Windows Server Backup to recover applications and related data from a backup. To enable applications to be recovered, you need to install recovery plug-ins. For more information, see http://go.microsoft.com/fwlink/?LinkId=93493.

Event Details

Product: Windows Operating System
ID: 225
Source: Microsoft-Windows-Backup
Version: 6.0
Symbolic Name: APP_RESTORE_SUCCEEDED_EVENT
Message: The restore of component(s) that started at ‘%9’ completed successfully.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Application Recovery

File Services

Related:

( () Proc ) Submit failure, bad invoke identifier on result Invoke id Remote entity (14)

Details
Product: Exchange
Event ID: 225
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: (<value> <value>(<process name>) Proc <number>) Submit failure, bad invoke identifier on result Invoke id <id> Remote entity <name> (14)
   
Explanation

There is no historical information to provide assistance on this event.

   
User Action

The diagnostics logging levels of the message transfer agent (MTA) interface and interoperability categories should be increased to create interoperability logs. These logs are text logs that consist of the binary contents of communication among MTAs in different sites, and between MTA and client applications within a site. They are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.

To help Microsoft Product Support Services determine the problem, create log files. For more information, see Microsoft Knowledge Base articles 163032 and 168906.

To create Ap*.log files, on the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA, and then set the logging level of the Interoperability and Interface categories to Maximum.

To create Bf*.log files, set the logging level of the Application Protocol Data Unit (APDU) and X.400 service categories to Maximum.

Save all MTA log files (mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services for assistance.

Related:

%1 (%2) %3 No log files can be truncated.

Details
Product: Exchange
Event ID: 225
Source: ESE
Version: 6.5.7596.0
Message: %1 (%2) %3 No log files can be truncated.
   
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:

Related: