Libraries not updating after server migration

[moviefan 187]

Recently migrated servers to new setup.  Got most things working but am noticing that it's not adding new media.  I've looked at the log and I see a couple of errors about file paths.  One of them is talking about something related to the collections in the regular AppData Emby path.

Another one is talking about a path that existed on my old server but does not anymore.  I've updated all of the paths I can find in the settings but I don't know where this reference is coming from.

Can someone take a look at the logs and provide any suggestions?

"Error saving to E:\Emby\metadata\library\b4\b4ab7d3344cbbac20b6ffbfa6f8c4163\auto_poster_5815_5820_5854_5863.jpg"

E: drive does not exist anymore.

"Error App: Error in validateChildren for 6 C:\Users\Emby\AppData\Roaming\Emby-Server\programdata\data\collections"

This path exists up to the \data directory but there is no collections directory.

embyserver.txt

[Luke 42078]

Quote

E: drive does not exist anymore.

Looks like it is still configured as the server metadata folder. I would suggest reconfiguring that option, making sure to read the help text as you do that. Once you've done that, then I would say let's see where things are after that.

[moviefan 187]

@Lukecan you help me find the metadata folder configuration in the settings?  I am not seeing it.

[Lessaj 467]

Library -> Advanced tab.

[moviefan 187]

Thanks @LessajI was missing that tab before while reviewing.  Found and it has fixed my issue of adding new items.

@LukeShould I still worry about the other error about the collections path?

[Happy2Play 9780]

10 hours ago, moviefan said:

Should I still worry about the other error about the collections path?

That is a really old issue I believe migration in 4.7.  And I believe before token collections path in db.  Will have to search but believe you have to remove the Collections library via api and allow it to rebuild to correct the old db path. 

As this old method will no longer work as info is db only.

@Luke will have to comment but you will probably have to remove the Collections library from the api per the bottom section of this how to. 

Not sure it you would just clear that old path via the db though.

I would make a backup of /metadata/collections as it will probably clear the new location also.

[moviefan 187]

@Lukeany thoughts on the above?  I'm having a little challenge following those threads. 

[Luke 42078]

13 hours ago, moviefan said:

@Lukeany thoughts on the above?  I'm having a little challenge following those threads. 

I would ignore it. The only way to make it go away is to start with a fresh database.