Resolving Quarantine Service Issues in GFI MailEssentials

Overview

This article consolidates common quarantine-related troubleshooting scenarios, including:

• Applying the latest product updates/patches (including manual patch installation when automatic patching fails).
• Dependency errors such as: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
• Quarantine database corruption (repair or recreate).
• Service startup failures caused by port conflicts.

The GFI MailEssentials services most commonly involved are:

• GFI MailEssentials Backend (hosts reporting and quarantine-related components). 
• GFI MailEssentials Quarantine Action Services (processes actioning for items detected as spam/malware).

Solution

1. Make sure you are on the latest version/build and fully patched.

   Quarantine-related issues are frequently resolved by upgrading and applying all available product updates. If patches fail to install via the UI, use the documented manual patch installation procedure.

2. Identify the symptom you are seeing.

   • If releasing quarantined items fails and you see: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. follow step 3.
   • If quarantine lists stop updating / quarantine appears corrupted, follow step 4.
   • If Backend / Quarantine Action services are failing to start and event logs indicate a remoting/socket bind problem, follow step 5.

3. Fix the Microsoft.ACE.OLEDB.12.0 provider error.

   Important: Microsoft has retired/out-of-support older Access Database Engine redistributables, and the old 2010 download URLs may return 404. 

   If the 2010 redistributable is unavailable, Microsoft’s recommended alternative is the Microsoft Access Database Engine 2016 Redistributable.

   After installing the dependency, re-test by releasing a quarantined item again.

4. Repair or recreate quarantine databases if corruption is suspected. 

   • Anti-Spam quarantine: recreate the Anti-Spam quarantine database.
   • EmailSecurity (malware) quarantine: recreate the EmailSecurity quarantine database.
   • If quarantine logs show errors like “Invalid API Parameter”, repair the quarantine store (ESE database) as described in the linked article. 

5. Note: Recreating quarantine databases can make previously quarantined emails inaccessible.

6. Check for Backend port conflicts that prevent services from starting.

   If multiple MailEssentials services (including Backend and Quarantine Action) fail to start and the event logs indicate a remoting/socket bind error, follow the port-conflict troubleshooting guidance in the linked article.

<supportagent>

Agent note: For quarantine issues, also check the product’s quarantine-related debug logs list (for example Quar.log, QuarQA.log, QASCoordinator.log, and QAS plugin logs) and ensure tracing was enabled before reproduction.

</supportagent>

Related Articles

1. Services Installed by MailEssentials
2. Released Quarantined Items Not Delivered to End Users
3. How to recreate the GFI MailEssentials Anti-Spam Quarantine database?
4. How to recreate the GFI MailEssentials EmailSecurity Quarantine database
5. Cannot Save Emails to Quarantine, Invalid API Parameter Error in Quarantine Logs
6. Backend port conflict on 9090 with Symantec Endpoint Protection
7. A large number of emails are building up in the BadMail folder and queues
8. Why are patches failing to install?
9. Manually installing product updates
10. How to Install or Upgrade GFI MailEssentials
11. Access Database Engine Redistributable 2010 no longer available? - Microsoft Q&A
12. Microsoft Access Database Engine 2016 Redistributable