Veeam Backup Service did not start after the Windows Server upgrade

//Veeam Backup Service did not start after the Windows Server upgrade

Veeam Backup Service did not start after the Windows Server upgrade

This week had it a strange error in at least 3 Veeam Servers. Veeam Backup Service did not start after the Windows Server upgrade, and it was not possible to start or fix the issue.

These three Veeam Server was running with Windows Server 2012 R2, and I needed to upgrade to Windows Server 2016.

So backup the Veeam Servers and start the Windows upgrade. After the upgrade finish run Windows updates and after the last reboot, try to run the Veeam Backup Server and error.

Veeam Backup Service did not start after the Windows Server upgrade

Checking Veeam services, I notice that most of them were down, and I was not able to start manually.

Veeam Backup Service did not start after the Windows Server upgrade

Checking the Windows events I saw this: Could not load type System.ValueTuple”2” from assembly ‘mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.

Veeam Backup Service did not start after the Windows Server upgrade

Is the first time I saw this error, and honestly, I did not know what is regarding.

Next is to check the Veeam Backup Service logs, that is located in: C:\ProgramData\Veeam\Backup\Svc.VeeamBackup.log

Honestly, I needed to google to know what this Could not load type System.ValueTuple”2”, and I found out that it is regarding Microsoft.NET Framework. Somehow during the upgrade, the Microsoft.NET Framework was corrupted and had mixed versions.

This is the first time I saw this type of error, I honestly didn’t know what it was referring to.

Download the latest Microsoft.NET Framework.

So I just downloaded the latest version 4.7.2 for Windows Server 2016 and installed. You can download it from Microsoft Site and install it.

The offline version is: NDP472-KB4054530-x86-x64-AllOS-ENU.exe

Install Microsoft.NET Framework.

In two of the Veeam Servers, installation did not recognize any Microsoft.NET Framework installed and did a fresh install.

In one Veeam Server, it recognizes that it was installed, and I just did a repair.

After install/repair Microsoft.NET Framework, I reboot the server, run Windows update again in case there are new updates for Microsoft.NET Framework, and all Veeam Backup Services were back to the started state.

I did not know what case this, but I know it is not a Veeam issue but instead a Windows issue. But since Veeam Server needs Microsoft.NET Framework, it was not able to start the services (particularly initialize the license manager).

I hope this blog post is useful if you have encountered this issue when upgrading your Veeam Servers.

Share this article if you think it is worth sharing. If you have any questions or comments, comment here or contact me on Twitter.

©2020 ProVirtualzone. All Rights Reserved
By | 2020-06-30T15:59:09+02:00 June 30th, 2020|VMware|0 Comments

About the Author:

I am over 20 years’ experience in the IT industry. Working with Virtualization for more than 10 years (mainly VMware). I am an MCP, VCP6.5-DCV, VMware vSAN Specialist, Veeam Vanguard 2018/2019, vExpert vSAN 2018/2019 and vExpert for the last 4 years. Specialties are Virtualization, Storage, and Virtual Backups. I am working for Elits a Swedish consulting company and allocated to a Swedish multinational networking and telecommunications company as a Teach Lead and acting as a Senior ICT Infrastructure Engineer. I am a blogger and owner of the blog ProVirtualzone.com

Leave a Reply

%d bloggers like this: