This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 66%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELW%3C/text%3E%3C/svg%3E)
Hi there,
We had a software app developed back in 2017 that suddenly stopped working a few days ago. I viewed the Application Event Logs and, on 9/1/2023, errors started getting logged which state the following:
Application 'MACHINE/WEBROOT/APPHOST/MYAPP' with physical root 'C:\home\site\wwwroot' failed to start process with commandline 'dotnet .\MyApp.dll', ErrorCode = '0x80004005' : 80008096.
I checked the nuget packages and saw that they are all deprecated. These packages include:
Microsoft.AspNetCore v1.1.0 and Microsoft.NETCore.App v1.1.2
There are updates available for all deprecated packages except for Microsoft.NETCore.App.
Can anyone tell me a possible reason why the app suddenly stop working? Are the deprecated packages to blame?
Any advice or guidance would be greatly appreciate!
Liz
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 24%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETW%3C/text%3E%3C/svg%3E)
Hi Liz, in your scenario, we'd better to try to collect the error message so that we could try to locate the issue. Could you please run the dll with dotnet command manually and see if there's any exception or error message in the command window?
Thank you for the quick response. I ran the dotnet with the dll locally on my PC and it worked fine. The app is hosted in an App Service Plan. Is there a way to connect to the virtual machine and run the dotnet command? (I think that's what you were suggesting)
Thank you very much for your kind reply. In my humble opinion, it's impossible to say a working-well app to stop working suddenly. And even if we were using some deprecated packages. Deprecated might only mean it's not supported. So I want to confirm that if the app could work well locally and if we could get some exception information when we run locally. According to the test, we didn't see any issue when test locally, so I'm afraid it's related to the host environment which is Azure App Service like you mentioned. Let's try to find some useful error message in the host then. But I'm not an expert in Azure web app. Maybe we could go to the console command to have a test.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 49%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Are you still experiencing this issue? We encountered a very similar issue around the same date.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 61%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
We have run into very similar issues, including the exact error message referenced above:
Application 'MACHINE/WEBROOT/APPHOST/[...]/[...]' with physical root 'C:\home\site\wwwroot\[...]\' failed to start process with commandline 'dotnet .\[...].dll', ErrorCode = '0x80004005' : 80008096.
Running the dotnet command in a console on the app service indicates that the needed framework "'Microsoft.NETCore.App' version '1.1.12'" is not available.
Our application was running successfully as recently as 8/30/2023 in the afternoon, thus it seems that the framework was available to the app service at that time. It seems to have become unavailable over that night, yielding an unusable app on the morning of 8/31/2023.
Chris B's suggestion below would, indeed, resolve the issue; however updating our code to allow it to compile for e.g. version 2.2.14 is a serious undertaking. Is there any other path forward, or any chance that the needed framework can be restored to our app service/app service plan?
Thanks!
-Max.
Thanks everyone for the guidance. I ran the dotnet command in the console and got the same message as Max where it says that the version of .NETCore is not available. What the heck? Where did it go? Echoing Max's comment: Can the older framework be restored?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
You should, under the console, run the following command to see what versions of .net are available in your environment - it's possible that .net core 1.X has been removed since this hit EOL in June 2019.
dotnet --info
You'll need to recompile your app to target a version of the .net core sdk that appears in that list.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
as you are running an unsupported runtime, which seems to not be installed on the server anymore, you could try deploying a self contained build, where the runtime is included in the build.
note: net 6 is the oldest supported runtime. There have been a few changes since asp.net core 1.0.
Thank you Bruce! :-D
Using this approach we were able to get our app back up and running on our current app service/app service plan.
Basically, we just added the two lines to our production publish profile (e.g. production.pubxml). One for a self-contained build and another for portability.
...
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
...
<SelfContained>true</SelfContained>
<IsPortable>true</IsPortable>
<PropertyGroup>
</Project>
(More or less as per the section on "Self-contained deployment without third-party dependencies" here: https://learn.microsoft.com/en-us/dotnet/core/deploying/deploy-with-vs?tabs=vs157#simpleSelf )
We then redeployed and were back up and running.
Well, I, on the other hand, opened a can of worms trying to update my app to use .NET 7.0. It broke a few things such as the Cake and webpack build and I've been working on getting all the pieces to place nicely together which has been a challenge. For fun, I just tried loading my app and.... ahem, it's back up. I went to the portal to check the available .NET runtimes and .NET Core 1.1 is back on the list. So... thank you, Microsoft??