Home > Support > Knowledge Base > Article

FAQ: Mail is not delivered and the error "The download/failure history file is corrupt" is reported in the Application Event Log

Symptoms

Email messages are not delivered to Exchange by Exchange Connector, and one or both of the following error messages are reported in the Windows Application Event Log:

  • The download history file is corrupt. Please delete the DownloadHistory.xml file (located at C:\ProgramData\Quantum Software Solutions\Exchange Connector), and restart the service.
  • The failure history file is corrupt. Please delete the FailureHistory.xml file (located at C:\ProgramData\Quantum Software Solutions\Exchange Connector), and restart the service.

Note: The paths in the error messages shown above are correct for Windows Server 2008. On Windows Server 2003, the paths reported in the above errors will be C:\Documents and Settings\All Users\Application Data\Quantum Software Solutions\Exchange Connector instead.

Resolution

As stated in the error message, you need to stop the service completely and delete the affected files:

  1. Stop the serivce by using the Stop button in the Exchange Connector Service Manager.
  2. Completely exit the Exchange Connector Service Manager by right-clicking the icon in the notification area (system tray) and selecting Exit.
  3. Browse to the path of the affected files, as stated in the error message, and rename or delete the corrupted file.
  4. Restart the service using the Exchange Connector Service Manager. The files will be automatically recreated.

Note: If the Download History file is corrupted, and the "leave messages on server" option is utilized for any mailboxes in Exchange Connector, some old messages which are still on the POP3 server may be re-delivered after performing the above procedure.

These errors are usually caused by the service processing being terminated while it is attempting to write to the above files. In rare circumstances, hard disk errors can also cause the above errors. These errors can usually be prevented by ensuring that the ExchangeConnectorService.exe process is never forcibly terminated, and that the system is always shut down correctly before being powered off.

Other Articles