Differences

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

faq_scheduler 2008-07-09 faq_scheduler 2009-03-05
Line 3: Line 3:
Possible consequences are: Possible consequences are:
-  * The script "hangs" because the host key is not known by the Scheduler's account and WinSCP asks for its [[ssh#verifying_the_host_key|verification]] (SFTP and SCP only).+  * The script "hangs" because the [[ssh#verifying_the_host_key|host key]] (SFTP or SCP) or [[ftps#certificate|certificate]] (FTPS) is not known by the Scheduler's account and WinSCP asks for its verification.
  * The connection fails, because your script depends on stored session, which is not known by the Scheduler's account.   * The connection fails, because your script depends on stored session, which is not known by the Scheduler's account.
  * Environment variables referenced in script are not resolved, because they are not set by the Scheduler's account.   * Environment variables referenced in script are not resolved, because they are not set by the Scheduler's account.
Solutions: Solutions:
-  * Make sure the [[ssh#verifying_the_host_key|host key is verified]] under the Scheduler's account or [[scripting#hostkey|specify fingerprint of expected hostkey]].+  * Make sure the [[ssh#verifying_the_host_key|host key]] or [[ftps#certificate|certificate]] is verified under the Scheduler's account. With SSH you can [[scripting#hostkey|specify fingerprint of expected hostkey]].
  * [[config#transfering_the_configuration|Transfer the stored session]] (or other settings) to the Scheduler's account.   * [[config#transfering_the_configuration|Transfer the stored session]] (or other settings) to the Scheduler's account.
  * or Use [[config|INI file]] instead of registry to store the configuration. The INI file can be accessed by all accounts.   * or Use [[config|INI file]] instead of registry to store the configuration. The INI file can be accessed by all accounts.

Last modified: by martin