VVLauncher archilles heel ...

[Nimral]

Hi TGRMN,

we use ViceVersa + VVLauncher (Bld. 2500) on some of our servers to synchronize files when they change.

Trying to track a file replication problem with logging enabled I found that, if someone opens the Viceversa GUI, and touches the fsf file, the VVLauncher service seems to sense the "modification" and disable itself internally. If the service is stopped, it does additionally write the line "active=0" into the VVlauncher.ini file, this making the disable permanent and even survive a server boot. This is, in my opinion, ridiculous, if confirmed true by TGRMN, especially when considering that, seen from the Service Control Panel, the VVlauncher seems to be running fine all the time.

I found three ways to re-enable the service: change the flag using a text editor, use the VVlauncher GUI, or re-install ViceVersa, but I don't like any of them much. Is there any way to get rid of that flag, when I restart the VVLauncher service? There is no reason I can think of to keep that flag if the service is restarted, it is just a trap for our less experienced administrators. They often use the GUI to check the replication, and don't realize that every now and then they do, as an unwanted and invisible side effect, deactivate the VVlauncher service. If they notice that something is wrong with the replication, they *always" try to straighten out things by rebooting the server, which doesn't help, of course, sicne the flag is permanently written into the ini file, and never resets.

Is it possible to change the flag back to 1 when the VVlauncher service is restarted? Isn't there any possibility to dynamically reload the fsf instead of setting this rather dumb lock flag? Maybe one of the new builds 2501-2504 changes this behaviour?

Another approach: Is there an alternative to the VVLauncher which does not have such a flag, but is able to run based on the existing fsf file (we put lots of work in creating proper replication profiles for all our servers, I don't like the idea to do this work all over again ...).

We still use build 2500 on Windows Server 2003 Standard Edition SP-2.

Thx

Armin

[TGRMN Software]

Hello,

VVLauncher disables the profile if the profile changes (e.g. it is saved), but not if the profile is opened without modifications.
Does that match your experience?

I recommend that you use VVEngine to run ViceVersa as a service. VVLauncher support for services is quite basic. VVEngine is the most complete service solution, including Event Log notifications and a complete user interface via the browser. See: http://www.tgrmn.com/web/vvengine/vvengine.htm

The profiles in VVEngine still get disabled if they are modified, but it's very easy to check them and re-enable them should that happen.

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com