Symptoms

Assume that you render a report in Microsoft SQL Server 2012 Reporting Services (SSRS 2012) or SSRS 2014, and that the report has some small errors, for example:

library!ReportServer_0-8!4798!12/16/2014-16:33:01:: i INFO: RenderForNewSession('/MyReport')
processing!ReportServer_0-8!4798!12/16/2014-16:33:03:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 8.;
processing!ReportServer_0-8!4798!12/16/2014-16:33:33:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: There is no data for the field at position 9.;

In this situation, the report runs successfully. However, it might take longer time than usual to render the report. Each error may cause a 30-second delay.

Cause

This issue occurs because Reporting Services is blocked from loading the unnecessary error-handling object.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×