SSRS内部服务器500错误：ReportViewer渲染时遇Http 500问题求助

Hey, let's tackle that 500 error you're hitting with ReportViewer—specifically the SessionKeepAlive request to Reserved.ReportViewerWebControl.axd. You've already tried some solid steps, so let's build on that with targeted fixes for your setup:

What you've already tried (good moves!): #

• Registered the ReportViewerWebControlHandler in <webserver> for integrated mode
• Updated the page directive with ValidateRequest="false" and AsyncRender="False"

Next steps to diagnose and fix: #

1. Register the Handler in Both Configuration Sections #

Sometimes the handler needs entries in both <system.web> and <system.webServer> to cover all runtime scenarios. Add this to your <system.web> block:

<httpHandlers>
  <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
</httpHandlers>

Double-check that the version number and PublicKeyToken match exactly what's in your project references—mismatches here are a common hidden culprit.

2. Confirm Session State is Working Correctly #

The SessionKeepAlive request depends on active session state. Make sure your web.config has session state configured properly:

<system.web>
  <sessionState mode="InProc" cookieless="false" timeout="20" />
</system.web>

If you're using a custom session provider (like SQL Server session state), verify it's set up correctly and that the ReportViewer can access session data without issues.

3. Validate Your ReportViewer Control Setup #

If you're using remote SSRS mode, double-check that your ReportViewer markup has the right server and report path details:

<rsweb:ReportViewer ID="ReportViewer1" runat="server" ProcessingMode="Remote">
  <ServerReport ReportServerUrl="http://your-ssrs-instance/ReportServer" ReportPath="/Development/pd_Report_SalesPricingGrid" />
</rsweb:ReportViewer>

For local mode, ensure your .rdlc file is properly embedded in the project and that all data sources are configured to pull data correctly—missing data connections can trigger 500 errors during rendering.

4. Check Permissions for the Target Report #

Since your SSRS server logs highlight the /Development/pd_Report_SalesPricingGrid report (marked with bold red), confirm that your web app's application pool identity has the necessary permissions to access this report on the SSRS server. If using Windows auth, make sure delegation is configured if the app pool runs under a service account.

5. Turn on Detailed Error Messages #

Generic 500 errors don't tell us much—enable detailed errors in web.config to get the actual exception:

<system.web>
  <customErrors mode="Off" />
</system.web>
<system.webServer>
  <httpErrors errorMode="Detailed" />
</system.webServer>

This will show you the exact line or issue causing the failure, whether it's a missing assembly, permission problem, or report rendering error.

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