MinimServer Forum
MinimWatch Problem - Printable Version

+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: MinimWatch Problem (/showthread.php?tid=711)



MinimWatch Problem - Wammer - 27-07-2013 18:05

I run MinimServer on a QNAP TS219PII controlled via MinimWatch on my iMac. MinimWatch has developed a problem. The Minim symbol still appears in the right side of the Menu Bar, but when I click on it the drop-down menu does not open, the icon's background simply turns blue. Obviously, this means I cannot update or amend MinimServer in any way.

I noticed the problem when I decided to check MinimServer after updating the QNAP's firmware from 3.7.3 to 4.0.1. However I have not run MinimWatch for some time so I cannot know whether it was working before I upgraded the firmware.

Furthermore, I have an installation of MinimServer on my iMac which is pointed at a "mirror' copy of my music collection on a hard drive attached to my iMac (I don't normally have it running, it is there as a fall-back if the QNAP fails). When I ran this version of MinimServer today I got the same problem - no menu, just an icon with a blue background. Since both the app and the database are on my iMac I don't see how this can have anything to do with the QNAP firmware upgrade - which suggests to me that the problem with MinimWatch may not have either.

Any ideas?


RE: MinimWatch Problem - simoncn - 27-07-2013 19:47

(27-07-2013 18:05)Wammer Wrote:  I run MinimServer on a QNAP TS219PII controlled via MinimWatch on my iMac. MinimWatch has developed a problem. The Minim symbol still appears in the right side of the Menu Bar, but when I click on it the drop-down menu does not open, the icon's background simply turns blue. Obviously, this means I cannot update or amend MinimServer in any way.

I noticed the problem when I decided to check MinimServer after updating the QNAP's firmware from 3.7.3 to 4.0.1. However I have not run MinimWatch for some time so I cannot know whether it was working before I upgraded the firmware.

Furthermore, I have an installation of MinimServer on my iMac which is pointed at a "mirror' copy of my music collection on a hard drive attached to my iMac (I don't normally have it running, it is there as a fall-back if the QNAP fails). When I ran this version of MinimServer today I got the same problem - no menu, just an icon with a blue background. Since both the app and the database are on my iMac I don't see how this can have anything to do with the QNAP firmware upgrade - which suggests to me that the problem with MinimWatch may not have either.

Any ideas?

This is a known problem caused by a faulty Java update from Apple. Please see this post for a solution.


RE: MinimWatch Problem - Wammer - 27-07-2013 20:28

(27-07-2013 19:47)simoncn Wrote:  
(27-07-2013 18:05)Wammer Wrote:  I run MinimServer on a QNAP TS219PII controlled via MinimWatch on my iMac. MinimWatch has developed a problem. The Minim symbol still appears in the right side of the Menu Bar, but when I click on it the drop-down menu does not open, the icon's background simply turns blue. Obviously, this means I cannot update or amend MinimServer in any way.

I noticed the problem when I decided to check MinimServer after updating the QNAP's firmware from 3.7.3 to 4.0.1. However I have not run MinimWatch for some time so I cannot know whether it was working before I upgraded the firmware.

Furthermore, I have an installation of MinimServer on my iMac which is pointed at a "mirror' copy of my music collection on a hard drive attached to my iMac (I don't normally have it running, it is there as a fall-back if the QNAP fails). When I ran this version of MinimServer today I got the same problem - no menu, just an icon with a blue background. Since both the app and the database are on my iMac I don't see how this can have anything to do with the QNAP firmware upgrade - which suggests to me that the problem with MinimWatch may not have either.

Any ideas?

This is a known problem caused by a faulty Java update from Apple. Please see this post for a solution.

Thanks, Simon. Both seem to be working OK now.