We have added an Excel named range to a report to be used in a pivot table but when the Excel report is created the named range is missing the bottom row.
See the sheet named Details on the attached spreadsheet. The named range cover rows 1 to 6 when it should be 1 to 7.
Also when we create an XLSX spreadsheet we get a pivot table but when we create an XLS there is no pivot table just text in a few cells. How do we get a pivot table in an XLS file?
We are using Reporting Services 2008 and Excel2007
Thank you for considering Aspose.Cells for Reporting Services.
At the moment, Asponse.Cells for Reporting Services doesn’t support Pivot Table Conversion from Excel 2007 to Excel 2003. Your designed report includes Pivot tables in Excel 2007, and you can only export Excel 2007 report file for having a pivot table.
However, we are planing to support Pivot Table conversion from Excel 2007 to Excel 2003 in future, which may take four months to achieve.
It has not solved the problem but I am wondering if this is due to us having problems updating a single DLL. Last time we had the same problems, this was only fixed by using a complete MSI install.
Do you have a new msi install to try?
We have updated the folder specifed and also tried repalcing every occurance of the file found. we have also restarted Report Services but cannot restart the sever
Please download the updated version of DLL & replace all instances of Aspose.Cells.ReportingServices.dll for reporting Services from SQL and also from Visual Studio Private Assemblies folder with this version of DLL.
It will resolve the problem.
If the persist, please let us know. we will share the MSI installer with you.
We have donwload the dll and have have updated "all" copies of the file on the server and development computer.
Now on the development computer we get a run time automation error within Execl. If we debug the excel macro we see it cannot create an instance of "Apsose.Cells.ReportingSevice.Client.AsposeClient". We have reregistered this assembly with RegAsm but this has not helped.
We are now in a desperate situation needing to finish a report today for a customer but have no means of continuing. We are in a worse state than before. Could you please release an MSI file as a matter of urgencey as clearly copying the dll alone does not work as you describe.
We are on the verge of loosing a valuable order and are utterly desperate to get a resolution to this bug which was reported 2 weeks ago.
We are more than happy to upgrade by using the dll if an msi file cannot be provided but we cannot find a way to get this new dll to work.
The problem is most likely with us but having numerous times followed the instructions given we find that our development machine is not longer usable and the live system appears to be still using the old dll (or the problem stilled exists).
Can somebody please help and tell us how we can get the new dll installed?
Attached is a screen shot of all the dlls replaced on the server.
We have reinstalled the old MSI on the development computer so we can continue developing. Otherwise I would include a screen shoot showing which files were replaced here as well.
We are using reporting services so have no code to provide.
We do not wish to continue using the existing msi we desperately want to use the latest dll released to us to fix the named range problem. Currenty the named range is missing the bottom row and as such means the pivot table is wrong.
Could you also explain how to remove the "&=UtilisationDataSet.Groupname" as this is created by your software (it maybe related to the above problem) and seems to be another bug.
We are currently using v5.2.12 but desperate to upgrade to v5.2.13. Please tell us how to do this.
Please verify the following information at your end:
the follow context is about Aspose.Cells.ReportingServices.DLL files deploy description at Aspose.Cells for Reporting Services installation folder.
There are six folders at ${Aspose.Cells for Reporting Services installation folder}/bin folder.
The Aspose.Cells.ReportingServices.DLL file which is at "ReportDesinger" folder is Aspose.Cells for Reporting Services report designer. it is deployed at ${Aspose.Cells for Reporting Services installation folder}/bin folder.
The Aspose.Cells.ReportingServices.DLL file which is at "SSRS2000" folder supports SQL Server 2000 for Reporting Services Extend render. it is deployed at ${SQL Server 2000 for Reporting Services folder}/ReportServer/bin folder.
The Aspose.Cells.ReportingServices.DLL file which is at "SSRS2005" folder supports SQL Server 2005 for Reporting Services Extend render. it is deployed at ${SQL Server 2005 for Reporting Services folder}/ReportServer/bin folder.
The Aspose.Cells.ReportingServices.DLL file which is at "SSRS2008" folder supports SQL Server 2008 for Reporting Services Extend render. it is deployed at ${SQL Server 2008 for Reporting Services folder}/ReportServer/bin folder.
The Aspose.Cells.ReportingServices.DLL file which is at "ReportViewer2005" folder supports report viewer for visual studio 2005 Extend render.
The Aspose.Cells.ReportingServices.DLL file which is at "ReportViewer2008" folder supports report viewer for visual studio 2008 Extend render.
Please also confirm the following:
1. Please find Aspose.Cells.ReportingServices.DLL file in ${SQL Server 208 for Reporting Services}\ReportServer\bin\ folder;
2.Check it version.
3.If it's version is not 1.5.2.13 ,please copy ${Aspose.Cells for Reporting Services installation foldler}\Bin\SSRS2008\Aspose.Cells.ReprotingServices.DLL file into ${SQL Server 208 for Reporting Services}\ReportServer\bin\ folder.
Attached is the result of the test performed on our end.
Reporting Services was on a seperate drive (D:) which was not searched. The dll was an older version and has now been replaced. All is working now, the named range problem is fixed.
When reporting services runs, Aspose.Cells.ReportingServices.dll which is at ${SQL Servr Reporting Services}\bin folder cannot replaced in the installation of Aspose.Cells for Reporting Services.
May be this is the possible reason that the dll is of older version.
Please reference following operations.
1. Stop the Reporting Service on the server. 2. Uninstall the previous version on computers. 3. Install the new version on computers 4. Start the Reporting Service on the server.
Yes, I believe this is the reason we had problems, along with the file being on a different driver (D:) to the main installation (C:), so was missed by us when searching for all dll's. Once we realized we did what you have suggested and all was okay. This probaly also explains why we could not update by just replacing the dll, as we did not replace this one.
Thanks
Phil
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
Enables storage, such as cookies, related to analytics.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.