No I enable logging in the WInSCP software. I AM USING WinSCP.com and a script to execute my SFTP.
Sure. So did you add the
/log=... to winscp.com parameters?
- martin
Sure. So did you add the
Post a reply
Topic review
Sure. So did you add the
- Guest
No I enable logging in the WInSCP software. I AM USING WinSCP.com and a script to execute my SFTP.
- Guest
No I enable logging in the WInSCP software.
- martin
How do you enable the logging for the SQL job? Do you use the
https://winscp.net/eng/docs/commandline
/log command-line switch?
https://winscp.net/eng/docs/commandline
- Guest
Here is some more information! I run WinSCP on my server and set up logging in WinSCP and that captures logging when I execute the script from the command line and when I execute my SSIS package in BIDS. However when I run the Package in as a SQL Job nothing is written to the Log that I set up in WINSCP..... Any ideas why it is not using the log configuration and any ideas what could be the cause of my problem?
- Guest
SSIS Package Works but When Running from a SQL Schedule Job the time stamp does not match.
I have a SSIS package on SQL server 2008 R2 using the latest version of WinSCP. Every thing works when I execute the package. the time stamp updates to the current time and the file is copies.
I take the package and set up a SQL Job and running the package from file system it run and SFTP the file to the destination however the timestamp on the target file is different that the timestamp of the source and the different from the current time as well.
It seems like it is using either the time stamp when the SQL job was created or the Time stamp from the parent folder of the source file. eg.
source file was created 10/06/2015 2:30 pm when copy the target has 9/25/2015/ 1:52 pm then Job was created on 9/25/2015 and so was the folder where the source file is created. Look forward to a solution or Question.
I take the package and set up a SQL Job and running the package from file system it run and SFTP the file to the destination however the timestamp on the target file is different that the timestamp of the source and the different from the current time as well.
It seems like it is using either the time stamp when the SQL job was created or the Time stamp from the parent folder of the source file. eg.
source file was created 10/06/2015 2:30 pm when copy the target has 9/25/2015/ 1:52 pm then Job was created on 9/25/2015 and so was the folder where the source file is created. Look forward to a solution or Question.