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...

PRB: The 'MMSender', 'MMEngine', and 'MMReceiver' services on a single server MailMarshal installation will not start

Expand / Collapse


This article applies to:

  • MailMarshal (SEG)

Symptoms:

  • The 'MMSender', 'MMEngine', and 'MMReceiver' services on a single server MailMarshal SMTP installation will not start.
  • The MMController log reports the following error: "Event - Cannot open connection Array Manager - node ping failed. Error 1722 - The RPC server is unavailable."
  • Restarting the MailMarshal services through the user interfaces generates the following error: "Failed to fetch service status: Server not online."
  • The MMController service is running, but the services will not start.

Causes:

The MailMarshal Array Manager cannot communicate with the Controller service because RPC port 19001 or 19002 is unavailable.

 

Resolution:

Ensure that ports 19001 and 19002 on the MailMarshal server are available. If MailMarshal has been configured to use non-standard RPC ports, ensure that they are available.

 

Notes:

The ports could be in use by other software, or they could be blocked by Windows Firewall or network interface filtering.

Current supported versions of SEG automatically add rules to Windows Firewall configuration to allow the required port communications.

This article was previously published as:
NETIQKB42587

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
.