Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.0] [wasm] [AOT] HTTP Error 500.30 - ASP.NET Core app failed to start #95160

Open
carlossanlop opened this issue Nov 23, 2023 · 4 comments
Open

[8.0] [wasm] [AOT] HTTP Error 500.30 - ASP.NET Core app failed to start #95160

carlossanlop opened this issue Nov 23, 2023 · 4 comments
Labels
area-Infrastructure Known Build Error Use this to report build issues in the .NET Helix tab os-windows
Milestone
Future

Comments

@carlossanlop
Copy link
Member

carlossanlop commented Nov 23, 2023 •
edited by build-analysis bot
Loading

Error Blob

{
  "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Reproduction Steps

========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd""
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 3 seconds before next attempt (2 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 7 seconds before next attempt (3 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676
Error message validated: HTTP Error 500.30 - ASP.NET Core app failed to start
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/23/2023 2:40:17 AM UTC

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@carlossanlop carlossanlop added arch-wasm WebAssembly architecture os-windows blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' wasm-aot-test WebAssembly AOT Test Known Build Error Use this to report build issues in the .NET Helix tab labels Nov 23, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 23, 2023
@ghost
Copy link

ghost commented Nov 23, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Error Blob

{
  "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Reproduction Steps

========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd""
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 3 seconds before next attempt (2 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 7 seconds before next attempt (3 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start
Author: carlossanlop
Assignees: -
Labels:

arch-wasm, os-windows, blocking-clean-ci, wasm-aot-test, Known Build Error
Milestone: -

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Nov 23, 2023
@ghost
Copy link

ghost commented Nov 26, 2023

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

Error Blob

{
  "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Reproduction Steps

========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd""
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 3 seconds before next attempt (2 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 7 seconds before next attempt (3 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676
Error message validated: HTTP Error 500.30 - ASP.NET Core app failed to start
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/23/2023 2:40:17 AM UTC

Report

Build Definition Step Name Console log Pull Request
478676 dotnet/runtime windows-x64 Release NativeAOT_Checked_Libs_SpeedOpt Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1
Author: carlossanlop
Assignees: -
Labels:

arch-wasm, area-Infrastructure-libraries, os-windows, blocking-clean-ci, untriaged, wasm-aot-test, Known Build Error, needs-area-label
Milestone: -

@ghost
Copy link

ghost commented Nov 27, 2023

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

Error Blob

{
  "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Reproduction Steps

========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd""
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 3 seconds before next attempt (2 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](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. 
Retrying. Waiting for 7 seconds before next attempt (3 of 5).
GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676
Error message validated: HTTP Error 500.30 - ASP.NET Core app failed to start
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/23/2023 2:40:17 AM UTC

Report

Build Definition Step Name Console log Pull Request
478676 dotnet/runtime windows-x64 Release NativeAOT_Checked_Libs_SpeedOpt Log

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1
Author: carlossanlop
Assignees: -
Labels:

arch-wasm, os-windows, blocking-clean-ci, area-Infrastructure, untriaged, wasm-aot-test, Known Build Error, needs-area-label
Milestone: -

@lewing lewing removed arch-wasm WebAssembly architecture wasm-aot-test WebAssembly AOT Test needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Nov 29, 2023
@jeffschwMSFT jeffschwMSFT removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Feb 15, 2024
@jeffschwMSFT
Copy link
Member

was not seen recently... dropping blocking-clean-ci

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

@agocke agocke added this to the Future milestone Jul 8, 2024
@agocke agocke removed the untriaged New issue has not been triaged by the area owner label Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-Infrastructure Known Build Error Use this to report build issues in the .NET Helix tab os-windows
Projects
Runtime Infra
Status: No status
Milestone
Future
Development

No branches or pull requests
5 participants
@lewing @agocke @carlossanlop @ViktorHofer @jeffschwMSFT