Export error using Aspose.cells

Aspose.Cells Product Family
1

We are getting the error below when we try to use the export to any Aspose type. It works to CSV but the native excel doesn’t allow us to go past the 65k row limit.

An error occurred while exporting the report.
error message Could not load type ‘Microsoft.ReportingServices.OnDemandReportRendering.Map’ from assembly ‘Microsoft.ReportingServices.ProcessingCore, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’.
stack trace at Aspose.Cells.ReportingServices.ReportItem. at Aspose.Cells.ReportingServices.ReportItem.xbd8cd0af7299d656.xb068ca8b20b829ba(ReportItem xe4de920c4d28a5eb)
at Aspose.Cells.ReportingServices.Report. at Aspose.Cells.ReportingServices.Renderer.x287918d12b9d430a(Report x64343a0786fb9a3f, NameValueCollection x4d7e972a483f38e6, NameValueCollection x769338e163ee6eb4, NameValueCollection x69ea43ef171861cd, Hashtable& xcc726f61cfb91835, CreateAndRegisterStream x6af66da7eca40f82)
at Aspose.Cells.ReportingServices.ReportItem. at Aspose.Cells.ReportingServices.Renderer at Aspose.Cells.ReportingServices.ReportItem.
2

Hi,

Thanks for reporting. Your issue has been logged as CELSSREP-24644.

3

Hi,

Thanks for providing us the RDL file.

We have checked your issue with our findings.

1) The .CSV format does support more than 65k rows limit.
2) Map report item is provided by SSRS2008 R2.
If you use Aspose.Cells for Reporting Services 2008 R2 version to deploy on SQL Server 2008 Reporting Services, the error will be occurred.
Please tell us how you deploy Aspose.Cells for Reporting Services and which version of Aspose.Cells.ReportingServices.dll version you are using?

Please try copying Aspose.Cells.ReportingServices.dll which is be ${installation folder} \Bin\SSRS2008R2\ folder into the following folder: ${ SQLSERVER2008R2 installation folder} \Reporting Services\ReportServer\bin.


Kindly give us your feedback.

Thank you.

4

That report was running on a 2008 instance. I downloaded the latest version of the dll and applied the correct version and it is working now.

5

Hi,

Thanks for updating us.