"Remote Name Could Not Be Resolved" Error
  • SamboNZ
    0
    I have a computer running a continuous backup (15min Intervals).

    I am receiving the following error from it almost daily:
    An error occurred (code: 1003)
    The remote name could not be resolved: 'bucket.s3.us-west-1.wasabisys.com'
    or
    An error occurred (code: 1003)
    The network path was not found

    I believe that this may be happening during OS shutdown, although I have yet to confirm this.

    I often also get the following error at the same time, or instead of the first error:
    Terminated Abnormally (code: 1023)
    The plan was interrupted abnormally

    This has only started happening since the 30th of Jan 2024 and there were no changes to the software or backup plan at the time (to my knowledge).

    Anyone know what might be going on here?
    SamboNZ Options
  • Alexander Negrash
    30
    Hello Sam,

    I have sent you an email with our engineer in cc. Most likely we will need logs to investigate.
    Alexander Negrash Options
  • WillC
    0
    Same issue this week. Was there a solution? Tried the other things in support.
    WillC Options
  • evit
    1
    Same problem here, still no solution. Tried all workarounds suggested by MSP360 and it still isn't working.
    evit Options
  • SamboNZ
    0
    Sorry, didn't see the responses until now.

    In the end the problem was the computer going to sleep during a backup and then when waking up, freaking out because it couldn't get to the network for a few seconds.

    The solution was basically under 'Options / Connection' increase the number of retries and or the time between retries to something a bit longer. I set it to 30sec in total (number of retries x time between retries).

    This fixed it for the most part, although I do occasionally get the same error for some reason; but it's way better than it was.
    SamboNZ Options
  • SamboNZ
    0
    Just a quick follow-up to this.

    I recently discovered another problem which was contributing to this issue; there was an Internet router DNS issue which was preventing correct resolution of the Wasabi storage DNS name.

    I think in the end, the problem was a combination of the sleep issue and the router DNS issue.
    SamboNZ Options
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment