Differences
This shows you the differences between the selected revisions of the page.
| 2019-03-08 | 2019-03-08 | ||
| no summary (78.96.45.130) (hidden) (untrusted) | old revision restored - this is not a chat - please use support forum to explain (martin) (hidden) | ||
| Line 5: | Line 5: | ||
| ~~SPLIT~~ | ~~SPLIT~~ | ||
| - | ===== [[host_key]] Continue connecting to an unknown server and add its host key to a cache? ===== | + | ===== [[host_key]] The server's host key was not found in the cache ===== |
| This error message occurs when WinSCP connects to a new [[SSH]] server. Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. | This error message occurs when WinSCP connects to a new [[SSH]] server. Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. | ||
| - | &screenshotpict(message_host_key) | ||
| - | If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator. ((&puttydoccite)) | ||
| - | Both SHA-256 and MD5 fingerprints of the host key are shown. As both fingerprints are for the same key, it is enough to check only one of them. Checking %%SHA-256%% fingerprint is safer though. | ||
| - | If the [[faq_hostkey|host key fingerprint is correct]], press //Yes//. The host key will be stored to cache and you will not be prompted the next time. If you are unsure, want to defer a host key verification until later, but still need to connect now (taking a risk), press //No//. The host key will not be cached and you will be prompted again the next time. If the fingerprint is not correct or if you do not know the correct fingerprint, press //Cancel// to abort connection. | + | If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator. ((&puttydoccite)) |
| - | If you have the correct host key (or its fingerprint) in a digital form, instead of checking the fingerprint manually, you can use //Paste Key// button (in drop down menu of //Yes// button) to have WinSCP compare the fingerprint for you, against a fingerprint or a full key stored in the clipboard. The clipboard can contain an %%SHA-256%% or %%MD5%% fingerprint or a full key in ''.pub'' format. | + | Read more about [[ssh_verifying_the_host_key|verifying host keys]]. |
| - | Use //Copy key fingerprints to clipboard// link to copy the fingerprints to clipboard. | ||
| - | |||
| - | |||
| - | Read more about [[ssh_verifying_the_host_key|verifying host keys]]. | ||
| Learn also how to [[scripting#hostkey|accept host key automatically in script]]. | Learn also how to [[scripting#hostkey|accept host key automatically in script]]. | ||
| Line 62: | Line 55: | ||
| > The server rejected SFTP connection, but it listens for FTP connections. | > The server rejected SFTP connection, but it listens for FTP connections. | ||
| > | > | ||
| - | > Did you want to use %%FTP%% protocol instead of %%SFTP%%? Prefer using encryption. | + | > Did you want to use FTP protocol instead of SFTP? Prefer using encryption. |
| The message is always associated with one of the following errors: | The message is always associated with one of the following errors: | ||
| Line 183: | Line 176: | ||
| </code> | </code> | ||
| - | For details refer to [[https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd421710(v=ws.10)|How to Configure Windows Firewall for a Passive Mode FTP Server]]. | + | For details refer to [[https://technet.microsoft.com/en-us/library/dd421710.aspx|How to Configure Windows Firewall for a Passive Mode FTP Server]]. |
| ===== Incoming packet was garbled on decryption ===== | ===== Incoming packet was garbled on decryption ===== | ||
| Line 367: | Line 360: | ||
| ===== [[preserve_time_perm]] Upload of file .. was successful, but error occurred while setting the permissions and/or timestamp. If the problem persists, turn off setting permissions or preserving timestamp. Alternatively you can turn on 'Ignore permission errors' option. ===== | ===== [[preserve_time_perm]] Upload of file .. was successful, but error occurred while setting the permissions and/or timestamp. If the problem persists, turn off setting permissions or preserving timestamp. Alternatively you can turn on 'Ignore permission errors' option. ===== | ||
| You get this error, when a server fails to update file timestamp or permissions for some reason: | You get this error, when a server fails to update file timestamp or permissions for some reason: | ||
| - | * On some systems (e.g. Linux), you need to be an owner of the file (write permissions are not enough) to modify its permissions or timestamp (you will see an error like //"Permissions denied"// in error details). | + | * On some systems, you need to be an owner of the file (write permissions are not enough) to modify its permissions or timestamp (you will see an error like //"Permissions denied"// in error details). |
| * Some servers do not support updating file timestamp or permissions at all (you will see an error like //"The server does not support the operation"// in error details). | * Some servers do not support updating file timestamp or permissions at all (you will see an error like //"The server does not support the operation"// in error details). | ||
| * Some servers are set up to pickup any uploaded file immediately, process it somehow and delete or move it away. If the server is quick enough, it does that before WinSCP is able to update the file timestamp or permissions (you will see an error like //"No such file or directory"// in error details). | * Some servers are set up to pickup any uploaded file immediately, process it somehow and delete or move it away. If the server is quick enough, it does that before WinSCP is able to update the file timestamp or permissions (you will see an error like //"No such file or directory"// in error details). | ||
| Line 414: | Line 407: | ||
| For details see [[https://support.microsoft.com/en-us/help/2888853/fix-the-supplied-message-is-incomplete-error-when-you-use-an-ftps-clie|Microsoft KB 2888853]]. | For details see [[https://support.microsoft.com/en-us/help/2888853/fix-the-supplied-message-is-incomplete-error-when-you-use-an-ftps-clie|Microsoft KB 2888853]]. | ||
| - | This is not applicable since 2014. Please fix the client. | ||
| ===== [[library_process_terminated_with_exit_code_3]] WinSCP process terminated with exit code 3 ===== | ===== [[library_process_terminated_with_exit_code_3]] WinSCP process terminated with exit code 3 ===== | ||
| Line 440: | Line 432: | ||
| ===== [[cannot_initialize_external_console]] Cannot initialize external console ===== | ===== [[cannot_initialize_external_console]] Cannot initialize external console ===== | ||
| - | If you are getting the error with [[library|WinSCP .NET assembly]] and the error details are like //"Request event - System Error. Code: 5. - Access is denied"//, the error indicates that the .NET assembly cannot communicate with [[executables|WinSCP executable]]. This usually happens, when the .NET assembly is used within a restricted environment like IIS Web Service as the assembly and the process are using different local accounts. | + | If you are getting the error with [[library|WinSCP .NET assembly]] and the error details are like //"Request event - System Error. Code: 5. - Access is denied"//, the error indicates that the .NET assembly cannot communicate with [[executables|WinSCP executable]]. This usually happens, when the .NET assembly is used within a restricted environment like IIS Web Service and the assembly and the process are using different local accounts. |
| Use the ''[[library_session#executableprocessusername|Session.ExecutableProcessUserName]]'' and the ''[[library_session#executableprocesspassword|Session.ExecutableProcessPassword]]'' to configure the local account to use for the WinSCP process. | Use the ''[[library_session#executableprocessusername|Session.ExecutableProcessUserName]]'' and the ''[[library_session#executableprocesspassword|Session.ExecutableProcessPassword]]'' to configure the local account to use for the WinSCP process. | ||
| Line 449: | Line 441: | ||
| You may get this error, if the [[library_install|WinSCP .NET assembly package]] was downloaded using Microsoft Internet Explorer and extracted using Windows Explorer. These applications, under certain circumstances, block libraries downloaded from Internet as potentially harmful, what prevents their loading. | You may get this error, if the [[library_install|WinSCP .NET assembly package]] was downloaded using Microsoft Internet Explorer and extracted using Windows Explorer. These applications, under certain circumstances, block libraries downloaded from Internet as potentially harmful, what prevents their loading. | ||
| - | To remove the block, open //Properties// for the ''WinSCPnet.dll'' in Windows Explorer. On an initial //General// page, click //Unblock// button on //Security// section. You may need to restart your IDE (if any), for the change to apply. | + | To remove the block, open //Properties// for the ''WinSCPnet.dll'' in Windows Explorer. On an initial //General// page, click //Unblock// button on //Security// section. |
| ===== [[net_system_cannot_find_file_specified]] Could not load file or assembly 'file:///...\WinSCPnet.dll' or one of its dependencies. The system cannot find the file specified. ===== | ===== [[net_system_cannot_find_file_specified]] Could not load file or assembly 'file:///...\WinSCPnet.dll' or one of its dependencies. The system cannot find the file specified. ===== | ||
| Line 455: | Line 447: | ||
| If the above is not your case, use [[https://docs.microsoft.com/en-us/dotnet/framework/tools/fuslogvw-exe-assembly-binding-log-viewer|Assembly Binding Log Viewer]] (''Fuslogvw.exe'') to debug assembly loading. | If the above is not your case, use [[https://docs.microsoft.com/en-us/dotnet/framework/tools/fuslogvw-exe-assembly-binding-log-viewer|Assembly Binding Log Viewer]] (''Fuslogvw.exe'') to debug assembly loading. | ||
| - | |||
| - | ===== [[net_exception_thrown_target_invocation]] Exception has been thrown by the target of an invocation ===== | ||
| - | |||
| - | This is just a high-level exception. The root cause is usually stored in the ''[[dotnet>system.exception.innerexception|InnerException]]''. | ||
| - | |||
| - | If you are getting this exception in SSIS, you can use ''try'' ... ''catch'' block to capture the error, as show in the [[library_ssis#example|example for using WinSCP .NET Assembly from SSIS]]. | ||
| - | |||
| - | If you cannot access the inner exception easily, inspect WinSCP session log and debug log file (''[[library_session#sessionlogpath|Session.SessionLogPath]]'', ''[[library_session#debuglogpath|Session.DebugLogPath]]''). If those file are not even created, the root cause can be loading of ''WinSCPnet.dll'' assembly. See [[message_net_system_cannot_find_file_specified|Could not load file or assembly 'file:///...\WinSCPnet.dll' or one of its dependencies. The system cannot find the file specified.]]. | ||
| ===== [[path_slash_ambiguous]] Selecting files using a path ending with slash is ambiguous. Remove the slash to select the folder. Append * mask to select all files in the folder. ===== | ===== [[path_slash_ambiguous]] Selecting files using a path ending with slash is ambiguous. Remove the slash to select the folder. Append * mask to select all files in the folder. ===== | ||