Veeam Support Knowledge Base
Veeam ONE Web Client Page Fails to Load After Updating .NET Runtime Components

Veeam ONE Web Client Page Fails to Load After Updating .NET Runtime Components

KB ID:	4545
Product:	Veeam ONE \| 11 \| 12 \| 12.1
Published:	2024-01-30
Last Modified:	2024-05-02

By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please, try again later.

.NET Version Requirements

Veeam ONE build 12.1.0.3208 requires and supports only .NET 6.0. All three component versions must match.

ASP.NET Core Runtime 6.0.x
^{Microsoft ASP.NET Core 6.0.x - Shared Framework (x64)}
.NET Desktop Runtime 6.0.x
^{Microsoft Windows Desktop Runtime - 6.0.x (x64)}
.NET Runtime 6.0.x
^{Microsoft .NET Runtime - 6.0.x (x64)}

For example. removing 6.x .NET components and installing 7.x or 8.x .NET components will cause the Veeam ONE services to fail to start.

Challenge

After updating .NET Runtime components, the Veeam ONE Web Client page fails to load with either of the following errors:

Error Failed to connect to Veeam ONE Server

This page isn't working
<server> is currently unable to handle this request.
HTTP ERROR 500

Cause

These issues may occur after .NET runtime components have been updated, either because the Veeam ONE Reporting Service has not been restarted or because the Veeam ONE Reporting Service is stopped and cannot be started because not all .NET runtime component versions match.

Solution

Check Installed .NET Runtimes

Use the following command to check which versions of the .net runtime components are installed:

dotnet --list-runtimes

Matching .NET Runtime Versions

If all .NET Runtime components are the same version, as shown in the example below, restart the Veeam ONE Reporting Service. The issue should then be resolved. If not, create a case with Veeam Technical Support.

Example of matching .net runtime components.

Mismatched .NET Runtime Versions

If .NET Runtime components are running different versions, update the older ones so all versions match. Then start the Veeam ONE Reporting Service. The issue should then be resolved. If not, create a case with Veeam Technical Support.

Example of mismatched .net runtime components.

In the mismatched version example above, the solution is to install version 6.0.26 of .NET Desktop Runtime and .NET Runtime to match the ASP.NET Core Runtime version.

.NET 6.0 Downloads

Name in Add/Remove Programs	Name on .NET Website	dotnet Command Name
Microsoft ASP.NET Core - Shared Framework	ASP.NET Core Runtime	Microsoft.AspNetCore.App
Microsoft Windows Desktop Runtime	.NET Desktop Runtime	Microsoft.WindowsDesktop.App
Microsoft .NET Runtime	.NET Runtime	Microsoft.NETCore.App

Swipe to show more of the table

When .NET runtime components are mismatched, Event 1023 will appear in the Event Viewer's Application log. The Event Properties will describe what components need to be updated and provide a download link to the version required.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.