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 > Archive > 2017December28 - Deletes > Alerts actions no longer sending SMS using 3rd party log to a file action

Alerts actions no longer sending SMS using 3rd party log to a file action


Alerts are not firing/triggering with the following symptoms or issues:

  • SMS and Email alerts are defined and they used to work as intended. But now they do not fire or trigger and nothing has been changed in the settings.
  • CPU alerts are still being received. But when a node/group is down, no alerts are received.
  • On the Active alerts window, alerts are not visible and only shows the An error has occurred message.
  • Alerts were working in NPM 11.5.2 and something stopped this from working in NPM 12.


NPM v12.0 or later


This is a known issue in NPM v12. 

In 11.5 the file generated was in UTF-8. In NPM 12,  it is saving the file in "UTF-8-BOM"

The result of this is that your Text file > SMS is no longer working after the upgrade.


We recommend investigating if the 3rd party tool can be updated, we are using standard format for our log file.
As temporary workaround, you can convert encoding for those files using Notepad++.


Last modified