# Since latest update "Something Went Wrong" **URL:** \ **Category:** Plex Media Server\ **Tags:** server-windows\ **Created:** [April 28, 2022, 6:42pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555 "2022-04-28T18:42:26Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Knuckleheadz](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/knuckleheadz/32/13435_2.png) [@Knuckleheadz](https://forums.plex.tv/u/Knuckleheadz)\ **Post date:** [April 28, 2022, 6:42pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/1 "2022-04-28T18:42:26Z")
Server Version#: 1.26.1.5772-872b93b91 Player Version#: 4.80 Since the latest all the my libraries now show this error message. Saw something in the log file that suggested DB corruption and followed the KB article to repair a corrupt database both automatically and manually but I see the same error. Running the DB check command returns the message OK but looking at the logs I still see: ERROR - SQLITE3:0x7e10a099, 11, database corruption at line 81887 of [1b256d97b5] ERROR - SQLITE3:0x7e10a099, 11, statement aborts at 25: [delete from metadata\_relations where metadata\_relations.related\_metadata\_item\_id in (select metadata\_items.id from metadata\_items where metadata\_items.guid in (select guid from (select ERROR - Exception inside transaction (inside=1) (E:\jenkins\server\3578859791\Library\DatabaseMigrations.cpp:237): sqlite3\_statement\_backend::loadOne: database disk image is malformed ERROR - Exception thrown during migrations, aborting: sqlite3\_statement\_backend::loadOne: database disk image is malformed [Plex Media Server Logs\_2022-04-28\_19-38-03.zip](https://forums.plex.tv/uploads/short-url/m4WoEGxdJc7aNWnvrQ5xLzhs69x.zip) (2.0 MB) I recently (although it has been working for over a month) migrated a number of my libraries to PCLOUD (Cloud Storage) although some libraries are still local and both. This only happened after the recent update to 1.26.1.5772 ☹ Help! ---
**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\ **Post date:** [April 28, 2022, 7:15pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/2 "2022-04-28T19:15:14Z")
> [@Knuckleheadz](#): > > database disk image is malformed Broken database 4 sure As the article mentions, regardless of check, try and do a manual repair ---
**Author:** ![Knuckleheadz](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/knuckleheadz/32/13435_2.png) [@Knuckleheadz](https://forums.plex.tv/u/Knuckleheadz)\ **Post date:** [April 28, 2022, 7:44pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/3 "2022-04-28T19:44:16Z")
Thanks Dane I did try the manual method but that hasn’t worked. I’ve copied the corrupt database to a different folder and am currently recreating my libraries. Annoyingly my backup folder was the same as my DB folder (not sure if thats right) and when I followed the restore a backed up DB some of the files mentioned were missing… specifically I was expecting to see a library.db-DATE file as well as a blobs.db-DATE file, but only the library.blobs.db-DATE file existed… The restore steps then didn’t make sense as I didn’t have a library.db-DATE file to rename as the recovered DB ---
**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\ **Post date:** [April 28, 2022, 8:18pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/4 "2022-04-28T20:18:01Z")
When a corruption is detected, PMS will no longer make backups, to avoid rolling over a valid database backup So if no backup files was ever made for the database, are you then sure it’s enabled? ![image](https://global.discourse-cdn.com/plex/original/4X/0/0/7/0076915c2ec3f05c47c74ab5b7a0155e00001bbb.jpeg) ---
**Author:** ![Knuckleheadz](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/knuckleheadz/32/13435_2.png) [@Knuckleheadz](https://forums.plex.tv/u/Knuckleheadz)\ **Post date:** [April 28, 2022, 8:21pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/5 "2022-04-28T20:21:27Z")
Ah right OK… makes sense, thanks Yep, definitely have that set… and I have created a BACKUP folder within DATABASES to create backups and set that in Settings as the backup location. Thanks for your help… library scanning is going to take a while from the cloud but it is what it is 🙂 ---
**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\ **Post date:** [April 28, 2022, 8:41pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/6 "2022-04-28T20:41:47Z")
Might wanna set up alarming: > [@Updated, and now all libraries get "Something Went Wrong" - logs say "BAD CAST"](https://forums.plex.tv/t/updated-and-now-all-libraries-get-something-went-wrong-logs-say-bad-cast/790428/10): > > If database was broken before the upgrade, it’ll break even more, and that’s what happens You can setup, so an alarm will be send to your mobile Ref: [Push Notifications | Plex Support](https://support.plex.tv/articles/push-notifications/) ---
**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\ **Post date:** [April 29, 2022, 12:36pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/7 "2022-04-29T12:36:13Z")
> [@Knuckleheadz](#): > > and I have created a BACKUP folder within DATABASES to create backups and set that in Settings as the backup location. I recommend you to clear out the input field for the backup location. Thus, resetting it back to the default. Because: if the folder is for some reason not accessible, the backup fails. So that is worse than having a backup directly inside the database folder. ---
**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\ **Post date:** [April 29, 2022, 12:41pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/8 "2022-04-29T12:41:52Z")
> [@OttoKerner](#): > > I recommend Me as well wants to recommend something 🙂 After changing/updating the path, you can check if it works using this 3. Party tool > **[Home](https://github.com/WebTools-NG/WebTools-NG/wiki/)** > > WebTools Next Generation for Plex. Contribute to WebTools-NG/WebTools-NG development by creating an account on GitHub. ---
**Author:** ![cecopido](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cecopido](https://forums.plex.tv/u/cecopido)\ **Post date:** [April 29, 2022, 6:11pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/9 "2022-04-29T18:11:00Z")
Plex Database Repair (MAC) cd /Users/HOME/Library/Application\ Support/Plex\ Media\ Server/Plug-in\ Support/Databases Check “/Applications/Plex Media Server.app/Contents/MacOS/Plex SQLite” com.plexapp.plugins.library.db “PRAGMA integrity\_check” Dump “/Applications/Plex Media Server.app/Contents/MacOS/Plex SQLite” com.plexapp.plugins.library.db “.output dump.sql” “.dump” Make a backup copy and delete com.plexapp.plugins.library.db Open the dump.sql file with an editor and look for corruption you’ll see a line like “CORRUPTION ERROR” with a bunch of \*\*\*\* around it. you can delete all the lines you find, change the very bottom from “rollback” to “commit”, and save. “/Applications/Plex Media Server.app/Contents/MacOS/Plex SQLite” com.plexapp.plugins.library.db “.read dump.sql” Done. As the last option, it should work ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [July 28, 2022, 6:11pm UTC](https://forums.plex.tv/t/since-latest-update-something-went-wrong/790555/10 "2022-07-28T18:11:11Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.