Server Error in PPT Renderer after SSRS 2008 SP2 installation

atetter · August 19, 2010, 8:50am

We got this error (pls. refer to the error msg. below) everytime we export our report from Report Manager to PPT/PPS renderer (all Aspose Slides) after installing SSRS 2008 SP2. This is not a problem before when we are in SSRS 2008 SP1. What you think is the problem? Your help will be appreciated!

Thanks, Ness

Server Error in '/Reports' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

mudassir.fayyaz · August 19, 2010, 1:11pm

Dear Agnes,

I have tried to understand the issue specified by you, but in order to reproduce the specified issue, I am already downloading SQL Server 2008 SP2. As soon as, I have some conclusion, I will share that with you. One possible reason for the error could be that you may have updated to SQL Server SP2 without un-installing the Aspose.Slides for Reporting Services. Can you please follow the guidelines mentioned here and perform the steps accordingly. Hopefully, by re-installing the Aspose.Slides for RS, things may work for you.

We are sorry for your inconvenience,

mudassir.fayyaz · August 19, 2010, 7:07pm

Dear Ness,

I have downloaded the MS SQL Server 2008 SP2 from here. I uninstalled the Aspose.Slides for Reportig Services from my machine first. Then I updated to my MS SQL Server 2008 SP1 to MS SQL Server 2008 SP2. I restarted the machine to effect the changes and after restart, I installed the Aspose.Slides for Reporting Services version 3.5.0. It successfully got installed and I was able to generate the reports in all formats supported by Aspose.Slides for RS. I feel, you may please un-install the existing Aspose.Slides for RS setup and re-install that as shared in my earlier post.

Thanks and Regards.

atetter · August 20, 2010, 6:49am

Thanks for the help Mudassir. It is now working!

mobilop · August 24, 2010, 9:59am

This also affects a fresh SQL 2008 R2 installation. I installed Aspose.Slides for Reporting Services 3.5 and after restarting the Reporting Services I get the following error which is also logged in the system event log. Is the current version compatible with 2008 R2, seeing System.MethodAccessException, rather not ... ?

This crash is always, even very simple reports, so nothing works.

In the Reporting Services\LogFiles folder crash dump files are created, which show a stack trace to Aspose.Slides:

reportrendering!ReportServer_0-15!d2c!08/24/2010-16:15:09:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: , Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: Fehler beim Rendern des Berichts. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: Fehler beim Rendern des Berichts. ---> System.MethodAccessException: Microsoft.ReportingServices.Rendering.RPLProcessing.RPLReport.Release()
at Aspose.Slides.ReportingServices.BaseRenderer.a(Object a, RPLReport a, c a, Int32 a)
at Aspose.Slides.ReportingServices.BaseRenderer.a(Object a, c a, Object a)
at Aspose.Slides.ReportingServices.BaseRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream createAndRegisterStream)
at Aspose.Slides.ReportingServices.BaseRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
--- End of inner exception stack trace ---
at Aspose.Slides.ReportingServices.BaseRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderFromOdpSnapshot(IRenderingExtension newRenderer, String streamName, ProcessingContext pc, RenderingContext rc)
--- End of inner exception stack trace ---;

Server Error in '/Reports' Application.

Microsoft.ReportingServices.Rendering.RPLProcessing.RPLReport.Release()

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Microsoft.Reporting.WebForms.ReportServerException: Microsoft.ReportingServices.Rendering.RPLProcessing.RPLReport.Release()

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ReportServerException: Microsoft.ReportingServices.Rendering.RPLProcessing.RPLReport.Release()]
[ReportServerException: Fehler beim Rendern des Berichts.]
[ReportServerException: Fehler beim Rendern des Berichts. (rrRenderingError)]

Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension) +558

Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +1040

Microsoft.Reporting.WebForms.ServerReport.Render(String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +28

Microsoft.Reporting.WebForms.ServerModeSession.RenderReport(String format, Boolean allowInternalRenderers, String deviceInfo, NameValueCollection additionalParams, Boolean cacheSecondaryStreamsForHtml, String& mimeType, String& fileExtension) +85

Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +151

Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +183

System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053

mudassir.fayyaz · August 24, 2010, 12:32pm

Dear Maurice,

I regret to inform you that support for SQL Server 2008 R2 is currently unavailable in Aspose.Slides for RS. An issue with ID 17670 has already been created in our issue tracking system to provide the desired feature support. This thread has also been linked with the issue, so that you may be automatically notified, once the feature is available online.

We are sorry for your inconvenience,

HSTMResearch · September 11, 2010, 10:28am

Mudassir --

I notice responses from you on this topic in several threads going back a couple of months, referencing the same issue number 17670. Can you provide any update on that issue? This is a growing problem for us, as we have client-facing features for our product that require R2 and we cannot upgrade because of the PowerPoint incompatibility.

As a development manager for web-based products that depend on other vendors' tools (including Microsoft's), I know how frustrating it can be when a vendor changes a tool that "breaks" your product through no fault of your own and your customers clamour to you for a fix. I understand that is your situation, and I know your staff is working to resolve it as quickly as they can, but we'd appreciate it if you can provide at least some information on the status of your fix and an estimate of the timeline for a release of an R2-compatible version.

Is there any information you can provide...please?

Thanks in advance...

Paul

mudassir.fayyaz · September 14, 2010, 12:36am

Dear Paul,

