Logfile send to your mail account.
Thx in advance for taking a look.
Regards Agent
Thx in advance for taking a look.
Regards Agent
- Agent
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- martin
Re: Error when using sftp a file to OpenSolaris0906 client.
Even if I turn off resume support in winscp settings the error message still comes up.
Please post a full log file showing that.
To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. For posting extensive logs you may use pastebin or similar application. 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.
- Agent
Error when using sftp a file to OpenSolaris0906 client.
Hi,
When I'm using an sftp connection to an OpenSolaris 0906 client with winscp 3.7 I'm getting the following error message:
Even if I turn off resume support in winscp settings the error message still comes up.
Any idea why this happens on OSOL only while the same approach on different flavours of Linux works fine?
Regards Agent
When I'm using an sftp connection to an OpenSolaris 0906 client with winscp 3.7 I'm getting the following error message:
Transfer was succesfully finished, but temporary transfer file 'filename.filepart' could not be renamed to target file name 'filename'. If the problem persists, you may try to turn off transfer resume support. General failure (server should provide error description). Error code: 4 Error message from server: Failure Request code: 18
Even if I turn off resume support in winscp settings the error message still comes up.
Getting the same error when trying to rename a remote file:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 18
Any idea why this happens on OSOL only while the same approach on different flavours of Linux works fine?
Regards Agent