0 Byte Downloads when connecting to Liaison VAN

[lcros]

Hi. We're having a problem with running Core on a Windows 7 64 bit Machine and downloading files from Liaison's VAN. The files are sometimes downloaded and at other times do not download, but create 0 byte files.

It occurs when downloading directly through Core or with a CMD.

Has anyone else experienced this? Any thoughts on what might cause this?


Thanks in advance for your help.
Lisa

[ForumAdmin]

Post the log from the session. It could be anything from local disk space to files being locked. Without more information it's just a guess.

[lcros]

[quote="ForumAdmin"]Post the log from the session. It could be anything from local disk space to files being locked. Without more information it's just a guess.[/quote]

Here's the log...
03/14/13 15:09 (1751)
Connect socket #328 to 63.78.198.2, port 990...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bitUSER *****
331 Password is required
PASS **********
332 Account is required
ACCT FADA
230 **** Logon ok
SYST
215 UNIX Type: L8
CWD RF/
250 CWD Successful
PBSZ 0
200 PBSZ=0
PROT P
200 Data Channel is secured
PASV
227 Entering Passive Mode (63,78,198,2,46,180)
LIST -al
Connect socket #344 to 63.78.198.2, port 11956...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bit150 Opening data connection for /$TCI39.#RMT (63,78,198,2,46,180)
226 Transfer Complete
PWD
257 "/$TCI39.#RMT/InBox/:EDINET" is the current directory.
CWD RF/
250 CWD Successful
PASV
227 Entering Passive Mode (63,78,198,2,46,182)
LIST -al
Connect socket #344 to 63.78.198.2, port 11958...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bit150 Opening data connection for /$TCI39.#RMT (63,78,198,2,46,182)
226 Transfer Complete
PASV
227 Entering Passive Mode (63,78,198,2,46,183)
LIST -al
Connect socket #344 to 63.78.198.2, port 11959...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bit150 Opening data connection for /$TCI39.#RMT (63,78,198,2,46,183)
226 Transfer Complete
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (63,78,198,2,46,184)
RETR STERLING13.KK13.1.ISA
Connect socket #348 to 63.78.198.2, port 11960...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bit150 Opening data connection for /$TCI39.#RMT (63,78,198,2,46,184)
Timeout (600 seconds), exiting Core FTP
150 Opening data connection for /$TCI39.#RMT (63,78,198,2,46,184)
STERLING13.KK13.1.ISA - 0 bytes transferred in 10 minutes, 603 seconds
Connect socket #328 to 63.78.198.2, port 990...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bitUSER ****
331 Password is required
PASS **********
332 Account is required
ACCT FADA
230 **** Logon ok
SYST
215 UNIX Type: L8
CWD RF/
250 CWD Successful
TYPE I
200 Type set to I
PBSZ 0
200 PBSZ=0
PROT P
200 Data Channel is secured
PASV
227 Entering Passive Mode (63,78,198,2,47,117)
RETR STERLING13.KK13.1.ISA
Connect socket #352 to 63.78.198.2, port 12149...TLSv1, cipher TLSv1/SSLv3 (AES128-SHA) - 128 bit150 Opening data connection for /$TCI39.#RMT (63,78,198,2,47,117)

[ForumAdmin]

Looks like connectivity issues.

If using the command line use corecmd.exe and check the %ERRORLEVEL% return code so you can try the transfer again.

[lcros]

[quote="ForumAdmin"]Looks like connectivity issues.

If using the command line use corecmd.exe and check the %ERRORLEVEL% return code so you can try the transfer again.[/quote]

Thanks. I don't have coremed.exe. Where do I download it?

The problem is that the VAN's FTP recognizes the file as being picked up, so it is no longer accessible after the first attempt.

[ForumAdmin]

It's in the installation directory (where coreftp.exe).

For connectivity issues, you could try setting your transfer rates (advanced -> connection) to use lower buffer sizes or a lower CPS rate. Having lower transfer rates might help if the server is sending data in larger streams and then disconnecting without waiting for the client to acknowledge receipt of the file.