Please attach a full log file showing the problem (using the latest version of WinSCP).
To generate log file, use
/log=path_to_log_filecommand-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
I just emailed you the log file - Pravin
OOps, What I shared is WER log report and not WINSCP; I will share the correct one. - Pravin
I have emailed you the WinSCP log. Request you to please analyze and share your feedback. - Pravin.
I just referred to the following post on WinSCP.
Assuming the cause is “limited buffer” of the issue which we are facing, how do we correct it using .Net assembly.
We don’t see any such property under session object of WinSCP.
:D :D :D :D Issue Finally Resolved :D :D :D :D
In a loop we were using Application.Doevents.
Just removed "Application.Doevents" and the issue just disappeared. :D :D :D :D
Refer to caution section under the following post from Microsoft;