Jump to content

Multi-version TV Series not merging


Go to solution Solved by Neminem,

Recommended Posts

Posted
1 minute ago, rbjtech said:

ie a receipe for db corruption.

Ha ha yes, logs are full of SQL errors 🤣😂

Ohh well mine is just a toss away test db.
 

2024-11-28 17:09:27.915 Error BaseItem: Error refreshing item Desire Is All You Need 285984 /media/Series 4K/Yellowstone (2018)/Yellowstone (2018) - S05E09 - Desire Is All You Need - [ WEBDL-2160p ][ 8-bit h265 ][ EAC3 5.1 ].disc
*** Error Report ***
Version: 4.9.0.32
Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Linux version 6.6.56-Unraid (root@Develop) (gcc (GCC) 14.2.0, GNU ld version 2.43.1-slack151) #1 SMP PREEMPT_DYNAMIC Thu Oct 10 21:34:15 PDT 2024
OS/Process: x64/x64
Framework: .NET 8.0.10
Runtime: system/System.Private.CoreLib.dll
Processor count: 8
Data path: /config
Application path: /system
SQLitePCL.pretty.SQLiteException: Constraint: FOREIGN KEY constraint failed
SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown.
at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc)
at SQLitePCL.pretty.StatementImpl.MoveNext()
at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql)
at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItemsInTranscation(IDatabaseConnection db, List`1 items, MetadataRefreshOptions metadataRefreshOptions)
at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItems(List`1 items, MetadataRefreshOptions metadataRefreshOptions, Action`1 afterSave, Boolean disableForeignKeys, CancellationToken cancellationToken)
at Emby.Server.Implementations.Library.LibraryManager.UpdateItems(List`1 items, BaseItem parent, ItemUpdateType updateReason, Boolean setDateLastSaved, Boolean saveMetadata, MetadataRefreshOptions metadataRefreshOptions, CancellationToken cancellationToken)
at Emby.Providers.Manager.MetadataService`2.SaveItem(MetadataResult`1 result, Boolean isFirstRefresh, LibraryOptions libraryOptions, ItemUpdateType reason, IDirectoryService directoryService, MetadataRefreshOptions metadataRefreshOptions, CancellationToken cancellationToken)
at Emby.Providers.Manager.MetadataService`2.RefreshMetadata(BaseItem item, MetadataRefreshOptions refreshOptions, BaseItem[] collectionFolders, LibraryOptions libraryOptions, CancellationToken cancellationToken)
at MediaBrowser.Controller.Entities.BaseItem.RefreshMetadata(MetadataRefreshOptions options, BaseItem[] collectionFolders, LibraryOptions libraryOptions, CancellationToken cancellationToken)
at MediaBrowser.Controller.Entities.BaseItem.RefreshMetadataRecursive(BaseItem[] children, MetadataRefreshOptions refreshOptions, BaseItem[] collectionFolders, LibraryOptions libraryOptions, Boolean recursive, Dictionary`2 newItemIds, IProgress`1 progress, CancellationToken cancellationToken)
Source: SQLitePCL.pretty
TargetSite: Void CheckOk(SQLitePCLEx.sqlite3, Int32)

 

  • Like 1
Posted

Okay, so removing my 4K library allows the series to merge. Thanks guys. 

I was hoping I'd be able to have a separate 4k television library like I do with 4k movies (just for easier access when using a 4k capable tv), but this is better than nothing

  • Like 2
  • 1 year later...
fabien_m2002
Posted

Hello

i had this issue today.

2 identical series, 2 versions (4K, FHD) which were not merged. Metadata were identical, tmdb field with correct ID for both.
The issue was that one version had IMDB field filled with ID, the other version had blank.

To resolve, i delete the IMDB field, re-scan and that did it! I have my serie merged with 2 versions.

It's the normal behavior? I am suprised that if one version has IDs metadata from different sources but if the ID points to the good serie/VOD, it should be OK i guess

  • 2 weeks later...
Posted
On 5/16/2026 at 5:31 AM, fabien_m2002 said:

Hello

i had this issue today.

2 identical series, 2 versions (4K, FHD) which were not merged. Metadata were identical, tmdb field with correct ID for both.
The issue was that one version had IMDB field filled with ID, the other version had blank.

To resolve, i delete the IMDB field, re-scan and that did it! I have my serie merged with 2 versions.

It's the normal behavior? I am suprised that if one version has IDs metadata from different sources but if the ID points to the good serie/VOD, it should be OK i guess

HI there, can you please provide a specific example?

How to Report a Problem

Thanks !

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...