Comprehensive data protection for all workloads
Post Reply
m.novelli
Veeam ProPartner
Posts: 644
Liked: 179 times
Joined: Dec 29, 2009 12:48 pm
Full Name: Marco Novelli
Location: Asti - Italy
Contact:

Failed to connect to the Veeam Updater service

Post by 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
Ciao,

Marco
Mildur
Product Manager
Posts: 12231
Liked: 3513 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Failed to connect to the Veeam Updater service

Post by 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
Product Management Analyst @ Veeam Software
m.novelli
Veeam ProPartner
Posts: 644
Liked: 179 times
Joined: Dec 29, 2009 12:48 pm
Full Name: Marco Novelli
Location: Asti - Italy
Contact:

Re: Failed to connect to the Veeam Updater service

Post by m.novelli »

Case # 08225792
Ciao,

Marco
m.novelli
Veeam ProPartner
Posts: 644
Liked: 179 times
Joined: Dec 29, 2009 12:48 pm
Full Name: Marco Novelli
Location: Asti - Italy
Contact:

Re: Failed to connect to the Veeam Updater service

Post by m.novelli » 1 person likes this post

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
Ciao,

Marco
Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Google [Bot] and 29 guests