2019: Problems initiating a scheduled copy job using WebDrive

2019: Problems initiating a scheduled copy job using WebDrive

Problem: I have created a batch file to run a copy job between a FTP site via WebDrive and a local hard drive. When I ran it locally, everything works just fine. However, when the batch file is initialized through a job scheduler, the mapped WebDrive is considered an invalid drive specification. Is there a solution or work around for this?

Answer: You'll need to set up the Scheduled Job so that it runs under the context of a user account that has defined the WebDrive sites. Also, in your batch file, add a line at the beginning to manually map the WebDrive.

There is a section in the WebDrive Help File outlining batch files and manually mapping drives from the command line.

    • Related Articles

    • 2019: Moving or Changing a WebDrive License to a New or Different Computer

      How can I move WebDrive to a new machine? Use the Export feature in WebDrive to export your Site Database and User Settings out to a .reg file. Run WebDrive, then from the main menu, select FILE -> EXPORT and export your data out to a file. Copy that ...

    • 2019: How do I use SyncBackSE to schedule a backup job to a WebDrive drive?

      When using the SyncBackSE scheduler you need to configure the job in SyncBackSE to run under the same NT user account that you created your WebDrive site profile in. Make sure you enter a password as well as this is required for the Windows ...

    • Where can I find pricing/cost information for WebDrive?

      You can find pricing information for WebDrive products here: WebDrive Pricing and Purchasing

    • What are the system requirements for WebDrive?

      Windows Mac WebDrive is supported on the 64-bit editions of Windows. Windows 11 Windows 10 Windows 8 Windows Server 2019 Windows Server 2016 R2 editions Windows Server 2016, all editions Windows Server 2012-R2 editions Windows Server 2012, all ...

    • WebDAV Timestamps

      WebDAV Timestamp WebDAV servers don't typically allow clients to set a files modified time on the server so WebDrive uses a work around to provide a way to store a files modified time using custom DAV properties. This is how WebDrive will determine ...