This article applies to:
Problem:
- New messages do not appear in Mail History
- Database logging files (dblog) could not be transferred to Array Manager
- MM Controller log entries like: Event - Database Logging Error: DBLog file <Server1.672ce4220000.dblog> could not be transferred to Array Manager after 30 attempts
- MM Array Manager log entries like: Event - Failed to process log file
Background:
MailMarshal Mail History is generated from the SQL database.
Mail processing information is transferred from each processing server to the Array Manager for insertion to the database.
This transfer is in the form of "DBLog" files.
If the files are corrupt or cannot be transferred, Mail History will not include the related information.
Procedure:
To troubleshoot DBLog issues:
- Check the MMController text log on each processing server. You should see lines similar to Server1.672ce4090000.dblog (338 bytes) sent to manager
- If you see lines with Database Logging Error, this indicates a problem sending the files.
- Also check for the presence of a large number of files in the DBLog folder on the processing node, by default C:\Trustwave\Secure Email Gateway\Logging\DBLog.
- Then check the MMArrayManager log file for Failed to process log file entries - this would indicate that the Controller can connect.
- If there are no errors in the MMArrayManager log, verify the connectivity between the processing node and Array Manager on the required ports.
- If there are errors in the Array Manager log (other than database connection failures), look for issues at the node.
- The most likely issues are disk full condition, or a third party anti-malware product interfering with the file creation.
Before proceeding, identify and correct the issue that is causing file corruption. Check the Windows Event Logs and other debugging tools.
To resume logging:
Transfer of each file is attempted 30 times, so the presence of a large number of corrupt files can delay Mail History for a significant time.
- Move all .dblog files from the DbLog folder to a temporary location.
- Check that newly generated files are being processed quickly and Mail History updates have resumed.
- You can attempt to recover history by moving small numbers of files from the temporary location back to the DBLog folder. Copy the latest files first (files from after the time you corrected any issue.) Check that the files are actually processed before copying additional files.
- If the original issue was due to lost connectivity, you can also try copying files from the processing server BadLog subfolder back to the DBLog folder.
Any files that are actually corrupt cannot be recovered. Message History covered in these files will be lost.
