Please add all this in loop for further update.
@vikash.kumar,
Our developers have investigated the case. We want to focus your attention on the fact that neither method
byte[] results = executionService.Render(PPTX, deviceinfo, out extension, out encoding, out mimeType, out warnings, out streamIDs);
nor method
byte[] result = executionService.Render("RPL", deviceInfo, out extension, out encoding, out mimeType, out warnings, out streamIDs);
is in any way related to Aspose.Slides for Reporting Services.
The difference in these methods is only in passing parameters to them. In this case, the transmitted parameters also do not relate to the Aspose.Slides for Reporting Services in any way. This method returns the result of the rendering performed on the report server, and again, neither this rendering itself nor passing the rendering result to the target object has anything to do with Aspose.Slides for Reporting Services. The work of the Aspose.Slides for Reporting Services begins only after the result of the pre-rendering has been received from the server, namely an array of bytes representing the RPL file. All the work of the Aspose.Slides for Reporting Services is contained in the renderer.RenderPage(rplStream) method and what happens before this call is not the responsibility of the Aspose.Slides for Reporting Services.
We recommend you eventually try to reinstall the server.
Do we need to re-install the Reporting Service or Window Server where our reporting service is installed?
Please Confirm .
Reporting Service
Regards
Preeti Arora
Hi All ,
Not sure is the right fix or not but we need to keep doing alternatives to fixed it up.
I have seen it from one link in google.
Regards
Preeti Arora
@Arora_Preeti_Global_D_T,
If you have problems with Aspose.Slides for Reporting Services, please create a new forum topic and describe the problems you encountered. We will do our best to help you.
8 posts were split to a new topic: Performance Issue while Retrieving the RPL Report with Aspose.Slides for SSRS