Java Exception Error after Update

[simoncn]

(12-12-2017 00:24)Tell Wrote:  I just poked install on Minimwatch to get to the point where it stopped working. Probably I moved beyond 111 to 112 before I found it wasn't working. I know I did the upgrade on Sunday but didn't test it, today was when I found it wasn't working. Hence I had to remove 112 rather than 111. Now it's working and offering me 112, which I guess is now sorted.

Thanks on advice on the other one.

All this makes sense. It should be fine to install 112 now.

[Tell]

(12-12-2017 06:51)simoncn Wrote:  

(12-12-2017 00:24)Tell Wrote:  I just poked install on Minimwatch to get to the point where it stopped working. Probably I moved beyond 111 to 112 before I found it wasn't working. I know I did the upgrade on Sunday but didn't test it, today was when I found it wasn't working. Hence I had to remove 112 rather than 111. Now it's working and offering me 112, which I guess is now sorted.

Thanks on advice on the other one.

All this makes sense. It should be fine to install 112 now.

Yes thanks Simon. I did the update to 112 before I went to bed and it took it fine.

[Mr Frog]

(11-12-2017 19:02)Mr Frog Wrote:  

(10-12-2017 19:23)simoncn Wrote:  

(10-12-2017 18:58)Mr Frog Wrote:  I tried the stop/start method from within the QNAP App Centre, many times - but to no avail.

However, leaving it 'stopped' for several hours and then restarting, did the trick!

Thank you for all your support

I don't know why leaving it stopped for a longer time would make a difference but I am glad that it is working now.

I don't know why leaving it stopped for a longer time would make a difference but I am glad that it is working now.

Oh dear ... just installed the latest 112 and the same issue has arisen (greyed out icon etc)

I tried the start/stop within QNAP App Centre ... but unfortunately this doesn't seem to work with 112.

Please can you help
[/quote]

Just installed version 113 and it all updated without any issues whatsoever (as was always the case before 111 and 112).

Seems like the issue is now fixed.

Awesome and thank you for all your support ... very much appreciated.