The /SYMXUFTO is home path of your account.
In your original code (in Session.PutFiles or similar) you have explicitly asked WinSCP to upload to / – effectively overriding the default path.

Anyway, I believe that now your code does exactly the same, what you do in GUI. I do not see a reason, why your server should not detect the files, if it does detect the files uploaded in GUI. Please check again. Or talk to the server admins.

That's a great point. I'm not sure why it shows it like that in the GUI log. SYMXUFTO is just the user that I'm logged in with. I never moved to a different directory after connecting before uploading in the desktop app, and the old .ftp file executed by the batch file does not cd to any sub directory.

I reconfigured the program to have the remote directory be reported the same in the session log as the one returned in the GUI log and both logs now report "upload successful", but the host system does not report having received the file at all well after the expected delay has expired and other files sent later by native ftp have been reported as received.

Isn't the problem that in code you are uploading to a root, while in GUI to a SYMXUFTO folder?
If this does not help, please post equivalent logs, showing upload of the same file to the same remote directory.

Hey Martin, thanks for getting back to me. I updated my package. Here's the session log that I produced using Session.SessionLogPath.

• You can see I have extended the timeout of my SessionOptions because it gives me a timeout detected if I don't.
  
• The rest of the SessionOptions are fine and the connection is opened with no issue. This server uses FTP.
  
• The error really occurs upon uploading using Session.PutFiles. I'm using default transfer options.
  
• The exception message was:
  

  Copying files to remote side failed.
  [5] [080F0000] User Data failed the Security Exit.

  
  
• Also, I was wrong, apparently it works by dragging the file over using the desktop app. I've included that log as well. The two logs don't feature the same upload file, but it's the same format that they expect and the one that failed in .NET was successfully uploaded using native FTP.
  
• The source folder doesn't seem to be the issue, because we usually upload these files from a completely different directory than the source directory that worked in my desktop app attempt.
  
• One difference to me is that the log with the failure has that "CWD Directory changed." part.
  

Thanks again!

Please attach a full session log file (not .NET assembly debug log) showing the problem (using the latest version of WinSCP).

First time poster here,

When I attempt to upload EDI files to sciftp.commerce.stercomm.com using WinSCP, I get the error,

Copying files to remote side failed. [5] [080F0000] User Data failed the Security Exit.

The upload works fine using built-in Windows FTP command line. I don't get this error for any other server when using WinSCP. Attached is an example log of this error when using the WinSCP .NET library. Any help would be greatly appreciated.

Ryan