DLNA profiles perhaps?

[ron.bali 5]

I was watching a movie this afternoon on an LG smart TV connecting to my Emby server on a Windows 10 laptop.  But I had forgotten to plug the power into the laptop, so the battery emptied and the movie stopped.  When I restarted the laptop, the Emby icon did not reappear among the DLNA icons on the LG TV or on a Panasonic TV.  This has been a recurring problem, sometimes all the DLNA connections are fine, sometimes not.

 

So DLNA is not working for the 3 smart TVs (LG and Panasonic), but Android clients (phone, tablet, Android TV) can use the Emby server OK.  I looked in the logs and found repeating messages about DLNA profiles.  I paste in a short segment below, and I wonder whether this is the problem.  Can anyone suggest what the problem could be?

 

Thanks in anticipation...

 

2016-12-03 18:50:22.1472 Info HttpServer: HTTP GET http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:22.1472 Info Dlna: No matching device profile found. The default will need to be used.
    Cache-Control: no-cache
    Connection: Close
    Pragma: no-cache
    Accept: text/xml, application/xml
    Host: 192.168.0.103:8096
    User-Agent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:22.1472 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 1ms. http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml
2016-12-03 18:50:22.6135 Info App: Entry point completed: MediaBrowser.Server.Implementations.Connect.ConnectEntryPoint. Duration: 1.4185358 seconds
2016-12-03 18:50:22.6135 Info App: All entry points have started
2016-12-03 18:50:22.6135 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=69e3dca768c99ea754a7e7178bd2b08b
2016-12-03 18:50:27.6697 Info HttpClient: HttpClientManager GET: http://bot.whatismyipaddress.com
2016-12-03 18:50:28.1010 Info HttpClient: HttpClientManager POST: https://connect.emby.media/service/Servers?id=69e3dca768c99ea754a7e7178bd2b08b
2016-12-03 18:50:28.6494 Info HttpClient: HttpClientManager GET: https://connect.emby.media/service/ServerAuthorizations?serverId=69e3dca768c99ea754a7e7178bd2b08b
2016-12-03 18:50:32.1662 Info HttpServer: HTTP GET http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:32.1662 Info Dlna: No matching device profile found. The default will need to be used.
    Cache-Control: no-cache
    Connection: Close
    Pragma: no-cache
    Accept: text/xml, application/xml
    Host: 192.168.0.103:8096
    User-Agent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:32.1662 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 1ms. http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml
2016-12-03 18:50:42.1854 Info HttpServer: HTTP GET http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:42.1854 Info Dlna: No matching device profile found. The default will need to be used.
    Cache-Control: no-cache
    Connection: Close
    Pragma: no-cache
    Accept: text/xml, application/xml
    Host: 192.168.0.103:8096
    User-Agent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:42.1854 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 1ms. http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml
2016-12-03 18:50:52.2084 Info HttpServer: HTTP GET http://192.168.0.103:8096/dlna/20a3fabeeb408d34b523dc74130b4d53/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-12-03 18:50:52.2084 Info Dlna: No matching device profile found. The default will need to be used.

[Luke 37994]

Hi, welcome @@ron.bali. Some have reported this issue with the current release server. If you would like to try a separate installation of the beta server that would be helpful. Please let me know and i'll give you instructions. thanks !

[ron.bali 5]

Thanks Admin, that gives me a Sunday occupation, and then probably I can finish watching the movie which is White Girl (2016). Oh and extra instructons will be appreciated.

Edited December 4, 2016 by ron.bali

[Luke 37994]

Ok @@ron.bali. What you can do is shutdown the server, then go here:

 

https://github.com/MediaBrowser/Emby/releases

 

Locate the latest beta release, then download the windows zip file contained within. Unzip this to anywhere you like, then go inside and run the mediabrowser.serverapplication.exe file. This will be a completely portable install that will not disrupt your existing installed version. That means you'll have to go through the startup wizard and add a media library. I would suggest just adding a small folder of test videos as a testing library. 

 

