FAQ and Knowledge Base

Main Page > Browse Categories > Solutions to Known Issues > Mapped Network Drives Do Not Work in Scheduled Tasks

Mapped Network Drives Do Not Work in Scheduled Tasks

Mapped network drives do not work in scheduled tasks, unless you explicitly map them before running the task (see note 1 below). Regardless, they may still fail for a number of reasons.

If you plan to schedule a ViceVersa profile to run in VVScheduler, VVLauncher or VVEngine (or on the command line), make sure you use the UNC network path directly in the ViceVersa profile, instead of the mapped drive.

For instance, instead of the mapped drive Y:\ use the UNC path \\ComputerName\Share\

If you need to provide a user / password combination to access \\ComputerName\Share\ , you can enter that information in the ViceVersa profile: profile settings -> folders -> network.

----------------
Note 1:
It is possible to re-map a network drive each time, when ViceVersa starts, by using a custom batch script. See profile settings->advanced settings. However, using the UNC path directly is the easiest solution.

----------------
Note 2:
If you are running VVEngine as a Windows Service, under the LocalSystem account, then the service won't have access to the network at all and using UNC paths will also fail. In this case, set the service to run under the NetworkService account or another account with access to the network. For more information on service accounts see: http://msdn.microsoft.com/en-us/library/ms686005(VS.85).aspx



User Comments
Add Comment
There are no user comments for this topic.
Add Comment
Attachments
No attachments

Did this help you?
Yes No

Statistics
65% found this information useful

Other Options
Printable Version

General Information
No. 93
Author: TGRMN Software

Download ViceVersa


Visit ViceVersa Forum
  
  
 A printable version of the entire ViceVersa FAQ and Knowledge Base is also available.

 For further queries, please contact us by E-Mail at support@tgrmn.com.