Issue with Actor Metadata (not all actors) v4.9.5.0

[antilog17 3]

As a follow up, I copied the library.db file an in read-only mode did a search and found in the MediaItems table, that there are 680 entries with Images column containing this butchered \\KSMEDIANAS path instead of the expected %MetadataPath%

I suspect that if I want to fix this problem. I would need to shut down Emby, modify the DB directly to fix these paths, clear out all cache files, load the modified DB file into Emby, start it back up. Does that sound like the correct sequence of steps?

[Luke 43402]

17 minutes ago, antilog17 said:

As a follow up, I copied the library.db file an in read-only mode did a search and found in the MediaItems table, that there are 680 entries with Images column containing this butchered \\KSMEDIANAS path instead of the expected %MetadataPath%

I suspect that if I want to fix this problem. I would need to shut down Emby, modify the DB directly to fix these paths, clear out all cache files, load the modified DB file into Emby, start it back up. Does that sound like the correct sequence of steps?

Yes. Those must be very old entries. It's actually been a few years since all of the storage switched to the variable path.

[antilog17 3]

50 minutes ago, antilog17 said:

I suspect that if I want to fix this problem. I would need to shut down Emby, modify the DB directly to fix these paths, clear out all cache files, load the modified DB file into Emby, start it back up. Does that sound like the correct sequence of steps?

To clarify, could I leave the Images column blank for those 680 rows and then they would get updated as refreshes occur or do I need to replace each entry with the proper equivalent value using the variable path?

[Luke 43402]

11 minutes ago, antilog17 said:

To clarify, could I leave the Images column blank for those 680 rows and then they would get updated as refreshes occur or do I need to replace each entry with the proper equivalent value using the variable path?

If you’re willing to let them get repopulated gradually then you can just run the scan metadata folder scheduled task. That should get the non existent records cleared out.

[antilog17 3]

The process fixed it. I NULL ed out the Images column for those 680 entries, put the database back in, and it fixed Christian Kane's image / profile. I am going to presume this is fixed now.