Re: Invalid access to memory
Thanks for your report. Will try to reproduce the problem.
Btw, WinSCP cannot display a log of another instance.
Btw, WinSCP cannot display a log of another instance.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- WillBeaden
Invalid access to memory
Win XP machine with 1GB RAM.
WinSCP version 5.5.6.4746
---------------------------
Error
---------------------------
Invalid access to memory.
Please help us improving WinSCP by reporting the error on WinSCP support forum.
---------------------------
OK Help Report
---------------------------
I was testing a script running from MS Access, but had the GUI interface open with the log up to see if it would log my upload. I had the box checked to show ALL LINES. Probably a mistake, since it crashed. I was not running the script when it crashed, just trying to scroll back to see previous lines in the log.
Here is the script, although it doesn't appear that it was at fault.
The problem I was trying to fix is that MS Access will not parse the entire command string. It stops before it gets to the logging command:
I think what I will have to do is create a batch file for Access to call, that contains the switches for WinSCP. That way Access won't get confused. BTW, I'm still waiting for the log viewer to refresh so I can disable it.
WinSCP version 5.5.6.4746
---------------------------
Error
---------------------------
Invalid access to memory.
Please help us improving WinSCP by reporting the error on WinSCP support forum.
---------------------------
OK Help Report
---------------------------
I was testing a script running from MS Access, but had the GUI interface open with the log up to see if it would log my upload. I had the box checked to show ALL LINES. Probably a mistake, since it crashed. I was not running the script when it crashed, just trying to scroll back to see previous lines in the log.
Here is the script, although it doesn't appear that it was at fault.
# Automatically abort script on errors
option batch abort
# Disable overwrite confirmations that conflict with the previous
option confirm off
# Connect
open ftp://stonegate
# Change remote directory
cd /sgdadmin/www/customer/uploads
# Force binary mode transfer
option transfer binary
# XML log is created in "UploadLog.txt"
# Upload All SoStat.pdf to working directory
put M:\Reports\RepSOStatus\*SoStat.pdf
# Disconnect
close
# Exit WinSCP
exit
The problem I was trying to fix is that MS Access will not parse the entire command string. It stops before it gets to the logging command:
"c:\Program Files\WinSCP\WinSCP.com" /script="C:\Program Files\WinSCP\TestScript2.txt" /xmllog=UploadLog.txt
I think what I will have to do is create a batch file for Access to call, that contains the switches for WinSCP. That way Access won't get confused. BTW, I'm still waiting for the log viewer to refresh so I can disable it.