With .NET 6.0 installed, publish .NET Framework 2.1 fails to error "HTTP Error 502.5 - Process Failure".

[v-elenafeng]

Testcases Affected
Publish ASP.NET Core 2.1 (.NET Framework)

Repro Steps

1. With .NET 6.0 Preview 6 installed, open VS and sign in with account
2. File > New project > ASP.NET Core Empty > .NET Core 2.1 > Check "Run on .NET Framework"
3. Right-click on the project > Publish to App service (Windows)

It shows "HTTP Error 502.5 - Process Failure" on the published website.

Actual Result

[BrennanConroy]

Can you please take a look at the docs (which should be linked from the error page you posted) and see if you can get diagnostics for the issue.
https://docs.microsoft.com/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-5.0#5025-process-failure

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

[v-elenafeng]

I will try to get the diagnostics next week, thanks!

[v-elenafeng]

I cannot get the information from the Application Event Log and the ASP.NET Core Module stdout log.
The versions of the ASP.NET Core shared framework:

Could you provide me with more guidance？

[mkArtakMSFT]

@BrennanConroy I assume this is not a blocker for preview6?

[BrennanConroy]

I cannot get the information from the Application Event Log and the ASP.NET Core Module stdout log.

Can you clarify? Why can't you get the info?

[v-elenafeng]

Application Event Log

Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Microsoft.Extensions.Logging.Console.ConsoleLogger..ctor(System.String, System.Func3<System.String,Microsoft.Extensions.Logging.LogLevel,Boolean>, Microsoft.Extensions.Logging.IExternalScopeProvider, Microsoft.Extensions.Logging.Console.Internal.ConsoleLoggerProcessor) at Microsoft.Extensions.Logging.Console.ConsoleLoggerProvider.CreateLoggerImplementation(System.String) at System.Collections.Concurrent.ConcurrentDictionary2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetOrAdd(System.__Canon, System.Func2<System.__Canon,System.__Canon>) at Microsoft.Extensions.Logging.LoggerFactory.CreateLoggers(System.String) at Microsoft.Extensions.Logging.LoggerFactory.CreateLogger(System.String) at Microsoft.Extensions.Logging.Logger1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(Microsoft.Extensions.Logging.ILoggerFactory)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(Microsoft.Extensions.DependencyInjection.ServiceLookup.ScopedCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine+<>c__DisplayClass1_0.<RealizeService>b__0(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(System.IServiceProvider, System.Type)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]
at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
at WebApplication4.Program.Main(System.String[])

1000 1 0 Keywords 553661843 Application RD0003FF2AD9DD Application 'MACHINE/WEBROOT/APPHOST/WEBAPPLICATION420210629194332' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'D:\home\site\wwwroot\WebApplication4.exe ', ErrorCode = '0x80004005' : e0434352. 1026 1 0 Keywords 553665015 Application RD0003FF2AD9DD Application: WebApplication4.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException

Exception Info: System.IO.FileNotFoundException
at Microsoft.Extensions.Logging.Console.ConsoleLogger..ctor(System.String, System.Func3<System.String,Microsoft.Extensions.Logging.LogLevel,Boolean>, Microsoft.Extensions.Logging.IExternalScopeProvider, Microsoft.Extensions.Logging.Console.Internal.ConsoleLoggerProcessor) at Microsoft.Extensions.Logging.Console.ConsoleLoggerProvider.CreateLoggerImplementation(System.String) at System.Collections.Concurrent.ConcurrentDictionary2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetOrAdd(System.__Canon, System.Func2<System.__Canon,System.__Canon>) at Microsoft.Extensions.Logging.LoggerFactory.CreateLoggers(System.String) at Microsoft.Extensions.Logging.LoggerFactory.CreateLogger(System.String) at Microsoft.Extensions.Logging.Logger1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(Microsoft.Extensions.Logging.ILoggerFactory)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(Microsoft.Extensions.DependencyInjection.ServiceLookup.ConstructorCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(Microsoft.Extensions.DependencyInjection.ServiceLookup.ScopedCallSite, Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine+<>c__DisplayClass1_0.<RealizeService>b__0(Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(System.IServiceProvider, System.Type)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]
at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
at WebApplication4.Program.Main(System.String[])

1000 1 0 Keywords 553665171 Application RD0003FF2AD9DD Application 'MACHINE/WEBROOT/APPHOST/WEBAPPLICATION420210629194332' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'D:\home\site\wwwroot\WebApplication4.exe ', ErrorCode = '0x80004005' : e0434352.

[ghost]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[BrennanConroy]

This can be reproed locally, no need to publish to app service. I used sdk 6.0.100-preview.7.21324.2 to repro the issue, but OP was using a preview6 SDK. Looking at the difference between the published output with a 5,0 SDK vs 6.0 SDK, there is 164 items vs. 68 items, so there is definitely a big difference between the SDKs.

Output from running the .exe from the 6.0 SDK:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Adding the missing dll will then move on to complain about the next missing dll, and I assume it will keep doing so until the ~100 missing files are added.

[dougbu]

From dotnet/aspnetcore#30419, it seems this issue started w/ the 6.0-preview1 SDK. Did that preview release make important changes in how apps are published @wli3 @dsplaisted @marcpopMSFT❔

@BrennanConroy I assume this is not a blocker for preview6?

I'd say it's not a preview6 blocker given our release timeline (shrug). Let's treat this as important and urgent but not s ship-stopper for our preview releases. That said, we should fix this before the next 6.0 release because it's a regression since 5.0 of a scenario important enough for CTI to test.

[Pilchie]

👀

[shirhatti]

I've root caused this issue to this change in the SDK- https://github.com/dotnet/sdk/pull/14020/files

Impacted customers can work around this by adding this to their project file

  <PropertyGroup>
    <ErrorOnDuplicatePublishOutputFiles>false</ErrorOnDuplicatePublishOutputFiles>
  </PropertyGroup>

[dougbu]

@shirhatti are you saying #14020 has a bug causing removal of files required in scenarios like this one❔

@sfoslund @AntonLapounov @dsplaisted is there a fix planned for this regression from 5.0.x❔ The workaround sounds simple enough but the connection to having too few files in the published output seems unlikely for customers to grok i.e. the workaround doesn't seem discoverable.

[shirhatti]

@shirhatti are you saying #14020 has a bug causing removal of files required in scenarios like this one❔

Looks like it to me. I have a before/after binlog handy if someone wants to take a look.

FWIW, I noticed we've disabled this in the aspnetcore repo as well https://github.com/dotnet/aspnetcore/blob/main/eng/Workarounds.props#L37

[dougbu]

FWIW, I noticed we've disabled this in the aspnetcore repo as well https://github.com/dotnet/aspnetcore/blob/main/eng/Workarounds.props#L37

That's worth a lot @shirhatti❕ I forgot about that workaround and dislike the idea of requiring it of many customers upgrading from 5.0.x to 6.0.x.

[dsplaisted]

It looks like this is the same thing as #18101

@marcpopMSFT Another hit on this regression

[dsplaisted]

This should be fixed in .NET SDK RC1 with #19731

[v-elenafeng]

Not repro with 17.0.0 Preview 4.0 [31622.41.main] + 6.0.100-rc.1.21422.7.