ViceVersa Pro runs OK VVEngine cant connect to UNC source

Grizzlie · Joined: 05 Apr 2008 Posts: 8

Using ViceversaPro to do a Backup from a UNC path.
ViceVersaPro has credentials for connecting to remote source file and Netwrok connection test completes OK.
Compare and Execute work fine.
But VVEngine fails because it cannot access the remote files.
[ERROR] "\\192.168.1.5" 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..

Surely VVEngine should get it's information from ViceVersaPro?

Cant figure out what is wrong.

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

Is VVEngine running as a service? This message usually is given by Windows when a user is already connected to a network drive and then tries to connect as a different user. If you use the command NET USE in a CMD window you should be able to get a list of current existing connections.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

Grizzlie · Joined: 05 Apr 2008 Posts: 8

Yes VVEngine is running as a service.
Firly certain that no drives have been mapped, but will certainly try and check with Net Use.
Unfortunately cannot get back on to the PC until middle of next week.

Thanks

Grizzlie · Joined: 05 Apr 2008 Posts: 8

OK the problem was that the Account on the PC the VVEngine Service was using was the same username and passowrd that ViceVersaPro used to access the netwok login on the remote PC.
Changed the VVEngine Service logine to the Administrator Account and it no longer fails at that point.

However it does still fail, now fails with [ERROR] Failed creating log file "C:\Documents and Settings\All Users\Application Data\ViceVersa PRO 2\log1.log": task aborted

There doesnt seem to be any security issues with that path.

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

Can you try deleting the file log1.log if already existing or change its location to another folder? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

Grizzlie · Joined: 05 Apr 2008 Posts: 8

Thanks for the reply.

I did make changes to the log file path before receiving your reply, as well as making some adjustments to the log file settings, and that does appear to have resolved the issue.

I did wonder if the log file had reached the default limit size but that did not appear to be the case. So I do not know what caused the problem.

Anyway as I said it now all appears to be working.

Thanks again