Skip to main content
Question

Error After Upgrade to 13.1. Failed to connect to the Veeam Updater Service

  • August 27, 2026
  • 4 comments
  • 22 views
F

I just upgraded Veeam B&R from 12.3 to 13.1 and everything appears to have gone smoothly, with all components being upgraded without issue. The only problem we have is that we are notified each morning with a Software Update Summary email that our Veeam server ‘VBR’ Failed to synchronize update settings. Error: Failed to connect to the Veeam updater service.

I was wondering if anyone is familiar with this error and how to resolve? Going through some steps online, I have verified the Veeam Updater service is running, backups are working, SQL connectivity and internet/DNS is working. Tried restarting service as well as a server reboot. Only the scheduled update-settings sync task is failing.

My next step was going to be mounting the ISO and trying to repair the program, but wondering if anyone may know how to resolve this before I go that route. Everything else seems to be working just fine, so hoping to avoid a full reinstall. Thanks!

    4 comments

    Chris.Childerhose
    Forum|alt.badge.img+22
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • August 27, 2026

    Based on your issue I am going to assume you have a Windows VBR server.  It is hard to say what is causing this.  Are you on 13.1.1.x now which was a patch released last week, I think?

    The VSA works much better for this process as I know the Updater for Windows piece is new.  You might need to check the logs - C:\ProgramData\Veeam and see; otherwise I might suggest a support ticket to get this resolved faster.

    Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
      F
      • Flinktron
      • Author
      • Comes here often
      • August 27, 2026

      Thanks Chris! I was able to get more specific info looking at the Veeam Updater logs. I pasted those errors below. I will research these errors, and if that leads me nowhere I’ll open a support ticket. 

      Log error:  Failed to run app
      System.AggregateException: One or more errors occurred. (Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host..)

      System.AggregateException: One or more errors occurred. (The read operation failed, see inner exception.)

        Chris.Childerhose
        Forum|alt.badge.img+22
        • Chris.Childerhose
        • Veeam Legend, Veeam Vanguard
        • August 27, 2026

        Best of luck it will be hard based on those errors and support would be the ideal way. Let us know what they say if you go that route.

        Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
        coolsport00
        Forum|alt.badge.img+23
        • coolsport00
        • Veeam Legend
        • August 27, 2026

        That doesn’t give me confidence in upgrading my environment. I was going to do one of VBR servers … 12.3 > 13.1 , but man...if all it does is error during upgrade, I don’t know. Seeing several posts on upgrade issues this week 😒 Curious what Support says...

        Shane Williford - Veeam VMCA/VMCE+ | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
        Terms & ConditionsAccessibility statement