| |
|
|
|
|
|
|
Display using:
|
|
Exporting to PDF produces Invalid Argument Exception
Posted: 13 Jul 2007 11:30 AM |
Hi all,
Iv run into a problem when exporting to PDF.
What im doing, is, using a Console Application to programatticly generate the PDF File.
However, when I try to run the report via the designer in visual studio, i get the Generic GDI+ Error also.
This is occuring with SQL 2000 Reporting Services with SP2 installed.
The following is an exception in the Reportign Services Log File.
w3wp!processing!874!7/13/2007-11:21:00:: e ERROR: System.ArgumentException: Invalid parameter used.
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height)
at Dundas.Charting.WebControl.Chart.SaveWithScaleFactors(Stream imageStream, Single scaleX, Single scaleY)
at Microsoft.ReportingServices.ReportRendering.DundasChart.GetImage(ImageType type, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.DundasChart.GetImage(ImageType type, ChartInstanceInfo instanceInfo, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.Chart.GetImage(ImageType type, Boolean& hasImageMap)
w3wp!processing!874!7/13/2007-11:21:03:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An error has occurred during rendering of chart chart1. Details: Invalid parameter used., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An error has occurred during rendering of chart chart1. Details: Invalid parameter used. ---> System.ArgumentException: Invalid parameter used.
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height)
at Dundas.Charting.WebControl.Chart.SaveWithScaleFactors(Stream imageStream, Single scaleX, Single scaleY)
at Microsoft.ReportingServices.ReportRendering.DundasChart.GetImage(ImageType type, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.DundasChart.GetImage(ImageType type, ChartInstanceInfo instanceInfo, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.Chart.GetImage(ImageType type, Boolean& hasImageMap)
--- End of inner exception stack trace ---
w3wp!reportrendering!874!07/13/2007-11:21:43:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: Exception of type Microsoft.ReportingServices.ReportRendering.ReportRenderingException was thrown., ;
Info: Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: Exception of type Microsoft.ReportingServices.ReportRendering.ReportRenderingException was thrown. ---> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: Exception of type Microsoft.ReportingServices.ReportRendering.ReportRenderingException was thrown. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An error has occurred during rendering of chart chart1. Details: Invalid parameter used. ---> System.ArgumentException: Invalid parameter used.
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height)
at Dundas.Charting.WebControl.Chart.SaveWithScaleFactors(Stream imageStream, Single scaleX, Single scaleY)
at Microsoft.ReportingServices.ReportRendering.DundasChart.GetImage(ImageType type, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.DundasChart.GetImage(ImageType type, ChartInstanceInfo instanceInfo, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.Chart.GetImage(ImageType type, Boolean& hasImageMap)
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.ReportRendering.Chart.GetImage(ImageType type, Boolean& hasImageMap)
at Microsoft.ReportingServices.ReportRendering.Chart.GetImage(ImageType type)
at Microsoft.ReportingServices.Rendering.ImageRenderer.Chart.LoadChart(Chart chart)
at Microsoft.ReportingServices.Rendering.ImageRenderer.Chart.CreateReportItemGraphics()
at Microsoft.ReportingServices.Rendering.ImageRenderer.Chart..ctor(Chart source, RenderingItem parent, Int32 parentIndex, CompositionBase composition)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItem.Create(SourceTypes type, Object source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemCollection..ctor(ReportItemCollection source, RenderingItem parent, CompositionBase composition, CreateItemContext createItemContext)
at Microsoft.ReportingServices.Rendering.ImageRenderer.ListContent..ctor(ListContent source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Boolean force)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItem.Create(SourceTypes type, Object source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.List.CreateListItems(List source, RenderingItem parent, Int32 parentIndex, Int32 renderingStart, CompositionBase composition, CreateItemContext listContext, Int32 listStartPage, Int32 listEndPage, Boolean checkItemsBelowPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.List..ctor(List source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItem.Create(SourceTypes type, Object source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemCollection..ctor(ReportItemCollection source, RenderingItem parent, CompositionBase composition, CreateItemContext createItemContext)
at Microsoft.ReportingServices.Rendering.ImageRenderer.Rectangle..ctor(Rectangle source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItem.Create(SourceTypes type, Object source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemCollection..ctor(ReportItemCollection source, RenderingItem parent, CompositionBase composition, CreateItemContext createItemContext)
at Microsoft.ReportingServices.Rendering.ImageRenderer.ListContent..ctor(ListContent source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Boolean force)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItem.Create(SourceTypes type, Object source, RenderingItem parent, Int32 parentIndex, CompositionBase composition, CreateItemContext createItemContext, Int32 startPage, Int32 endPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.List.CreateListItems(List source, RenderingItem parent, Int32 parentIndex, Int32 renderingStart, CompositionBase composition, CreateItemContext listContext, Int32 listStartPage, Int32 listEndPage, Boolean checkItemsBelowPage)
at Microsoft.ReportingServices.Rendering.ImageRenderer.List.ResumeCreation(Boolean canDelete)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.CalculatePage(Orientation orientation, Boolean repeatableParent, Boolean canDelete, Double& minimumCoordinate, Double& distance)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.CalculatePage(Orientation orientation, Boolean repeatableParent, Boolean canDelete, Double& minimumCoordinate, Double& distance)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.CalculatePage(Orientation orientation, Boolean repeatableParent, Boolean canDelete, Double& minimumCoordinate, Double& distance)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.CalculatePage(Orientation orientation, Boolean repeatableParent, Boolean canDelete, Double& minimumCoordinate, Double& distance)
at Microsoft.ReportingServices.Rendering.ImageRenderer.RenderingItemContainer.CalculatePage(Orientation orientation, Boolean repeatableParent, Boolean canDelete, Double& minimumCoordinate, Double& distance)
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)
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.a(DateTime A_0, GetReportChunk A_1, ProcessingContext A_2, RenderingContext A_3, CreateReportChunk A_4, Boolean& A_5)
--- End of inner exception stack trace ---
ANY insight or help would be greatly apreicated.
Regards,
Daniel Brown |
|
|
 |
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 16 Jul 2007 08:59 AM |
Daniel
Don't you just love the real helpful .Net exceptions :)
Buried in all that, the second "ERROR" line says that there is a problem with chart1.
Are you dynamically changing the chart in anyway, or have formulas for any of the settings?
|
Thanks
Phill
Colt 45 - the original point and click interface ;)
[url]http://philcart.blogspot.com/[/url] |
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 16 Jul 2007 10:00 AM |
Hi Philcart,
Yes, these generic .NET errors really make our life easier! /not!
Ys, I am creating the charts dynamicly. However the only expressions I am using is for the title of the chart, and on the X asis, i.e =MONTH(Date), Year(Date), etc
nothing beyond that compliexity
I will try removing all expressions and go from there.
Regards,
Daniel.
P.S I plan to invesitgate the possibilityof upgrading to SQLRS2k5 (I recommended we didnt at the inital stage, due to all our other systems using .NET 1.1, thought it best to keep it all on the same version for now, but 2k5 really offers more functionaltiy of what we what, but thats another story hehe) |
|
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 16 Jul 2007 02:40 PM |
In that case I'd check the resultset and see if there are any invalid dates.
|
Thanks
Phill
Colt 45 - the original point and click interface ;)
[url]http://philcart.blogspot.com/[/url] |
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 16 Jul 2007 03:09 PM |
Ok, I removed all expressions and everything else, even readded the cart with no expressions or whatnot.
Same error.
However, I am detecting thaton occasion my AppPool is crashing. Event Logs say:
'"Reporting Services" suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '1116'. The data field contains the error number. '
Has anyone experianced this before? |
|
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 16 Jul 2007 05:00 PM |
After some googling on this error, it appears to happen when Reporting Services Runs out of Memory.
I have changed the RSReportServer.config to use more ram (default was 60, now its 300).
-Daniel |
|
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 17 Jul 2007 10:11 AM |
OK, iv checke dthe data and all appears to be fine.
Could it be anissue with me trying to generate 543 charts? It also fails in the IDE with a "A generic error occured in GDI+".
Im all out of idea's now. :(
-Daniel Brown |
|
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 17 Jul 2007 10:33 AM |
Ahhh ... yeh ... I'm not aware of any specific limitations, but I think 543 charts would be up there :)
Who is honestly going to look at 543 charts in one report?
|
Thanks
Phill
Colt 45 - the original point and click interface ;)
[url]http://philcart.blogspot.com/[/url] |
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 17 Jul 2007 11:38 AM |
I thought as much.
But yes, its excessive, but its what the spec has in it a chart for each server monitor on each server the client has :)
It does now seem to be somehow data related, I can generetae the report, with the first 10 machines, im slowing increasing this to see where the error comes from :)
Ill keep the thread updated, incause anyone else has this problem.
-Daniel Brown |
|
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 17 Jul 2007 11:49 AM |
In that case I think it's time to review the specs and re-evaluate how this "report" is being used.
I can't concievably think of trawling through a report that has that many graphs, let alone the other data that's in the report. How many pages is it expected to be?
|
Thanks
Phill
Colt 45 - the original point and click interface ;)
[url]http://philcart.blogspot.com/[/url] |
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 17 Jul 2007 01:41 PM |
Its epxtected to range from 44 to 70 pages.
However, this report goes to the clients who liek to chop it up and use the charts in their own reports. I agree that having all these charts in there does max the report vastly bigger.
There are other options which are aleady implimented, i.e having hyperlinks to a website, which shows the charts on the selected server and such.
However for smaller reports (say only 5 servers), they may just wish to include the servers directly.
However, for now, the task is for me to get this working to some degree. However It seems I am runninging into more and more issues with memory/hardware.
After all it is only a p4 2.8 with 760MB of ram which is used to genereate the PDF/report.
-Daniel |
|
|
|
|
 vidival
|
| Joined: 20 Mar 2008 |
| Total Posts: 1 |
| |
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 20 Mar 2008 06:43 AM |
| I'm having a worse problem that this. I have to export to pdf a report with 18.000 pages. Anyone knows if it's possible to do this using reporting services? |
|
|
|
|
|
Re: Exporting to PDF produces Invalid Argument Exception
Posted: 20 Mar 2008 11:29 AM |
vidival
Firstly, I'm presuming you're talking about producing an 18 thousand page PDF file. Have you run this report and got an error, or are you just asking if it’s feasible? What is contained in the report that makes it so long? Are people honestly going to look at 18 thousand pages? Can the report be broken down into smaller chunks?
Secondly, it's good etiquette to start your own forum thread and not post a reply to a thread that is nearly 12 months old.
|
Thanks
Phill
Colt 45 - the original point and click interface ;)
[url]http://philcart.blogspot.com/[/url] |
|
|
|
|
| |
|
|
|
|
|
|
|
|