Differences

This shows you the differences between the selected revisions of the page.

2016-07-14 2016-07-28
In Other Languages (martin) bug 1436 (martin)
Line 421: Line 421:
~~AD~~ ~~AD~~
-There are two major reasons for the error:+There are several possible reasons for the error:
  * WinSCP was run using a different local account and cannot communicate with the [[library|.NET assembly]]. This typically happens, when the assembly is used in IIS web application and impersonation is turned on. Turn the impersonation off for the web  application that uses the assembly. Alternatively, if you know, what account is being used, 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.   * WinSCP was run using a different local account and cannot communicate with the [[library|.NET assembly]]. This typically happens, when the assembly is used in IIS web application and impersonation is turned on. Turn the impersonation off for the web  application that uses the assembly. Alternatively, if you know, what account is being used, 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.
  * WinSCP could not create/write to log file that it uses to report back to the .NET assembly. Make sure your process has write permissions to the temporary folder. Alternatively, you can use (undocumented) property ''Session.XmlLogPath'' to change the log file location.   * WinSCP could not create/write to log file that it uses to report back to the .NET assembly. Make sure your process has write permissions to the temporary folder. Alternatively, you can use (undocumented) property ''Session.XmlLogPath'' to change the log file location.
  * WinSCP did not correctly start. Make sure your process has permissions to access WinSCP [[executables|executable]] and to execute processes. See also [[bug>996|related fix for frequent use of the .NET assembly]].   * WinSCP did not correctly start. Make sure your process has permissions to access WinSCP [[executables|executable]] and to execute processes. See also [[bug>996|related fix for frequent use of the .NET assembly]].
 +  * One some locales (e.g. Welsh), WinSCP has problems recognizing command-line arguments from the .NET assembly. See [[bug>1436|related fix]].
===== [[cannot_initialize_external_console]] Cannot initialize external console ===== ===== [[cannot_initialize_external_console]] Cannot initialize external console =====

Last modified: by martin