A Transport database operation stopped because there is not enough disk space to complete the operation
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.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
17004 |
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 |
A Transport database operation stopped because there is not enough disk space to complete the operation. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. |
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 Microsoft Exchange Server 2007 Hub Transport server or an Edge Transport server.
By default, the message queue database file is named Mail.que and is located at C:\Program Files\Microsoft\Exchange Server\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 C:\Program Files\Microsoft\Exchange Server\Bin.
By default, the Content Filtering database is named Ipfiltering.edb and is located at C:\Program Files\Microsoft\Exchange Server\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 C:\Program Files\Microsoft\Exchange Server\Bin.
Typically, the back pressure resource monitoring feature reserves 4 GB 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 Database Backup and Restore. 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 2007 Hub Transport server or Edge Transport server to deliver the messages that are contained within the database. For more information, see Working with the Queue Database on Transport Servers.
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
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.