Metadata Images No Longer Downloading In Windows 10

[Guardian Hope 117]

I haven't touched Emby since moving up to Windows 10 Pro, however, today I fired up Emby amd after adding ABC Family's Stitchers to the media library I realized something was wrong: its downloading show and episode information buy it is not downloading metadata images.

 

Thinking it may have just been the show I hopped up a few to Pretty Little Liars and saw the same thing happen to newly added episodes. Than I tried Once Upon a Time much to the same results and realized I had a problem.

 

I've tried to manually add the images by selecting them through the Metadata Manager but all that ends with is a never ending spinning circle.

 

This issue only seems to effecting metadata images for shows and movies - it seems to have no problem downloading cast and crew photos.

 

The log file reports Windows 8.1 Pro with Media Center as my OS but I am actually running Windows 10 Pro Build 10525.

 

Log File: http://paste2.org/V4wm6Hmx

[ebr 16187]

It doesn't look like you actually did anything during that log session related to your image downloading problem but I do see every network request timed out.  Check your firewalls or anti-malware software and be sure it is allowing the server out to the internet.

 

 

The log file reports Windows 8.1 Pro with Media Center as my OS but I am actually running Windows 10 Pro Build 10525.

 

This is just how Win 10 reports.  We have to actually re-compile our program with manifest changes in order for Win 10 to report itself to us.  Otherwise, it just looks like 8.1.  I assume they did this for maximum compatibility.

[Guardian Hope 117]

It doesn't look like you actually did anything during that log session related to your image downloading problem but I do see every network request timed out.  Check your firewalls or anti-malware software and be sure it is allowing the server out to the internet.

 

 

 

This is just how Win 10 reports.  We have to actually re-compile our program with manifest changes in order for Win 10 to report itself to us.  Otherwise, it just looks like 8.1.  I assume they did this for maximum compatibility.

 

 

However, yet I did. I've checked, disabled, re-enabled (etc.) my firewalls and anti-malware software. In fact, they are showing the connection of Emby Server opening the ports and reaching out on the ports. I monitored Emby's activities and it can most certainly connect to the internet. Even the backbone routers and the gateway reported Emby's connection to the internet. As someone who has to work with backbone providers like Equinix and companies like AWS, Azure, and SoftLayer - I have become fairly adept at monitoring network communications. 

 

I will be the first to admit that I haven't really cared for how Emby gets to work its magic so as long as it works (that's what's been great about MediaBrowser/Emby for all these years!) but if I interpret some of the log files it says that I'm not even receiving remote communications from you all like information about updates yet I am.

 

Perhaps this is a problem with Emby and Windows 10 Pro? I know a lot of Windows 10 problems are going around lately as its a new OS.

 

In either case, I have attached five log files - all from today. I think one of them is actually the update log but I located everything from the 23rd.

 

