A new non-nullable column was added to the schema. The database must be recreated

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 an Edge 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\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\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\Bin.

To resolve this error, perform the following steps:

1. Verify that the Microsoft Exchange Transport service is stopped.
   
   
2. 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. Note that if the specified database is a message queue database that contains messages awaiting delivery, it is possible to use a different Exchange 2010 Hub Transport server or Edge Transport server to deliver the messages within the database. For more information, see Understanding Transport Queues.
     
     
   • 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.
     
     
3. 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. If the message queue database transaction logs or the Content Filtering database transaction logs do not exist, new logs will be created.
   
   

For more information, see the following topics:

• Understanding Transport Queues
  
  
• Change the Location of the Queue Database
  
  

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.