Topic Last Modified: 2010-01-28
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
- From the Operations Console, double-click this alert, and then
click the General tab. Review the description of the alert
that includes the variables specific to your environment.
- From the Operations Console, double-click this alert, and then
click the Alert Context tab. Review the logged events that
meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
17006 |
Event Source |
MSExchangeTransport |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
Rule Name |
The Transport database log file path is invalid. The Microsoft Exchange Transport service is shutting down. |
Explanation
This Error event indicates that the Extensible Storage Engine (ESE) database transaction log location for either the message queue database or the Content Filtering database on a Microsoft Exchange Server 2007 Hub Transport server or Edge Transport server is missing or invalid.
During an ordinary shutdown of the Microsoft Exchange Transport service, uncommitted database changes that are found in the transaction logs are always committed to the database.
Circular logging is used for the message queue database and the Content Filtering database. This means that the history of committed transactions that are found in the transaction logs is not maintained. Any transaction logs that are older than the current checkpoint are immediately and automatically deleted. Therefore, the transaction logs cannot be replayed for database recovery from backup.
By default, the message queue database transaction logs are located at C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue. The location of the message queue database transaction logs is controlled by the QueueDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file that is located in C:\Program Files\Microsoft\Exchange Server\Bin.
By default, the Content Filtering database transaction logs are located at C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\IPFilter. The location of the Content Filtering database transaction logs is controlled by the IPFilterDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file that is located in C:\Program Files\Microsoft\Exchange Server\Bin.
User Action
To resolve this error, follow these steps:
- Verify that the Microsoft Exchange Transport service is
stopped.
- Note the name of the database that is specified in the error
message text. Verify that the corresponding transaction log
location that is specified by the QueueDatabaseLoggingPath
parameter or the IPFilterDatabaseLoggingPath parameter in
the EdgeTransport.exe.config application configuration file exists,
and has the correct permissions assigned to it.
- Start the Microsoft Exchange Transport service. If transaction
logs exist in the specified location, the database will try to use
them. If no transaction logs exist in the specified location, new
transaction logs will be created automatically.
For more information, see the following topics:
For More Information
If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.