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

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.

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.)

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.

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...

We have the same issue after upgrading to the latest Version. Have not find a solution yet, hence it would be great if you keep us posted.

Are you sure this isn’t cosmetic? I get an error email daily with:
“Failed to synchronize update settings. Error: Failed to connect to the Veeam Updater service”

but at drive://ProgramData/Veeam/Updater/Logs/updater.txt I don’t appear to actually have any errors. The service is running fine, and my firewall logs don’t appear to be blocking any traffic.

This should not be a “cosmetic” message as Veeam does try to sync update settings.

No, I agree and understand. I suddenly had this appear in the last 24 hours. I have been on v13.1 for a few weeks with zero issues. I have no logs or indication that it actually did fail. That or I haven’t found the needle in a haystack log yet.

Ah, gotcha.  Are you on the latest patch for 13.1 by chance?  Wondering if that resolved the issue maybe??

Seems like something to be reported to Support or check the Forums perhaps to see - https://forums.veeam.com 

I am not entirely sure, but I can say I am on v13.1.0411 and have not committed an update since install early August. I did however apply some Windows updates on this box.
 

I do have an alarm in VOne that says I am having issues with “Veeam B&R server data Collection delay” which is odd and only appeared after the updates and is alongside the service issues described by OP.

There is a 13.1.1.18 update (Day 0 Patch) that came out which you can get here - KB4738: Release Information for Veeam Backup & Replication 13 and Updates

I also just within the past 2 days updated many Veeam servers in our environment to v13.1.1.18 and woke up this morning to this same error “Failed to synchronize update settings. Error: Failed to connect to the Veeam updater service”. The only thing that has changed is applying the update, as far as I can see nothing is actually failing and logs are showing any hints so far. Still looking for a solution but wanted to note this is also happening here after latest v13 update

thanks for your input! Are you having a similar error in VeeamOne (if you use it) about backup server data collection delays? I’m trying to rule it out as an internal issue. thanks!

​@Chris.Childerhose - that’s for VBR; I think you meant to provide the one for VeeamONE?

https://www.veeam.com/kb4905

No, because the thread is about VBR, so I assumed this when posting the link.

I have seen the delay issue, and I am working to resolve it but only on one VBR server.  It could be network related possibly so working with my network team.

Ah, ok.. I saw the previous comment on VONE & “assumed” for that 😉

We do not currently have Veeam One deployed unfortunately so I cannot comment there sorry!

If that is the case it could be another issue altogether, maybe.  There is the Day 0 Patch for that too.

Thanks all… I am going to get to updating 😅

Hopefully, it resolves the issues, but I think the updater piece with Windows is new and probably will have kinks to work out. 🫣

Support resolved my issues by having me generate a new self signed TLS certificate from within Veeam B&R options. Certificate regeneration is the documented workaround for this specific 503 signature.

I did that yesterday, and this morning I did not receive any failed software updates summary so I assume the issue is now resolved.

I still have a backup of our VBR server failing every day since the upgrade, so I am also inquiring about that before closing my case. That error is “failed to finalize guest processing. Error: Failed to create new binary file. Win32 error: the system cannot find the path specified. Code 3.“

Great to hear you got the software update issue fixed, and it was as simple as a new cert.  Keep us posted on the other issue.