# Errors in log: SQLITE3:0x80000001, 17, statement aborts

**URL:** <https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485>\
**Category:** Plex Media Server\
**Tags:** server-linux\
**Created:** [July 29, 2022, 2:52pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485 "2022-07-29T14:52:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fly](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/fly/32/82069_2.png) [@fly](https://forums.plex.tv/u/fly)\
**Post date:** [July 29, 2022, 2:52pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485/1 "2022-07-29T14:52:57Z")

</div>

Server Version#: 1.27.2.5929

I’m seeing a bunch of these errors in my [PMS logs.](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) I ran through the KB article on repairing the database. While I didn’t get any errors, the error persists in the logs. Any ideas on how I can fix this? If it matters, the server appears to be functioning normally.

SQLITE3:0x80000001, 17, statement aborts at 57: [select \* from metadata\_items limit 1] database schema has changed

[Plex Media Server Logs\_2022-07-29\_10-52-11.zip](https://forums.plex.tv/uploads/short-url/pYkExYDoD5EMrOIeSLIXDzchmg6.zip) (781.2 KB)

---

<div class="post-metadata">

**Author:** ![gbooker02](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/gbooker02/32/9726_2.png) [@gbooker02](https://forums.plex.tv/u/gbooker02)\
**Post date:** [July 29, 2022, 3:01pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485/2 "2022-07-29T15:01:57Z")

</div>

This is normal during database migrations (which is where your logs have them). When the db schema changes (as the migration often do), the sqlite connection will output this error message on the next query. So on the migrations we actually do a simple query just to flush this.

---

<div class="post-metadata">

**Author:** ![fly](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/fly/32/82069_2.png) [@fly](https://forums.plex.tv/u/fly)\
**Post date:** [July 29, 2022, 3:02pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485/3 "2022-07-29T15:02:35Z")

</div>

But its constant. Was happening before the db repair, and continues now.

---

<div class="post-metadata">

**Author:** ![gbooker02](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/gbooker02/32/9726_2.png) [@gbooker02](https://forums.plex.tv/u/gbooker02)\
**Post date:** [July 29, 2022, 3:11pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485/4 "2022-07-29T15:11:36Z")

</div>

Each time it is on an EPG database and it keeps running the migrations over and over. Is this database corrupt and in need of repair?

---

<div class="post-metadata">

**Author:** ![fly](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/fly/32/82069_2.png) [@fly](https://forums.plex.tv/u/fly)\
**Post date:** [July 29, 2022, 3:20pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485/5 "2022-07-29T15:20:49Z")

</div>

I already did the repair.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [October 27, 2022, 3:21pm UTC](https://forums.plex.tv/t/errors-in-log-sqlite3-0x80000001-17-statement-aborts/802485/6 "2022-10-27T15:21:29Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.