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: Services will not start due to Internal error 2140

PRB: Services will not start due to Internal error 2140

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • MailMarshal (SEG)
  • MailMarshal ECM/MailMarshal Exchange

Symptoms:

  • Services will not start
  • Error: 'Internal error 2140'

Causes:

This message is a generic Microsoft Windows error message simply meaning that one or more of the services were unable to start.

 

Information:

To confirm the cause of this error, check the Windows Event Log. The error may be related to irregularities in the MailMarshal Configuration. For example, a Rule may have missing information. A check of the relevant log file (for instance the Engine log) in the MailMarshal Logging directory may yield more information.

You can also try running the MailMarshal service in "debug" mode from a command prompt. This enables the user to immediately see the results of the system logging, and is especially useful when a service fails to start - often you can see why by running the service in debug mode.

  • If necessary stop the MailMarshal system services.
  • From a command prompt in the MailMarshal directory enter:

    start MMEngine -debug
To debug other services substitute the desired service name, such as:
  • MMReceiver, MMSender, MMController (MailMarshal SMTP)
  • MMEEngine, MMEController (MailMarshal Exchange 5.X)
  • MEXEngine, MEXController (MailMarshal Exchange 7.X)

This article was previously published as:
NETIQKB29679
Marshal KB24

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.031. 8 queries. Compression Disabled.
Powered by InstantKB.NET