J
jjkatz
I have a .cmd file that calls a PuTTY script to download and rename a file. The .cmd file runs just fine if I double-click it. If I set it to run in Task Scheduler, the task hangs until the timeout expires and then stops without success. I have the task set to run whether or not the user is logged on. I am running the task under a System account, but I've also tried running it using my own credentials, with the same results. I do not have the necessary permissions to stop and restart the Task Scheduler service on the server.
This is a new server I am setting up, and this task runs without issue in Task Scheduler on my old server, which is running Windows Server 2003. It is only in Windows Server 2012 that this behavior occurs. PuTTY appears to be installed and configured correctly, since the script runs fine when I just double-click the .cmd file.
I've checked CPU usage and the script is not causing any spikes. Any suggestions? Please let me know if you need more information.
Continue reading...
This is a new server I am setting up, and this task runs without issue in Task Scheduler on my old server, which is running Windows Server 2003. It is only in Windows Server 2012 that this behavior occurs. PuTTY appears to be installed and configured correctly, since the script runs fine when I just double-click the .cmd file.
I've checked CPU usage and the script is not causing any spikes. Any suggestions? Please let me know if you need more information.
Continue reading...