Jump to content

Theater Classic Exception on start up


claw

Recommended Posts

After the current version of Emby Sever for Windows, 3.0.5934.0, auto updated, Theater Classic throws an unhandled exception.  Theater Crash Log attached.  

 

I downloaded and reinstalled Emby Server but the exception still occurs.   Restarted Windows 8.1 several times.   Emby Server and Theater Classic are both installed on the same PC.

 

Problem signature:
  Problem Event Name:    CLR20r3
  Problem Signature 01:    MediaBrowser.UI.exe
  Problem Signature 02:    3.0.5859.23399
  Problem Signature 03:    569a851f
  Problem Signature 04:    System
  Problem Signature 05:    4.6.81.0
  Problem Signature 06:    5584e6d4
  Problem Signature 07:    2001
  Problem Signature 08:    158
  Problem Signature 09:    MediaBrowser.Model.Net.Http
  OS Version:    6.3.9600.2.0.0.256.48
  Locale ID:    1033
  Additional Information 1:    5861
  Additional Information 2:    5861822e1919d7c014bbb064c64908b2
  Additional Information 3:    a10f
  Additional Information 4:    a10ff7d2bb2516fdc753f9c34fc3b069

 

crash_2c96a3b3-3a69-4900-94ba-381015cea350.txt

Edited by claw
Link to comment
Share on other sites

I resolved the issue.  At the bottom of the crash log there is a connection time out.   The IP address of the PC had changed.   Emby Server was now listening on a different IP.   Edited the servers.json file with the new IP.

 

I have had this issue before, but never did Theater crash.  It just reported that it did not find the server.

Link to comment
Share on other sites

Well done, thanks for the report. As you saw, the old app is mostly resilient to the timeout but there are some situations where it is not.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...