Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > File Transfer

Reply
 
Thread Tools Display Modes
  #1  
Old 08-28-2019, 03:41 AM
DPCotswold DPCotswold is offline
Registered User
 
Join Date: Aug 2019
Posts: 3
Remote session file fails to close

Hi

I am having an issue with a SFXCL file transfer via command line to a remote host.

Basically the file seems to transfer OK (but once it did not) and the log is showing conflicting information.

On one line it logs:
Opening file 'hrcash.txt' for upload as 'hrcash.txt'. (ASCII)
SEND : Open: /TO_CBH/hrcash.txt, mode 0x1a
File transfer completed: 0x00000000.

Then a couple of lines later:
Destination file closed with error (0xe0000001): Failure
SUMMARY: Attempted to transfer 1 files.
SUMMARY: Transferred 0 files successfully.
hrcash.txt: Failed to close destination file.
Channel Closed.


So for some reason the .txt file is maybe not closing correctly after transfer, the log suggests it may not have transferred (but it usually DOES transfer) however, occasionally it DOES fail.

Is there any known reason for this type of behaviour?

And is there a solution?

Thanks in advance

Dave
Reply With Quote
  #2  
Old 08-28-2019, 07:26 AM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 3,976
Hi Dave,

What version of SecureFX is installed?

On what OS?

It's typically not a good idea for us to attempt to analyze a few lines of the log out of context. Please post the entire log (with sensitive data redacted) or send it to support@vandyke.com and include Attn Brenda - Forum Thread #13890 in the subject line.

If the SFXCL command-line you are running is not included in the log, please post/send it as well (again, with sensitive data redacted).
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
  #3  
Old 08-28-2019, 07:53 AM
DPCotswold DPCotswold is offline
Registered User
 
Join Date: Aug 2019
Posts: 3
Thank Brenda

Hi Brenda,

Sorry - I cannot see any means of uploading a log file so I have pasted it below.

This is the command line (in a .bat file triggered by a Windows Scheduled Task running with local admin user running on Windows Server 2012 R2 64 bit):

sfxcl /TRANSFERTYPE ascii /MOVE /NOPROMPT /RETRYCOUNT 0 /LOG "C:\Files\Live\Logs\SFXCL_LOG__2019-08-28.txt" \\fs\Icon\Exports\rents\hrcash.txt /S "Server" TO_CBH



Log file text (The file DID transfer OK in this example):

