Minimserver crashes after updating to 0.8.3

[Spark58]

Error: unexpected exception java.lang.NullPointerException

I got this error (end red minimwatch icon) after upgrading Minimserver 0.8.2 to 0.8.3 strictly according to the installation instruction ("Updating MinimServer and Java").

My Setup: Minimserver running on QNAP TS-219P+, firmware: 4.1.1, Minimwatch running on laptop, Win 8.1

Before the current update I was running Minimserver version installed before June 2014 major changes to the MinimServer and Java packages for QNAP.

I succesfully concluded the update process (to Minimserver 0.8.3 and JRE_ARM 8.6.0) but failed to complete restarting the new version of Minimserver - the restarting process take few minutes and the red icon appears with error description: 'unexpected exception java.lang.NullPointerException'.

Attached is the last part of the MinimServer log file.

Please advise how to solve the problem

[simoncn]

(21-12-2014 22:53)Spark58 Wrote:  Error: unexpected exception java.lang.NullPointerException

I got this error (end red minimwatch icon) after upgrading Minimserver 0.8.2 to 0.8.3 strictly according to the installation instruction ("Updating MinimServer and Java").

Thanks for letting me know about this. This problem will be fixed in the next update. As a temporary workaround, you can add

Album.sortTags={Album, Artist}

to the tagOptions property.

[stampie]

(21-12-2014 23:41)simoncn Wrote:  

(21-12-2014 22:53)Spark58 Wrote:  Error: unexpected exception java.lang.NullPointerException

I got this error (end red minimwatch icon) after upgrading Minimserver 0.8.2 to 0.8.3 strictly according to the installation instruction ("Updating MinimServer and Java").

Thanks for letting me know about this. This problem will be fixed in the next update. As a temporary workaround, you can add

Album.sortTags={Album, Artist}

to the tagOptions property.

I also have this error, and can confirm the workaround enables Minimserver to start correctly.

regards
Nick

[simoncn]

(21-12-2014 23:41)simoncn Wrote:  Thanks for letting me know about this. This problem will be fixed in the next update. As a temporary workaround, you can add

Album.sortTags={Album, Artist}

to the tagOptions property.

This problem is now fixed in update 53.

[Spark58]

(23-12-2014 22:35)simoncn Wrote:  

(21-12-2014 23:41)simoncn Wrote:  Thanks for letting me know about this. This problem will be fixed in the next update. As a temporary workaround, you can add

Album.sortTags={Album, Artist}

to the tagOptions property.

This problem is now fixed in update 53.

Simon,
Many thanks! As usual great and quick support.