#1 Global Leader in Data Protection & Ransomware Recovery

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-01-30
mailbox
Get weekly article updates
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

error icon

Oops! Something went wrong.

Please try again later.

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
Failed to connect
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.

Match
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.

mismatched runtime versions
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 (Microsoft.WindowsDesktop.App) and .NET Runtime (Microsoft.NETCore.App) to match the version of ASP.NET Core Runtime (Microsoft.AspNetCore.App) version.
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.
Event Log
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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

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

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
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!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.