Occasional XML-error when loading new files

[Ultroman 87]

This is the first example I've found. Looks like something that should be useful for debugging an XML-parser or -writer.

 

2015-11-02 00:46:53.3321 Info - MediaEncoder: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server\ffmpeg\20150918\ffprobe.exe -show_packets -print_format compact -select_streams v:0 -show_entries packet=flags -show_entries packet=pts_time "D:\3D film\The Lego Movie\The Lego Movie - [hsbs] [2014.3D.1080p.BluRay.DTS-HDA.DUAL]-ASM.mkv"
2015-11-02 00:48:09.8905 Info - MediaEncoder: Keyframe extraction took 76,5583789 seconds
2015-11-02 00:48:10.0335 Error - App: Error parsing xml file D:\3D film\The Lego Movie\The Lego Movie - [hsbs] [2014.3D.1080p.BluRay.DTS-HDA.DUAL]-ASM.xml
2015-11-02 00:48:10.0335 Error - App: Error in Emby Xml
    *** Error Report ***
    Version: 3.0.5781.0
    Command line: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
    Processor count: 8
    64-Bit OS: True
    64-Bit Process: False
    Program data path: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server
    Application Path: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe
    'Element' is an invalid XmlNodeType.
    System.Xml.XmlException
     at System.Xml.XmlReader.FinishReadElementContentAsXxx()
     at System.Xml.XmlReader.ReadElementContentAsString()
     at MediaBrowser.Controller.Providers.BaseItemXmlParser`1.FetchDataFromXmlNode(XmlReader reader, MetadataResult`1 itemResult)
     at MediaBrowser.LocalMetadata.Parsers.BaseVideoXmlParser`1.FetchDataFromXmlNode(XmlReader reader, MetadataResult`1 result)
     at MediaBrowser.Controller.Providers.BaseItemXmlParser`1.Fetch(MetadataResult`1 item, String metadataFile, XmlReaderSettings settings, Encoding encoding, CancellationToken cancellationToken)
     at MediaBrowser.Controller.Providers.BaseItemXmlParser`1.Fetch(MetadataResult`1 item, String metadataFile, CancellationToken cancellationToken)
     at MediaBrowser.LocalMetadata.Providers.MovieXmlProvider.Fetch(MetadataResult`1 result, String path, CancellationToken cancellationToken)
     at MediaBrowser.LocalMetadata.BaseXmlProvider`1.<GetMetadata>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
     at MediaBrowser.Providers.Manager.MetadataService`2.<RefreshWithProviders>d__35.MoveNext()

[Happy2Play 8239]

Was this xml created by Emby or just processed by Emby?

[Ultroman 87]

Was this xml created by Emby or just processed by Emby?

Both. There are no xml-files in my media folders. It happens during a library scan.

[Ultroman 87]

Wow, a lot of these happening! See below. This too seems to link to my other issue, with files which do not play when placed in a Home Videos content-type folder. Not that these all are in such a folder; only the Arrow episodes are. None of these files get any media info aside from the container (mkv/mp4) and do not get any images. I do believe this is the root of 2-3 of my largest annoyances with Emby. And when I say largest annoyances, I mean that my GF rants about them to me all the time

 

EDIT: The examples below may not be the exact same error as first posted, in that the ones below do not post the exact xml-error, like the first one did.

 

2015-11-02 12:26:26.1310 Error - App: Error parsing xml file D:\Film\Pirates of the Caribbean 4\Pirates of the Caribbean IV - On Stranger Tides - 1080p.xml

 

 

2015-11-02 12:48:05.0699 Info - MediaEncoder: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server\ffmpeg\20150918\ffprobe.exe -show_packets -print_format compact -select_streams v:0 -show_entries packet=flags -show_entries packet=pts_time "D:\Serier - nye afsnit\Arrow.S04E01.720p.HDTV.X264-DIMENSION[eztv].mkv"

2015-11-02 12:48:12.9814 Info - MediaEncoder: Keyframe extraction took 7,9114525 seconds

2015-11-02 12:48:15.1465 Error - App: Error parsing xml file D:\Serier - nye afsnit\Arrow.S04E01.720p.HDTV.X264-DIMENSION[eztv].xml

 

 

2015-11-02 12:48:15.6545 Info - MediaEncoder: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server\ffmpeg\20150918\ffprobe.exe -show_packets -print_format compact -select_streams v:0 -show_entries packet=flags -show_entries packet=pts_time "D:\Serier - nye afsnit\Arrow.S04E02.720p.HDTV.X264-DIMENSION[eztv].mkv"

2015-11-02 12:48:23.8530 Info - MediaEncoder: Keyframe extraction took 8,1984689 seconds

2015-11-02 12:48:25.5041 Error - App: Error parsing xml file D:\Serier - nye afsnit\Arrow.S04E02.720p.HDTV.X264-DIMENSION[eztv].xml

 

 

2015-11-02 12:49:27.7473 Info - MediaEncoder: C:\Users\Ultrofamilien\AppData\Roaming\MediaBrowser-Server\ffmpeg\20150918\ffprobe.exe -show_packets -print_format compact -select_streams v:0 -show_entries packet=flags -show_entries packet=pts_time "D:\Film\The Hobbit Trilogy\The Hobbit - An Unexpected Journey (extended) (2012)\The.Hobbit.An.Unexpected.Journey.2012.EXTENDED.1080p.BluRay.DTS.x264-PublicHD.mkv"

2015-11-02 12:51:31.5244 Info - MediaEncoder: Keyframe extraction took 123,7770796 seconds

2015-11-02 12:51:32.7695 Error - App: Error parsing xml file D:\Film\The Hobbit Trilogy\The Hobbit - An Unexpected Journey (extended) (2012)\The.Hobbit.An.Unexpected.Journey.2012.EXTENDED.1080p.BluRay.DTS.x264-PublicHD.xml

Edited November 2, 2015 by Ultroman

[Luke 36997]

you could try switching to nfo and seeing if the same thing happens there.

[Ultroman 87]

you could try switching to nfo and seeing if the same thing happens there.

Thanks for the answer

 

What do you mean? I have neither xml- nor nfo-files for either of these titles. They must be generated during the scan. I have frame-by-frame enabled, as well as every other checkbox under Metadata.

 

Under Metadata => Nfo, the introductory text hints that I can change some nfo-settings under an Advanced-tab, but I can't find it anywhere.

Edited November 2, 2015 by Ultroman

[Happy2Play 8239]

What do you have enabled in Metadata-Services  There is a drop down for each content type.

[Ultroman 87]

What do you have enabled in Metadata-Services There is a drop down for each content type.

Everything

 

But hey, just for kicks I tried a Refresh on one of the items, and suddenly it got all of the media info. After a refresh of each title, they work...wtf? I also tried deleting a few of the titles, and now they're picked up, no problem. Must've had a baaad glitch or something. Still seeing the XML-errors, though.

 

I found the nfo-settings you were talking about, and they're all set to nfo first and then Emby xml. Since I have no nfos, it must do Emby XML for everything. About 10% of those are failing.

 

Oh, and the frame-by-frame thing keeps processing the same bunch of files every scan...

Edited November 2, 2015 by Ultroman

[Ultroman 87]

Come to think about it, the addition of those files may have coincided with the database changes, so that's probably it.

 

The question is why the scans didn't fix them. They were obviously processed at every scan.

Edited November 2, 2015 by Ultroman

[TheShanMan 34]

I'm having this same problem with some of my metadata (perhaps all metadata since a bug was introduced - I haven't tried to narrow it down too much). The log file will say something like "2016-02-05 16:33:06.6266 Error App: Error parsing xml file \\theater\Media\Video\Common\Movies\The Truman Show (1998)\The Truman Show (1998).xml" but the xml file doesn't exist. I know it's not an access problem because it saves images in the movie directories. It simply isn't creating the xml files.

 

I see on Metadata -> Services that under "Metadata Savers" only "nfo" is listed (and not checked). Is emby no longer capable of creating xml metadata files? Do I need to turn nfo on and use nfo from now on? I'm not having this problem with TV shows so I'm guessing that's not the answer. I guess it's a bug? Or if not, how do I get it working again?

 

I'm not sure where the metadata is being saved since metadata is working as far as the clients are concerned. Maybe the metadata is being fetched and cached in memory every time the server starts? I would like the metadata saved in the movie directories, preferably as xml. Any advice on how to get this working would be appreciated!

[Happy2Play 8239]

There are several topics on this but the majority of xml creation have been removed from the server core and you need the "xml saver plugin" if you want to continue using xml files.

[TheShanMan 34]

Thanks for the info! Somehow I missed that news.

 

2 questions.

 

First, how do I get Emby to generate all the missing xml files? Installing the plugin, restarting the server, and kicking off a library rescan doesn't do it.

 

Second, why didn't Emby tell me that I had a configuration problem? If metadata hasn't been saved for who knows how long (whenever the xml functionality was moved into the plugin), it seems like Emby should say somewhere that I need to fix my metadata settings (preferably on the main server page but at least on the metadata page).

[Happy2Play 8239]

Have you verified the options are enabled in Metadata-Services use the drop down for each content type.  Ensure you still have "Saving artwork and metadata into media folders" is still enabled. Metadata-Basics

Edited February 6, 2016 by Happy2Play

[TheShanMan 34]

Yes I have. the XML saver is checked in the relevant media types and saving in media folders is as well (always has been). So does that mean it should be generating those xml files for pre-existing media that don't have them?

[Luke 36997]

No, only when the content is saved during the refresh process.

[TheShanMan 34]

Ugh. So I have to manually find all the missing ones and manually regenerate them one by one? Where was the metadata being stored from the time xml support was moved into the plugin?

 

I sure wish Emby told me about my invalid configuration. Does Emby have any provision for bubbling up messages to the web interface (or a notification) when an invalid configuration is detected? If not, seems like it would be a very helpful addition.

[Luke 36997]

What's an invalid configuration? If you can set something up in the web interface, it's not invalid.

[Happy2Play 8239]

It should, but is sounds like it has already go the information cached do the saver option not being available at the time.

Just tested this and by removing the xml save and adding a movie.  I got all the metadata but couldn't find where exactly it was, but adding the xml saver and restarting, then doing a library scan created a movie.xml during scan.  Only tested with a movie.

[Happy2Play 8239]

What's an invalid configuration? If you can set something up in the web interface, it's not invalid.

When xml was removed from core the you end up with no visible saver option.  Didn't check config to see if xml was still enable but not selectable, but I assume it is do to adding xml save already has options enable and visible via services.

 

Metadata was save somewhere, not the media folder when xml wasn't an available option.

[Luke 36997]

nfo wasn't visible as a saver?

[Happy2Play 8239]

nfo wasn't visible as a saver?

 

nfo was available but unselected as only xml was previously selected and I would guess maintained in system.xml.  I can test if you would like.

[Happy2Play 8239]

This will be affecting everyone that has xml saving enabled and didn't have the "Xml Saver" plugin installed during the 3.0.5821.0 release.  No metadata will be saved to media folder.

[Luke 36997]

Yup, we'll have to toggle nfo on as part of the migration.