Source/Target folders not found

cschleter · Joined: 02 Aug 2020 Posts: 7

Running VVPro 3 on profiles with network sources or targets in scheduled mode (using Windows Scheduler) was working well until I installed Win10 2004. Once 2004 was installed, these tasks did not run at all - the old Source/Target not found issue. Now I can run any of my profiles manually from the UI but they will not run at all from Windows Scheduler or VVEngine.

With one (syncing my desktop and laptop - laptop is the source) I get "Source Folder not Found". With the other (backing up my desktop to my NAS - desktop is, obviously, the source) I get "Target Folder not Found". The credentials for both the laptop and NAS are obviously correct since the profiles run under the UI. In fact, I just re-entered them to be sure they were correct.

I have spent several hours trying different solutions but none of them work and I have no idea what to do next.

Any suggestions (please be specific) would be helpful.

Thanks in advance.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Hello, does this article help?

https://www.tgrmn.com/web/kb/item141.htm

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

cschleter · Joined: 02 Aug 2020 Posts: 7

No. I am not using mapped drives. I have specified the IP address of the network resources used in each profile.

If I am at the computer, the profiles will run under VVEngine (either manually or by changing the schedule to a time close to the current time) but will not run unattended at night. I reboot my desktop every night and the sync/backup jobs run a couple of hours later. If I reboot the system and manually run the profiles immediately from VVEngine, they both run.

Another thought just occurred to me. When running unattended in the middle of the night, the network drives may be in hibernation mode. Could that be causing the problem? I have changed the hibernation trigger time on the NAS from 2 hours to 4 hours and have turned hibernation off on the laptop. I'll see tonight if anything changes.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Hi, that could be an issue if the drives do not "wake-up" when the profiles run.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

cschleter · Joined: 02 Aug 2020 Posts: 7

A bit of further information:

I disabled my desktop's automatic reboot for several days and both jobs ran fine from VVEngine unattended at night. Yesterday I manually rebooted the desktop and neither job ran last night yet both ran from the UI this morning.

Given that I am not mapping drives, what is it about rebooting that makes the jobs fail when run unattended from VVEngine but not when they are run from the command line? I'm kind of running out of ideas here.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Sounds like the connection is not automatically re-established by Windows after reboot... what action do you take after reboot to make the connection work again? e.g. do you need to click on the drive in File Explorer for example?

cschleter · Joined: 02 Aug 2020 Posts: 7

I'm not sure what changed overnight but I can't get either profile to run from VVEngine this morning, even after using the computer for an hour and running both profiles from the UI (they both ran fine - they ALWAYS run from the UI).

To test further, I just rebooted the computer. Without doing anything else, I can open Windows Explorer and open both drives (as mapped drives, from the share name or from the IP address) so I am pretty sure the drives are, in fact, connected.

Unless we can find the root cause of this, I guess I am just going to have to take the 30-45 minutes every night before I go to bed to run the jobs manually which is not going to make me very happy.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

So now the profiles always give an error that folder paths not found on the network?

cschleter · Joined: 02 Aug 2020 Posts: 7

They wouldn't run at all from VVEngine this morning but tonight they both ran normally. I'm stumped.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Do you have the credentials entered in the ViceVersa profile settings for the NAS and the laptop in profile settings ->folders->network?
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

cschleter · Joined: 02 Aug 2020 Posts: 7

No since there are multiple paths in each profile (multiple folders on the laptop syncing to the desktop and multiple folders on the desktop being backed up to the NAS - there are some excluded subfolders in each profile). Since I can't find any documentation on exactly how to set the network paths to handle this, I was just using Connect using default user's credentials. I would really rather not have to set up a profile for each of the mapped folders...

Here are the source and target lines from the profiles:

Sync
; ******* Source
Source Folder=\\192.168.0.106\Laptop D\__Data\ | \\192.168.0.106\Laptop C\Users\Chris\Documents\ | \\192.168.0.106\Laptop C\ProgramData\Rosetta Stone\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Dilbert-Garfield\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Ads\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Flickr\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Pinterest\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Instagram\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Flickr New\ | \\192.168.0.106\Laptop C\Users\Chris\Pictures\Misc\ | \\192.168.0.106\Laptop C\Users\Chris\Videos\XVid\
; ******* Target
Target Folder=D:\__Data\ | C:\Users\Chris\Documents\ | C:\ProgramData\Rosetta Stone\ | L:\Graphics\Dilbert-Garfield\ | L:\Graphics\Ads\ | L:\Graphics\Flickr\ | L:\Graphics\Pinterest\ | L:\Graphics\Instagram\ | L:\Graphics\Flickr New\ | L:\Graphics\Misc\ | L:\Graphics\Videos\

Backup (L is a local USB drive)
; ******* Source
Source Folder=D:\__Data\ | L:\Graphics\Ads\ | L:\Graphics\Dilbert-Garfield\ | L:\Graphics\Instagram\ | L:\Graphics\Videos\
; ******* Target
Target Folder=\\192.168.0.59\NAS\K_Drive\Desktop_Backup\D_Data\ | \\192.168.0.59\NAS\K_Drive\Desktop_Backup\L\Graphics\Ads\ | \\192.168.0.59\NAS\K_Drive\Desktop_Backup\L\Graphics\Dilbert-Garfield\ | \\192.168.0.59\NAS\K_Drive\Desktop_Backup\L\Graphics\Instagram\ | \\192.168.0.59\NAS\K_Drive\Desktop_Backup\L\Graphics\Videos\

If you can tell me exactly how to set up the paths, I'll be happy to try it.

Thanks

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Use the same info as you would map a drive (with net use or in Windows File Explorer).

Path: \\192.168.0.106\Laptop C\
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

cschleter · Joined: 02 Aug 2020 Posts: 7

I tried that but I got invalid credentials, which I know is wrong since I used the same credentials to map the drive.

What I found was if I move the reboot to occur after all VV profiles run, they all run correctly every night. Still not sure why but at least it seems to be working.