Author |
Message |
hyounker
Joined: 19 Feb 2018 Posts: 3
|
Posted: Mon Feb 19, 2018 8:43 pm Post subject: "Source Target Not Found" VVScheduler Windows 10 |
|
|
Doing a search for this problem brings 100s of results that have absolutely nothing to do with the problem. In addition, the few topics I've found that address this error are never completed to a fix.
I am running:
ViceVersa PRO 2.5 Build 2518
VVScheduler 2.1.0.0
Windows 10 Version 1709 OS Build 16299.248
The profile performs a Replication of one large folder that contains many smaller folders. The source is located in another city with access provided via VPN. The target is a SATA hard drive connected locally via USB.
The profile is scheduled to run once a day at 6pm in VVScheduler.
Running the profile via ViceVersa PRO is always successful.
Running the profile via the "Run Task" button in VVScheduler is always successful.
However, the profile fails nearly every day with the subject error when running as scheduled at 6pm. Occasionally, it will work. This scheduled task was created in early January and worked until approximately February 5th. I cannot find any correlation of dates versus changes of any kind.
The computer hosting ViceVersa PRO and VVScheduler is rarely used for anything else.
Can you please help?
Thanks,
hyounker |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8763
|
|
Back to top |
|
|
Guest
|
Posted: Tue Feb 20, 2018 11:36 am Post subject: |
|
|
Neither of these are the problem. Again, it works fine when I hit the "Run Task" button in VVScheduler.
Source: \\192.168.0.100\E\Images\2018\Q1\
Target: E:\Q1\
Again, this worked for about a month. |
|
Back to top |
|
|
hyounker
Joined: 19 Feb 2018 Posts: 3
|
Posted: Tue Feb 20, 2018 11:49 am Post subject: |
|
|
I didn't realize that I was not logged in for that last post. That was me.
Also, because you mentioned it, I downloaded ViceVersa PRO 3.0. Now it's telling me that I need to purchase another license? |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8763
|
Posted: Wed Feb 21, 2018 1:25 am Post subject: |
|
|
Hi, I think it's an issue with accessibility to \\192.168.0.100\E\Images\2018\Q1\
Re version 3, you are able to reinstall version 2.5 if you prefer.
thanks _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
hyounker
Joined: 19 Feb 2018 Posts: 3
|
Posted: Thu Feb 22, 2018 8:24 pm Post subject: |
|
|
Every other method of connecting to that drive is successful. As a matter of fact, I waited to get the email with the failure report, then immediately started VVScheduler and hit "Run Task". Worked perfectly. You have a bug, or something here.
Is there a log file that would help?
Or, rather than upgrading, maybe I should ask about a refund. |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8763
|
|
Back to top |
|
|
johnf@forbin.com Guest
|
Posted: Tue Feb 27, 2018 2:03 pm Post subject: |
|
|
There was a recent change with Windows 10 1709 and Server 2016 that tightened security accessing SMB2 guest shares. What used to be ok now fails.
Here is the relevant info:
check out this site: support.microsoft.com/de-ch/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016
I ran into this on a customer's network where they had a third party machine/service that was not joined to the domain but had a public shared folder that needed to be written to. The 1709 Upgrade caused this share to fail all the time until I patched the registry as specified.
Hope this helps.
John |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8763
|
|
Back to top |
|
|
|