Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > No emails received after the alert is triggered

No emails received after the alert is triggered

Created by Flavio Porfirio Correia, last modified by Karen Valdellon on Jun 27, 2016

Views: 102 Votes: 0 Revisions: 5

Overview

 

This article applies when an alert is configured to send an email but when triggered, no email is received.

Simulating the alert, the email is received, but does not send when triggered by NPM.

 

The following error may also appear in the Alerting.Service.V2.log file:

 

2016-05-17 12:10:06,624 [AlertingService.OnStart] ERROR SolarWinds.Alerting.Service.AlertingService - Unhandled exception caught by Alerting Service. System.ArgumentOutOfRangeException: Specified time is not supported in this calendar. It should be between 04/30/1900 00:00:00 (Gregorian date) and 11/16/2077 23:59:59 (Gregorian date), inclusive.
Parameter name: time
   at System.Globalization.UmAlQuraCalendar.CheckTicksRange(Int64 ticks)
   at System.Globalization.UmAlQuraCalendar.GetDatePart(DateTime time, Int32 part)
   at System.DateTimeFormat.FormatCustomized(DateTime dateTime, String format, DateTimeFormatInfo dtfi, TimeSpan offset)
   at System.DateTimeFormat.Format(DateTime dateTime, String format, DateTimeFormatInfo dtfi, TimeSpan offset)
   at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)
   at SolarWinds.Orion.Common.SqlHelper.GetQueryParametersString(SqlCommand command)
   at SolarWinds.Orion.Common.SqlHelper.LogLongRunningQuery(Stopwatch stopwatch, SqlCommand command)
   at SolarWinds.Orion.Common.SqlHelper.ExecuteReader(SqlCommand command, SqlConnection connection, SqlTransaction transaction, CommandBehavior behavior)
   at SolarWinds.Orion.Core.Common.DALs.OrionAlertDAL.<GetItemsSince>d__0.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
   at SolarWinds.Orion.Core.Alerting.Service.Monitors.AlertDefinitionsMonitor.RefreshAlertConfigurations(Boolean isInitial)
   at SolarWinds.Orion.Core.Alerting.Service.Monitors.AlertDefinitionsMonitor.StartMonitoring()
   at SolarWinds.Orion.Core.Alerting.Service.AlertingServiceManager.StartService()
   at SolarWinds.Alerting.Service.AlertingService.StartServiceManager()
   at SolarWinds.Alerting.Service.AlertingService.DoStart()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
   Sender: Name:SolarWinds.Alerting.Service.exe
There are no context policies.

Environment

NPM 11.5.3 or earlier

Cause 

This occurs because the Orion Server is configured in a locale which is not supported by NPM.

Resolution

Configure the server to any other locale which allows the Gregorian date/times.

  1. Go to the Control Panel and click Region.
  2. In the Administrative tab, go to Change system locale.
  3. Change the locale to any other locale which allows the Gregorian date/times.

Alternatively, you can check the database table EngineProperties to find a similar row 1 OSLocale String ar-SA.

 

 

Last modified

Tags

Classifications

Public