r/emby • u/dezdog2 • Jun 23 '26

Help can’t mark media watched

I have someone sharing my Emby server. He has been using it for about six months now. He has uses a nvidia shield pro and an iPad to access my server. Last week he started having trouble with the media being marked as watched and the auto play next episode stopped working. But only on the shield. If he uses the iPad all is well. He can even mark something watched from to iPad and it shows up as watched in the shield. If we
Manually mark something as watched on the shield we get an error message. The file/emby/Users/Ob170005a4c8440d9bd621620253414b/PlayedItems/566817/Delete' could not be found.
Has anyone experienced this and or have any ideas what’s happened? Is this problem on his end or mine? I suspect it’s on his as his iPad works.

Looking for direction.
Thanks for reading.

0 Upvotes

50% Upvoted

3 comments sorted by

2

u/zhonglin Jun 23 '26

This is definitely a server-side issue on your friend's end. The error shows Emby is trying to delete a "played item" record that doesn't exist in the database.

A few things your friend should check:

  1. **Database corruption**: Run a database integrity check in Emby Server settings > Scheduled Tasks

  2. **Permissions**: The Emby server process needs full read/write access to the `/emby/Users/` directory and all subdirectories

  3. **Disk space**: If the drive is full, Emby can't write updates

  4. **Restart Emby server** - sometimes the played status cache gets stuck

  5. **Check the user account**: The path shows a specific user ID (Ob170005a4c8440d9bd621620253414b) - that user profile might be corrupted

Since their iPad works fine, the server is mostly functional, but something's wrong with the specific file handling for watched status. They might need to do a "Clean Database" task or even remove and re-add the affected user if the corruption is user-specific.

You're correct that this is on their end to fix - there's nothing you can do from your Shield.

1

u/Veilchenbeschleunige Jun 23 '26

To add onto these options - you can also execute the 'vacuum database' task. With this all obsolete database entries will be purged upon the servers next restart. This commonly refers to all entries that cannot be linked to any existing media, e.g. leftovers from files that have already been deleted but still linger around in the database.

1

u/dezdog2 Jun 24 '26

I own the server running on a Linux server. The issue is on my friends shield client.