We are very hopeful that the support for SQL Server 2008 for R2 will be available by end of September. Our development team is striving hard for the issue resolution and we will be really happy to share the good news with you soon.

Thanks and Regards,

HSTMResearch · September 27, 2010, 9:34am

Mudassir --

Thanks for your notes a couple of weeks ago. Is there any update on the status of an R2-compatible version of Aspose.Slides?

Thanks,

Paul

mudassir.fayyaz · September 27, 2010, 11:00am

Dear Paul,

We are very much hopeful that the support for SQL Server 2008 R2 will be available by end of Septmeber. You will be automatically notified, once the feature is available.

Thanks and Regards,

HSTMResearch · September 27, 2010, 11:02am

Thanks for letting me know, Mudassir.

Paul

aspose.notifier · September 30, 2010, 2:52pm

The issues you have found earlier (filed as 17670) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(3)

mobilop · October 1, 2010, 3:28am

Hi Paul/pccox,

can you install this update (3.6.0) on SQL2008 R2 and confirm the error I am getting.

1. I deinstalled the old setup
2. I installed with the new setup and copied the dll in the 2008R2 folder again
3. rssrvpolicy.config looks ok, with FullTrust entry for Aspose.Slides
4. I restarted the Reporting service

Check the log file, such as
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQL2008\Reporting Services\LogFiles\SQLDmpr0014.log

library!ReportServer_0-99!102c!10/01/2010-10:05:42:: w WARN: Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: Fehler beim Rendern des Berichts. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: Fehler beim Rendern des Berichts. ---> System.NullReferenceException: Object reference not set to an instance of an object.
webserver!ReportServer_0-99!102c!10/01/2010-10:05:42:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Fehler beim Rendern des Berichts. ---> Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: Fehler beim Rendern des Berichts. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: Fehler beim Rendern des Berichts. ---> System.NullReferenceException: Object reference not set to an instance of an object.
ui!ReportManager_0-100!1520!10/01/2010-10:05:42:: Unhandled exception: Microsoft.Reporting.WebForms.ReportServerException: Fehler beim Rendern des Berichts. (rrRenderingError) ---> Microsoft.Reporting.WebForms.ReportServerException: Fehler beim Rendern des Berichts. ---> Microsoft.Reporting.WebForms.ReportServerException: Object reference not set to an instance of an object.
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WebForms.ServerReport.Render(String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension)
at Microsoft.Reporting.WebForms.ServerModeSession.RenderReport(String format, Boolean allowInternalRenderers, String deviceInfo, NameValueCollection additionalParams, Boolean cacheSecondaryStreamsForHtml, String& mimeType, String& fileExtension)
at Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
library!ReportServer_0-99!120c!10/01/2010-10:07:09:: i INFO: RenderFromSession('/AssessmentReview/EvidenceReport')
reportrendering!ReportServer_0-99!120c!10/01/2010-10:07:09:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: , Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: Fehler beim Rendern des Berichts. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: Fehler beim Rendern des Berichts. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at ..ctor(Object )
at Aspose.Slides.ReportingServices.RendererBase.(Object )
at Aspose.Slides.ReportingServices.RendererBase.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream createAndRegisterStream)
at Aspose.Slides.ReportingServices.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
--- End of inner exception stack trace ---
at Aspose.Slides.ReportingServices.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderFromOdpSnapshot(IRenderingExtension newRenderer, String streamName, ProcessingContext pc, RenderingContext rc)
--- End of inner exception stack trace ---;

Trueblue · October 1, 2010, 9:05am

i can confirm the error!!!

i upgraded my version to 3.6.0 (i buyed license 3 months ago for my
sqlrs2008r2 and i’d never used!) and this morning i was so happy to know
that the new version would solve my problem but after installation the
surprise…

mudassir.fayyaz · October 1, 2010, 9:34am

Hello Dear,

We are greatly sorry for your inconvenience. We are investigating the matter and will share the necessary information with you.

Thanks and Regards,

mudassir.fayyaz · October 1, 2010, 9:50am

Hello Dears,

I have discussed with our development team. Initially, it does not seem to be an installation issue. We need to further investigate the issue as the all tests exports worked fine on our end. This should be additionally investigated and It would be great if you may please provide some simple RDL for testing and check if TIFF export works fine on their server with the same reports. Please share requested information to expedite the issue resolution.

We are sorry for your inconvenience,

mobilop · October 1, 2010, 10:07am

Hello Mudassir,

I confirm that the TIFF export works perfectly.

This is our production server where we export XLS, DOC and PDF very smoothly.

Please find a very simplified RDL attached which we use as XLS export normally and does work as TIFF but not PPT.

Regards

mobilop

mudassir.fayyaz · October 1, 2010, 11:14am

Dear Mobilop,

Thanks for sharing the necessary piece of information. We are working in the specified issue and will share the feedback with you ASAP.

Thanks and Regards,

HSTMResearch · October 1, 2010, 11:57am

Mudassir --

Here is another very simple example of an RDL that exports from R2 to all formats except PPT, PPS, PPTX, PPSX using 3.6.

Change the data source to any ReportServer database you have.

I've also attached SSRS Log output I got when attempting to export to the various PPT formats.

Paul C.

mudassir.fayyaz · October 4, 2010, 12:47am

Dear Paul,

Thanks for sharing added piece of information for necessary investigation. Our development team is investigating the issue and we really appreciate your patience response for that. We will share information and possible fix with you ASAP issue is resolved.

We are sorry for your inconvenience,