2019-08-28 10:20:15, 00001: Session(00000000): sfxcl version 7.3.1.685 (Official Release - December 4, 2014)
2019-08-28 10:20:15, 00001: Session(00000001): Session 00001 established for transfer from Server
2019-08-28 10:20:15, 00001: Session(00000001): SSH2Core version 7.3.0.685
2019-08-28 10:20:15, 00001: Session(00000001): Connecting to *.*.*.*:22 ...
2019-08-28 10:20:16, 00001: Session(00000001): Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT
2019-08-28 10:20:16, 00001: Session(00000001): Using protocol SSH2
2019-08-28 10:20:16, 00001: Session(00000001): RECV : Remote Identifier = 'SSH-2.0-CoreFTP-0.3.3'
2019-08-28 10:20:16, 00001: Session(00000001): CAP : Remote can re-key
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote sends language in password change requests
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote sends algorithm name in PK_OK packets
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote sends algorithm name in public key packets
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote sends algorithm name in signatures
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote sends error text in open failure packets
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote sends name in service accept packets
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote includes port number in x11 open packets
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote uses 160 bit keys for SHA1 MAC
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote supports new diffie-hellman group exchange messages
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote correctly handles unknown SFTP extensions
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote correctly encodes OID for gssapi
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote correctly uses connected addresses in forwarded-tcpip requests
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote can do SFTP version 4
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote uses SHA1 hash in RSA signatures for x.509v3
2019-08-28 10:20:17, 00001: Session(00000001): CAP : Remote x.509v3 uses ASN.1 encoding for DSA signatures
2019-08-28 10:20:18, 00001: Session(00000001): CAP : Remote correctly handles zlib@openssh.com
[GSSAPI/Kerberos trace removed]
2019-08-28 10:20:20, 00001: Session(00000001): The following key exchange method has been filtered from the key exchange method list because it is not supported: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
2019-08-28 10:20:20, 00001: Session(00000001): SEND : KEXINIT
2019-08-28 10:20:20, 00001: Session(00000001): RECV : Read kexinit
2019-08-28 10:20:20, 00001: Session(00000001): Available Remote Kex Methods = diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group-exchange-sha256
2019-08-28 10:20:20, 00001: Session(00000001): Selected Kex Method = diffie-hellman-group14-sha1
2019-08-28 10:20:20, 00001: Session(00000001): Available Remote Host Key Algos = ssh-rsa,rsa-sha2-512,rsa-sha2-256
2019-08-28 10:20:20, 00001: Session(00000001): Selected Host Key Algo = ssh-rsa
2019-08-28 10:20:20, 00001: Session(00000001): Available Remote Send Ciphers = aes128-ctr,aes192-ctr,aes256-ctr
2019-08-28 10:20:20, 00001: Session(00000001): Selected Send Cipher = aes256-ctr
2019-08-28 10:20:21, 00001: Session(00000001): Available Remote Recv Ciphers = aes128-ctr,aes192-ctr,aes256-ctr
2019-08-28 10:20:21, 00001: Session(00000001): Selected Recv Cipher = aes256-ctr
2019-08-28 10:20:21, 00001: Session(00000001): Available Remote Send Macs = hmac-sha2-256,hmac-sha2-512,hmac-sha2-384,hmac-sha1
2019-08-28 10:20:21, 00001: Session(00000001): Selected Send Mac = hmac-sha2-512
2019-08-28 10:20:21, 00001: Session(00000001): Available Remote Recv Macs = hmac-sha2-256,hmac-sha2-512,hmac-sha2-384,hmac-sha1
2019-08-28 10:20:21, 00001: Session(00000001): Selected Recv Mac = hmac-sha2-512
2019-08-28 10:20:21, 00001: Session(00000001): Available Remote Compressors = none,none
2019-08-28 10:20:21, 00001: Session(00000001): Selected Compressor = none
2019-08-28 10:20:21, 00001: Session(00000001): Available Remote Decompressors = none,none
2019-08-28 10:20:21, 00001: Session(00000001): Selected Decompressor = none
2019-08-28 10:20:21, 00001: Session(00000001): Changing state from STATE_EXPECT_KEX_INIT to STATE_KEY_EXCHANGE
2019-08-28 10:20:21, 00001: Session(00000001): SEND : KEXDH_INIT
2019-08-28 10:20:21, 00001: Session(00000001): RECV : KEXDH_REPLY
2019-08-28 10:20:21, 00001: Session(00000001): Changing state from STATE_KEY_EXCHANGE to STATE_READY_FOR_NEW_KEYS
2019-08-28 10:20:21, 00001: Session(00000001): RECV: Remote Hostkey (SHA-1 hash):
2019-08-28 10:20:21, 00001: Session(00000001): RECV: Remote Hostkey (MD5 hash):
2019-08-28 10:20:22, 00001: Session(00000001): SEND : NEWKEYS
2019-08-28 10:20:22, 00001: Session(00000001): Changing state from STATE_READY_FOR_NEW_KEYS to STATE_EXPECT_NEWKEYS
2019-08-28 10:20:22, 00001: Session(00000001): RECV : NEWKEYS
2019-08-28 10:20:22, 00001: Session(00000001): Changing state from STATE_EXPECT_NEWKEYS to STATE_CONNECTION
2019-08-28 10:20:22, 00001: Session(00000001): SEND: SERVICE_REQUEST[ssh-userauth]
2019-08-28 10:20:22, 00001: Session(00000001): RECV: SERVICE_ACCEPT[ssh-userauth] -- OK
2019-08-28 10:20:22, 00001: Session(00000001): SENT : USERAUTH_REQUEST [none]
2019-08-28 10:20:22, 00001: Session(00000001): RECV : USERAUTH_FAILURE, continuations [password]
2019-08-28 10:20:22, 00001: Session(00000001): SENT : USERAUTH_REQUEST [password]
2019-08-28 10:20:22, 00001: Session(00000001): RECV : AUTH_SUCCESS
2019-08-28 10:20:22, 00001: Session(00000001): RECV : Server Sftp Version: 3
2019-08-28 10:20:22, 00001: Session(00000001): SEND : fs-multiple-roots-supported request[On]
2019-08-28 10:20:22, 00001: Session(00000001): SEND : vendor-id request
2019-08-28 10:20:22, 00001: Session(00000001): RECV : fs-multiple-roots-supported reply: 8
2019-08-28 10:20:22, 00001: Session(00000001): SEND : Stat .
2019-08-28 10:20:23, 00001: Session(00000001): SEND : RealPath, base=.
2019-08-28 10:20:23, 00001: Session(00000001): Resolved RealPath: /
2019-08-28 10:20:23, 00001: Session(00000001): Transfer(00000001): SEND : Stat /TO_CBH
2019-08-28 10:20:23, 00001: Session(00000001): Transfer(00000001): SEND : RealPath, base=/TO_CBH
2019-08-28 10:20:23, 00001: Session(00000001): Transfer(00000001): Resolved RealPath: /TO_CBH/
2019-08-28 10:20:23, 00001: Session(00000001): Transfer(00000001): Opening file 'hrcash.txt' for upload as 'hrcash.txt'. (ASCII)
2019-08-28 10:20:23, 00001: Session(00000001): Transfer(00000001): SEND : Open: /TO_CBH/hrcash.txt, mode 0x1a
2019-08-28 10:20:23, 00001: Session(00000001): Transfer(00000001): File transfer completed: 0x00000000.
2019-08-28 10:20:24, 00001: Session(00000001): Transfer(00000001): Destination file closed with error (0xe0000001): Failure


