5/29/2023 0 Comments Synkron long filenamesI don't have a lot of experience with powershell. Recurse should include every file and folder within those folders that I am starting at, yes? Irregardless of file name or folder name? Well, it didn't. The first time this program ran it actually went pretty fast. I'm transfering files from one networked server to another. The $error.clear() is there because I was testing to see if maybe the $error variable was getting bogged down. The #$streams are commented out right now because I was testing to see if that was what was slowing it down. * 21:47:33.#$stream.WriteLine("Make directory $tht\T Drive\ was successful")Ĭatch I'm doing this more or less. * 21:47:33.242 (ESkipFile) Error creating folder 'E:\FTP_Box_Backup\\Background Checks'. < 21:47:33.242 The filename or extension is too long < 21:47:33.242 Script: Error creating folder 'E:\FTP_Box_Backup\\Background Checks'. 21:47:33.242 The filename or extension is too long") 21:47:33.242 Error creating folder 'E:\FTP_Box_Backup\\Background Checks'. * 21:47:33.242 The filename or extension is too long Let me know if you need any additional info or original log file. Note that I am running Windows 10 Professional and have enabled long paths using instructions from this article ( ). However, I seem to get the same error using 5.14.4 RC (Build 9136) build over FTP. My apologies, I downloaded the latest beta build. Let me know if I can help with the troubleshooting. I've attached logs of both sessions to the post. I don't want to workaround this problem by just disabling the "Preserve Timestamp" option since that is very important to make sure we are uploading the correct files to the server. Reconnecting to the FTP server I can see that it did delete this file, but I get the same session timeout error preventing WinSCP from deleting the remaining files. However, then when I tried deleting these files I got another error when trying to delete a file with a name 49 characters long. I then disabled the "Preserve Timestamp" option from the Default transfer settings() and retried uploading the files, which this time worked, uploading files with names of 94 characters long. I can see from the log WinSCP tried to do a "MDTM" command after which it got a session timeout. I again tried uploading a series of files with increasing filename length, and when it reached a file name of 82 characters long plus a. Thanks for sending me the 5.14 download link, but it looks like I'm still having the problem. Please let me know if you need any other information. I have attached a log of my FTP session in case that is helpful. Can I get an early release of version 5.14 to see if it fixes my problem? I'm currently running 5.13.3, which is the same version available on your download page. I noticed an existing bug ticket reporting a long file name problem is fixed in version 5.14, but I'm not sure if I'm having the same issue or not. When running via script it simply stops working and I don't see any error message. When running this in a the GUI the upload progresses then stops for about 20 seconds, and I get this error message. I can upload these same files, and longer ones, using FTP command line as well as FileZilla. The folder I was uploading to was 21 characters long. As a test I created a bunch of files with increasing length names to test the upload, and found the upload stopped working after the file name was 82 characters plus a 3 character extension. I'm having problems uploading files to our FTP server which have long file names.
0 Comments
Leave a Reply. |