Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Alert emails do not trigger due to log file errors

Alert emails do not trigger due to log file errors

Updated June 14, 2017

Overview

This article describes an issue where the alert email actions are not received.

The following errors are found in the logs:

ActionExecutionAlert.log file:

2097-02-15 16:03:04,915 [102] ERROR AlertingLogger - (null)  Sending the email from solarwinds@solarwinds.com to solarwinds@solarwinds.com with subject ALERT: Resolved : Managed Node MyNode IP 10.1.1.1 has started polling using SMTP Server 192.168.1.1 failed. The message could not be sent to the SMTP server. The transport error code was 0x800ccc67. The server response was 421 4.3.2 Service not available
System.Runtime.InteropServices.COMException (0x80040211): The message could not be sent to the SMTP server. The transport error code was 0x800ccc67. The server response was 421 4.3.2 Service not available
   at Interop.cdosys.MessageClass.Send()
   at SolarWinds.Orion.Core.Actions.Utility.Smtp.Clients.CdoSmtpClient.Send()
   at SolarWinds.Orion.Core.Actions.Impl.Email.EmailExecutor.SendEmail(EmailConfiguration config)
   at SolarWinds.Orion.Core.Actions.Impl.Email.EmailExecutor.ExecuteInternal()

 

ActionsExecution.log file:

2097-02-15 16:03:04,915 [16] WARN  SolarWinds.Orion.Core.Actions.Utility.Smtp.SmtpServerConnectionChecker - (null)  Failed to get host entry 192.168.1.1 port 25. No such host is known

Environment

NPM 12.0.1

Cause 

The SMTP server does not accept the SMTP traffic from the Orion server.

Resolution

  1. Make sure that the correct SMTP host is configured in alerts. This can be configured by bulk in the Web Console (Settings > All Settings > Manage SMTP Servers).
  2. Verify that the SMTP server is correctly configured to accept SMTP traffic from the Orion server.

 

Last modified

Tags

Classifications

Public