Then once you've completed the startup wizard, then you can test the Dlna features. So my intention here is just to have you do some testing and then be able to go back to your existing installation. Thanks.

[ron.bali 5]

So far no luck with 3.1.245-beta.  

 

I installed as you said using just a sub-folder of the full media library.  As before access from Android phone/tablet/TV is OK, but it does not appear on either of the LG TVs or the Panasonic Viera TV.  I have re-started the Emby server, re-started Windows 10, switched the TVs off and on, but no luck.

 

Here is a bit of the log where DLNA errors are mentioned.

 

2016-12-04 15:17:01.9877 Info HttpServer: HTTP GET http://localhost:8096/favicon.ico. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
2016-12-04 15:17:01.9877 Error HttpServer: Error processing request
    *** Error Report ***
    Version: 3.1.245.0
    Command line: C:\Temp\Emby\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.2.9200.0
    64-Bit OS: True
    64-Bit Process: True
    Processor count: 8
    Program data path: C:\Temp\Emby
    Application directory: C:\Temp\Emby\System
    System.IO.FileNotFoundException: Unable to find the specified file.
    System.IO.FileNotFoundException
    No Stack Trace Available
    
2016-12-04 15:17:01.9877 Info HttpServer: HTTP Response 404 to ::1. Time: 6ms. http://localhost:8096/favicon.ico
2016-12-04 15:18:23.9410 Info HttpServer: HTTP GET http://10.22.18.113:8096/dlna/4adf22bd15e44af5b7202f395eda7787/description.xml. UserAgent:
2016-12-04 15:18:23.9550 Info Dlna: No matching device profile found. The default will need to be used.
    Host: 10.22.18.113:8096
    Connection: close
2016-12-04 15:18:23.9720 Info HttpServer: HTTP Response 200 to 10.22.18.113. Time: 31ms. http://10.22.18.113:8096/dlna/4adf22bd15e44af5b7202f395eda7787/description.xml
2016-12-04 15:19:31.1348 Info App: Udp message sent to 192.168.0.92:37805
2016-12-04 15:19:31.1348 Info App: Udp message sent to 192.168.0.92:37805
2016-12-04 15:19:32.9118 Error App: Error receiving udp message
    *** Error Report ***
    Version: 3.1.245.0
    Command line: C:\Temp\Emby\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.2.9200.0
    64-Bit OS: True
    64-Bit Process: True
    Processor count: 8
    Program data path: C:\Temp\Emby
    Application directory: C:\Temp\Emby\System
    System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
     at System.Net.Sockets.Socket.EndReceiveFrom(IAsyncResult asyncResult, EndPoint& endPoint)
     at Emby.Common.Implementations.Net.UdpSocket.ProcessResponse(IAsyncResult asyncResult)
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at Emby.Server.Implementations.Udp.UdpServer.<StartListening>d__13.MoveNext()
    System.Net.Sockets.SocketException
     at System.Net.Sockets.Socket.EndReceiveFrom(IAsyncResult asyncResult, EndPoint& endPoint)
     at Emby.Common.Implementations.Net.UdpSocket.ProcessResponse(IAsyncResult asyncResult)
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at Emby.Server.Implementations.Udp.UdpServer.<StartListening>d__13.MoveNext()
    
