5 Replies Latest reply on Jun 21, 2013 4:11 PM by howards

    FTP Scheduler stopped working - could not retrieve additional information about remote path errors

    ilauder

      I've had FTP Voyager and FTP Scheduler installed for many years.

       

      On 11/2/2012 the scheduler stopped running nightly backups and now only generates errors when manually executing the jobs.

       

      "Could not retrieve additional information about the local path. Please make sure the path exists and the local user has permissions".

       

      This system has been setup for years and has not changed. The FTP Voyager can manually connect to the profile and I can download files from the server manually without problems.

       

      The only major change to the system were recent FTP software upgrades and patches.

       

      I've double checked the FTP Scheduler Profiles (which never changed passwords in the first place).

       

      I've added a brand new FTP folder with new login password to the server which connects in FTP Voyager, but generates the same errors when manually executing a synch job in FTPV Scheduler.

       

      And I've tried restarting the FTP Voyager Scheduler service and rebooting.

       

      Also nothing has changed on the server and all the files and folders have full read/write access (and can be copied down manually from the FTP Voyager).

       

      Its only when executing the job from within FTP Scheduler that it now fails with these messages and it started around 11/2/12.  But I can't recall on what dates I applied the FTP software patches and upgrades.

        • Re: FTP Scheduler stopped working - could not retrieve additional information about remote path errors
          abdulwahab

          I started using FTPV with ver 16.0.2.0

          And I am facing the same problem with <Sync> action. The <Download> action is working fine.

           

          A bug maybe ?

          • Re: FTP Scheduler stopped working - could not retrieve additional information about remote path errors
            ilauder

            I tried everything I could, double checked every remote and local path and password multiple times, tried creating new tasks, reinstalled FTP Voyager 16 from scratch and setup new tasks and nothing works to get the scheduler to function without errors.

             

            But as soon as I gave up and reinstalled Version 15.2.0.19 reloaded my profiles and setup the scheduler again it works just fine.

             

            So its nothing I am doing wrong, someone fubar'd the Version 16 scheduler.

            • Re: FTP Scheduler stopped working - could not retrieve additional information about remote path errors
              Thomas Parikka

              Hi,

               

              Both the Local and Remote folders MUST exist prior to a Synchronize task for the task to operate successfully - FTP Voyager will not automatically create them. If FTP Voyager Scheduler is running as a system service, it CANNOT access mapped drive letters per Microsoft (see msdn.microsoft.com/en-us/library/ms685143(VS.85).aspx) - instead, you'll need to use UNC paths in conjunction with the directions at Configuring Serv-U and FTP Voyager Scheduler To Access Network Files/Folders to set up access to those UNC paths.

               

              Let us know if this helps!

               

              Thomas Parikka

                • Re: FTP Scheduler stopped working - could not retrieve additional information about remote path errors
                  howards

                  I'm getting this same error when attempting a scheduled sync from godaddy to a local directory when the the task's remote folder name is set to a single slash / or ./ or a single dot .  If I use a subdirectory name such as /_db_backups  it downloads perfectly.  Using FTP Voyager 16.0.2.0.  What should I enter to download the current directory?

                    • Re: FTP Scheduler stopped working - could not retrieve additional information about remote path errors
                      howards

                      Update: This appears to be a conflict between the threads.  If I set workers to 1, it downloads the files completely. No 0 byte files.

                       

                      Previously:

                       

                      In addition to the above problem, even the "successful" sync created 0 byte files almost half the time.  For example, the _db_backups/DATABASE_NAME_09.sql.gz file was 0 bytes due to "550 Can't open _db_backups/DATABASE_NAME_09.sql.gz: No such file or directory".  Other files in the same directory downloaded perfectly.  Average size was 140KB.  There's no reason to believe the failed files were being accessed or written to at the time. Downloading the _09 file manually with FTP Voyager worked fine.

                       

                      The ftp server identifies itself as:

                      220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

                       

                      Here's the log of the _09 file:

                       

                      [03] Fri 21Jun13 15:10:50 - Receiving: _db_backups/DATABASE_NAME_09.sql.gz -> D:\shared\backup\websites\godaddy\_db_backups\DATABASE_NAME_09.sql.gz

                      [05] Fri 21Jun13 15:10:50 - PASV

                      [06] Fri 21Jun13 15:10:50 - 227 Entering Passive Mode (72,167,183,26,204,212)

                      [03] Fri 21Jun13 15:10:50 - Opening passive mode data connection to 72.167.183.26, port 52436.

                      [06] Fri 21Jun13 15:10:50 - 226-File successfully transferred

                      [06] Fri 21Jun13 15:10:50 - 226 0.691 seconds (measured here), 203.42 Kbytes per second

                      [05] Fri 21Jun13 15:10:50 - RETR _db_backups/DATABASE_NAME_09.sql.gz

                      [06] Fri 21Jun13 15:10:50 - 550 Can't open _db_backups/DATABASE_NAME_09.sql.gz: No such file or directory

                      [04] Fri 21Jun13 15:10:50 - Download of "D:\shared\backup\websites\godaddy\_db_backups\DATABASE_NAME_09.sql.gz" failed.

                       

                      Here's a portion of my local directory after the scheduled sync (database name changed slightly):

                       

                      06/14/2013  02:20 AM                 0 DATABASE_NAME_13.sql.gz
                      06/15/2013  02:20 AM           151,519 DATABASE_NAME_14.sql.gz
                      06/16/2013  02:20 AM                 0 DATABASE_NAME_15.sql.gz
                      06/17/2013  02:20 AM           154,340 DATABASE_NAME_16.sql.gz
                      06/18/2013  02:20 AM                 0 DATABASE_NAME_17.sql.gz
                      06/19/2013  02:20 AM           151,398 DATABASE_NAME_18.sql.gz
                      06/20/2013  02:20 AM                 0 DATABASE_NAME_19.sql.gz
                      06/21/2013  02:20 AM           151,452 DATABASE_NAME_20.sql.gz
                      06/21/2013  02:20 PM                 0 DATABASE_NAME_21.sql.gz
                      05/23/2013  02:20 AM                 0 DATABASE_NAME_22.sql.gz
                      05/24/2013  02:20 AM           148,529 DATABASE_NAME_23.sql.gz
                      05/25/2013  02:20 AM           151,831 DATABASE_NAME_24.sql.gz
                      05/26/2013  02:20 AM                 0 DATABASE_NAME_25.sql.gz
                      05/27/2013  02:20 AM           151,699 DATABASE_NAME_26.sql.gz
                      05/28/2013  02:20 AM                 0 DATABASE_NAME_27.sql.gz
                      05/29/2013  02:20 AM                 0 DATABASE_NAME_28.sql.gz
                      05/30/2013  02:20 AM           147,737 DATABASE_NAME_29.sql.gz
                      05/31/2013  02:20 AM                 0 DATABASE_NAME_30.sql.gz
                      06/01/2013  02:20 AM           147,818 DATABASE_NAME_31.sql.gz
                      02/21/2013  02:57 PM        55,786,017 dbfiotdbinaryboy.sql
                      02/21/2013  02:59 PM               180 db_backup.sh
                                    35 File(s)     58,291,510 bytes
                                     2 Dir(s)  565,737,238,528 bytes free

                      D:\shared\backup\websites\godaddy\_db_backups>