Target folder not found

BL · Guest

We have ViceVersa running on multiple servers. For some reason on one server all jobs fail with "Target folder not found." I have tried every combination of \\?\\ I can think of and tried mapping by path, IP, or drive letter but it always fails.

BL · Guest

OK, I changed the destination to just plain \\server\share\folder and it worked but all other ViceVersa installs on multiple other servers have \\?\Z:\folder as the path. Why are they working and this one is not?

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

Hi, this could be an access issue to the mapped drive for this server:
https://www.tgrmn.com/web/kb/item141.htm
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

BL · Guest

I don't think that is it. The link you suggested says "there could be an issue accessing mapped drives, if they were mapped under a standard user account." But they were mapped by the same domain admin account hat is running ViceVersa. Also, no other server has the registry key set that is suggested in https://www.tgrmn.com/web/kb/item141.htm and they are all set to "Connect using default user's credentials.

BL · Guest

It must have something to do with the VVScheduler because if I run Compare and Execute from the profile screen it works.

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

Under which account is the ViceVersa task in the VVScheduler running?

Does it work if you run the profile from ViceVersa after starting ViceVersa "elevated" e.g. with "Run as Administrator"?

If you are able to send the profile log to support via e-mail, we can review it.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

Alice · Joined: 29 Jan 2015 Posts: 283

Maybe the VVScheduler/Profile and the account that's logged in to the server are both trying to map to the Target ? If so you might get a message (or a log file entry) similar to the below :

2024-04-04 10:34:40 :

Connecting to \\server-01\export with user "SVC-Admin" ... \\server-01\export is not accessible using the credentials entered in the profile settings. 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.

so the user that is logged in to the Source Server already has a mapped drive to the Target, then the VV Job tries to map to the same location but with a different account (?)

Doubtless there's lots of solutions to clear the mappings ('net use'), but when this happens for me I just restart the server to fix (note I'm using VVEngine 3.0 running as a 'service' on Windows Server 2019).