I have a SSRS report with chart, which chart can not be viewed recently. Error message 'Bad IL Range'

Question

I have a SSRS report with chart, in which chart can not be viewed recently.

Error message 'Bad IL Range'.

I have no idea what this error mean.

Any idea how to fixed it?

Answer 1

Hi,

I've been working with Qun to investigate this issue. A reinstall of .NET Framework 3.5 and 4.8 has been carried out on the Windows Server and after some additional digging I've found the following error in the SSRS logs:

reportrendering!ReportServer_0-1!15b4!07/14/2023-15:01:18:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: , Microsoft.ReportingServices.ReportProcessing.RenderingObjectModelException: Bad IL range. ---> System.BadImageFormatException: Bad IL range.
   at Microsoft.Reporting.Chart.WebForms.Borders3D.BorderTypeRegistry..ctor(IServiceContainer container)
   at Microsoft.Reporting.Chart.WebForms.Chart..ctor()
   at Microsoft.ReportingServices.OnDemandReportRendering.ChartMapper.InitializeChart()
   at Microsoft.ReportingServices.OnDemandReportRendering.ChartMapper.RenderChart()
   --- End of inner exception stack trace ---;

Any guidance would be most welcome as looking online there really doesn't seem to be much in terms of what to look for.

Answer 2

Hi @Qun Lu

I don't know much about .NET/C#. I found this similar thread for you and hope it can help you: https://stackoverflow.com/questions/13416240/what-does-bad-il-range-exception-mean.

Best regards,

Aniya

Answer 3

Hello Qun,

Thank you for your question and for reaching out with your question today.

The "Bad IL Range" error message in SSRS (SQL Server Reporting Services) indicates an issue with the Intermediate Language (IL) code that is generated by the .NET compiler when processing the report. This error typically occurs when there is a problem with the compiled code.

Here are a few steps you can try to resolve the "Bad IL Range" error:

1. Clear the temporary files: Sometimes, the issue can be caused by corrupted or outdated temporary files. Try clearing the temporary files related to SSRS on the server. The temporary files are typically located in the following directory: C:\Windows\Microsoft.NET\Framework\vX.X.XXXXX\Temporary ASP.NET Files\.
2. Restart the SSRS service: Restarting the SSRS service can help refresh the system and resolve any temporary glitches. Go to the Services console, locate the SQL Server Reporting Services service, and restart it.
3. Republish the report: If the error persists, try republishing the report to ensure that the compiled code is regenerated correctly. Publish the report again and check if the issue is resolved.
4. Check the .NET framework version: Ensure that the correct version of the .NET framework is installed and configured for SSRS. Verify that the .NET framework version used for compiling the report matches the version configured in the SSRS environment.
5. Review the report and chart configuration: Double-check the configuration of your report and chart. Make sure there are no errors or inconsistencies in the chart properties, data sources, expressions, or parameters that could be causing the issue.
6. Check the event logs: Examine the SSRS logs or event logs for any additional error messages or details that could provide more insight into the cause of the issue.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.