Failed to connect to the Veeam Updater service

[m.novelli]

Hi guys, I've started to update some customers from v12.3 to v13.1 and after update I'm getting for all customers this email warning next morning

[VBR-SERVERNAME] Failed to synchronize update settings. Error: Failed to connect to the Veeam Updater service

I can see that the "Veeam Updater Service" is running

Is this an know bug? I can't find nothing in forums

Ciao ciao

Marco

[Mildur]

Hi Marco,

Please contact our Customer Support team.

The forums is not the place for asking about known issues, since the people behind the forum are not part of the Support department. Our Support team is fully aware of any current known issues.

Please provide a support case ID for this issue, as requested when you click New Topic. Without a case number, the topic will eventually be deleted by moderators.

Best regards,
Fabian

PS: Support can only help if you upload logs: https://www.veeam.com/kb1832

[m.novelli]

Case # 08225792

[m.novelli]

Confirmed to a be a known bug since v13.1

One more "FAILED" thing to ignore across all customers and products

"This a known problem at Veeam, it started appearing in 13.1. It's a cosmetic issue caused by a reboot of the VBR server within a 24-hour window.

We plan to fix that in a future version, it's unclear yet in which one exactly, I do not have a specific date to share with you. We opted to not hotfix it, as we treat it as a cosmetic issue with no impact - and hotfixes sometimes complicate the update path for our customers.

It may come with 13.2 but I can't 100% confirm that today. Right now, no workaround other than ignoring it."

Marco

[Woegerbaeur]

Hi everyone,

I already opened a support case about this before (Case #08202633), but I closed it because I thought it was a one-time problem. The emails stopped for several days after that. But now the problem is back.

Since updating to Veeam Backup & Replication 13.1.1.18, we've been getting emails from the "Software Update Summary" with an error, across several customer installations.


The strange part: it runs completely fine for several days (Status "Success", Sync "Success"), and then suddenly on one day it flips to "Error", sometimes at multiple customers at the same time. The days later it goes back to working normally without any changes on our end.



What we've already ruled out:

Firewall/network: Can't be the cause, since the connection works fine on other days.
Reboots: No server reboots occur at 22:00 (the job's scheduled time) on the affected days that could interrupt the Updater service.

Has anyone else observed this since 13.1?
Is this a known issue/bug in 13.1.1.18?
Does anyone have an idea what might be causing it?

Thanks in advance for your help!

[d.artzen]

Hi Florian,
I see the same in our environment, but always only after the VBR Server was rebooted.
There is a topic here describing this issue: veeam-backup-replication-f2/failed-to-c ... 04401.html
If I understand correctly this is a cosmetic issue and there is currently no fix.

Best regards
Daniel

[vnikiforov]

Hello, Florian,

Please find the answer above, that is know cosmetic issue which will be fixed in future versions.

[m.novelli]

It will be a mass mailing event after every monthly Windows Update and subsequent reboot of the Backup Server...

Marco