# Error executing historical tag read - Edge v 8.1.7

**URL:** <https://forum.inductiveautomation.com/t/error-executing-historical-tag-read-edge-v-8-1-7/87490>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [March 18, 2024, 2:29pm UTC](https://forum.inductiveautomation.com/t/error-executing-historical-tag-read-edge-v-8-1-7/87490 "2024-03-18T14:29:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Erik\_Nizenkoff](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@Erik\_Nizenkoff](https://forum.inductiveautomation.com/u/Erik_Nizenkoff)\
**Post date:** [March 18, 2024, 2:29pm UTC](https://forum.inductiveautomation.com/t/error-executing-historical-tag-read-edge-v-8-1-7/87490/1 "2024-03-18T14:29:18Z")

</div>

I'm getting this error often on an Ignition Edge v.8.1.7 system. The easy charts using historian are coming up blank (of course). I've not seen this before when running on the first machine for months, but just deployed the app 2 to new systems on another site and this is popping up now. It looks like a database error. Any ideas where I can start looking to troubleshoot this? It's running on the Edge built in SQLite server.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/2/52048edfc678f430d725f7c80a76e5fdee81e5c9.png)  
I'm also getting these 2 errors approximately every 5 minutes while it is happening.  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/3/c37acf0f881e329c49e3d9bdc9e9706ad72e1c02.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 18, 2024, 4:10pm UTC](https://forum.inductiveautomation.com/t/error-executing-historical-tag-read-edge-v-8-1-7/87490/2 "2024-03-18T16:10:08Z")

</div>

It looks like the attached SQLite database that Edge uses for history has some kind of problem.  
I would recommend you contact our support department so they can take a live look at your system.
