Confirm that the web.config file is present in the deployment and that its contents are correct.Redeploy the contents of the app's publish folder to the hosting system using your normal method of deployment, such as Visual Studio, PowerShell, or manual deployment:.Delete all of the files and folders from the deployment folder on the hosting system.The web.config file is missing from the deployment, or the web.config file contents are malformed.The deployment process failed to move all of the app's files and folders to the deployment folder on the hosting system.The app is deployed to the wrong folder on the hosting system.The error is usually caused by a broken deployment on the hosting system, which includes any of the following scenarios: The following error is logged: The Web server is configured to not list the contents of this directory. A 502.5 - Process Failure or a 500.30 - Start Failure that occurs when debugging locally can be diagnosed using the advice in this topic. In Visual Studio, an ASP.NET Core project defaults to IIS Express hosting during debugging. The guidance applies to both Windows Server and Windows desktop deployments.Įxplains what to do when incoherent packages break an app when performing major upgrades or changing package versions. Provides troubleshooting advice for apps deployed to IIS or running on IIS Express locally. Provides troubleshooting advice for apps deployed to Azure App Service.
#Trados studio 2017 is slow after confirming segment how to#
This article provides information on common app startup errors and instructions on how to diagnose errors when an app is deployed to Azure App Service or IIS:Įxplains common startup HTTP status code scenarios.