Persistent Error: Device descriptor retrieval failed, no response:

[speckledegg]

Since upgrading from v13 to v14 (in all it's versions) I've had a fair few problems with UMS on my Samsung TV. It either stalls, can't be detected, disappears, won't let you stop and change to a different file, won't load a file. There have been a range of issues, none of them reliably replicated. However, the one thing that has been consistent in upgrading from v13 to v14 is the introduction of the below error message which repeats, constantly, in the log. I can't help but think that this is somehow causing all the issues. v13 doesn't have this problem (but for some ungodly reason, I *cannot* get v13 to load at startup on Windows 11).

My latest attempt to try v14 failed to show any content to the shared directory "No Content Found".

Any help would be greatly appreciated!

Many thanks

Mark

[mik_s]

There was a change to a different networking module and that logged more information than is needed.
That message just says something did not respond with the right descriptor or is ignoring that request.
It may be from another service on the device like second screen, something on your router, or even windows media player.
These messages will be filtered out in the next version.

There was an error with your database which will be the cause of your problems. It looks like a failed database update that can happen sometimes after doing a big upgrade.

Code: Select all

TRACE 2025-05-05 11:02:42.522 [main] Execute Update with SQL "CREATE INDEX IF NOT EXISTS VIDEO_METADATA_BASIC_COLUMNS_IDX ON VIDEO_METADATA(IMDBID, MEDIA_YEAR, TITLE, TVSERIESID, EXTRAINFORMATION, ISTVEPISODE, TVSEASON, TVEPISODENUMBER, ISSAMPLE)"
ERROR 2025-05-05 11:02:42.535 [main] Error checking tables: Column "ISSAMPLE" not found; SQL statement:
CREATE INDEX IF NOT EXISTS VIDEO_METADATA_BASIC_COLUMNS_IDX ON VIDEO_METADATA(IMDBID, MEDIA_YEAR, TITLE, TVSERIESID, EXTRAINFORMATION, ISTVEPISODE, TVSEASON, TVEPISODENUMBER, ISSAMPLE) [42122-232]

Deleting or renaming C:\ProgramData\UMS\database will allow UMS to build a new one which will fix this.