exchange server uses an extensible storage engine (ese) database for message queue storage. all the different queues are stored in a single ese database. Queues exist on Exchange Mailbox servers and Edge Transport servers. for more information on queues, see queues and messages on queues.
The location of the queue database and the queue database transaction logs are controlled by keys in the %exchangeinstallpath%binedgetransport.exe.config xml application configuration file. this file is associated with the interchange transport service. the following table explains each key in more detail.
- mail.que
- trn.chk
the default location is %exchangeinstallpath%transportrolesdataqueue.
- trn.log
- trntmp.log
- trn nnn.log
- trnres00001.jrs
- trnres00002.jrs
- temp.edb
Note that temp.edb is used to check the queue database schema when the exchange transport service starts. Although temp.edb is not a transaction log file, it is kept in the same location as the transaction log files.
the default location is %exchangeinstallpath%transportrolesdataqueue.
what do you need to know before you start?
-
estimated time to complete: 15 minutes.
exchange permissions do not apply to the procedures in this topic. these procedures are carried out in the operating system of the exchange server.
When you stop or restart the exchange transport service, mail flow on the server is interrupted.
When you change the location of the queue database or transaction logs, the existing queue database and transaction log files are not moved. a new queue database and new transaction logs are created in the new location. old files are left in the old location, but are no longer used. if you want to reuse the old queue database or transaction log files in the new location, you must move the files to the new location while the swap transport service is stopped.
The folder for the queue database and transaction logs needs the following permissions:
-
network service: full control
system: full control
administrators: full control
if the folder doesn’t exist, but the parent folder has these permissions, the new folder is created automatically.
any custom exchange or internet information server (iis) settings you have made in the exchange application xml configuration files on the exchange server (for example, web.config files or the edgetransport.exe file .config) will be overwritten when you install a cu swap. be sure to save this information so that you can easily reapply the settings after installation. after installing exchange cu, you need to reconfigure these settings.
For information about keyboard shortcuts that can be applied to the procedures in this topic, see the keyboard shortcuts in the exchange admin center.
have problems? ask for help in the exchange forums. visit the forums at: exchange server, exchange online or exchange online protection.
use the command prompt to create a new transaction log and queue database in a new location
-
create the folder where you want to save the queue database and transaction logs. make sure you apply the correct permissions to the folder.
In a command prompt window, open the edgetransport.exe.config file in notepad by running the following command:
find and modify the following keys in <appsettings> section.
for example, to create a new queue and transaction log database in d:queuequeuedb, use the following values:
When you’re done, save and close the edgetransport.exe.config file.
restart the exchange transport service by running the following command:
how do you know this worked?
To verify that you have successfully created a new queue database and new transaction logs in the new location, follow these steps:
-
verify that the new database files mail.que and trn.chk exist in the new location.
verify that the new transaction log files trn.log, trntmp.log, trnres00001.jrs, trnres00002.jrs, and temp.edb exist in the new location.
If you can remove the old queue database and transaction log files from the old location after the Exchange Transport service has started, the old queue database will no longer be used.
use the command prompt to move the existing queue database and transaction logs to a new location
Although you’ll need to move the existing queue database to preserve dead-letter, you typically don’t need to move existing transaction logs because:
-
An ordinary shutdown of the exchange transport service writes all uncommitted transaction log entries to the queue database.
circular logging is used, so transaction logs containing previously committed database changes are not kept.
-
create the folder where you want to save the queue database and transaction logs. make sure you apply the correct permissions to the folder.
In a command prompt window, open the edgetransport.exe.config file in notepad by running the following command:
find and modify the following keys in <appsettings> section:
for example, to change the location of the queue database and transaction logs to d:queuequeuedb, use the following values:
When you’re done, save and close the edgetransport.exe.config file.
stop the exchange transport service by running the following command:
Move the existing database files mail.que and trn.chk from the old location to the new location.
Move the existing transaction log files trn.log, trntmp.log, trn nnnnn.log, trnres00001.jrs, trnres00002.jrs, and temp.edb from the old location to the new one.
start the exchange transport service by running the following command:
how do you know this worked?
To verify that you have successfully moved the existing queue database and transaction logs to the new location, follow these steps:
-
verify that the queue database files mail.que and trn.chk exist in the new location.
verify that the transaction log files trn.log, trntmp.log, trnres00001.jrs, trnres00002.jrs, and temp.edb exist in the new location.
verify that there is no queue database or transaction log files in the above location.
-
-
-
-
-
-