Page 1 of 1
Unable to view media after upgrade from 13.x to 14.11
Posted: Fri Apr 11, 2025 9:05 am
by binary512
I just upgraded from UMS v13.60 to v14.11.0 and now cannot even view the media available. My TV (Sony Bravia KDL-55HX750) says "Content not available".
Everything worked fine prior to the upgrade. I am running Windows 11 24H2.
I have attached log files.
Thank you.
Kurt
Re: Unable to view media after upgrade from 13.x to 14.11
Posted: Fri Apr 11, 2025 12:38 pm
by mik_s
There is an error related to the database and if this is not working then nothing will show up when browsing.
Code: Select all
ERROR 2025-04-10 16:55:14.887 [main] net.pms.database.MediaDatabase Error checking tables: Scalar subquery contains more than one row; SQL statement:
UPDATE VIDEO_METADATA SET TVSERIESID = (SELECT TV_SERIES.ID FROM TV_SERIES WHERE TV_SERIES.TITLE = VIDEO_METADATA.MOVIEORSHOWNAME) [90053-232]
This may have happened after a failed update of the database when you upgraded.
If you quit UMS and delete (or rename) C:\ProgramData\UMS\database then a new on will be built when it is next run.
There is something else I have seen in several logs that I don't know the source of
Code: Select all
Creating HTTP request. URI: 'http://192.168.111.9:2869/upnphost/udhisapi.dll?content=uuid:d92e123d-b2e4-4b86-aa03-ae87a8ce088f' method: 'GET'
Sending HTTP request: (StreamRequestMessage) GET http://192.168.111.9:2869/upnphost/udhisapi.dll?content=uuid:d92e123d-b2e4-4b86-aa03-ae87a8ce088f
Send a request to 192.168.111.9:
==================================== HTTPCLIENT REQUEST BEGIN ====================================
GET /upnphost/udhisapi.dll HTTP/1.1
HEADER:
User-agent: UMS/14.11.0 UPnP/1.0 DLNADOC/1.50 (Windows_11)
==================================== HTTPCLIENT REQUEST END ======================================
Received HTTP response: Bad Request
HTTP response message contains text entity
[Fatal Error] :1:10: DOCTYPE is disallowed when the feature "http://apache.org/xml/features/disallow-doctype-decl" set to true.
Received a response from 192.168.111.9:
==================================== HTTPCLIENT RESPONSE BEGIN ===================================
HTTP/1.1 400 Bad Request
HEADER:
Server: Microsoft-HTTPAPI/2.0
Connection: close
Date: Thu, 10 Apr 2025 20:55:31 GMT
Content-type: text/html; charset=us-ascii
Content-length: 339
CONTENT:
Content isn't valid XML, using text formatting: DOCTYPE is disallowed when the feature "http://apache.org/xml/features/disallow-doctype-decl" set to true.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Header</h2>
<hr><p>HTTP Error 400. The request has an invalid header name.</p>
</BODY></HTML>
==================================== HTTPCLIENT RESPONSE END =====================================
Device descriptor retrieval failed: http://192.168.111.9:2869/upnphost/udhisapi.dll?content=uuid:d92e123d-b2e4-4b86-aa03-ae87a8ce088f, 400 Bad Request
This is UMS trying to talk to some program on your computer and it is being ignored but I don't know what it is. Are you using a VPN, antivirus, or other media players?
Maybe you can see what program is using port 2869.
This should show you how to find out what it is.
As far as I can tell these are just warning and can be ignored but I have seen where this is excessive on some logs so it may point to a potential problem.
Re: Unable to view media after upgrade from 13.x to 14.11
Posted: Sat Apr 12, 2025 12:14 am
by binary512
I was hoping to keep my database intact. But all upgrades in the past from 13.x to 14.x caused this error in the database. I deleted the database as suggested and that fixes the problem.
As far as what is using port 2869, running the Netstat command returns "Can not obtain ownership information" for that particular port...even running it as Administrator. I did find out that Port 2869 is used for UPnP (Universal Plug and Play) discovery and control. This error did not show in v13.x, so maybe something in v14.11 is causing this erroneously.? Might be worth checking into as I am getting lots of these errors. I can help troubleshoot if necessary.
I am also getting a lot of the following warnings that I did not get before...not sure why it is trying to read from the Recycle Bin.? Can this be fixed to ignore the Recycle Bin?
08:23:45 WARN Can't list files in non-readable directory: d:\$RECYCLE.BIN\S-1-5-21-3744764888-621709543-3030384407-1001
Thank you for the help.
Kurt
Re: Unable to view media after upgrade from 13.x to 14.11
Posted: Sat Apr 12, 2025 2:59 am
by mik_s
I did find some
reference to the Xbox app in windows as something that uses this port, otherwise it is a legit service for UPnP discovery.
It might just be what UMS is sending is incorrect so it replies as a "HTTP Error 400. The request has an invalid header name."
The recycle bin should be ignored, but that WARN message is just saying it cannot read it anyway so can be ignored.
It might only be showing up if you are sharing the root of a drive.
You really should only share the folders that contain media although you may have a drive which you only use for videos then this is fine but can cause problems if there are system folders on there too. I did see that UMS is scanning its own database in the logs.
Code: Select all
WARN 2025-04-10 16:56:00.858 [jupnp-sync-protocol 476-1] net.pms.util.FileUtil Can't list files in non-readable directory: d:\$RECYCLE.BIN\S-1-5-21-3744764888-621709543-3030384407-1001
TRACE 2025-04-10 16:56:00.859 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "medias.mv.db"
TRACE 2025-04-10 16:56:00.860 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "medias.trace.db"
TRACE 2025-04-10 16:56:00.860 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "medias.trace.db.old"
TRACE 2025-04-10 16:56:00.861 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "USERS.mv.db"
TRACE 2025-04-10 16:56:00.862 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "Pigasus.kurt.conf"
TRACE 2025-04-10 16:56:00.862 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "Roku-Roku3-6-7.conf"
TRACE 2025-04-10 16:56:00.862 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "Sony-BraviaHX WORKING CONFIGURATION.conf"
TRACE 2025-04-10 16:56:00.863 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "Sony-BraviaHX.conf"
TRACE 2025-04-10 16:56:00.864 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "Sony-BraviaHX.conf.ORIG"
TRACE 2025-04-10 16:56:00.864 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "UMS.bat"
TRACE 2025-04-10 16:56:00.864 [jupnp-sync-protocol 476-1] net.pms.formats.FormatFactory Could not match any format to "UMS.conf"
Re: Unable to view media after upgrade from 13.x to 14.11
Posted: Sat Apr 12, 2025 6:46 am
by binary512
Can we figure out why the "HTTP Error 400. The request has an invalid header name." is occurring? I am getting zillions of these every 7 minutes 15 seconds.
I have changed my drive location to individual subdirectories to eliminate the Recycle Bin message.
Thanks.
Re: Unable to view media after upgrade from 13.x to 14.11
Posted: Sat Apr 12, 2025 7:33 am
by mik_s
I brought it up
here if it could be ignored and not logged.
In theory these should have no effect on UMS however Subjunk mentioned his logs grew to over 12GB so this is being looked into.
Do you have an Xbox or use the Xbox app? If so does quitting these programs stop the messages?
This would at least confirm this is the source of these. I don't get these messages in my logs but I don't use anything Xbox.
Re: Unable to view media after upgrade from 13.x to 14.11
Posted: Sat Apr 12, 2025 7:58 am
by binary512
Anything Xbox-related has been disabled and no Xbox services are running.
The only thing that has changed was upgrading UMS from 13.x to 14.11. The older version had no issues.
Hope this helps.
Update: I Stopped the "UPnP Device Host" service and that stops the error messages.