VVEngine can't find source folder - but VV can

[sveneven]

Short explanation of problem: I'm backing up from shares on remote PC's via a server (where VV runs) to a connected NAS. This works when I run the VV profile - but NOT when I schedule that exact profile in VVengine. I then get the error 'Source folder not found'.

The shares are mappe dusing a dedicated user account - but again, it works in VV. I have tried to 'Run as' that other user, I have tried to run VVengine as a service - but no.

I was wondering - how does VVengine work in detail? Does it call VV, or is all the executable code inside the VVengine.exe? (Don't really know if this matters either...).
Why is there a difference in access rights?

This seems to be selectively a problem of the network mapped folders.

[TGRMN Software]

Hi, you need to remap the drive in the ViceVersa profile settings, as VVEngine might run with different elevation mode compared to ViceVersa and/or different user.

ViceVersa PRO version 3 or newer supports mapping drives in the profile settings.

Or you could use the UNC paths, please see:
https://www.tgrmn.com/web/kb/item93.htm
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Alice]

Hi, now by chance a very similar issue happened to me today. VV 3.0 on a client PC (Windows 7) worked faultlessly with a Profile, copy the same Profile to a Windows Server 2008 R2 SP1 and I received the 'Source not Found' message in both VV (3.0) and VVE (2.2 Server Premium) when run there.

key to success was to make two changes :

1 - Use the IP Address of the 'Source' server, not the Server Name under the option [ 'Network' ] / [ 'Connect using the following credentials' ], so I entered :