Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
The provided information doesn’t include details about this specific web app or its deployment, so only general Azure guidance can be given.
To troubleshoot the Sales Reports and Manage Products pages not loading in an Azure App Service deployment:
- Verify the app is running
- In Azure portal, open the App Service.
- Confirm the Status is Running and there are no recent Failed events in Activity log.
- Check deployment behavior
- If the app is using Run-From-Package (for example, an
WEBSITE_RUN_FROM_PACKAGEapplication setting), deployments may be applied asynchronously and new files might not appear immediately. - In the App Service:
- Go to Configuration → Application settings.
- Look for a setting like
WEBSITE_RUN_FROM_PACKAGE. - If present and the app is a simple web app where immediate updates are required, remove this setting or set it to
0, then Save and allow the app to restart.
- This ensures new deployments are written directly to the file system so updated pages become available immediately after deployment.
- If the app is using Run-From-Package (for example, an
- Confirm files and routes exist
- Use Kudu/Advanced Tools for the App Service and browse the
site/wwwrootfolder. - Verify that the files or routes for Sales Reports and Manage Products pages are present after deployment.
- If they are missing, the deployment package or pipeline is incomplete; redeploy with all required files.
- Use Kudu/Advanced Tools for the App Service and browse the
- Inspect application logs
- In the App Service, enable Application logging and Detailed error messages if not already enabled.
- Reproduce the issue by clicking Sales Reports and Manage Products, then review logs for routing errors, missing files, or unhandled exceptions.
- Test another region or slot (if available)
- If the issue appears only in this deployment, try deploying the same code to another region or a deployment slot to rule out environment-specific issues.
- If the portal or deployment experience itself is failing
- Use Azure CLI or REST to redeploy or inspect resources if any portal blade fails to load.
- If deployment or quota issues are suspected and can’t be resolved via the portal, open a support request from the Azure portal Help + support blade.
If, after these steps, the pages still don’t load and logs show no clear cause, capture the exact error messages or HTTP status codes from the browser’s developer tools and use them to drive further debugging or to include in a support request.
References:
- Quickstart: Create and run a load test with Azure Load Testing
- Quickstart: Create and run a load test by using a Locust script and Azure Load Testing
- Load test a website by using a JMeter script in Azure Load Testing
- Support and troubleshooting for Azure Load Balancer
- Unable to deploy resources, can't view Quotas or request increases - Microsoft Q&A
- Unable to Access or Connect to VM - Microsoft Q&A
- Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A
- Can not access Azure - Microsoft Q&A
- How to Deploy my Web App with a Minimum Delay? - Microsoft Q&A