Winscp.com is not working

winscp.com commandline utility is not working in production server
it is working good in test server


code inside the bat file

C:
CD\Program Files (x86)\WinSCP
winscp.com /command "option batch abort" "option confirm off" "close" "exit"


when i execute the bat file in test server output like this


NULL
C:\Windows\system32>C:
NULL
C:\Windows\system32>Cd\Program Files (x86)\WinSCP
NULL
C:\Program Files (x86)\WinSCP>winscp.com /command "option batch abort" "option confirm off" "close" "exit"
batch abort
confirm off
No session.
NULL



when i execute the bat file in production server output like this


NULL
C:\Windows\system32>C:
NULL
C:\Windows\system32>Cd\Program Files (x86)\WinSCP
NULL
C:\Program Files (x86)\WinSCP>winscp.com /command "option batch abort" "option confirm off" "close" "exit"
NULL

Did it ever work on the production server? What is exit code of winscp.com?

martin wrote:

Did it ever work on the production server? What is exit code of winscp.com?

it is working in production server
from yesterday only it is not working
it is urgent.please give me some suggestion

it is working in production server
from yesterday only it is not working
it is urgent.please give me some suggestion

If exit code is 3, you are possibly a victim of this issue:
https://winscp.net/tracker/996

Currently, the only known workaround is to restart the server.

Anonymous wrote:

martin wrote:

Did it ever work on the production server? What is exit code of winscp.com?

it is working in production server
from yesterday only it is not working
it is urgent.please give me some suggestion

CODE IN PRODUCTION SERVER

BAT FILE CODE :

"C:\Program Files (x86)\WinSCP\WinSCP.com" -script=C:\temp\SFTPOUTPUT.TXT

SCRIPT FILE CODE :

option batch abort
option confirm off
open sftp://112:thEWape2@ftp.alphamcs.com:22
close
exit

martin wrote:

it is working in production server
from yesterday only it is not working
it is urgent.please give me some suggestion

If exit code is 3, you are possibly a victim of this issue:
https://winscp.net/tracker/996

Currently, the only known workaround is to restart the server.

IS ANY OTHER WAY TO SOLVE THIS ISSUE
IT IS NOT POSSIBLE TO RESTART THE SERVER
SAME PROCESS IS SCHEDULED IN TEST SERVER IT IS WORKING GOOD FOR PAST TWO MONTHS
WITH IN TWO DAYS WE HAVE THE ISSUE IN PRODUCTION SERVER

SAME PROCESS IS SCHEDULED IN TEST SERVER IT IS WORKING GOOD FOR PAST TWO MONTHS
WITH IN TWO DAYS WE HAVE THE ISSUE IN PRODUCTION SERVER

It depends on frequency or starts. There's no other workaround as of now.

martin wrote:

SAME PROCESS IS SCHEDULED IN TEST SERVER IT IS WORKING GOOD FOR PAST TWO MONTHS
WITH IN TWO DAYS WE HAVE THE ISSUE IN PRODUCTION SERVER

It depends on frequency or starts. There's no other workaround as of now.

we restarted server yesterday it was works good
again we have same the same issue today

neelakandan wrote:

martin wrote:

SAME PROCESS IS SCHEDULED IN TEST SERVER IT IS WORKING GOOD FOR PAST TWO MONTHS
WITH IN TWO DAYS WE HAVE THE ISSUE IN PRODUCTION SERVER

It depends on frequency or starts. There's no other workaround as of now.

we restarted server yesterday it was works good
again we have same the same issue today

when i execute the bat file manually it works good
through xp..cmdshell it is not working

neelakandan wrote:

when i execute the bat file manually it works good
through xp..cmdshell it is not working

There's some resource that is exhausted in scheduler's (or similar) session.