Differences
This shows you the differences between the selected revisions of the page.
| 2019-03-28 | 2019-03-28 | ||
| typography (martin) | typography (martin) | ||
| Line 25: | Line 25: | ||
| Learn also how to [[scripting#hostkey|accept host key automatically in script]]. | Learn also how to [[scripting#hostkey|accept host key automatically in script]]. | ||
| - | ===== [[security_breach]] Warning - Potential security breach! ===== | + | ===== [[security_breach]] Warning -- Potential security breach! ===== |
| This message, followed by "The server's host key does not match the one WinSCP has in cache", means that WinSCP has connected to the SSH server before, knows what its host key should be, but has found a different one. | This message, followed by "The server's host key does not match the one WinSCP has in cache", means that WinSCP has connected to the SSH server before, knows what its host key should be, but has found a different one. | ||
| Line 286: | Line 286: | ||
| To fix the problem, find out, what command in your login script prints the text. Once you find it, move the command to a proper interactive script, or remove it entirely. The scripts are usually hidden (their name starts with dot) and are located in your home directory on the server. Typically you will need to move the commands from ''.bashrc'' script to ''.bash_profile''. | To fix the problem, find out, what command in your login script prints the text. Once you find it, move the command to a proper interactive script, or remove it entirely. The scripts are usually hidden (their name starts with dot) and are located in your home directory on the server. Typically you will need to move the commands from ''.bashrc'' script to ''.bash_profile''. | ||
| - | There are other possible sources of the message in addition to the profile script - some SSH servers print messages, if they are unable to start an %%SFTP%% server, or encounter a fatal error. You should contact your server administrator. | + | There are other possible sources of the message in addition to the profile script -- some SSH servers print messages, if they are unable to start an %%SFTP%% server, or encounter a fatal error. You should contact your server administrator. |
| Another possibility is that the server is configured to only allow an SCP protocol and not the %%SFTP%% protocol, in such a way that %%SCP%% fallback mechanism of WinSCP does not work. The solution is to explicitly choose %%SCP%% protocol on the [[ui_login#session_settings|Login dialog]]. | Another possibility is that the server is configured to only allow an SCP protocol and not the %%SFTP%% protocol, in such a way that %%SCP%% fallback mechanism of WinSCP does not work. The solution is to explicitly choose %%SCP%% protocol on the [[ui_login#session_settings|Login dialog]]. | ||
| Line 426: | Line 426: | ||
| This error comes in variants: | This error comes in variants: | ||
| - | * //Timeout waiting for WinSCP to respond - WinSCP has not responded in time// | + | * //Timeout waiting for WinSCP to respond -- WinSCP has not responded in time// |
| - | * //Timeout waiting for WinSCP to respond - Log file ... was not created in time, please make sure WinSCP has write permissions to the folder// | + | * //Timeout waiting for WinSCP to respond -- Log file ... was not created in time, please make sure WinSCP has write permissions to the folder// |
| ~~AD~~ | ~~AD~~ | ||
| Line 439: | Line 439: | ||
| ===== [[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 as 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 500: | Line 500: | ||
| The ''12'' means "EOF" and is sent to indicate a close of the session. The ''15'' means "ping" and is used to [[ui_login_connection#keepalives|keep a session alive]]. | The ''12'' means "EOF" and is sent to indicate a close of the session. The ''15'' means "ping" and is used to [[ui_login_connection#keepalives|keep a session alive]]. | ||
| - | ===== [[no_mapping_for_unicode]] No mapping for the Unicode character exists in the target multi-byte code page - The file must be in UTF-8 or UTF-16 encoding. ===== | + | ===== [[no_mapping_for_unicode]] No mapping for the Unicode character exists in the target multi-byte code page -- The file must be in UTF-8 or UTF-16 encoding. ===== |
| You get this error message, when you try to execute a [[scripting#using_scripting|script]] that does not use a valid UTF-8 (or UTF-16) encoding. | You get this error message, when you try to execute a [[scripting#using_scripting|script]] that does not use a valid UTF-8 (or UTF-16) encoding. | ||