2019-08-28 10:20:24, 00001: Session(00000001): Transfer(00000001): SUMMARY: Attempted to transfer 1 files.
2019-08-28 10:20:24, 00001: Session(00000001): Transfer(00000001): SUMMARY: Transferred 0 files successfully.
2019-08-28 10:20:24, 00001: Session(00000001): Transfer(00000001): SUMMARY: hrcash.txt: Failed to close destination file.
2019-08-28 10:20:24, 00001: Session(00000001): Channel Closed.

Last edited by bgagnon; 08-28-2019 at 08:22 AM. Reason: VMICON.cbc-local.cbc.gov.uk replaced with fs
Reply With Quote
  #4  
Old 08-28-2019, 08:10 AM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 3,976
Hi Dave,

Version 7.3.x is pretty old. I do recall that the file transfer could be logged as failed when it was just due to the failure to close the source file, as you had indicated in prior post.

What problem is this causing you?

Is it the failure exit code?

In version 8.3, we created categories of errors to more closely match what occurred:

Changes in SecureFX 8.3 (Beta 1) -- September 21, 2017
------------------------------------------------------

New features:

  • SFXCL: now returns the following exit codes:
    0 (SUCCESS)
    100 (Network error)
    200 (Source file system error)
    300 (Target file system error)
    400 (General failures)

You can check your SecureFX Update Eligibility here. Or contact the orders team directly (orders@vandyke.com) and they can check your serial number to see if it's been upgraded.
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
  #5  
Old 08-28-2019, 08:17 AM
DPCotswold DPCotswold is offline
Registered User
 
Join Date: Aug 2019
Posts: 3
Thanks - I will check our upgrade position...

Thanks Brenda,

I will check our availability for upgrade. It would be useful to be able to trap the actual error if possible.

Generally this false failure doesn't cause an issue (because the file is actually transferred) but on one occasion it actually failed to transfer so I could do with knowing the exit code so that I can generate an alert.

If that requires a version update then i'll need to go down that route.

Thanks for your assistance and time.

Dave
Reply With Quote
Reply

Tags
0xe0000001 , failure


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 08:26 PM.