Symptoms
Assume that you have a report that contains tablix with two or more groups, and the LayoutDirection is set to RTL in Microsoft SQL Server 2012 Reporting Services (SSRS 2012) or SQL Server 2014 Reporting Services (SSRS 2014). When you use the report, you may encounter the following issues:
-
When you print the report, you receive the following error:
An error occurred during printing. ( 0x80004005)
-
When you print preview the report, you receive the following error:
An error occurred trying to render the report. (0x80004005)
-
When you export the report to PDF, you receive the following error:
[ReportServerException: Index was outside the bounds of the array.] [ReportServerException: An error occurred during rendering of the report.][ReportServerException: An error occurred during rendering of the report. (rrRenderingError)] Microsoft.Reporting.WebForms.SoapReportExecutionService.ServerUrlRequest(AbortState abortState, String url, Stream outputStream, String& mimeType, String& fileNameExtension) +1002 Microsoft.Reporting.WebForms.SoapReportExecutionService.Render(AbortState abortState, String reportPath, String executionId, String historyId, String format, XmlNodeList deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +1121 Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +425 Microsoft.Reporting.WebForms.ServerModeSession.RenderReport(String format, Boolean allowInternalRenderers, String deviceInfo, NameValueCollection additionalParams, Boolean cacheSecondaryStreamsForHtml, String& mimeType, String& fileExtension) +209 Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +219 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +221 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +586 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +177
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 4 for SQL Server 2014 /en-us/help/2999197
Cumulative Update 2 for SQL Server 2012 SP2 /en-us/help/2983175
Cumulative Update 11 for SQL Server 2012 SP1 /en-us/help/2975396
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.
