Topic Last Modified: 2010-02-18

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	9005
Event Source	MSExchangeTransport
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport
Rule Name	Pickup service cannot submit the message due to database issues.

Explanation

This Error event indicates that the Pickup directory or the Replay directory couldn't submit a message because of problems with the message queue database.

The location of the message queue database and the transaction logs is controlled by the following parameters in the EdgeTransport.exe.config application configuration file that is located in C:\Program Files\Microsoft\Exchange Server\V14\Bin:

QueueDatabasePath
QueueDatabaseLoggingPath

By default, the message queue database and transaction logs are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue.

User Action

To resolve this error, do one or more of the following:

Verify that the message queue database and the corresponding transaction log locations that are specified in the EdgeTransport.exe.config application configuration file exist, and have the following permissions assigned:
- Administrators: Full Control
- Network Service: Full Control
- System: Full Control
If this error occurs frequently, you may consider creating a new message queue database by using the following steps:
1. Pause the Microsoft Exchange Transport service. This allows existing messages in the message queue database to be delivered, while not allowing new messages to enter the message queue database.
2. After all the existing queued messages have been drained from the database, stop the Microsoft Exchange Transport service. You can verify the message queue database is empty by using Queue Viewer in the Exchange Management Console. For more information, see Using Queue Viewer.
3. Delete or move the existing message queue database files.
4. Start the Microsoft Exchange Transport service.
For more information, see Understanding Transport Database Configuration Options.

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.