Also remember that I specifically went into Metadata manager and tried to download the missing images for Switchers (I didn't even bother with Age of Ultron, Pretty Little Liars, or Once Upon a Time this time) and it just sat there and hung.

 

Yet it has no problems downloading cast and crew photos or the actual synopsis information. 

 

http://paste2.org/8sNxkaes (this one is nearly 2000 lines long!)

 

http://paste2.org/pME7vZZm (this one is nearly 35000 lines long!)

 

http://paste2.org/yMj0ksgg (this one also comes in at around 2000 lines long!)

 

http://paste2.org/W0s7yxdF (this one appears to be the update log, very small - about 16 lines)

 

http://paste2.org/AsPN6KYz (I am assuming this is just the log from the server restart after updating)

 

I hope this helps because Emby is establishing connections and everything but metadata image downloading for series, episodes, and movies are working fine.

 

Edit - I took a look at the log files and saw lines like "\\AHMS\Media\TV Shows\Stitchers\Season 1\folder.jpg access denied" yet I have full network share access to and was able to create files through File Explorer by means of using the network share address.

Edited August 24, 2015 by Guardian Hope

[Luke 42081]

I would start by fixing this. some kind of permission problem preventing emby from saving metadata.

 

 

 

1. Access to the path '\\AHMS\Media\TV Shows\Stitchers\Season 1\metadata' is denied.
2. System.UnauthorizedAccessException

[Guardian Hope 117]

I would start by fixing this. some kind of permission problem preventing emby from saving metadata.

 

It would seem Windows 10 reset network share read/write permissions when it updated to Build 10525 (probably started at 10240).

 

I guess Emby specifically uses the user account that starts it to read/write network shares? Because the Administrators group had full control but I had to specifically [re]input my account before Emby scanned the library and started downloading Stitchers, Pretty Little Liars, Once Upon a Time, and Age of Ultron metadata images. 

 

This of course, after I Googled the error only to find information about people making mistakes in coding namely for IIS of which Emby is not.

 

They really should put a big warning label with Windows 10 that says "recheck all your network permissions" - this probably resolved a lot of network share problems I was facing unrelated to Emby.

 

Out of curiosity, and unrelated to the issue we just resolved, any reason why Emby's log would show it failing to connect to the internet when it clearly can?

Edited August 24, 2015 by Guardian Hope

[ebr 16187]

Out of curiosity, and unrelated to the issue we just resolved, any reason why Emby's log would show it failing to connect to the internet when it clearly can?

 

At the time Emby tried, it couldn't.

[enthous 0]

I haven't yet moved to Windows 10, am still running Windows 7, but suddenly I'm having the same issue. 

 

I've been ripping 7 seasons of a TV show from DVDs and for the first 5 seasons everything was great. I added the episodes to the Season folders and the server got the images for me.  Now the images aren't downloading automatically.  I've used the same naming convention for all seasons,  but suddenly I'm not getting the episode images automatically.  I've had to go to TVdb and get them manually.  Even when I copy them into my folder with the correct naming convention (I add "-thumb" to the video filename), they're not being recognized automatically.  I have to use the Upload image feature to get the server to see and display them. 

 

I've also noticed that the server isn't taking the episode name from my filenames the same and it's not filling the TVdb id field either.  I use the naming convention "SnnEnn <episode title>.mkv" for my video files.  When things were working correctly the server would fill the metadata Name field with <episode title>,  now it's using the whole filename, eg  "SnnEnn <episode title>" for the Name field.  It is filling in the Season Number and Episode Number fields correctly.  I tried changing the Name field to only the episode title and refreshing to see if that was why it couldn't find the images, but that didn't help.  I tried giving it the TVdb ID number:  nothing.  Scanning the library after these changes didn't help either, nor has restarting the server.

 

I've been working on this series for a few days and this behavior just started yesterday.  In fact, it was late yesterday; I'm pretty sure it worked earlier in the day when I moved the files I had processed overnight.  We haven't changed any network settings, but there was a security update to Microsoft Silverlight sometime the day before. 

Edited August 26, 2015 by enthous

[enthous 0]

Update:  If I manually enter the TVdb ID and fix the Name field in the metadata, do a Save, then do a Refresh, it finds the image.

[enthous 0]

One final update:  I've now discovered I don't need to enter anything.  If I just do a Save, then a Refresh, everything gets downloaded.  I don't know why it's not registering without the Save first, but a Refresh without the Save doesn't work.  I can live with this workaround for the final 22 episodes I'm ripping.

[Guardian Hope 117]

One final update:  I've now discovered I don't need to enter anything.  If I just do a Save, then a Refresh, everything gets downloaded.  I don't know why it's not registering without the Save first, but a Refresh without the Save doesn't work.  I can live with this workaround for the final 22 episodes I'm ripping.

 

Well, this isn't actually the same issue; mine was that Windows 10 reset the share permissions and Emby uses the user account's permission rather than the group (Administrators) resulting in Emby unable to write to the network share.

 

What you are experiencing is a naming convention error. I'm not sure what you are ripping from DVDs but personally I use one of two conventions:

 

Series Name - S##E## - Episode Title.mkv

 

Series.Name.S01E04.Episode.Title.mkv

 

 

For example, for an episode of Once Upon a Time the full network address from the first example looks like:

 

\\AHMS\Media\TV Shows\Once Upon a Time\Season 4\Once Upon a Time - S04E01 - A Tale of Two Sisters.mkv

 

 

Depending on the title of the series is what decides the convention as while it has improved, MediaBrowser doesn't always decipher the numbers in a title correctly if a show has a title with numbers in it. However, I haven't experienced anything like that in about a year.

 

There have been rare occasions however that MediaBrowser can't identify a piece of media (typically when there are conflicting titles) in which case you have to input TheTVDB or IMDB numbers and save it; than refresh and it'll find everything.