[ISS Support Case] Not receiving event tag alerts Reconfiguring Database Mail

Last updated: March 7th, 2025

Description

Triggered event tag alerts are not being received. The alerts are writing to the SQL Server table EventHistory in the Runtime database, but are just not getting to the intended recipients. Manually running the contents of the Action Query from the triggered event tag within a SQL query are successfully received by the intended recipients. Have restarted the AVEVA Historian Event System service, but that does not resolve the issue. sysmail_log not creating a db mail process when the wonderware events are fired.

Author: Kevin Modlin
Published: March 7th, 2025

Details:

Product: Historian

Version: 2020 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	07/06/2023
Case:	84782

Give feedback about this article

Recommended articles

[ISS Support Case] Historian loses connection after shutting down

If the historian is shut down and disabled then re-enabled it doesn't connect to tags that haven't changed. Reboot re-establishes connection.

[ISS Support Case] Trying to access old history blocks

They have a very old system they're trying to open a trend or see the data, but they don't see a trend program and can't figure out how to open the file. They believe they have the data, but it's running in demo mode and won't show data. This is an offline PC and they want to avoid putting it online, so we can't do a screen share.

[ISS Support Case] Trend SQL Login Failure

Client reached out due to receiving time out error message when logging into SQL to View Trends remotely on Development node.

[ISS Support Case] Wanting to pull 9 months of historized data

-Customer is wanting Historized data from the last 9 months in a .CSV file. Or in SQL. and wants to know the best practices.