MinimServer Forum

Full Version: MinimWatch grey
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I am running minimserver on Windows 2016 core (2PCs, always working very well) but now Minimwatch is grey. I uninstalled / reinstalled minimserver but no change. All network connections are ok. It happened after I tried another transcoder (avconv) and then wanted to go back to the native transcoder. I also modified the ohnet subnet but then changed it again.
So I probably screwed up something but would appreciate some hints on how to proceed.
Thanks you!
Regards Herman.
As you have changed ohnet.subnet (not sure whether you are referring to the MinimServer or MinimWatch setting for this), this is probably the place to start.

When you start MinimWatch, the MinimWatch log (not the MinimServer log) shows the active subnet for MinimWatch. You can view this log by selecting Options > Show log (watch) from the MinimWatch minim icon. What value is this showing and is it what you are expecting?
(20-02-2018 21:29)simoncn Wrote: [ -> ]As you have changed ohnet.subnet (not sure whether you are referring to the MinimServer or MinimWatch setting for this), this is probably the place to start.

When you start MinimWatch, the MinimWatch log (not the MinimServer log) shows the active subnet for MinimWatch. You can view this log by selecting Options > Show log (watch) from the MinimWatch minim icon. What value is this showing and is it what you are expecting?

Minimwatch reports: Active subnet is 192.168.1.0. Minimserver runs on 192.168.1.64 (pings ok from my Minimwatch macbook). I have no firewall on both machines.
OK, let's move on to the next level of debugging.

Try setting the MinimWatch logging level to Debug and stopping and restarting MinimWatch. From the MinimWatch log window, click 'Save as' to save the log file. Zip the log file and attach it to a post here. I will look at the log file to see if there are any clues.
(20-02-2018 21:36)Herman Wrote: [ -> ]
(20-02-2018 21:29)simoncn Wrote: [ -> ]As you have changed ohnet.subnet (not sure whether you are referring to the MinimServer or MinimWatch setting for this), this is probably the place to start.

When you start MinimWatch, the MinimWatch log (not the MinimServer log) shows the active subnet for MinimWatch. You can view this log by selecting Options > Show log (watch) from the MinimWatch minim icon. What value is this showing and is it what you are expecting?

Minimwatch reports: Active subnet is 192.168.1.0. Minimserver runs on 192.168.1.64 (pings ok from my Minimwatch macbook). I have no firewall on both machines.

Fixed: used the command line to get the current value of the subnet, corrected it and it's back now. Thanks for pushing me in the right direction Simon!
Did you change the ohnet.subnet setting for MinimServer? This could cause the problem you are seeing. To check this or to change it back to the correct value, you can use the mscript command.

Edit: looks like our posts crossed and the problem was what I suspected.
Reference URL's