Export (0) Print
Expand All
Expand Minimize

The Transport database could not be opened because the log file path that was supplied is invalid

 

Topic Last Modified: 2007-11-16

The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this event, do one or more of the following:

  • Review the description of the event that includes the variables specific to your environment. From the Operator Console, select this alert, and then click the Properties tab.

  • Review all events that have been logged that meet the criteria of this Operations Manager alert. From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.

 

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

17006

Event Source

MSExchangeTransport

Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Hub Transport and Edge Transport/Transport

MOM Rule Name

The Transport database could not be opened because the log file path that was supplied is invalid. The Microsoft Exchange Transport service is shutting down.

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.

To resolve this error, follow these steps:

  1. Verify that the Microsoft Exchange Transport service is stopped.

  2. 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.

  3. 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:

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 alerts, see the Events and Errors Message Center.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft