Comprehensive data protection for all workloads
Post Reply
nate.cottrell
Novice
Posts: 6
Liked: 1 time
Joined: Jan 13, 2015 8:14 pm
Full Name: Nate Cottrell
Contact:

Error after update to Veeam Backup & Replication 11.0.1.1261 P20211211

Post by nate.cottrell »

Support case number is 05240187

After updating to the latest version I see an alert of missing update. When clicking the missing update I receive the error of

Code: Select all

---------------------------
Veeam Backup and Replication
---------------------------
Type 'Veeam.Backup.DBManager.CUpdateNotificationsDbScope+d__3' in Assembly 'Veeam.Backup.DBManager, Version=11.0.0.0, Culture=neutral, PublicKeyToken=bfd684de2276783a' is not marked as serializable.
---------------------------
OK
---------------------------
A screenshot of the error can be found at https://drive.google.com/file/d/1bj7Lng ... sp=sharing
wishr
Veteran
Posts: 3077
Liked: 453 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Error after update to Veeam Backup & Replication 11.0.1.1261 P20211211

Post by wishr »

Hi Nate,

Let's wait for our customer support engineers to review the details and determine the root cause.

P.S. Please make sure that all the debug logs are collected and uploaded to the case.

Thanks
nate.cottrell
Novice
Posts: 6
Liked: 1 time
Joined: Jan 13, 2015 8:14 pm
Full Name: Nate Cottrell
Contact:

Re: Error after update to Veeam Backup & Replication 11.0.1.1261 P20211211

Post by nate.cottrell »

I am using community edition of Backup & Replication. Case #05228596 was auto closed after 7 days as support did not respond, so I have created a new case.

Are you able to nudge the customer support engineers to look into my issue?
wishr
Veteran
Posts: 3077
Liked: 453 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Error after update to Veeam Backup & Replication 11.0.1.1261 P20211211

Post by wishr »

According to our support policy, technical support for free Veeam products is provided on the "best-effort" basis, based on staff availability, so there is always a chance that a case will be closed, for example, due to high load. In such situations, you may open another one or try to fix the issue on your own.

Upd: I've spoken to our QC team about this issue. The described behavior looks unexpected and we'll take a look at it on our end. Thanks for the heads up.
Post Reply

Who is online

Users browsing this forum: Google [Bot], olafurh and 112 guests