FTP GET error: "Can't check for file existence"

[geodosch]

I have a macro that I've been using for years which downloads a file from an FTP site.  Recently it stopped working, and upon debugging I discovered that when it performs an FTP GET, the result string is "Can't check for file existence".  However, it can connect to the site and list the files.  Here are the relevant steps in the macro:

 

1. FTP Connect
2. FTP List Directory
3. Check variable from 'List' to make sure it contains expected filename
4. FTP Get File
5. If Not File Exists (downloaded file) generate error & abort macro

 

In step 4 the return string is "Can't check for file existence".  I am able to perform the FTP download via FileZilla, and also from a command line using the native Windows 10 ftp client.

 

I found a post on another site which appears to be related to this error.  It's possible that ME is attempting to perform a validation prior to the actual GET command, which is resulting in an error, though that step is unnecessary.  I did update to the most current ME 3 version (from 11a to 11b), but this had been working with the 11a version.  It's possible a Windows update broke this functionality.

[JohnGarziglia]

I have run into the same error on a each of the macros I am running which results in files that should be deleted not being deleted, and thus unwanted files proliferating.   The issue appeared to start sometime in mid-November 2020.  The error occurs regardless of whether ME 3 is running in Windows 10 or Windows XP.   

[JohnGarziglia]

As an addendum, although I have rarely posted to this forum (or relied upon it because I have not had to), I have been using the FTP commands referenced above in ME3 since 2003 and only recently am getting the FTP "Can't check for file existence" error and a result that the specified file is either not downloaded from the FTP site or deleted from the FTP site.   That this error message appears, given no change in computers, OS, ISP or remote  server, is perplexing.    

[Greg Atkinson]

Any chance Windows Update installed kb4023057 about the time this stopped working?  I'm having the same problem (though I don't use Macro Express).