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	17004
Event Source	MSExchangeTransport
Alert Type	Error
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport
Rule Name	There wasn't enough disk space to complete the database operation. The Microsoft Exchange Transport service is shutting down.

Explanation

This Error event indicates that there is insufficient free space on the hard disk drive that holds the message queue database or the Content Filtering database on a Exchange Server 2010 Hub Transport server or an Edge Transport server.

By default, the message queue database file is named Mail.que and is located at %ExchangeInstallPath%\TransportRoles\data\Queue. The location of the message queue database is controlled by the QueueDatabasePath parameter in the EdgeTransport.exe.config application configuration file that is located in %ExchangeInstallPath%\Bin.

By default, the Content Filtering database is named Ipfiltering.edb and is located at %ExchangeInstallPath%\TransportRoles\data\IPFilter. The location of the Content Filtering database is controlled by the IPFilterDatabasePath parameter in the EdgeTransport.exe.config application configuration file that is located in %ExchangeInstallPath%\Bin.

Typically, the back pressure resource monitoring feature reserves 4GB of free space on the hard disk drive that holds the message queue database. Also, two special transaction log files named Trnres00001.jrs and Trnres00002.jrs exist for each database. These special transaction log files are only used when the hard disk drive that contains the transaction log lacks sufficient space to stop the message queue database cleanly.

User Action

To resolve this error, follow these steps:

Verify that the Microsoft Exchange Transport service is stopped.
Free hard disk drive space. Uninstall nonessential programs and remove temporary files. If the computer on which the Hub Transport server is installed also has the Mailbox server role installed, information store transaction logs can quickly grow if the information stores are not backed up. Only a full backup or an incremental backup of an information store removes committed transaction logs from the hard disk drive. For more information, see Understanding Backup, Restore and Disaster Recovery. If you determine the message queue database itself is the cause of the low disk space, you can move the message queue database to another location, and use a different Exchange 2010 Hub Transport server or Edge Transport server to deliver the messages that are contained within the database. For more information, see Understanding Transport Queues
Start the Microsoft Exchange Transport service. If the message queue database or the Content Filtering database does not exist, a new, empty database will be created.

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.