Before posting, and to avoid disappointment, please read the following:

  • This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
  • If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.

Network does not attempt reconnect, gives invalid path error

SyncBackFree is the freeware version of SyncBack. It is *not* an evaluation version of SyncBackPro/SE.
Post Reply
Posts: 2
Joined: Sat Sep 17, 2016 2:13 pm

Network does not attempt reconnect, gives invalid path error

Post by OceanBagel »


I'm running a backup profile from my local hard drive to a network location over a VPN connection. The problem is that this VPN connection occasionally drops connectivity. When the network drops, I'd expect the profile to use up all its reconnect attempts before skipping files, but it only goes through a single reconnect attempt. I have the MaxNetowrkRecons variable currently set to 99999, but it only goes through attempt 1 of 99999 before failing. In the log, every skipped file shows "The specified path is invalid" as the reason for failure. Is there a way to force the profile to keep trying to reconnect, rather than skip these files?

I'm using SyncBackFree v7.6.28.0 on a Windows 10 64-bit machine.
2BrightSparks Staff
2BrightSparks Staff
Posts: 992
Joined: Mon Apr 13, 2015 6:22 am

Re: Network does not attempt reconnect, gives invalid path error

Post by Swapna »


SyncBackFree didn’t attempt to reconnect as the connection to your network (Network Access Server) was still ‘up’ and connected. It’s only the VPN connection was lost when it dropped intermittently. SyncBack itself isn’t aware you are connected to the remote-side via VPN, and thus will not be able to tell if your VPN connection is lost. As far as SyncBack is concerned, it’s only aware that the main network connection is still ‘up’, and therefore, no reconnection attempts was made.

Although the main network connection is still connected, SyncBack couldn’t communicate with your remote side to read/copy data (as the VPN connection was dropped), thus it failed with the error “The specified path is invalid”.

Sorry, there is not much we can do from SyncBack to resolve this issue. However, you could check if it is possible to try reconnecting using your VPN software when the VPN connection was dropped. Or you can try waiting until off-peak hours when the VPN software is better able to maintain a stable connection.

Thank you.
Post Reply