Free Support Forum - aspose.com

Zero byte file with Aspose.PDF for SSRS 2.2

Hi - we are running Aspose.PDF for Reporting Services 2.2.0 on Windows 2003 R2 x64 / SQL Server 2008 Standard SP1.


The rendering extension has installed fine using the MSI package (both the rsreportserver.config and rssrvpolicy.config files contain Aspose entries) and the extension appears in the export list within SSRS reports.

When we try to export a report to PDF via Aspose.PDF format via the SSRS interactive site (/Reports), we get a zero byte file with no file extension. Normal PDF export works (as does the other file formats). The ReportServerService__date.log file just shows that it’s rendered something with no errors:

library!ReportServer_0-47!1e8c!06/03/2011-14:01:17:: i INFO: RenderFromSession(’/PCD Reports/Valuations/DiscretionaryValuation’)
webserver!ReportServer_0-47!1e8c!06/03/2011-14:01:17:: i INFO: Processed report. Report=’/PCD Reports/Valuations/DiscretionaryValuation’, Stream=’‘


When we export via the SSRS /ReportServer/, we get an Object reference not set to an instance of an object error with the following exception shown in the log

library!ReportServer_0-47!1bdc!06/03/2011-13:49:03:: i INFO: RenderFromSession(’/PCD Reports/Valuations/DiscretionaryValuation’)
library!ReportServer_0-47!1bdc!06/03/2011-13:49:04:: Unhandled exception was caught: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.WebServer.ReportExecution2005Impl.InternalRender(String Format, String DeviceInfo, PageCountMode pageCountMode, Stream& Result, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds)
at Microsoft.ReportingServices.WebServer.ReportExecutionService.InternalRender(String Format, String DeviceInfo, PageCountMode PaginationMode, Stream& Result, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds)
at Microsoft.Reporting.WebForms.ServerReport.InternalRender(String format, String deviceInfo, PageCountMode pageCountMode, String& extension, String& mimeType, String& encoding, String[]& streams, Warning[]& warnings)
at Microsoft.Reporting.WebForms.ServerReport.Render(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& extension)
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-47!1bdc!06/03/2011-13:49:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. —> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.WebServer.ReportExecution2005Impl.InternalRender(String Format, String DeviceInfo, PageCountMode pageCountMode, Stream& Result, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds)
at Microsoft.ReportingServices.WebServer.ReportExecutionService.InternalRender(String Format, String DeviceInfo, PageCountMode PaginationMode, Stream& Result, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds)
at Microsoft.Reporting.WebForms.ServerReport.InternalRender(String format, String deviceInfo, PageCountMode pageCountMode, String& extension, String& mimeType, String& encoding, String[]& streams, Warning[]& warnings)
at Microsoft.Reporting.WebForms.ServerReport.Render(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& extension)
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)
— End of inner exception stack trace —


Could you let us know how to fix.

Thanks
Graeme.

Hello Graeme,

Thanks for using our products.

We are working over this query and will get back to you soon. We are sorry for your inconvenience.

Hello Graeme,

Thanks for using our products.

I have tested the scenario and I am able to notice that Aspose.Pdf for Reporting Services is causing an issue while exporting an RDL file into PDF format when using SQL 2008 Reporting Services. For the sake of correction, I have logged this problem as PDFREP-28108 in our issue tracking system. We are further look into the details of this problem and will keep you updated on the status of correction. We are really sorry for this inconvenience.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Hi Nayyer, has any progress been made on this issue?

Regards,

Graeme

Hello Graeme,

I am pleased to inform you that we have made some significant progress towards the resolution of this problem and we expect to include its HotFix in next release version. As soon as the new version becomes available, we would be more than happy to update you with the status of correction. Please be patient and spare us little time. We apologize for your inconvenience.

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


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