0

An instance of a BizTalk send pipeline has started to run continuously. On 09/12/2021 an attempt was made to send a file via SFTP, which retried several times but ultimately failed due to a network issue. The error from the event logs is:

The adapter failed to transmit message going to send port "Deliver Outgoing - SFTP" with URL "sftp://xxx.xxxxxx.co.nz:22/To_****/%SourceFileName%". It will be retransmitted after the retry interval specified for this Send Port. Details:"WinSCP.SessionRemoteException: Network error: Software caused connection abort.

For some reason BizTalk made another send attempt at 1:49pm on 10/12/2021 which succeeded as confirmed by the administrator of the SFTP site. Despite this, BizTalk continued making intermittent send attempts and the pipeline instance is still running. The same file has been sent 4 times to the SFTP server.

The pipeline instance in theory should have suspended at 9:47pm on 09/12/2021. I have been able to confirm definitively whether anybody resumed it, but it seems unlikely at this stage. In any case, after sending successfully the pipeline instance should have terminated and should not be re-executing intermittently.

Does anybody know what could account for this behaviour? This is occurring on BTS2020 with CU2 applied.

enter image description here

Batperson
  • 145
  • 2
  • 7
  • That is very odd, never seen that behaviour before. Is the instance still in a running state? – Dijkgraaf Dec 14 '21 at 03:47
  • I terminated the instance, because it seemed likely to send more copies of the file. But since it stayed in a running state for over 36 hours, it likely would still be running if I hadn't done that. – Batperson Dec 14 '21 at 04:26
  • The send port didn't have ordered delivery enabled? That is usually the only time that an instance keeps running until you restart the host instance or terminate it. But even then, it should resend a message that has been successfully sent. – Dijkgraaf Dec 14 '21 at 06:42
  • It doesn't have ordered delivery. It's just a standard send port using the BizTalk out-of-box SFTP adapter. – Batperson Dec 14 '21 at 21:54

1 Answers1

0

I've sent messages over SFTP where the WinSCP interpretation of the date-modified attribute doesn't work with a specific type of SFTP server.

With the WinSCP GUI a dialogue box appears and you can disregard this error, but this option isn't available with BizTalk's GUI. This error appears when a file with the same filename already exists on the server and is supposed to be overwritten.

My solution was to create a pipeline component that removed %SourceFileName% on the server. The pipeline component (just like WinSCP GUI) can disregard the modified-date.

Jonas Grundén
  • 1
  • 4