I'm using an alarm journal tied to an SQL database to show alarm history. I am also using a date range component so the user can select to view alarms in a specific time range. Under stress testing, several alarms are turned on and off frequently to ensure all events are captured. The display eventually stops working and turns red. When this happens, alarm journal quality changes to Error_IO. At this point, there were ~ 15,000 alarms in the db to display but nothing will display. It also causes other components displayed to flicker or have a quality overlay. Can anyone help with what might cause the Error_IO? Are there settings I need to change to increase the number of viewable alarms in the alarm journal? Thanks in advance!
Ttoth,
Something similar happened to me recently with Error_IO; the reason was because the database hosting the journal was not connected, it didn’t have a "Valid" status, so I would recommend checking the status of the database connection and ensuring that the journal alarm tables exist.
After reestablishing the connection, you may need to refresh the journal so that the query runs and refreshes with the now valid connection.