guest6549 wrote:

same problem here! are there any solutions?
task will only work if option "only run if user is logged on" is selected

You are probably a victim of this issue:
https://winscp.net/tracker/996

Everyone, please upvote my related question on StackOverflow:
https://stackoverflow.com/q/18893366/850848

same problem here! are there any solutions?
task will only work if option "only run if user is logged on" is selected

vj wrote:

Have you resolved this?
Nothing gets logged.

Did you try to restart the machne that runs WinSCP?

Have you resolved this?
Nothing gets logged.

Did you try to restart the machne that runs WinSCP?

I've got exactly the same issue, frustratingly it was working for ages then just stopped one day. It certainly fits in with your memory leak idea.

Seems my DCOM was throwing an error and timing out trying to start the Microsoft WMI Provider Subsystem Secured Host.

If you have any ideas it would be much appreciated before i wade through more wmidiag reports.

Many thanks.

Yes, I am.
I have a start of an answer. It looks like a memory leak related to how WMI is handeled on Windows Server 2008 R2 (use WMI in my script, after WinSCP).
The problem is not WinSCP related but I guess I'm not the onlyone who uses the kind of script.

If you use a WMI script as system, it will eventualy fail after several days. If you try your script interactively, it will run without problem...

I go deeper in my research and will comme back with more details.

Bye

Are you sure it produces no log when you specify /log command-line parameter in scheduler task?

Hi,

I wrote a very little script to get a file from an SFTP server.
The script runs just fine.
I can get it to run thru the Task Scheduler but...
As soon as I ask it to run wheter i'm logged on or not (I have to enter my password then), it doesn't run at all. I mean nothing at all. No execution, no log, no output, NOTHING.

Off course, I'm sure of the password I entered.
I tried several times and if I include my script in a batch file, the previous and post parts of the batch file are executed. The winscp.com line is just ignored by the process.

It runs on a Windows 2008R2 Server. I have the same problem on several servers (same OS).

I'm open to give any additionnal information I can to help you discover the origin of this strange problem as I'm unable to do it myself...


Best regards from Belgium and happy new year to all of you :-)