Azure App Service部署后无法从Azure SQL Database返回数据，报“An error has occurred”错误求助

Hey there, sorry to hear you're hitting this vague 500 error after deploying your .NET Framework Web App to Azure Web App—let's break down the most common causes and how to troubleshoot them step by step:

The generic "An error has occurred" message tells you nothing about what's actually breaking. Let's fix that to see the real issue:

• In Azure Portal: Navigate to your Web App > App Service logs > Turn on "Application Logging (Filesystem)" and set the log level to "Error" or "Verbose". You can then check the Log stream in real-time, or download logs via Kudu (Advanced Tools > Go > Debug console > LogFiles > Application).
• Temporarily update web.config: Add or modify this section to expose full error details (remember to revert this for production!):

  <system.web>
    <customErrors mode="Off"/>
    <compilation debug="true"/> <!-- Only for debugging, disable later -->
  </system.web>
  

  Redeploy, and now you'll see the actual exception stack trace instead of the generic message.

This is the #1 culprit when local works but Azure doesn't:

• Verify Connection String in Azure: Go to your Web App > Configuration > Connection Strings. Paste the correct ADO.NET connection string from your Azure SQL Database (you can copy this directly from the SQL Database portal under "Connection strings"). Ensure the Type is set to "SQLAzure"—this tells Azure to handle it as a database connection string.
• Check Firewall Rules: In your Azure SQL Server portal > Firewalls and virtual networks > Make sure "Allow Azure services and resources to access this server" is checked. If you're testing from a local machine via Postman, temporarily add your IP to the firewall rules to rule out access blocks.
• Validate SQL Permissions: The username/password in your connection string needs proper access to your database. Double-check that the SQL login has db_datareader (or appropriate read/write) permissions on your target database.

Local and Azure environments must use the same .NET Framework version:

• Go to your Web App > Configuration > General settings > Check the ".NET Framework version" dropdown. Make sure it matches the version your project targets (e.g., if you built with 4.7.2, select "v4.7" or "v4.7.2" if available).

Sometimes critical files get missed during publish:

• Use Kudu (Web App > Advanced Tools > Go) to navigate to site\wwwroot. Confirm all your project files, NuGet packages, and dependencies are present. If you're using a publish profile, ensure you're publishing in "Release" mode and including all necessary files.
• For any local DLLs (not from NuGet), set their "Copy to Output Directory" property to "Copy always" in Visual Studio before publishing.

• Ensure your API routes are consistent when deployed. If using attribute routing, double-check that route templates don't rely on local paths or configurations.
• If you deployed to a virtual directory (not the root), adjust your API requests to include the virtual directory in the URL (e.g., https://your-app.azurewebsites.net/virtual-dir/api/your-endpoint).

• Store Secrets in Azure: Never hardcode connection strings or credentials in web.config. Use Web App > Configuration > Connection Strings or Application Settings—Azure encrypts these at rest and keeps them separate from your code.
• Enable Application Insights: Go to your Web App > Application Insights > Enable it. This gives you detailed telemetry, exception tracking, and performance metrics to diagnose issues faster.
• Production-Friendly Error Handling: Once you fix the issue, set <customErrors mode="On"/> in web.config and create a friendly error page for users, while keeping detailed logs enabled in Azure for debugging.
• Set Up Backups: Configure automatic backups for your Azure Web App and SQL Database to avoid data loss if something goes wrong.

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