Multiple duplicate library sections

[dzoulias 2]

Hello all.

 

I updated Emby Server today (or installed on top of it since i had the most current version but i was troubleshooting something i had asked in a previous post).

 

My library is devided into 4 sections:

 

Movies HD, Movies SD, Series, Trailers

 

Web app shows the library correctly.

 

However, Emby Theater shows 3 "Movies HD", 1 "Movies SD" and 1 "Series".

 

Meaning 3 times the HD movies one.

 

How do i troubleshoot that?

 

Thank you in advance.

 

Dimitris

[marcassaim 1]

Hi,

 

I have the same issue. Updated today and on Emby home I now have multiple duplicates libraries. Sometimes 4-5 dupes of the same library.
There are no dupes when I check in the libraries administration.

 

Any idea how to clean this ?

 

Thanks

[Luke 38808]

HI, where exactly does the web app show them correctly?

[marcassaim 1]

It show them corretly in the admin part. Where you add/edit libraries. 

However on the Home the libraries are duplicated.

 

I ended up renaming the library.db file and started a full rescan of my libraries. Problem seems to be gone but I don't know yet, I'm only a 10% of the scan

[Luke 38808]

Thanks for the info. I think the issue is related to the upgrade from 3.5. We are looking into it.

[dzoulias 2]

HI, where exactly does the web app show them correctly?

Hello there and thank you for replying.

 

As my friend stated in the reply above, it shows the libraries correctly in the server configuration part, in the library section.

 

Dimitris

[dzoulias 2]

Thanks for the info. I think the issue is related to the upgrade from 3.5. We are looking into it.

Nice! Lets keep this active then.

 

In the meantime, is there a workaround? For my part, i am technically proficient and i would love to know if in the meantime there is a file or anything i can edit in order not to have this issue.

 

One more thing. It goes away if i delete and reinstall, after having of course removed library.db, but that is not an option since the viewing status will be lost and the backup plugin will backup the bug as well.

 

Thank you for your good work however.

 

Do we check solution status here?

 

Dimitris

Edited February 5, 2019 by dzoulias

[Luke 38808]

I would try what the user did above as a workaround. Thanks.

[dzoulias 2]

So, i wook the following steps as the person a few posts above suggested:

 

1. Used the Backup and Restore Plugin

2. Renamed library.db to library.db.old

3. Used the Backup and Restore Plugin to restore the backup created in step 1.

 

Problem fixed.

 

Tnank you all.

[Luke 38808]

Thanks for the feedback.