You are here: Application Interface > File menu > Import Message Tracking Data

Import Message Tracking Data

Introduction

Use this option to import Exchange message tracking files into the database.

The message tracking data source is used to produce various traffic reports. Microsoft Exchange uses message tracking files to record all e-mail activity.

Interface description

Option Description
Available server(s) Lists all Exchange servers discovered in the organization.
Selected server(s) Lists Exchange servers selected for message tracking file import. Use the button to select additional servers.
Use this option to open the Server Properties dialog box for one single server, or to configure import options for an entire group of servers.
Import from
  • The last import: Start importing data from the last imported file onwards. Dates may differ between servers.
  • A fixed date for all servers: Start importing data from a given date that will apply to all servers. This is the default option.
  • A fixed date specific to each server: Start importing data from a given date that can be specifically set for each server in the Message Tracking tab of the Server Properties dialog box. To access it, double-click the server in the list.
Import to End date of the period to be imported. This date applies to all selected servers.
Import directory (On-Premises, Office 365)
  • No import: No directory import operation is performed if this option is selected. This option is only available if the last update or complete re-import was carried out less than 24 hours ago.
  • Quick update: Search for new recipients in the directory/hosted organization, or known recipients that have been modified since the last import. The  import process will be much faster. However, an object that was recently deleted in the directory will not be marked as deleted in the database.
  • Full update (Office 365): Re-import all Exchange-related objects, including existing and already known recipients. However, it only processes those that were found to have been modified since the last import took place.
  • Complete import (On-Premises): Re-import all Exchange-related objects, including existing and already known recipients. Objects that can no longer be found, but that are still present in the database, will be marked as deleted.
Compact database after import Select this check box to compact or shrink the database at the end of the import process.

Import steps

  1. Use the Import Message Tracking Data option in the File menu, or click the button on the toolbar.
  2. Add or remove server(s) in the right pane if necessary.
  3. Click the Apply button.
  4. Click the Import from button. If you are not sure of the date you should select, choose From last import.
  5. Make sure that the Import to date is correct.
  6. Click OK.

Import report

At the end of the process, a summary report is displayed to summarize what has been imported and the errors and warnings that may have occurred.

How to interrupt an import

You can interrupt the import at any time by clicking the Cancel button. Events already completely processed will be kept in the database. However, the last processed file will not be considered as imported, and will not be listed in the import history, until it has been fully imported later on.

How to reimport message tracking data

You may need to reimport message tracking data, for example because an error occurred during the import process. You will have to delete them from the database first.

  1. Double-click the server name in the organization tree to open the Server Properties dialog box.
  2. In the Message Tracking tab, click the Import history button.
  3. Select the imports you wish to clear.
  4. Click the Delete button or hit the <Del> key.
  5. Use the Import Message Tracking Data option as described above. Change the import period so that the events you have previously removed are reimported.

Behavior on errors

If an error occurs during the import of a message tracking file, the behavior of the application is the following:

Situation Behavior
An error occurs while an event is being imported The event is skipped. The application attempts to process the next event in the message tracking file.
Promodag Reports does not manage to read a message tracking file Events already processed are kept in the database. The file is marked as damaged, and skipped. The application attempts to read the next file in chronological order.
Imports from the selected server cannot be processed due to a license issue The server is skipped. The application attempts to process imports from the next server in the servers list.