Wasabi

Support claims the issue relates to DNS specifically larger EDNS queries failing but I'm not seeing it fail in any other application OR in any identically configured network.

I even tried disabling EDNS on the server, changing DNS servers and it still doesn't work

So much for community support.

Support suggested the issue is with my cloud storage provider DNS but that isn't a configurable option as far as I can tell when you set it up.

Is it possible to remove the storage configuration in MSP360 and then re-add it as S3 compatible and point to the same bucket? They suggest this as a workaround but I'm skeptical as they have suggested a dozens reason why this isn't a bug.

US east

Same problem here, still no solution. Tried all workarounds suggested by MSP360 and it still isn't working.

Upgraded to 7.9.4.103, checked anti-malware and network rules and verified these are correct. Still getting the same error:

An error occurred (code: 1003)
The underlying connection was closed: An unexpected error occurred on a send.

Any ideas?

I do this entire folder C:\Program Files (x86)\CloudBerryLab\

Looks like in the logs:

2024-03-25 22:00:12,724 [Base] [1] ERROR - Request failed, retrying in 400 msec, 3 attempts left
2024-03-25 22:00:13,125 [Base] [1] ERROR - CloudBerryLab.Base.Exceptions.RequestWasAbortedException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Looks like a bug to me as it only started after upgrading to

Support suggested I increment the connection tries in >> Tools - Options - Connection. I will try tonight and let you all know.

Seems like it could be related to a network issue in the code itself like detailed here https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/tls-exist-connection-closed but I need to dig deeper.

I'm guessing you are on MSP360 latest 7.9.4.83 ? I started seeing error code 1003 once I upgraded.
https://kb.msp360.com/backup/errors/1003

Looks like it may relate to what you are experiencing as well. Support has said they are seeing a LOT of connection issues w/ the latest release. Hopefully, they will fix these bugs.

I'm seeing the same error code 1003 since upgrading to 7.9.4.83 on W2K16/19 servers.

Time is correct on my servers and I'm still seeing this error. Must be something else I'm missing...