dhenning - Friday, June 29, 2007 2:52 PM:
I have a report linked in Innovator to reporting services which produces an error when I run it in Innovator. however, if I take the link for Report Manager (from innovator) I can run the report in Reporting services and it runs fine - exactly as I would expect.
The error that comes back to the screen is:(partially):
System.Web.Services.Protocols.SoapException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.ArgumentOutOfRangeException: Non-negative number required. Parameter name: value at System.IO.MemoryStream.set_Position(Int64 value) at Microsoft.ReportingServices.Rendering.ImageRenderer.CanvasPDF.MonochromeJpeg(MemoryStream memStream) at Microsoft.ReportingServices.Rendering.ImageRenderer.CanvasPDF.ProcessImage(CanvasImagePDF image, Double left, Double top, Double width, Double height, Boolean scaleImage) at Microsoft.ReportingServices.Rendering.ImageRenderer.CanvasPDF.DrawImage(OutlineObjects outlines, CanvasImage image, Double left, Double top, Double width, Double height) at Microsoft.ReportingServices.Rendering.ImageRenderer.Image.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.Rectangle.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.SubReport.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.Rectangle.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage
I cannot seem to figure out where the problem is. I have reattached the report to a shared data source which works with other reports (that was a source of problems for me before), and that does not solve the problem.
Anyone have any ideas that could cause this rendering problem?
Thank you.
snnicky - Wednesday, July 4, 2007 8:26 AM:
Does any report work for you via Innovator? For example some sort of "Hello, World!" report?
Please try different report formats also. For example:
- &rs:Format=Excel
- or &rs:Format=PDF
- or &rs:Format=HTML4.0
Add a proper string at the end of your report query.
If nothing works please post the complete error stack trace (the error you posted partially).
dhenning - Tuesday, July 10, 2007 10:19 AM:
My delay in reply has not been from lack of interest. (We were shut down and mandatory vacation for week of July 4th). I have gone back and worked on this with your suggestions. A.) Other reports work - specifically I have a generic report listing items and their related items. B.) Using other report format of HTML 4.0 - report comes back but picture does not. As an additional chase down, I went into the vault and changed the file name of the picture that was being referenced in the report; then ran the report from Innovator and report showed fine except there was no picture (since it could not find it any longer). But, if I take the item I am reporting on and get its id ( right click, properties, copy) and go into Report Manager from Innovator. There I select the report and run it - entering the id - and the report runs fine....picture and all.
In Innovator when I run the report the full error message is:
System.Web.Services.Protocols.SoapException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.ArgumentOutOfRangeException: Non-negative number required. Parameter name: value at System.IO.MemoryStream.set_Position(Int64 value) at Microsoft.ReportingServices.Rendering.ImageRenderer.CanvasPDF.MonochromeJpeg(MemoryStream memStream) at Microsoft.ReportingServices.Rendering.ImageRenderer.CanvasPDF.ProcessImage(CanvasImagePDF image, Double left, Double top, Double width, Double height, Boolean scaleImage) at Microsoft.ReportingServices.Rendering.ImageRenderer.CanvasPDF.DrawImage(OutlineObjects outlines, CanvasImage image, Double left, Double top, Double width, Double height) at Microsoft.ReportingServices.Rendering.ImageRenderer.Image.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.Rectangle.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.SubReport.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.Rectangle.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.RenderToPage(Measurement parentClipBorder) at Microsoft.ReportingServices.Rendering.ImageRenderer.ImageRendererBase.ProcessPages(CompositionBase theComposition, Report theReport, Boolean needTotalPages, Int32 startPage, Int32 endPage, Boolean render) at Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport.RenderReport(Report report, NameValueCollection deviceInfo, EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions, CreateAndRegisterStream createAndRegisterStreamCallback, Int32 streamPageNumber) at Microsoft.ReportingServices.Rendering.ImageRenderer.ImageRendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions, CreateAndRegisterStream createAndRegisterStream) --- End of inner exception stack trace --- at Microsoft.ReportingServices.Rendering.ImageRenderer.ImageRendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension renderer, DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc, CreateReportChunk cacheDataCallback, Boolean& dataCached) --- End of inner exception stack trace --- at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension renderer, DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc, CreateReportChunk cacheDataCallback, Boolean& dataCached) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc) at Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext reportContext, ItemProperties properties, ParameterInfoCollection effectiveParameters, Guid reportId, ClientRequest session, String description, ReportSnapshot intermediateSnapshot, DataSourceInfoCollection thisReportDataSources, Boolean cachingRequested, Boolean isLinkedReport, Warning[]& warnings, ReportSnapshot& resultSnapshotData, DateTime& executionDateTime, RuntimeDataSourceInfoCollection& alldataSources, UserProfileState& usedUserProfile) at Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters) at Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames) at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute() at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper() --- End of inner exception stack trace --- at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper() at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobType type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames) at Microsoft.ReportingServices.WebServer.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, Byte[]& Result, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds) --- End of inner exception stack trace --- at Microsoft.ReportingServices.WebServer.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, Byte[]& Result, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds)
It obviously has something to do with the picture, and it is only happening when I invoke the report inside Innovator.
-Dennis
dhenning - Tuesday, July 10, 2007 11:37 AM:
Later developments on this issue:
In the Report Manager context of running this report, I just found that if I try to take the report result in reporting services (which renders just fine) and export it to PDF format, it encounters a rendering error too. So that means the problem does lie within reporting services - not the link from Innovator that I was thinking it was. Is there someone with reporting services knowledge that may have encountered this type of problem before?
snnicky - Wednesday, July 11, 2007 3:50 AM:
I tried to make a report using Reporting Services on SQL Server 2005.
That was quite simple 3 columns and an image in header.
1) I saw the problem you mentioned with HTML4.0 report format (image didn't display when run via Innovator)
2) PDF format run fine for me.
What happens to PDF report if you try some other image ? Other image format ?
dhenning - Wednesday, July 11, 2007 8:16 AM:
Aha! I tried a different image format (a GIF instead of JPG) and the image displayed! (different image). So then I went back and selected a different JPG image from the same directory on my computer and it failed as before. Then I picked a JPG from a different directory and it displayed. Then I went and tried some others - each time I went back to Innovator and edited the item instance and changed the picture being referenced in the file type attachement - and it turns out that some jpg's display some do not. but bmp's in those same directories do display. The size of the jpg's that don't display - which I tried - ranged from 612 KB to 642 KB. The size of one of the jpg's that did display was 675 KB! And the bitmap I tried was 5.2MB!
Is this a real bug in reporting services? it is truely confounding me. Thanks for your disciplined questions.
snnicky - Wednesday, July 11, 2007 11:16 AM:
I would say this is a bug in Reporting Services. I saw software (not related to Innovator) that accepted JPG files created in Photoshop and rejected JPG created in mspaint. Perhaps Reporting Services have similar problem.
Please let us know what version of Reporting Services you use. Do you have the latest service pack for Reporting Services installed ?
dhenning - Monday, July 16, 2007 11:50 AM:
We were on SQL SErver 2005 SP 1. So we upgraded to Service Pack 2 - but the problem still persists....same error message....same behavior...some pictures display/render fine, others - of equivalent size, same file type (jpg) - generate the error.
