Topic Last Modified: 2010-08-16

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:

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

1013

Event Source

MSExchangeTransport

Alert Type

Warning

Rule Path

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

Rule Name

The SMTP Receive connector rejected the specified error message because of a database issue.

Explanation

This Error event indicates the specified Receive connector rejected an inbound message because of a message queue database error. The extensible storage engine (ESE) database error is specified in the event text.

By default, the message queue database 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.

For more information, see the following topics:

  • Managing Transport Queues

  • Change the Location of the Queue Database

User Action

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

  • Verify that the message queue database location that is specified by the QueueDatabasePath parameter in the EdgeTransport.exe.config application configuration file exists and has the following permissions assigned:

    • Administrators: Full Control

    • Network Service: Full Control

    • System: Full Control

  • If this error occurs frequently, you may want to consider creating a new message queue database. To do this, follow these steps:

    1. Pause the Microsoft Exchange Transport service. This action allows existing messages in the message queue database to be delivered, and it does not allow new messages to enter the message queue database.

    2. After all existing queued messages are drained from the database, stop the Microsoft Exchange Transport service. You can verify that the message queue database is empty by using the 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

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.