2016-12-04 15:19:33.4227 Info HttpServer: HTTP GET http://192.168.0.103:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.0; ASUS_Z00AD Build/LRX21V)
2016-12-04 15:19:33.5993 Info HttpServer: HTTP Response 200 to 192.168.0.92. Time: 177ms. http://192.168.0.103:8096/emby/system/info/public?format=json
2016-12-04 15:19:33.6293 Info HttpServer: HTTP GET http://192.168.0.103:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.0; ASUS_Z00AD Build/LRX21V)
2016-12-04 15:19:33.6293 Error HttpServer: Error processing request
    *** Error Report ***
    Version: 3.1.245.0
    Command line: C:\Temp\Emby\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.2.9200.0
    64-Bit OS: True
    64-Bit Process: True
    Processor count: 8
    Program data path: C:\Temp\Emby
    Application directory: C:\Temp\Emby\System
    MediaBrowser.Controller.Net.SecurityException: Access token is invalid or expired.
     at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken(IServiceRequest request, String token)
     at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateUser(IServiceRequest request, IAuthenticationAttributes authAttribtues)
     at ServiceStack.ServiceStackHost.ApplyRequestFilters(IRequest req, IResponse res, Object requestDto)
     at ServiceStack.Host.RestHandler.<ProcessRequestAsync>d__19.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__60.MoveNext()
    MediaBrowser.Controller.Net.SecurityException
     at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken(IServiceRequest request, String token)
     at Emby.Server.Implementations.HttpServer.Security.AuthService.ValidateUser(IServiceRequest request, IAuthenticationAttributes authAttribtues)
     at ServiceStack.ServiceStackHost.ApplyRequestFilters(IRequest req, IResponse res, Object requestDto)
     at ServiceStack.Host.RestHandler.<ProcessRequestAsync>d__19.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
     at Emby.Server.Implementations.HttpServer.HttpListenerHost.<RequestHandler>d__60.MoveNext()
    
2016-12-04 15:19:33.6293 Info HttpServer: HTTP Response 401 to 192.168.0.92. Time: 12ms. http://192.168.0.103:8096/emby/system/info?format=json
2016-12-04 15:25:23.9895 Info HttpServer: HTTP GET http://10.22.18.113:8096/dlna/4adf22bd15e44af5b7202f395eda7787/description.xml. UserAgent:
2016-12-04 15:25:23.9895 Info Dlna: No matching device profile found. The default will need to be used.
    Host: 10.22.18.113:8096
    Connection: close
2016-12-04 15:25:23.9895 Info HttpServer: HTTP Response 200 to 10.22.18.113. Time: 1ms. http://10.22.18.113:8096/dlna/4adf22bd15e44af5b7202f395eda7787/description.xml
2016-12-04 15:27:30.3303 Info HttpServer: HTTP GET http://192.168.0.103:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; SM-T715Y Build/MMB29K)
2016-12-04 15:27:30.4929 Info HttpServer: HTTP Response 200 to 192.168.0.90. Time: 163ms. http://192.168.0.103:8096/emby/system/info/public?format=json
2016-12-04 15:28:01.3793 Info HttpServer: HTTP GET http://192.168.0.103:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; SM-T715Y Build/MMB29K)
2016-12-04 15:28:01.3793 Info App: App Activity: app: Emby for Android Mobile, version: 2.8.27, deviceId: d5c61ac98e1eba50, deviceName: SMT715Y
2016-12-04 15:28:01.8189 Info HttpServer: HTTP Response 200 to 192.168.0.90. Time: 440ms. http://192.168.0.103:8096/emby/system/info?format=json
2016-12-04 15:28:02.5051 Info HttpServer: HTTP GET http://192.168.0.103:8096/mediabrowser/users/93909d4b03ec4a09b97c8bb4a3deef12?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; SM-T715Y Build/MMB29K)

[Luke 37994]

@@ron.bali there is a new beta up. Please try that. Thanks !

[ron.bali 5]

Well, good news with 3.1.246-beta.

 

The switched on TVs immediately show up on the server Dahsboard as active devices, and Emby shows up on the TVs as clickable.

 

Movies all play on the LG TVs, while on the Panasonic Viera some play immediately while others take some time then say cannot read file.  Perhaps this is because some play directly while others are trying to transcode and fail.  This is not a problem for me just now as I have an Android TV box connected to the Panasonic and the Emby app on the Android TV works fine.

 

I have looked at the logs and do not see any errors that relate to DLNA.  There are quite a few errors though and one that repeats that puzzled me a bit is "Error getting response from http://192.168.0.1:1900"

 

So, should I switch to using this beta as my everyday Emby Server or should I await your next stable release?

 

Thanks.

[Luke 37994]

Thanks for reporting back. I would suggest staying with stable. The next release should not be too far away now. thanks.