Microsoft .net 6.0 Runtime X64

0 views
Skip to first unread message

Ronald

unread,
Aug 5, 2024, 12:21:22 AM8/5/24
to onlyterib
Ithink there must be some issue with how I've configured IIS, the sites, or the application pools, but as best I can tell there isn't any difference. If anyone has encountered this, I'm all ears for suggestions.

To be more specific, my problem was that I accidentally installed just the runtime instead of the hosting bundle. I assumed the "x64" link in the picture below would download an x64 version of the bundle, but it does not.


I was getting the same error messages for a new .NET Core 3.1 framework-dependent web app on an IIS server which was already hosting other .NET Core 3.1 framework-dependent web apps with no problem. The messages in Event Viewer were slightly different; but also very hard to find - sometimes I couldn't see any events which seemed to relate.


In the AppPool's Advanced Settings, there is an "Enable 32-Bit Applications" setting, which IIS considers the default to be False; but on mine was True. Toggling this setting caused the site to work and fail, when False and True, respectively.


Using the tool suggested (and created) by @LexLi I was able to determine the issue was caused by the application pool not having permissions to the site folder. Giving it permissions fixed the issue. This was not clear from the error messages. Answered here in case anyone else experiences the same error message.


For me, I had to install both .NET 5 and .NET Core 3.1. Some folks here were suggesting to download 3.1 (my app is targeting 3.1) but when I go to the Microsoft site it "recommends" the latest which at the time of this post is 5.0 ( ).


I had this issue on production after few days of deployment. Suddenly stopped working with the error (HTTP Error 500.31 - Failed to load ASP.NET Core runtime). In my case, I just repaired the installed version and it worked.


In my case the problem was the IIS server had the required version Microsoft.AspNetCore.App 5.0 and when I ran the dotnet cmd I noticed that it only had Microsoft.AspNetCore.App 6.0 installed.I found the required version of Microsoft.AspNetCore.App on the IIS server by consulting the deps.json file.


I'm now moving a site to another server so in the process of setting up the new server to host the website I came across this issue. I like another user above thought that the latest supported versions of .Net6 or .Net7 where downward compatible, which it is not having following this thread.


Would also like to point out that even the latest version may not be compatible with the targeted framework as well. So I initially tried using 5.0.17 (latest version of .NET5) and was still having the same issue. I was able to resolve this issue by installing the 5.0.4 version. At the time, the website was built using NET 5.0 framework.


For me, I needed to install a newer release of .net 6 hosting bundle. I had recreated the project with a higher .net6 release after another error but the server was using an earlier version of .net6 hosting bundle.

3a8082e126
Reply all
Reply to author
Forward
0 new messages