[release/8.0.3xx] Update dependencies from dotnet/arcade #41743
Merged
Azure Pipelines / dotnet-sdk-public-ci (Build Windows_NT Build_Release)
failed
Jul 1, 2024 in 2m 35s
Build Windows_NT Build_Release failed
Annotations
Check failure on line 13 in Build log
azure-pipelines / dotnet-sdk-public-ci (Build Windows_NT Build_Release)
Build log #L13
(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.
Check failure on line 25 in Build log
azure-pipelines / dotnet-sdk-public-ci (Build Windows_NT Build_Release)
Build log #L25
(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.
Check failure on line 37 in Build log
azure-pipelines / dotnet-sdk-public-ci (Build Windows_NT Build_Release)
Build log #L37
(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.
Check failure on line 49 in Build log
azure-pipelines / dotnet-sdk-public-ci (Build Windows_NT Build_Release)
Build log #L49
(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.
Check failure on line 61 in Build log
azure-pipelines / dotnet-sdk-public-ci (Build Windows_NT Build_Release)
Build log #L61
(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.
Loading