SSRS 2012 Excel Rendering Error

Hi
I need help
Platform
Sharepoint 2013
SSRS 2012 integrated in sharePoint 2013
I've no problem when I export my report (25000 records) to EXCELOPENXML format, but each time I try to export it with 140 000 records i've always the error described below , however I can export it to csv format
at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream
createAndRegisterStream)
at Microsoft.ReportingServices.ReportProcessing.Execution.RenderReport.Execute(IRenderingExtension newRenderer)
--- End of inner exception stack trace ---;
w3wp!library!1b!02/25/2014-12:18:44:: e ERROR: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Threading.ThreadAbortException: Thread was being aborted.
at System.AppDomain.GetId()
at System.Threading.Thread.GetCurrentCultureNoAppX()
at Go17(RegexRunner )
at System.Text.RegularExpressions.RegexRunner.Scan(Regex regex, String text, Int32 textbeg, Int32 textend, Int32 textstart, Int32 prevlen, Boolean quick, TimeSpan timeout)
at System.Text.RegularExpressions.Regex.Run(Boolean quick, Int32 prevlen, String input, Int32 beginning, Int32 length, Int32 startat)
at System.Text.RegularExpressions.Regex.Match(String input)
at Microsoft.ReportingServices.ReportProcessing.Validator.ValidateColor(String color, Color& c, Boolean allowTransparency)
at Microsoft.ReportingServices.OnDemandReportRendering.ReportColor..ctor(String color, Boolean allowTransparency)
at Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.OpenXmlGenerator.AddColor(String colorString)
at Microsoft.ReportingServices.Rendering.ExcelRenderer.Layout.LayoutEngine.ItemInfo.FillBorders(RPLStyleProps style, Boolean omitBorderTop, Boolean omitBorderBottom, IExcelGenerator excel)
at Microsoft.ReportingServices.Rendering.ExcelRenderer.Layout.LayoutEngine.RenderNewItem(IRowItemStruct item, Int32 top, Int32 topRow, IExcelGenerator excel, String pageContentKey, Dictionary`2 sharedBorderCache, Dictionary`2 sharedImageCache,
Boolean& autosizableGrow, Boolean& autosizableShrink)
at Microsoft.ReportingServices.Rendering.ExcelRenderer.Layout.LayoutEngine.RenderPageToExcel(IExcelGenerator excel, String key, Dictionary`2 sharedBorderCache, Dictionary`2 sharedImageCache)
at Microsoft.ReportingServices.Rendering.ExcelRenderer.MainEngine.RenderRPLPage(RPLReport report, Boolean headerInBody, Boolean suppressOutlines)
at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream
createAndRegisterStream)
at Microsoft.ReportingServices.ReportProcessing.Execution.RenderReport.Execute(IRenderingExtension newRenderer)
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.ReportProcessing.Execution.RenderReport.Execute(IRenderingExtension newRenderer)
at Microsoft.ReportingServices.Library.RenderFromSnapshot.CallProcessingAndRendering(ProcessingContext pc, RenderingContext rc, OnDemandProcessingResult& result)
at Microsoft.ReportingServices.Library.RenderStrategyBase.ExecuteStrategy(OnDemandProcessingResult& processingResult)
w3wp!wcfruntime!1b!02/25/2014-12:18:44:: e ERROR: Reporting Services fault exception System.ServiceModel.FaultException`1[Microsoft.ReportingServices.ServiceContract.RsExceptionInfo]: An unexpected error occurred in Report Processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
An unexpected error occurred in Report Processing. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors (Fault Detail is equal to Microsoft.ReportingServices.ServiceContract.RsExceptionInfo).
Any solutions

Hi Vichu,
According to your description, you encountered the timeout issue when rendering your report. Right?
In Reporting Services, sometimes this issue happens when rendering big report, and it exceed the default Query Timeout time. Generally, we increase the Query Timeout and Session Timeout so that it will have more time to retrieving data.
In this scenario, since you have done this adjustment and the issue still exists randomly. We suggest you optimize the performance of your report. Please refer to the articles below:
Processing large reports:
http://technet.microsoft.com/en-us/library/ms159638.aspx
Performance (Reporting Services):
http://technet.microsoft.com/en-us/library/bb522786.aspx
Improving report performance with caching:
http://technet.microsoft.com/en-us/library/ms155927.aspx
Report performance optimization tips:
http://blogs.msdn.com/b/robertbruckner/archive/2009/01/08/report-performance-optimization-tips-subreports-drilldown.aspx
In addition, we recommend you install the Updates for SSRS 2012:
http://sqlserverbuilds.blogspot.com/
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Similar Messages

SSRS 2012 excel export is still coming out as an xls not xlsx

Hello, All
I am pretty new to SSRS 2012 and trying to migrate existing SSRS 2005 reports to SSRS 2012 to resolve the limited record export function with classic excel format.
The server is using .Net Framework 2 application pool as below and it's not showing any page with .Net Framework 4.
I have migrated RDL files using SQL Data Tools and updated web.config and aspx pages too.
<system.web>
<httpHandlers>
<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" validate="false" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpHandlers>
<compilation debug="true" strict="false" explicit="true">
<assemblies>
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="Infragistics2.WebUI.Shared.v7.3, Version=7.3.20073.38, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>
<add assembly="Infragistics2.WebUI.WebDateChooser.v7.3, Version=7.3.20073.38, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
</assemblies>
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</buildProviders>
</compilation>
Also, Report Viewer 2012, 2010 and 2008 (all of them) were installed on the server.
I checked the RSReportServer.config file and it does have xlsx available and xls visible=false instead.
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="false"/>
<Extension Name="EXCELOPENXML" Type="Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.ExcelOpenXmlRenderer,Microsoft.ReportingServices.ExcelRendering"/>
The target RDL file looks working fine with .xlsx file export in the SQL Data Tools(Report Designer) but it's not exporting xlsx file and trying to export classic xls and failed to generate more than 65536 records.
Can anyone help me with this issue?
Did I miss anything in the settings or something?
Your help would be much appreciated.

Hello,
If I understand correctly, Excel render format is working fine when you export RDL file, but cannot work for RDLC file.
RDL files are created by the SQL Server 2012 version of Report Designer. RDLC files are created by the Visual Studio 2010 version of Report Designer. RSReportServer.config file is control RDL file rather than RDLC file. Based on my test, in Visual Studio
2010, when we export RDLC file, Excel render format is .xls. You can try to use Visual Studio 2012 to test, if it can export .xlsx file.
In order to solve the excel limitation issue, please refer to the document below:
http://msbitips.com/?p=624
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

SSRS 2012 Session Expired Error..

We have reporting environment with SSRS 2012 configured with forms authentication…
When users taking reports we are getting following errors randomly. We increased the valued of Query Timeout and Session Timeout in WebConfig. But still the error is persisting…Any one help us to resolve this issue?
microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
session!ReportServer_0-9!1070!08/11/2014-03:08:58:: e ERROR: Error in getting session data: Invalid or Expired Session: e3z2csibgn4kmbum1wm2cs2b

Hi Vichu,
According to your description, you encountered the timeout issue when rendering your report. Right?
In Reporting Services, sometimes this issue happens when rendering big report, and it exceed the default Query Timeout time. Generally, we increase the Query Timeout and Session Timeout so that it will have more time to retrieving data.
In this scenario, since you have done this adjustment and the issue still exists randomly. We suggest you optimize the performance of your report. Please refer to the articles below:
Processing large reports:
http://technet.microsoft.com/en-us/library/ms159638.aspx
Performance (Reporting Services):
http://technet.microsoft.com/en-us/library/bb522786.aspx
Improving report performance with caching:
http://technet.microsoft.com/en-us/library/ms155927.aspx
Report performance optimization tips:
http://blogs.msdn.com/b/robertbruckner/archive/2009/01/08/report-performance-optimization-tips-subreports-drilldown.aspx
In addition, we recommend you install the Updates for SSRS 2012:
http://sqlserverbuilds.blogspot.com/
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

SSRS 2008 R2 rendering error when executing a report

The value '1' is invalid. Valid values are between '0' and '1'. (rrRenderingError)
I am receiving the above error when running the report in SSRS 2008 R2. It has run find in the 2005 version. After research, I read that this issue caused by tablix split on a new page or something. However, I have not found anything to be the resolution. I
installed the latest hotfix that I thought addressed this issue but still not working. Any suggestions outside of touching the report?Sonya

The value '1' is invalid. Valid values are between '0' and '1'. (rrRenderingError)
I am receiving the above error when running the report in SSRS 2008 R2. It has run find in the 2005 version. After research, I read that this issue caused by tablix split on a new page or something. However, I have not found anything to be the resolution. I
installed the latest hotfix that I thought addressed this issue but still not working. Any suggestions outside of touching the report?
Sonya
We too are encountering this problem with reports migrated from 2005 to 2008. We are getting the rendering error only when trying to use the paging controls to navigate forward through the report. This is on SSRS 2008 R2 running SharePoint Integration. When
the result set is empty we get the tablix errors mentioned instead. The reports ran fine prior to migration to SSRS2008.

SSRS 2012 service application error in sharepoint 2010

Hi,
I have installed MS SQL SERVER 2012 enterprise edition and sharepoint 2010 SP2 standalone as i want to learn a few things. Everyting went smooth upto the point when i wanted to configure a Create the Reporting Services Service application in sharepoint.
Firstly i cant change the account from network service on the checkbox predifined under Select security account for this application pool.
Secondly I get a error if i try to proceed >>>>> "The database engine
instance 'SERVER\SharePoint' does not meet the edition requirements for the Reporting Services database."
Please help me on this one im stuck i cant proceed

Hello,
I think this thread may help you:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/dddc7f63-935d-40fa-8402-ec43bd288c56/cant-create-a-ssrs-2012-service-application-in-sharepoint-2010?forum=sqlreportingservices
http://blogs.msdn.com/b/psssql/archive/2013/02/20/rs-database-engine-does-not-meet-edition-requirements.aspx
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

SSMS 2014 to SSRS 2012 WMI connection error / Invalid namespace

We have swapped out the default SSRS2012 Windows Authentication with our own FormsAuth custom authentication.
From SSMS2012, I can connect to our reporting server instance via FormsAuth without issue.
From SSM2014, I can't connect to our reporting server instance. I get this error:
Invalid namespace (Microsoft.SqlServer.Management.UI.RSClient).
How should I troubleshoot / resolve this error?

Hi scott_m,
Based on my understanding, you come across an Invalid namespace error when connecting to Report Server 2012 from SSMS 2014.
In Reporting Services, the namespace for SSRS 2014 is root\Microsoft\SqlServer\ReportServer\RS_<EncodedInstanceName>\v12\Admin
while the namespace for SSRS 2012 is root\Microsoft\SqlServer\ReportServer\RS_<EncodedInstanceName>\v11\Admin. When using SSMS 2014 for connecting to SSRS 2012, by default, it also access v12 instead of v11 , so we will get Invalid
namespace error. In other words, we can’t connect to SSRS 2012 from SSMS 2014 because of different namespace.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

SQL SSRS 2012 - Excel OpenXML Export Performance

Hello,
Does anyone have details on what the Excel 2007 XML renderer is doing in Reporting Services and why it is taking 10 minutes to export and timing out as opposed to 30 seconds for CSV export or display in HTML? The database shows 25k for Data Retrieval,
25k for Processing, 60 for Rendering so it appears it is outside of these metrics.
The report contains 40 columns and 40,000 rows, with some textual data. The resulting XLSX is 10MB, or 100MB unzipped. There is no report or page header. The report contains a tablix with just details group, and some minor formatting. It
is inside a rectangle.
I would expect @ 2-3 minutes to export, though getting better performance than this would be nice.
Server is 11.0.3373.
Any suggestions or feedback on this issue and suggestions on presenting basically a formatted data dump in Excel to the customer would be helpful.
thanks,
Andrew
Andrew Sears, T4G Limited, http://www.performancepointing.com

Hello,
If I understand correctly, Excel render format is working fine when you export RDL file, but cannot work for RDLC file.
RDL files are created by the SQL Server 2012 version of Report Designer. RDLC files are created by the Visual Studio 2010 version of Report Designer. RSReportServer.config file is control RDL file rather than RDLC file. Based on my test, in Visual Studio
2010, when we export RDLC file, Excel render format is .xls. You can try to use Visual Studio 2012 to test, if it can export .xlsx file.
In order to solve the excel limitation issue, please refer to the document below:
http://msbitips.com/?p=624
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

SSRS 2012 Initial Rendering Incorrect

I'm running into an issue in the Report Manager where reports do not render correctly initially.
If a report requires user input (a parameter that does not have a default value), the report loads incorrectly--all images are missing (including charts) and document maps do not exist. Once a report is rendered this first time, if I click the Refresh Button
in the Report Viewer toolbar or try to browse to the next page, the report completely re-renders, but this time correctly.
I'm at a total loss as to why this is happening; any ideas or suggestions would be much appreciated.

Hi BradleyJamrozik,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Excel Rendering Extension: Unknown Image Format Imag/GIF - SSRS Excel Export

We are using the SSRS 2012 [ExportOpenXML].
When a report is export to excel, getting the message Unknow Image Format IMage/GIF.
Please suggest a fix the above issue.
As per article Excel Rendering extension: Unknow Image Format image/x-png suggestion verified in Visual studio selected the gif file in the Solution Explorer panel, checked the Properties
the MIME Type which is already set as image/gif.
Note: Dev environment its working as expected and but issue is observed in QA environment. I wonder some setting is missing on QA enviornment which I'm unable to get the difference exactly.
Quick help would be higly appreciated.

Hi Niranjan,
Based on the current description, I understand that there should be no issue when exporting the report containing image which is Image/Gif type in Dev environment because you have changed the MIME type to Image/Gif.
To narrow down the scope to find the cause, I want to confirm some information below:
1. Check Reporting Services edition in QA environment, if the Reporting Services edition is same between QA and Dev environment, you can back up the .rdl file and copy the .rdl file to QA environment and then export the report in Excel format to check
whether the issue persists.
2. If you export the report to other format such as PDF rather than Excel format in QA environment, please confirm whether the issue persists.
3. If you change the MIME type to Image/Png and then export the report to Excel in Dev and QA environment, please confirm whether the issue persists.
Supposing there is error message, please post the details to the forum for further analysis.
Reference:
How do you check what version of SQL Server for a database using TSQL?
Regards,
Heidi Duan
Heidi Duan
TechNet Community Support

Passing rendering format and report parameters in the URL to call a report - SSRS 2012

Hi,
I've a SSRS 2012 with the integer and multivalue Creation_Years parameter that I need to call directly to export data in the Excel format.
I've tried to use this URL:
http://reportserv/Reports/Pages/Report.aspx?ItemPath=%2fInsurance%2fInstallations_Excel&rs:Format=excel&Creation_Years=2014 but the parameter is required in an interactive manner.
I've tried to set the hidden property for the parameter, I've tried to invert the position of the "rs:Format=excel" string with the "Creation_Years=2014", but the error message doesn't change. Also if I specify the 2015 year, the parameter
isn't overwritten with the 2015 value.
Any helps to me, please? Thanks

Ok, thanks, I note that you have added "rs:Command=Render": looking to the official documentation this string seems optional.
Your url functions but the parameter cannot be a multivalue one. Do you confirm this?
Thanks
If you want to sent value for multi valued parameter through URL you need to repeat it
ie like this
http://reportserv/ReportServer/Pages/ReportViewer.aspx?%2fInsurance2fInstallations_Excel&rs:Command=Render&rs:Format=excel&Creation_Years=2014&Creation_Years=2015&Creation_Years=2016...
also see
https://msdn.microsoft.com/en-us/library/ms155391.aspx
If parameter value itself has characetrs like & in it you need to escape them first using javascript
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

SSRS 2012 background color format by expression issue when exporting to Excel.

We are using SSRS 2012. We have a report that conditionally formats a background color for some cells. The report renders properly in a browser and in Excel 2003 format. In Excel format all cells after the first one that meets the condition are highlighted,
even if only one cell should.
The sample expression that triggers this condition looks like this:
=IIF(Fields!VIOL_NOTE.Value="Internal","Green","No Color")
All cells after the first one that meets the condition Fields!VIOL_NOTE.Value="Internal" have a green background.
Excel 2003 (proper) results:
Excel (improper) results:
Zenon

Hi Zenon,
Based on your description, I try to reproduce the issue in my test environment, however it is work well. After export the report to Excel and Excel 2003, I can get exact same result when open the Excel file in Excel 2010.
Did you open the repot in Excel 2003 or Excel 2007-2010? Please post more deatils, so we can help to work out this issue.
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support

SSRS 2012 problem with excel export

Hello
I updated SSRS 2005 up to SSRS 2012. When I exported report in excel (xlsx) I got following warning :
"We found a problem with some conent in 'filnename.xlsx'.Do you want to try to recover as much as we can? if you trust the source of this workbook,click yes"
After Pressing Yes Button
"REpaired Recors: Cell information from .xl.worksheets.sheet1.xml port"
15
0.00000000000000000000 this is in string format instead decimal
2
0.00000000000000000000
This heppens if i have decimal(38.20) variable in table and record value is 0.
To avoid this problem i must change report and use this expression
=IIF(Fields!SomeValue.Value = 0, 0, Fields! SomeValue.Value)
for value in report, but this is not sulution for me because we have more then hundred reports.
Is any other solution?

Hi LashaGurgenidze,
The issue seems to be related to the Excel 2010 or the Excel 2007-2010 rendering extension in SSRS 2012. If possible, I suggest that you keep the Office 2010 and the SQL Server 2012 up to date, and check the issue again.
In order to solve the issue, we can enable the Excel 2003 rendering extension in SSRS 2012, and use this render when exporting to Excel. We can modify the EXCEL render extension in the rsreportserver.config file as follows:
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"/>
Then, the Excel 2003 render extension will be available in the Export drop-down list.
By default, the file is located in: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer. Before we modify it please backup the rsreportserver.config file.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

SSRS 2012 export to Excel 2010 Via IE8 has many compatibility issues

Hi There,
We have many reports in SSRS 2012 which had originally developed in SSRS 2005. When ever we render these report into Excel we face two major issues;
First: After reports render in to Excel (xlsx) format, we have cell, column, row shifting problem and every element of the report is not in the same place as appose to 2005 render to xls format. Second.
for any drill through (link) report all the url will be blocked by Excel.
We use SSRS 2012, Office 2010 and IE 8. Also we don't want to add Export to Excel 2003 feature. In other word we want out put in xlsx.
Any solution, suggestion, hotfix is appreciated

Hi Mercede,
According to your description, after you updated SSRS 2005 reports to SSRS 2012, reports render appose to 2005 when export them to Excel, and drill through link is blocked.
Question1:
A report definition file includes a reference to the RDL namespace that specifies the version of the report definition schema that is used to validate the .rdl file. After a report is upgraded locally or on the report server, you might notice additional errors,
warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying problems in the report are detected.
When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace. This is the only way
you can upgrade a report definition file.
In order to improve the efficiency of troubleshooting, I need to ask several questions:
“we have cell, column, row shifting problem and every element of the report is not in the same place as appose to 2005 render to xls format” Could you please provide detailed information about the problem? I would be appreciated it if you could provide
a screenshot.
Did you update the reports by opening the .rdl files in SSDT?
Could you export report to Excel 2003 to see if it displays correctly?
This may be a lot of information to ask for at one time. However, by collecting this information now, it will help us move more quickly toward a solution.
Question2:
I tested the issue in my local machine, when we add drillthrough action to the report, if we select Go to report or Go to URL, the link works fine after we export report to excel. It failed to work when we use javascript:void window.open to open a URL in new
windows, the “window.open” can’t work in Excel because of the JavaScript protocol can work only with an exact page.
For more information about Upgrade Reports, please refer to the following document:
https://msdn.microsoft.com/en-us/library/ms143674(v=sql.110).aspx
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support
Hi Wendy,
Thank you much for your fast respond. And as for your questions:
1- Yes I did upgrade them by using SSDT tools in VS2012 and then deploy them again into our SSRS2012 report server.
2- For URLs and Hyperlinks, because the action is go to sub report, I used "Go To Report" and by look at content that been blocked by Excel, I have noticed that (Go To Report) action passes IP address of our SSRS Server . I don't know how can I change
it to use the actual path instead.
3- Shifting the Cells and Rows means when I export report (from SSRS 2005) to excel in xls format (Excel 2003 for example), has very same look as it shows in screen, but when I export it from ssrs 2012 to render it in to xlsx format (Excel 2010 in our case)
I face with merging cells and when I compare this xlsx out put with xls out put of very same report I have see the row that used to be on A23 for example now is in A20 or the column that used to be in A7 now is in B9 for example. And required a lot of manual
work on design to work with spaced between text boxes and location of each data region, and overlaps to get the same result. I want to know is there more efficient way to achieve the same out put as xls.
4- I can't export report to render in Excel 2003 (xls) format directly from SSRS server for we don't have that option in our export list, but I did "save it as" xls and faced the same Row, column, cell shifting as with xlsx.
Thank you so much
I am realistic, I expect miracles.

SSRS 2012 Conditional Formatting Color Issues When Exporting to Excel

Hi all,
We recently upgraded to SQL 2012 from SQL2008 R2. I'm having a strange issue with SSRS2012.
One of the report has conditional formattings on cell background colors. Everything works fine when render the report in browser or preview mode. However, the conditional formatting stop working when export the report to Excel (no issues if
export to pdf). All cells are high-lightened with pre-defined color although it should only high-lighten those cells that fulfil the condition.
Has someone encountered this issue before ? Thanks for any help.

Hi ZZ02,
I have test the scenario in my testing environment, however, everything goes well when exporting to Excel format. The issue might be related to the expression for the conditional background color. To make further analysis, please post the expression as well
as the report design structure.
Additionally, in SQL Server 2012 Reporting Services, the Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010, the format of which is ExcelOpenXML. By default, the previous version of the Excel rendering extension,
compatible with Microsoft Excel 2003, is disabled. At this time, I suggest that you enable the Excel 2003 rendering extension by modifying the RSReportServer.config file. After that, the Excel 2003 rendering format will be available on report manager (not
available in Report Designer). So, please export the report from report manager and check the result again.
For more information about enable the Excel 2003 rendering extension, please see:
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0713de27-dcc0-4e51-81ac-5272647d171f
Regards,
Mike Yin
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Mike Yin
TechNet Community Support

Error on the reports with drill-through links on SSRS 2012 SP2 -- Invalid URI: The Uri string is too long

Hi, We are migrating SSRS 2008 R2 reports to SSRS 2012 SP2. (PS. SSRS 2012 SP2 has been applied.) Everything went smooth expect some reports which were using reporting services. These reports have some drilin-through actions and was passing in a huge
xml parameter. I referred to some other posts in which there were also some similar issues like "The Uri string is too long." but they're different. My reports can be opened and the error only occurred when accessing the drill-through actions.
As I know, Microsoft has provided the fix for the known issue "The Uri string is too long." in sp1 but it looks it can't cover this kind of situation since I have installed the SSRS SP 2. Is there any solution? In addition, there's no such
issue on SSRS 2008 R2.
Thanks,
onizga

Hi onizga,
According to your description that you are migrating SSRS 2008 R2 reports to SSRS 2012 SP2, after migration you got some error like “The Uri string is too long” which only occurred when accessing the drill-through actions, right?
Usually, the issue can be caused when you try to pass some parameters that cause the URL length to exceed 65,520 characters for a Microsoft SQL Server 2012 Reporting Services (SSRS 2012), you cannot render the report, and you may receive the following error
message:
The value of parameter 'param' is not valid. (rsInvalidParameter).Invalid URI: The Uri string is too long.
This is an known issue and already have the hotfix SQL Server 2012 Service Pack1 Cumulative Update 9 (CU9) as you know, you can try to reinstall this hotfix to fixed this issue:
http://support.microsoft.com/kb/2916827 .Any issue after applying the update, please post it on the following thread or you can submit an feedback:
http://connect.microsoft.com/SQLServer/feedback/details/788964/ssrs-2012-invalid-uri-the-uri-string-is-too-long
Similar threads for your reference:
SSRS - The value of parameter 'param' is
not valid. ---> System.UriFormatException: Invalid URI: The Uri string is too long.
Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException:
The value of parameter 'pSetOfScopes' is not valid. ---> System.UriFormatException: Invalid URI: The Uri string is too long
If you still have any question, please feel free to ask
Regards
Vicky Liu
If you have any feedback on our support, please click here

SSRS 2012 Excel Rendering Error

Similar Messages

Maybe you are looking for