Unhanlded Exception

[craigtrombly 0]

Approximately now 2 to 3 times a day, the server is now sending an unhandled exception error from .Net,    

 

"Unhanlded Exception. Object reference not set to an instance of an object:"

 

When this happens and I try to mouse over the software in lower corner in running services, it dissappears and requires restart.  I have not been able to determine any action or what the actions were prior to the error being thrown.  I can say this has never happed not once in any previous build in the last 4 to 5 months and I use the software everyday. 

[Luke 42078]

can you post the server log?

[craigtrombly 0]

I see multiple unhandled errors in the server logs. Let me know if you need more.  This one is the most 2 recent filesserver-63537820369.txtunhandled_65c3696f-ee37-4b52-b040-fc5451089600.txt

[Luke 42078]

Ah, easy fix for @@ebr probably, in autobox sets

[ebr 16184]

First thing you need to do is get rid of all of those auto box sets that are in your movies folder.  Do a search in explorer for "MB Auto Set" and delete them all.  The plug-in no longer creates them in the library like that and that is the reason the logging is going goofy.

 

Deleting all of those should then make auto box sets re-create them in the proper place.

 

This was announced when the plug-in was re-worked but you may not have seen it.

 

A new version of the plug-in won't crash anymore but you really do need to migrate your auto box set stuff to avoid further issues.

[ebr 16184]

@@Luke this is the result of a simple operation like this:

 Logger.ErrorException("Error adding box set member {0}", e, member.Name);

If the Name of that item happens to be null the logger completely chokes.  Can we control this and make that not happen?

 

I have put safety null coalescing on those lines now but that is something one would not think to do normally.

[Luke 42078]

i'm guessing yes, that can probably be trapped in low level logging. But it would have to wait until the next public release.