HTTP Error 500

Auf dieser Seite

There are many different HTTP Error 500 types, each with their own solution(s). This topic contains the most commonly encountered:

500.19 - Internal Server Error

When trying to load the Devolutions Server web page, the following HTTP Error 500.19 - Internal Server Error is displayed in the browser: HTTP Error 500.19 - Internal Server Error

This error is due to the absence of the IIS ASP.NET Core Module (ANCM) and/or the IIS Rewrite Module: IIS features diagnostic

Solution

  1. From the Devolutions Server Console, edit the instance.

  2. Select the IIS tab.

  3. Click on IIS diagnostic.

  4. Click on Install prerequisites. Install prerequisites

If running the PowerShell script from the Devolutions Server Console is blocked due to restrictions on the system, the script is located in the Scripts folder of the Devolutions Server Console installation folder.

500.30 – Enable the data source TrustServerCertificate option

Most of the time, Devolutions Server returns this 500.30 error when a SQL server (Azure or local) is configured with a self-signed certificate not found in the certificate store.

Solution

In File – Data sources, choose the data source experiencing the 500.30 error. Then go to Edit data source – Advanced and set the TrustServerCertificate to true.

Set TrustServerCertificate to true
Set TrustServerCertificate to true

500.30 - ASP.NET Core app failed to start

Following the upgrade process, when trying to open the Devolutions Server web page, the browser displays HTTP Error 500.30 - ASP.NET Core app failed to start. HTTP Error 500.30 - ASP.NET Core app failed to start

Solution

Verify that Enable 32-bit applications is set to False in the Devolutions Server application pool's Advanced settings in IIS Manager. Enable 32-bit applications set to False

If Enable 32-bit applications is already set to false, ensure that the service account designated as the Application pool identity in the Devolutions Server application pool has enough rights on the App_Data subfolder in the Devolutions Server web application folder.

Make sure that the APS.Net Core Hosting Bundle installed on the server where Devolutions Server is hosted is the latest version.

500.31 - Failed to load ASP.NET Core runtime

When updating Devolutions Server to version 2024.1 or later, the web UI displays HTTP Error 500.31 - Failed to load ASP.NET Core runtime. The reason is that the ASP.Net Core version 8.0.x is not installed on the server where Devolutions Server is hosted. HTTP Error 500.31 - Failed to load ASP.NET Core runtime

Solution

  1. Update the Devolutions Server Console to version 2024.1.x or later.

  2. Download the ASP.Net Core Module 8.0.x hosting bundle.

  3. Install it on the server where Devolutions Server is hosted.

Contact our customer support technicians at service@devolutions.net if these solutions do not solve your problem.

Devolutions Forum logo Give us Feedback