Jump to content

Unhandled exception after installing 3.0.5713.4


mozez314

Recommended Posts

mozez314

After auto-upgrading from 3.0.5713.3 to .4 yesterday, I now get the following error on server startup.

 

(from the "unhandled" log)

 

Object reference not set to an instance of an object.
System.NullReferenceException
   at MediaBrowser.Server.Implementations.LiveTv.EmbyTV.EntryPoint.<Run>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__5(Object state)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

 

Full logs attached.

 

 

 

server-63576362093.txt

unhandled_8a8aad5c-c70b-4325-affc-a53a43fbf660.txt

Link to comment
Share on other sites

there are some fundamental problems there. i would try reinstalling the current beta on top of your existing install.

Link to comment
Share on other sites

JustEric78

I am having the same issue after installing the latest stable version and then installing the beta version as recommended. 

 

Correction: I get the same error on versions 5675.1 as well as beta 5713.5. I have tried to uninstall first then reinstall with the same problem.

server-63576388129.txt

unhandled_7c9779eb-a1b6-4965-ad90-c2e17aa81ac0.txt

Edited by JustEric78
Link to comment
Share on other sites

Happy2Play

I am having the same issue after installing the latest stable version and then installing the beta version as recommended. 

 

Correction: I get the same error on versions 5675.1 as well as beta 5713.5. I have tried to uninstall first then reinstall with the same problem.

Your is and issue with MBPlus.ServerEntryPoint were OP has and issue with LiveTv.EmbyTV.EntryPoint.

Edited by Happy2Play
Link to comment
Share on other sites

JustEric78

Your is and issue with MBPlus.ServerEntryPoint were OP has and issue with LiveTv.EmbyTV.EntryPoint.

So do I have to manually remove MBPlus to fix the problem? Obviously it tries to start the add-on then stops the service completely. I assume I am going to have to wait for them to find a fix before I can move forward. 

Link to comment
Share on other sites

mozez314

Installing the stable version over the top and THEN installing the latest beta version does seem to have done the trick for me. Just reinstalling the beta didn't.

Link to comment
Share on other sites

So do I have to manually remove MBPlus to fix the problem? Obviously it tries to start the add-on then stops the service completely. I assume I am going to have to wait for them to find a fix before I can move forward. 

 

No, your problem actually has nothing to do with that plug-in.  Here is the real problem:

2015-08-28 19:48:53.1196 Error - ServerManager: The http server is unable to start due to a Socket error. This can occasionally happen when the operating system takes longer than usual to release the IP bindings from the previous session. This can take up to five minutes. Please try waiting or rebooting the system.

Re-starting the whole server machine probably fixed it, huh?   The above can happen if there is a stranded ffmpeg process stuck running.

  • Like 1
Link to comment
Share on other sites

JustEric78

No, your problem actually has nothing to do with that plug-in.  Here is the real problem:

2015-08-28 19:48:53.1196 Error - ServerManager: The http server is unable to start due to a Socket error. This can occasionally happen when the operating system takes longer than usual to release the IP bindings from the previous session. This can take up to five minutes. Please try waiting or rebooting the system.

Re-starting the whole server machine probably fixed it, huh?   The above can happen if there is a stranded ffmpeg process stuck running.

 

Normally that is the first thing I try, thank you that resolved it. 

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...