Jump to content

Emby 4.5.3 Library issue


nanohits

Recommended Posts

nanohits

Hi All,

After I updated to 4.5.3 when I scan library I get this error. Was working fine with the previous version

Scan media library failed

Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown.

at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc)

at SQLitePCL.pretty.StatementImpl.MoveNext()

at Emby.Server.Implementations.Data.SqliteItemRepository.GetUserDataKeyId(String userDataKey, IStatement insertUserDataKeyStatement, IStatement getUserDataKeyStatement)

at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItemsInTranscation(IDatabaseConnection db, List1 tuples)

   at Emby.Server.Implementations.Data.SqliteItemRepository.SaveItems(List1 items, CancellationToken cancellationToken)

at Emby.Server.Implementations.Library.LibraryManager.CreateItems(List1 items, BaseItem parent, CancellationToken cancellationToken)

   at MediaBrowser.Controller.Entities.Folder.ValidateChildrenInternal(IProgress1 progress, CancellationToken cancellationToken, Boolean recursive, Boolean refreshChildMetadata, MetadataRefreshOptions refreshOptions, IDirectoryService directoryService)

at MediaBrowser.Controller.Entities.Folder.ValidateSubFolders(BaseItem[] children, IDirectoryService directoryService, IProgress1 progress, CancellationToken cancellationToken)

   at MediaBrowser.Controller.Entities.Folder.ValidateChildrenInternal(IProgress1 progress, CancellationToken cancellationToken, Boolean recursive, Boolean refreshChildMetadata, MetadataRefreshOptions refreshOptions, IDirectoryService directoryService)

at Emby.Server.Implementations.Library.LibraryManager.PerformLibraryValidation(IProgress1 progress, CancellationToken cancellationToken)

   at Emby.Server.Implementations.Library.LibraryManager.ValidateMediaLibraryInternal(IProgress1 progress, CancellationToken cancellationToken)

at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.ExecuteInternal(TaskOptions options)

Edited by nanohits
Link to comment
Share on other sites

Happy2Play

FYI the error was "Busy: database is locked" so restarted resolved what ever database lock issue that happened.

  • Like 1
Link to comment
Share on other sites

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...