Nice. The issue for the managed user was solved by updating to desktop player version 1.4
The Unknown metadata type: folder error is still thrown in the console.
Thank you for your quick response and the easy fix.
Would just like to kick my two cents in here. I’ve been seeing this error on the latest public PMS version - Mac. I have traced it to my Movies library. I disabled Local Media Assets when I created the library, but apparently not before PMS still chose to grab the local folder assets for some of my media. Because of this, when I scroll the list view of my movies, any time it tries to load a section that used Local Media Assets, it throws that error because I have LMA disabled. I can tell this because those items that were previously matched with Local Media Assets have the filename as the media name, even though it also pulled the rest of the metadata from Plex Movie. I’m having to go through and refresh metadata for each of those items, after which the Unknown Metadata Type: Folder error does not occur when viewing the same list of titles. Not sure why or if this is a bug (Pretty sure I had LMA disabled before I added the library, but it is still trying to use it) - Just thought I’d share in case this helps anyone.
Same issue for me too.
I managed to get rid of it for some time by going through each of the movie files that were showing with file name as the movie title, removing each file metadata through Windows properties. I also unticked Local Media Assests on all scanners, then analysed all libraries.
This seemed to resolve the issue.
However after several months it has returned and flooding the Server logs.
Hopefully a Plex guru will be able to shed some light on what is causing the issue and resolve it finally.
PMP Version 4.29.2 (2.57.0)
PMS Version 1.19.3.2793
mmmh… it seems that this one is one of strange behaviors/bugs.
added a new video inside my video library folder and a few seconds later, the video is shown in the list as usual.
I added a new album folder inside my music library folder and this one don’t want to appear in my music library. very very strange.
According to this post, this error is safe to ignore. It is apparently related to some development work being done.
This thread has been marked as solved for more than six months and the title is not related to the actual problem the user was experiencing (one of their users was unable to access one of their libraries). You may be better served by starting a new thread and describing, in detail, the actual problem you’re experiencing.