Differences

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

2013-04-08 2013-04-09
5.2: stored session => site (martin) 5.2: stored session => site (martin)
Line 8: Line 8:
  * Access to files on mapped network drives fails, because the drives are not mapped for the service's account.   * Access to files on mapped network drives fails, because the drives are not mapped for the service's account.
-To check what [[config|configuration storage]] is used, whether a site name was recognised or under what Windows account the script is running, inspect a beginning of [[logging|session log]]. For example, following log shows that the configuration was read from Windows registry, the script was running under local account ''martin'' and ''mysession'' was recognised as a stored session name.+To check what [[config|configuration storage]] is used, whether a site name was recognised or under what Windows account the script is running, inspect a beginning of [[logging|session log]]. For example, following log shows that the configuration was read from Windows registry, the script was running under local account ''martin'' and ''mysession'' was recognised as a site (stored session) &beta name.
<code> <code>
Line 17: Line 17:
Login time: 07 October 2011 08:55:53                                      Login time: 07 October 2011 08:55:53                                     
-------------------------------------------------------------------------- --------------------------------------------------------------------------
-Session name: mysession (Stored session)                            +Session name: mysession (Site)                           
</code> </code>
-If there was no such stored session in current configuration storage (Windows registry in this case), ''mysession'' (as passed to ''[[scriptcommand_open|open]]'' command) would be interpreted as host name and the log line would say:+If there was no such site (stored session) &beta in current configuration storage (Windows registry in this case), ''mysession'' (as passed to ''[[scriptcommand_open|open]]'' command) would be interpreted as host name and the log line would say:
<code> <code>
Line 28: Line 28:
Solutions: Solutions:
  * [[scripting#hostkey|Specify fingerprint of expected hostkey or certificate]] explicitly in the script. ((Alternatively make sure the [[ssh#verifying_the_host_key|host key]] or [[ftps#certificate|certificate]] is verified under the service's account.))   * [[scripting#hostkey|Specify fingerprint of expected hostkey or certificate]] explicitly in the script. ((Alternatively make sure the [[ssh#verifying_the_host_key|host key]] or [[ftps#certificate|certificate]] is verified under the service's account.))
-  * Use [[config|INI file]] instead of registry to store the configuration to make sure the [[session_configuration#stored|stored session]] (and/or other settings) can be accessed by all accounts. ((Alternatively [[config#transfering_the_configuration|transfer the stored session]] (and/or other settings) to the service's account.))+  * Use [[config|INI file]] instead of registry to store the configuration to make sure the [[session_configuration#site|site]] (and/or other settings) can be accessed by all accounts. ((Alternatively [[config#transfering_the_configuration|transfer the site]] (and/or other settings) to the service's account.))
When dealing with SSIS see also guide to [[guide_ssis|SFTP task in SSIS]]. When dealing with SSIS see also guide to [[guide_ssis|SFTP task in SSIS]].
//See also more generic article on [[faq_environment|making WinSCP work in a new environment (operating system, machine, user account, network)]].// //See also more generic article on [[faq_environment|making WinSCP work in a new environment (operating system, machine, user account, network)]].//

Last modified: by martin