-
Notifications
You must be signed in to change notification settings - Fork 60
ASP.NET Core 2.1.1 fails with HTTP Error 502.5 - Process Failure #945
Comments
Please follow the troubleshooting steps and let us know if you still have an issue: |
I had the same exact issue. |
-Open Command Prompt |
I had the same issue after installing the hosting package. The fix was much simpler for me. Just running IISRESET resolved it. |
I added the following line in the csproj and it started working. All troubleshoots suggested by @Tratcher did not help me at all because of misleading information
|
I just update my dotnet sdk core version in global.json file with installed dot net version, and my project start working C:>dotnet --version global.json{ |
This answer is really helpful - only "Run 'dotnet .\test.dll'" should be "Run 'dotnet .\NameOfYourMainApplication.dll'" (obviously "NameOfYourMainApplication" is a placeholder for the name of your application DLL ;-) Also, I personally found it easier to upgrade the .netcore runtime than doing another build and uploading it to my server. I guess after each Visual Studio update, you should probably check this URL and upgrade your server, if a new version is available: .NET Core 2.1 downloads Eventually, you'll move to .NET Core 2.2 and that's simply "2.2" at the end of the URL: https://www.microsoft.com/net/download/dotnet-core/2.2 I'm leaving this here for others and my future self when I run into a broken Web app update process during the next crunch mode when the last thing I have time for is following useless "troubleshooting" guides. PS: Ah, even better is this URL: .NET download archives (https://www.microsoft.com/net/download/archives) |
This happens for me when I create a new .NET Core Web project with AngularJS and publish to Azure. All else I have done is to add Application Insights. The site loads like it should in IIS Express with Chrome (IE does not work, don't know why). 2.1.402 |
@estomagordo have you tried the self-contained deployment? This worked for me. |
@rpawlaszek yes, eventually I noticed someone mentioned this. And it worked. Thanks. |
Happens for me when on a .NET Core Web / Angular 6 App Runs locally just fine, getting the 502.5 of death when I publish, here's what I've tried:
trying to read through to see if i missed something... |
In the release folder:
Could the last line be throwing it off? If so, how to update? the package is blocked by nuget |
@adamcweitzman, could you check your nuget version? |
maybe i need to manually set the path? in my runtime.config in \bin I still have the correct version |
I meant the version of nuget you use. I had no problem with installing the 2.1.5 version of Microsoft.AspNetCore.App. Go to powershell and simply type in 'nuget' |
4.6.0 |
the app service running the site is 2.1.403 any idea how to roll that back? |
The version I have installed is 4.8.1 Could you try with this one? And another thing: what is the environment you have set for the self-contained deployment? (mine: win-x86) |
Got same error on a VM hosted on Azure with IIS, the self-contained deployment seems to fix this issue for me for now. |
I deployed an app to IIS in an Azure VM (which worked), came back to it after a few hours and it started showing this error. |
I had the same issue! The dotnet Core version of Visual Studio and server didn't match. This solution also works: Hope it helps |
Hello,
After upgarding my project from .NET CORE 2.0 to .NET CORE 2.1, and upgraded all microsoft packages to 2.1.1. With updated visual studio to 15.7.4, .NET CORE 2.1 sdk(V2.1.3) and .NET CORE 2.1 runtime(V2.1.1) installed i am getting this error when i try run my app.
The text was updated successfully, but these errors were encountered: