Hi,
I have an RDL that I am rendering as a PDF and it is creating one long page for the output without any page breaks. Also, it is a 2 column report and it is rending as 1 column. Are 2 columns supported by this engine?
Thanks
@dduclos,
Thank you for contacting support. If the report server renders a report with 2 columns and Aspose.Pdf API export this report with 1 column, then it might be a bug. Kindly send us your RDL file, we will investigate and share our findings with you.
Best Regards,
Imran Rafique
@dduclos,
We are preparing the required environment of reporting services and will get back to you soon at the end of this week or early next week. Please spare us a little time.
Best Regards,
Imran Rafique
1 Like
Thank you, we are under some time pressure to evaluate if we can use your engine for our purposes, so the sooner the better.
Also, I updated the original RDL file that we are working with for this.
Thanks again
Sure, we are in progress to replicate the issue in our environment and will get back to you soon.
Best Regards,
Imran Rafique
Thanks for your patience.
I have tried opening the input .RDL file in VisualStudio Business Intelligence studio 2008 but I am unable to view it. When I have viewed the code for file, it shows SQL 2008 as report definition. However, can you please share some details regarding your working environment so that we can again try replicating the issue in our environment. We are sorry for this delay and inconvenience.
@dduclos,
In addition to the above reply, kindly also send us your RSPreviewPolicy.config, RSReportDesigner.config, rssrvpolicy.config and rsreportserver.config files. It will help us to replicate the problem in our environment. Your response is awaited.
Best Regards,
Imran Rafique
@imran.rafique Thank you for your assistance. I am editing the RDL in Visual Studio 2010 Professional, I believe it was created in this as well, running against SQL Server 2012. I am not seeing the files you mention on my system. I don’t have Reporting Services installed, we are using the Microsoft Report Viewer 2012 Runtime.
Let me know of any other information or files that are needed.
Thanks
@dduclos,
Thank you for the details. We have prepared an environment to work with RDLC files. Kindly create a small project, which reproduces this issue in your environment, and then send us the Zip file of this project along with the database. You may create a small database to share with us because it will save our time to create it. It would not be possible for us to insert the same values as you are fetching from the database in your environment. Please also give a brief note on the flow of the project. Your response is awaited.
PS, we recommend our clients to share the complete details of the use case.
Best Regards,
Imran Rafique
Adding more to Imran’s comments, in order to view the report, we had to first change the file extension from .RDLC to .RDL and when I have tried viewing the file in SQL Server 2012 Report Server, it requested the credentials to connect the server and upon provision of local machine credentials, it requested some parameters. Can you please share some details on how we can further test the scenario. Please take a look over attached image file.
PS, as requested by Imran, if report is based on some database, please share the data source, so that we can further look into this matter.
Report_Preview.PNG (16.8 KB)
Hi,
@imran.rafique @codewarior
Here is a small project reproducing the issue https://drive.google.com/open?id=0B879LsYu0fSPc09uSGJxeE9oWGc I’m running it in Visual Studio 2010 and the report opens under that as well. The project contains an MDF database with test data. On the default page there are 2 buttons that invoke the rendering of the PDF with and without use of Aspose component. When the report is rendered normally it is 2 columns, when it is rendered with Aspose it has only 1 column and 1 continous page.
Let me know if the project is sufficient to illustrate issue or if more information is needed.
Thank you
@dduclos,
Thank you for sharing a small project. We managed to replicate the said behavior in our environment. We have logged an investigation under the ticket ID PDFRS-33547 in our issue tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates. We are sorry for the inconvenience.
Best Regards,
Imran Rafique
@dduclos,
Well, the issue logged under the ticket ID PDFRS-33547 has just been identified and it will take some time for our product team to further investigate the issue as per the development schedule. We will let you know when a significant progress has been made in this regard.
Best Regards,
Imran Rafique
The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan