Bot Framework网站部署报错排查：修改文本后构建失败且恢复无效

I’ve dealt with similar Azure Bot deployment headaches before—let’s walk through actionable fixes to get your bot back up and running:

1. Get the exact deployment error details #

The generic "An error has occurred during web site deployment" message doesn’t tell us enough. Here’s how to uncover the real issue:

• Head to your Azure App Service portal, navigate to Deployment Center and check recent deployment records for failed steps or specific error codes.
• Open Advanced Tools (Kudu) (access via https://<your-app-name>.scm.azurewebsites.net/), then go to Debug Console > CMD. Run build.cmd manually here and look at the full output—you’ll likely see specific issues like missing dependencies, compilation failures, or file permission problems.

2. Clean stale files and re-deploy the original build #

Even after restoring files, residual cached data or partial updates can break things. Let’s start fresh:

• In Kudu’s Debug Console, run these commands to clear temporary and web root files:

  del /s /q %TEMP%
  rmdir /s /q D:\home\site\wwwroot\
  

• Re-upload the entire original Release folder from your local project to the wwwroot directory in Kudu. Then run build.cmd again to ensure a clean, complete build.

3. Verify critical configuration settings #

Deployment issues often mess up core bot configurations without you noticing:

• Check appsettings.json in wwwroot to confirm your QnA Maker subscription key, knowledge base ID, and endpoint are 100% correct—even a tiny typo here can break the bot.
• Double-check your Azure Bot resource’s Configuration tab to ensure the Microsoft App ID and password match what’s in your bot’s code—deployments sometimes reset these values accidentally.

4. Test connectivity and service health #

The ServiceUnavailable error usually points to connectivity or service issues:

• In your Azure Bot resource, go to Test in Web Chat and send a message. The detailed error here might reveal root causes like authentication failures or QnA Maker service timeouts.
• Verify your QnA Maker knowledge base works independently: go to the QnA Maker portal, run a test query to confirm the service itself isn’t down.

5. Deploy a fresh build from your local machine #

If all else fails, start over with a clean local build:

• On your local machine, rebuild the bot project in Release mode first—make sure there are no compilation errors locally.
• Zip the entire Release output folder, then use Azure App Service’s Deployment Center > Zip Deploy to upload the zip file. This ensures all dependencies and files are deployed consistently, no partial updates or missing pieces.

内容的提问来源于stack exchange，提问作者Zenkaliia