We are seeing a similar issue recently with v12.2.9. Upgraded to v12.2.11 and the same issue occurs along with a new issue with emailing the backup results.

11/3/2019 4:13 AM Destination error: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
11/3/2019 4:16 AM Destination error: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

This email error started after upgrading to v12.2.11 (the addresses were modified for privacy)
11/3/2019 4:17 AM Can’t send email to admin@xxxxx.xx: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
11/3/2019 4:17 AM Can’t send email to support@xxxxx.xxx: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

Hello, We have the same issue, though intermitantly. We’re not using a proxy and our backup destination is a local drive. Internet connection test works fine.

06/11/2019 00:48:31

[Error]

Destination error: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

06/11/2019 00:51:31

[Error]

Destination error: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

Any easy way to fix this so backups are more reliable?
Thanks in advance

Thank you for your log, we have checked it, but there is no error message. Could you please make sure that the issue is reproduced before the log will be sent. Also please provide us with your Application ID (“Help” > “About”) to identify it.

ERROR: Destination error: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

we’re facing the same issue. After update from SQLBackupAndFTP (SBF) v10.x.x to v12.2.11 job fails each day and we changed nothing in network configuration.

Details (all steps here are carried out by SBF):

we’ve got a job backingup ~190GB MS SQL database, full backup

backup is downloaded on backup server where SBF is installed

file is then compressed (actually just splitted due to another issues in SBF software I’ve already reported, but that was the reason I’ve updated SBF version) which creates 3 volumens 01 (58,6GB), 02 (58,6GB), 03 (47,4GB)

next we try to upload them on 2 destinations (local drive and Amazon S3)

upload on local drive fails due to timeout error

remove from local drive fails due to timeout error

anything related to the local drive fails but it used to work each time before update to new SBF

next, S3 upload and cleaning ends without any error (thanks to split into volumes)

My co-worker told me “in previous version there was some kind of a timeout setting, now it dissapeared”.

Steps order also seems to be strange:

uploading 001 on local drive

uploaded 99,7%

deleting 001 from local drive (???)

ERROR: timeout destination

uploading 002 on local drive

ERROR: timeout delete 001

Log:
• 3:07:09 PM : The current destination folder is “E:\abc\Backups”
• 3:07:09 PM : Sending backup of “abc_FileStore” to Folder destination “E:\abc\Backups”
• 3:07:09 PM : Uploading local “abc_FileStore201912151215.7z.001” to remote “abc_FileStore201912151215.7z.001” in folder “E:\abc\Backups”
• 3:23:38 PM : Uploaded 99.07 % (average speed = 60.1 MB/s)
• 3:15:32 PM : Deleting file “abc_FileStore201912151215.7z.001”
• 3:21:32 PM : ERROR: Destination error: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
• 3:12:32 PM : Uploading local “abc_FileStore201912151215.7z.002” to remote “abc_FileStore201912151215.7z.002” in folder “E:\abc\Backups”
• 3:18:32 PM : ERROR: Failed to delete file “E:\abc\Backups\abc_FileStore201912151215.7z.001”: This request operation sent to net.pipe://localhost/pranasnet/net/sbf/Trace/Net.pranasnet.sbf.Trace did not receive a reply within the configured timeout (00:03:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
• 3:23:43 PM : Connecting to Amazon S3 destination “xyz-abc”