[Solved] For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
fu24
Posts: 8
Joined: Fri Jan 11, 2013 12:57 pm

[Solved] For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by fu24 »

I have been using UMS to watch media on my SONY BRAVIA KDL-32W700B.
This month I updated UMS and started to get an error. No media or folders appear on my TV anymore.
This error only occurs on this KDL-32W700B TV. My other KDL-40EX520 is all normal.

I tried to install several earlier versions. I found that this error started to appear after UMS 10.6.0
Attachments
ums10.8.2_dbg_2021-08-05-22-02.zip
(34.47 KiB) Downloaded 25 times
User avatar
mik_s
Moderator
Posts: 459
Joined: Wed Aug 23, 2017 11:03 pm
Location: UK

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by mik_s »

Could you try and recreate those logs, UMS was not in trace mode when they were made for some reason.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
fu24
Posts: 8
Joined: Fri Jan 11, 2013 12:57 pm

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by fu24 »

This is the log file after installing the latest version of UMS 10.9.0.
thanks
Attachments
ums10.9.0_Trace_dbg_2021-08-14-11-44.zip
(149.66 KiB) Downloaded 30 times
User avatar
mik_s
Moderator
Posts: 459
Joined: Wed Aug 23, 2017 11:03 pm
Location: UK

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by mik_s »

I see communication between UMS and your TV so in theory it should show your files. I do see a SQL error when UMS receives a browse request so the result sent back is basically empty.

Code: Select all

WARN  2021-08-14 11:43:03.701 [HTTPv2 Request Worker 9] error transforming searchCriteria to SQL.
java.lang.RuntimeException: Unknown type : 
	at net.pms.network.SearchRequestHandler.getRequestType(SearchRequestHandler.java:69)
	at net.pms.network.SearchRequestHandler.createSearchResponse(SearchRequestHandler.java:79)
	at net.pms.network.RequestV2.searchHandler(RequestV2.java:1101)
	at net.pms.network.RequestV2.answer(RequestV2.java:680)
	at net.pms.network.RequestHandlerV2.writeResponse(RequestHandlerV2.java:414)
	at net.pms.network.RequestHandlerV2.messageReceived(RequestHandlerV2.java:270)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.codec.http.HttpChunkAggregator.messageReceived(HttpChunkAggregator.java:145)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
	at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
I know little about the protocols used but my guess is that your TV is using field that UMS is not handling correctly.

Another possibility is a problem with the database. To rule that out you can delete the database and it will be recreated when UMS restarts.
The database is located in C:\ProgramData\UMS\database
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
User avatar
SubJunk
Lead Developer
Posts: 3490
Joined: Sun May 27, 2012 4:12 pm

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by SubJunk »

10.6.0 is when we added UPnP search support so that seems related. I'll make a test build for you soon
fu24
Posts: 8
Joined: Fri Jan 11, 2013 12:57 pm

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by fu24 »

SubJunk wrote: Sun Aug 15, 2021 6:03 pm 10.6.0 is when we added UPnP search support so that seems related. I'll make a test build for you soon
Thank!

I have one more question.
I have a new TV (Android TV),
The brand model is TOSHIBA U8000VS.
What I need to do to add this new renderer.
Attachments
ums10.9.0_U8000VS_Trace_dbg_2021-08-15-14-30.zip
(74.29 KiB) Downloaded 26 times
User avatar
mik_s
Moderator
Posts: 459
Joined: Wed Aug 23, 2017 11:03 pm
Location: UK

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by mik_s »

Your TV does not give much info to to make a good conf for it. You will have to check the specs in the manual to see what it can support.
I found a copy online but it is only in Japanese and is bad scan so I can't translate it. pages 43-46 show the supported formats but TBH I'm not sure how to start that one.

Best way to make a new conf for your TV is to take an existing conf (the Samsung-UHD.conf might be a good start), copy it and using the info from the manual you can edit the supported formats section to match. A good way of testing if a file will play on your TV is to try playing from the #--TRANSCODE--# folder and choose "No transcoding"
(if you do not see it, enable "show the #--Transcode--# folder" in the GUI on the navigation tab). If that works then you can add that format to the conf.

You will also need to set

Code: Select all

UserAgentSearch = U8000VS
UpnpDetailsSearch = U8000VS
so that UMS will know to use it.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
User avatar
SubJunk
Lead Developer
Posts: 3490
Joined: Sun May 27, 2012 4:12 pm

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by SubJunk »

I think I see what is happening - the Sony TV is using a search request instead of a browse request, even though it just wants the folders with no search parameters, which we don't support. I will try to make support for that.
fu24
Posts: 8
Joined: Fri Jan 11, 2013 12:57 pm

Re: For SONY KDL-32W700B in UMS10.6.0 and later versions, an error occurs

Post by fu24 »

SubJunk wrote: Mon Aug 16, 2021 8:02 pm Please try this on the Sony https://www.universalmediaserver.com/up ... 3353c3.exe
There are still errors.

Code: Select all

20:14:43 INFO  error transforming searchCriteria to SQL.
java.lang.RuntimeException: Unknown type : upnp:class derivedfrom "object.item.imageItem"
	at net.pms.network.SearchRequestHandler.getRequestType(SearchRequestHandler.java:69)
	at net.pms.network.SearchRequestHandler.createSearchResponse(SearchRequestHandler.java:78)
	at net.pms.network.RequestV2.searchHandler(RequestV2.java:1112)
	at net.pms.network.RequestV2.answer(RequestV2.java:689)
	at net.pms.network.RequestHandlerV2.writeResponse(RequestHandlerV2.java:414)
	at net.pms.network.RequestHandlerV2.messageReceived(RequestHandlerV2.java:270)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.handler.codec.http.HttpChunkAggregator.messageReceived(HttpChunkAggregator.java:145)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
	at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:459)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
	at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
	at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Attachments
ums10.9.1-ik666-searchErrorFallback-f3353c_dbg_2021-08-16-19-16.zip
(144.71 KiB) Downloaded 25 times
Post Reply