This issue is potentially caused by the build-up of messages in the reporting queues.
- Open Computer Management by navigating to Start > Run > compmgmt.msc
- Navigate to Computer Management > Services and Applications > Message Queuing > Private Queues
- Right Click and purge all Reporting queues that are backed up
- Verify that the queues are not building up.
- Install or reinstall Microsoft Access Database Engine 2010 Redistributable. If it is already installed, it should be uninstalled first, and then a clean copy should be installed.
- Recreate the Reporting databases:
- Navigate to \GFI\MailEssentials\Data\
- Rename the Reports.FDB file to Reports.old
- Navigate to \GFI\MailEssentials\Attendant\data
- Rename the Logs.FDB file to Logs.old
- Navigate to\GFI\MailEssentials\Attendant\bin
- Double-click on LogsFDBCreator.exe
- Confirm there is a new Logs.FDB file in \GFI\MailEssentials\Attendant\data
If the database file is growing too quickly and approaching the 7GB limit, the reporting performance can be affected. In such a scenario, using a SQL Server database is a viable alternative for customers who wish to retain their old reporting data.
More information about migrating to a SQL Server database may be found in the How to migrate the reporting database from Microsoft Access / Firebird to Microsoft SQL article.
- Navigate to GFI MailEssentials > Reporting > Settings and select the Auto-purge tab.
- Select Enable Auto-Purging and specify how long mail items in the database should be stored in months to a lesser value than the current.
- Click on Apply.
- Open the Windows Services Manager by navigating to Start > Run > services.msc and restart the following services:
- Microsoft Transport Agent service
- GFI List Server
- GFI MailEssentials Attendant
- GFI MailEssentials AS Scan Engine
- GFI MailEssentials Autoupdater
- GFI MailEssentials AV Scan Engine
- GFI MailEssentials Backend
- GFI MailEssentials Legacy Attendant
- GFI POP2Exchange
- GFI MailEssentials Quarantine Action Services