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.

Unable to scan source

For technical support visit
Post Reply
Posts: 9
Joined: Thu Nov 24, 2016 9:38 pm

Unable to scan source

Post by mouse »

using Synchback SE V8 on Win 7/64 bit -
I am running a job manually that under one profile has 4 jobs attached (3 of these jobs looking at specified folders on a network drive and one on an internal drive as the source). When I wanted to check on the relevant sub-folders that are ticked for the jobs, using modify to see the details in three of the four cases everything is fine but the 4th job comes up with error: "unalbe to scan Source: Multiple connections to a server or shared resource by the same user, using more than one user name are not allowed. Disconnect all previous connections to the server or shared resource and try again".

I am not clear on what this means. Three of the jobs go to the same networked drive named: \\Data1\e\.... and two of these jobs run fine, so I am not sure why the third job going to the same shared source (just different folder) has a problem. Also this was the working set up for months, so not sure what has changed just now.

How would I disconnect all prior connections to the server? I exited Synchback and restarted and also restarted my pc but the outcome is still the same.
Posts: 1020
Joined: Mon Apr 13, 2015 6:22 am

Re: Unable to scan source

Post by Swapna »


Please read this KB article for more details about the error and workarounds to resolve it: ... d-resource

Thank you
Post Reply