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
View All Services
Solutions
BY INDUSTRY
BY REGULATION
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
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » MailMarshal (SEG) » PRB: None of the MailMarshal services will start

PRB: None of the MailMarshal services will start

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • MailMarshal (SEG)

Symptoms:

  • None of the MailMarshal services will start.
  • There are no entries in the Windows event log.

Causes:

A simple way to see what is causing the services to fail on startup is to run one of the MailMarshal services in debug mode.

Debug mode enables the user to immediately see the results of the system logging, and is especially useful for resolving problems or when a service fails to start. From a command prompt in the MailMarshal directory enter:

mmengine -debug

(or "mmreceiver -debug" or "mmsender -debug" depending on the service that is to be debugged).

If no entries are written to the event log, the event log may be full, preventing MailMarshal from writing entries to it. A full event log will not in itself cause the services to fail, it will just prevent useful errors being written to the log. 

Reply:

LevelBlue recommends that the Event Logs is set to at least 4000K in size, and generally they should be configured to overwrite events as needed so that the latest items are always available. 

This article was previously published as:
NETIQKB29231
Marshal KB145

 

 

To contact LevelBlue about this article or to request support:

Rate this Article:
     

Add Your Comments


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


Execution: 0.094. 8 queries. Compression Disabled.
Powered by InstantKB.NET