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 |
17001 |
Event Source |
MSExchangeTransport |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
Rule Name |
A column in the Extensible Storage Engine (ESE) contains an incorrect data type. |
Explanation
This Error event indicates a version mismatch between one of the following files that comprise the message queue database or the Content Filtering database on an Edge Transport server or a Hub Transport server:
- The database file Temp.edb that is used to verify the
database schema on service startup This file
is always located with the database transaction logs.
- The database file itself The message
queue database is named Mail.que. The Content Filtering database is
named IpFiltering.edb.
By default, the message queue database and the transaction logs are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue. The location of the message queue database is controlled by the QueueDatabasePath parameter in the EdgeTransport.exe.config application configuration file. The location of the message queue transaction logs is controlled by the QueueDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file.
By default, the Content Filtering database and the transaction logs are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IPFilter. The location of the Content Filtering database is controlled by the IPFilterDatabasePath parameter in the EdgeTransport.exe.config application configuration file. The location of the Content Filtering database transaction logs is controlled by the IPFilterDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file.
The EdgeTransport.exe.config application configuration file is located in C:\Program Files\Microsoft\Exchange Server\V14\Bin.
User Action
To resolve this error, follow these steps:
- Verify that the Microsoft Exchange Transport service is
stopped.
- Delete or move the following files from their current
location:
- The database file and the checkpoint file in the database
directory that corresponds to the database that is specified in the
error message text The database files are
described in the following list:
Mail.que or IpFiltering.edb The main database file
Trn.chk The checkpoint file
The location of the message queue database is controlled by the QueueDatabasePath parameter in the EdgeTransport.exe.config application configuration file. The location of the Content Filtering database is controlled by the IPFilterDatabasePath parameter in the EdgeTransport.exe.config application configuration file. If the specified database is a message queue database that contains messages awaiting delivery, you can use a different Microsoft Exchange Server 2010 Hub Transport server or Edge Transport server to deliver the messages within the database.
- The transaction log files in the transaction log directory
that correspond to the database that is specified in the error
message text The transactions logs are
described in the following list:
Trn*.log The transaction logs
Trnres*.jrs The reserved transaction logs that serve as placeholders
Temp.edb A sample database file that is used to verify the database schema. Although this is not a transaction log file, it is always kept with the transaction logs.
The location of the message queue database transaction logs is controlled by the QueueDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file. The location of the Content Filtering database transaction logs is controlled by the IPFilterDatabaseLoggingPath parameter in the EdgeTransport.exe.config application configuration file.
- The database file and the checkpoint file in the database
directory that corresponds to the database that is specified in the
error message text The database files are
described in the following list:
- Start the Microsoft Exchange Transport service. If the
message queue database or the Content Filtering database does not
exist, a new empty database is created. If the message queue
database transaction logs or the Content Filtering database
transaction logs do not exist, new logs are created.
For more information, see the following topics:
- Managing Transport Queues
- Change the Location of the Queue Database
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.