2024-01-03, 09:25 AM
I keep getting this issue even after updating Jellyfin and dependencies. It happened unexpectedly and I can't figure out why or which XML document has an error:
[09:23:19] [INF] [1] Main: Jellyfin version: 10.8.13
[09:23:19] [INF] [1] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /home/redacted/jellyfin/log]"]
[09:23:19] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll"]
[09:23:19] [INF] [1] Main: Operating system: Linux
[09:23:19] [INF] [1] Main: Architecture: X64
[09:23:19] [INF] [1] Main: 64-Bit Process: True
[09:23:19] [INF] [1] Main: User Interactive: True
[09:23:19] [INF] [1] Main: Processor count: 8
[09:23:19] [INF] [1] Main: Program data path: /home/redacted/jellyfin
[09:23:19] [INF] [1] Main: Web resources path: /usr/lib/jellyfin/bin/jellyfin-web
[09:23:19] [INF] [1] Main: Application directory: /usr/lib/jellyfin/bin/
[09:23:19] [FTL] [1] Main: Unhandled Exception
System.InvalidOperationException: There is an error in XML document (0, 0).
---> System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerConfiguration.Read10_ServerConfiguration()
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader)
at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromStream(Type type, Stream stream)
at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromFile(Type type, String file)
at Jellyfin.Server.Migrations.MigrationRunner.RunPreStartup(ServerApplicationPaths appPaths, ILoggerFactory loggerFactory)
at Jellyfin.Server.Program.StartApp(StartupOptions options)
at Jellyfin.Server.Program.<Main>(String[] args)
Short of uninstalling and reinstalling Jellyfin, is there any way of identifying what XML document is at fault?
[09:23:19] [INF] [1] Main: Jellyfin version: 10.8.13
[09:23:19] [INF] [1] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /home/redacted/jellyfin/log]"]
[09:23:19] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll"]
[09:23:19] [INF] [1] Main: Operating system: Linux
[09:23:19] [INF] [1] Main: Architecture: X64
[09:23:19] [INF] [1] Main: 64-Bit Process: True
[09:23:19] [INF] [1] Main: User Interactive: True
[09:23:19] [INF] [1] Main: Processor count: 8
[09:23:19] [INF] [1] Main: Program data path: /home/redacted/jellyfin
[09:23:19] [INF] [1] Main: Web resources path: /usr/lib/jellyfin/bin/jellyfin-web
[09:23:19] [INF] [1] Main: Application directory: /usr/lib/jellyfin/bin/
[09:23:19] [FTL] [1] Main: Unhandled Exception
System.InvalidOperationException: There is an error in XML document (0, 0).
---> System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerConfiguration.Read10_ServerConfiguration()
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader)
at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromStream(Type type, Stream stream)
at Emby.Server.Implementations.Serialization.MyXmlSerializer.DeserializeFromFile(Type type, String file)
at Jellyfin.Server.Migrations.MigrationRunner.RunPreStartup(ServerApplicationPaths appPaths, ILoggerFactory loggerFactory)
at Jellyfin.Server.Program.StartApp(StartupOptions options)
at Jellyfin.Server.Program.<Main>(String[] args)
Short of uninstalling and reinstalling Jellyfin, is there any way of identifying what XML document is at fault?