Dan33702 0 Posted October 31, 2019 Posted October 31, 2019 (edited) I was going to share my content with another user, but for some reason, one particular library has 6 listings pointing to the same directory. What can I do to fix this? Edited October 31, 2019 by Dan33702
Happy2Play 9783 Posted October 31, 2019 Posted October 31, 2019 Does it appear correct in Dashboard-Library?
Dan33702 0 Posted October 31, 2019 Author Posted October 31, 2019 Does it appear correct in Dashboard-Library? No, but it only shows the TV folder 5 times.
Luke 42083 Posted October 31, 2019 Posted October 31, 2019 What version of Emby Server are you running?
Dan33702 0 Posted October 31, 2019 Author Posted October 31, 2019 What version of Emby Server are you running? 4.2.1.0
Luke 42083 Posted October 31, 2019 Posted October 31, 2019 Try removing them from Emby library setup. Then when finished, run two complete library scans. Then add it back.
Dan33702 0 Posted October 31, 2019 Author Posted October 31, 2019 It worked, but it took a couple of extra tries. After deleting and running 2 library scans, I added the library back. Four instances immediately popped up, all with different names (TV Shows, TV Shows1, TV Shows11, TV Shows111.) I deleted 3 of them, but all 4 still showed up on my main library page. I went back and deleted the library, and did another 2 scans, added the library back, and it worked. Not sure why I had so much trouble. My library still worked, no matter which one I selected, it just made my screen cluttered. Thanks for all your help.
Happy2Play 9783 Posted November 1, 2019 Posted November 1, 2019 I think you actually have to do as many scans as you have duplicated libraries. There was a issue awhile back that clicking save multiple times caused this when creating libraries. How long ago did you initially create this library?
Dan33702 0 Posted November 1, 2019 Author Posted November 1, 2019 I think you actually have to do as many scans as you have duplicated libraries. There was a issue awhile back that clicking save multiple times caused this when creating libraries. How long ago did you initially create this library? It was within the last few weeks. I had a hard drive crash and salvaged what I could to a new drive.
Dan33702 0 Posted November 1, 2019 Author Posted November 1, 2019 What browser are you using? Chrome beta.
Luke 42083 Posted November 1, 2019 Posted November 1, 2019 If you create another new library, does this happen with that?
Dan33702 0 Posted November 1, 2019 Author Posted November 1, 2019 If you create another new library, does this happen with that? I just tried and the new one seems to work.
Luke 42083 Posted November 2, 2019 Posted November 2, 2019 Ok great, thanks. If you're happy with this new library name, then you can proceed as-is. We can probably clean this up though to allow you to use the old library name. If you locate the server's programdata folder (printed near the top of the log file)....under that there is /root/default. Under there will be sub-folders for each library. Is there one for the old library? You could try deleting that folder, restarting the server, then seeing if you can add the library again.
cfanguy 2 Posted January 18, 2020 Posted January 18, 2020 Same problem as Dan33702. 1 instance of library on server ver. 4.4.0.7 beta. 3 instances of library on user homescreen along with 3 options to move/display library in user options (unchecking 2 of the 3 options to display library makes no change). Deleted library from server. Deleted library folder from /root/default. Rescanned library. 0 instance of library on server. 2 instances of library on user homescreen. No library folder in /root/default this time. Rescanned library. 0 instance of library on server. 1 instance of library on user homescreen. No library folder in /root/default as before. Rescanned library. 0 instance of library on server. 0 instance of library on user homescreen. Readded and rescanned library. 1 instance of library on server. 1 instance of library on user homescreen. I also have several other libraries on same server that were not affected by this problem.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now