Jump to content

Search the Community

Showing results for tags '4.3.1.0'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. killianbe

    Crash Emby Server Linux lastest

    Hi (Sorry i'm bad in english!) I've error when i've update my docker emby *** Error Report *** Version: 4.3.1.0 Command line: /app/emby/EmbyServer.dll -programdata /config -ffdetect /app/emby/ffdetect -ffmpeg /app/emby/ffmpeg -ffprobe /app/emby/ffprobe Operating system: Unix 4.9.0.11 64-Bit OS: True 64-Bit Process: True User Interactive: True Runtime: file:///app/emby/System.Private.CoreLib.dll Processor count: 4 Program data path: /config Application directory: /app/emby SQLitePCL.pretty.SQLiteException: Busy: database is locked - PRAGMA journal_mode SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteDatabaseConnection.PrepareStatement(String sql, String& tail) at SQLitePCL.pretty.DatabaseConnection.PrepareStatement(IDatabaseConnection This, String sql) at Emby.Sqlite.BaseSqliteRepository.PrepareStatement(IDatabaseConnection connection, ReadOnlySpan`1 sql) at Emby.Sqlite.BaseSqliteRepository.CreateConnection(Boolean isReadOnly) at Emby.Server.Implementations.Data.SqliteItemRepository.Initialize(SqliteUserDataRepository userDataRepo, IUserManager userManager) at Emby.Server.Implementations.ApplicationHost.InitDatabases() at Emby.Server.Implementations.ApplicationHost.Init() at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken) Source: SQLitePCL.pretty TargetSite: SQLitePCL.pretty.IStatement PrepareStatement(System.String, System.String ByRef) Info Main: Shutdown complete Can you please help me to resolve that ? Thx error emby.txt
  2. The subtitles are not working during playback and not automatically downloading like i think they are supposed to be since I have signed up for Open Subtitles. And even when I download the exact subtitles for my video file, I cannot make them display. There is not the option to select the subtitles even when I place them in the same folder video file. They used to work ok, until about the time I updated to 4.3.1.0.
  3. After updating to 4.3.1.0 upon starting the service, emby immediately began removing content from my library alongside with errors similar to: Error App: Error in MusicAlbumResolver resolving /mnt/nas/media/Music/Tycho System.IO.FileLoadException: System.IO.FileLoadException: Could not load file or assembly 'MediaBrowser.Model, Version=4.3.1.0, Culture=neutral, PublicKeyToken=null'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) I think it's an issue with the update mechanism because the emby service still shows it was started with v4.3.0.30 (dashboard reflects this as well). The paths listed in the 'resolving' errors all exist and are accessible. I gathered the embyserver logs before I restored from snapshot, but can try replicating this again if needed.
×
×
  • Create New...