VVLauncher not able to connect to remote destination folder

[krist9]

Hi,

We are having an intermittent issue where VVLauncher is not able to access the target folder. The vv log error is as below (I have removed the share name)
2014-07-22 01:02:29 : Checking target \\<share name>\ ...
2014-07-22 01:04:11 : [ERROR] \\<sharename>\*.* : The specified network name is no longer available.
2014-07-22 01:04:11 : Total found: 1
2014-07-22 01:04:11 : [ERROR] Error scanning target folder.
2014-07-22 01:04:11 : Aborted.
2014-07-22 01:04:11 : Exit Code: 2. Execution not completed. [ERROR]

We have got the network team confirming that there is no issue from the connectivity side. Have got both source and destination server support confirm the ports are ports are open and tracert is working as expected and folder permissions are intact. Another instance of VV in a different server is syncing up with the same destination server without issue. It is only a problem with this particular pair of source and destination. We have now run out of options to troubleshoot this. Please let me know what could be causing this.

[krist9]

Please note that this is an intermittent issue that get auto resolved after a few hours.

[TGRMN Software]

Hi, it sounds like a network connectivity issue....
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[SimplyJLH]

[krist9]

For my case, even the manual run is n't working as it can't compare the target folder. To make it worse, the syncing stops when the target folder has 204 files, the magic no., again not always but more times to definitely suggest this is not some random occurrence.

We have done a wide range of investigation on this issue involving the Network team (bandwidth, connectivity) and server support team (port 445, permissions, CPU& Memory utilization ). All such investigation suggests no issue in any of these areas.

Also noticed a trend where issue has started occurring at 2:30 PM server time and auto resolves by around 5 AM server time the next day. Again these are not consistent figures, but they do tend to follow this pattern more times than otherwise.

This friday when the issue occurred at 2:30PM, I stopped and disabled the VVLauncher from system tray, manually copied over the files from source to target, reset the tracking DB and then enable -> Run Now. This has somehow seemed to resolve the issue. Not sure if this has got something to do with resetting Tracking DB. Because I had already tried stopping/disabling the VVLauncher and re-enabling it. I had even tried uninstalling and reinstalling the VVLauncher service using InstServ.

I tried but I have no clue how to open tracking DB to see if i get some pointers.

Does uninstalling the software completely and then reinstalling help?

[TGRMN Software]

Can you try VVEngine instead ?
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[SimplyJLH]

Does VVEngine hand off to Task Scheduler?

I was able to resolve my VVScheduler problem by using the UNC for each network device (huge pain...) instead of the "mapped" device designation. Using the mapped names is much quicker and easier.

[TGRMN Software]

VVEngine does not rely on the Windows Task Scheduler, however it would have the same issue with mapped drives.

The reason is that when you mapped a drive in Windows, it is mapped for that one account only, and since Windows Vista, only mapped for that account elevation status. http://stackoverflow.com/questions/1267085/vista-uac-trouble-mapping-network-drives

When VVEngine and / or VVScheduler run under different accounts they then can't see the mapped drives and UNC must be used instead.

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

[SimplyJLH]

Thanks for the clarification as to the why. Before 8.1 I had the same user account name on ll of my PC's and MAC. With Windows 8 and the new PC the initial startup of the system makes you (me anyway) think the user name had to be an email address. As I investigated after my setup I saw that I could have used a normal account name. Oh well....
Thanks again.

[krist9]

Hi,

We cannot download VVEngine as this requires business approval and is a lenghty process.

Can you answer into below queries for me please ?
is there limitation to the no of file /minutes or folders to sync up for vice versa tool
if yes , can we increase that value
if yes, can you please let us know the settings where excatly
NOTE: we have since recent past 2 weeks more number of files to be synced and we are having the issue since then.
THanks.

[TGRMN Software]

Hi, there is no limitation to the number of file /minutes or folders to sync up.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[TGRMN Software]

Hello,

ViceVersa/VVLauncher are merely reporting what Windows has told them, that the remote end is no longer available, which can be a pain to debug.

Do you maybe have an anti-virus software on source or target that is blocking file / folder access?

Are the NIC cards OK?

This could be also related to TCP Chimney Offload, Receive Side Scaling, or Network Direct Memory Access, see more info here:
http://support.microsoft.com/kb/951037

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

[TGRMN Software]

Update: it turned out that the culprit was not VVLauncher/ViceVersa. Customer tested a different target server while the issue was there in the existing one and the test was successful. After having applied some network everything is now working fine. Probably something to do with network end.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com