Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

ERRMSG: 3502 - Transaction log file error (MMController error)

Expand / Collapse


This article applies to:

  • MailMarshal (SEG)
  • MailMarshal ECM/MailMarshal Exchange 7.X

Symptoms:

Event ID: 3502
Type: Error
Source: MMController (MailMarshal SMTP) or MEXController (MailMarshal Exchange)
Description: Transaction log file error

Causes:

The MailMarshal Controller service was unable to create a DBLOG file.

The error can be a result of the file being removed manually or by another process outside of MailMarshal's control.

The error can also result from the MailMarshal Controller service being unable to to create or rename files in the DBLog folder.

The error indicates that the MMController was unable to create a temporary database log datafile, or was unable to rename an existing temporary file.

Background

The MailMarshal Controller service, running on a MailMarshal email processing node, uses files to hold information that will later be sent to the Array Manager and written to the MailMarshal logging database. These database logging files are located in a folder "DBLog", within MailMarshal's "Logging" folder.

The MailMarshal Controller service writes the logging data to a temporary file. Periodically a new temporary file is started, and the previous file is renamed. 

As an example, the temporary file used for the database logging might be named

~SVR2003MM.455cf89f0001.dblog

Once the MailMarshal Controller service finishes building the needed SQL logging data, this file would be renamed to:

SVR2003MM.455cf89f0001.dblog

Resolution:

  • Verify that virus scanners and archiving applications are not attempting to access the files.
  • Verify that the MailMarshal Controller has sufficient permissions over this folder.

To contact LevelBlue about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.