Parameter Validation Failed when renderin a report to PDF, Works OK to Excel

Question

Parameter Validation Failed when renderin a report to PDF, Works OK to Excel

sebastian.streiger

SSC Rookie

Points: 42
More actions
March 19, 2009 at 3:48 pm

#207160

Hi, I´m facing this error, and can´t find what could be happening:
From an asp.net application i´m using the following code to render a report to PDF format:
Return rs.Render( _
report, _
format, _
historyID, _
deviceInfo, _
parametros, _
Nothing, _
showHideToggle, _
encoding, _
mimeType, _
Nothing, _
warnings, _
streamIDs)
The format variable holds the desired format output.
When I pass the value "EXCEL" i works OK (obviously it generates an excel file).
If I pass it "PDF" i get the following exception:
System.Web.Services.Protocols.SoapException occurred
Actor="http://desarrollo/ReportServer/ReportService.asmx"
Lang=""
Message="Se inició una excepción de tipo Microsoft.ReportingServices.ReportRendering.ReportRenderingException. --> Se inició una excepción de tipo Microsoft.ReportingServices.ReportRendering.ReportRenderingException. --> Se inició una excepción de tipo Microsoft.ReportingServices.ReportRendering.ReportRenderingException. --> Se inició una excepción de tipo Microsoft.ReportingServices.ReportRendering.ReportRenderingException. --> Parámetro utilizado no válido."
Node="http://desarrollo/ReportServer/ReportService.asmx"
Role=""
Source="Microsoft.VisualBasic"
StackTrace:
en Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
en Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
en Hipernet.Framework.Web.Reports.ReportsHandler.ReporteRender(Object rs, String report, String format, Object[] parametros, String& mimeType) en C:\Hipernet\Framework\Version Base\web\Reports\ReportsHandler.vb:línea 288
The same code was working OK untill we moved the report server to a new server.
I checked the reporting services configuration file to see if the new one was missing the Format Extension but it was there.
Can anybody give me a clue?
Thanks in advance
Sebastián Streiger
Argentina

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Gift Peddie SSC Guru Points: 73570 More actions · Answer 1

In Asp.net PDF uses the file upload which default to only 4megs so most code that runs without over ride of the Max length property blows. So check below and read the Microsoft docs and in the second link how to set your web.config to increase your max length property.

http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.fileupload.aspx

http://www.bloggingdeveloper.com/post/Limiting-the-File-Upload-Size-in-ASPNET.aspx

Kind regards,
Gift Peddie

sebastian.streiger SSC Rookie Points: 42 More actions · Answer 2

Gift:

Thanks for your suggestion.

I read the links you provided, but I see no relation to my problem.

I´m using the reporting server library to get a stream that contains the pdf. That Stream is redirected tho the requesting browser page.

It was working well, and on the client side IE asked the user to open or save the file.

So, I don´t know hay could be maxRequestLength affecting.

Anyway, we do have file uploads in our application, and we have raiser the value of that parameter up to 10MB. Also, all reports are failing to render. I tested with one of them, that used to generate a 400Kb PDF file and fails too.

So , I don´t think it has to do with maxRequestLength.

Thank you very much

Sebastián Streiger

Argentina

Gift Peddie SSC Guru Points: 73570 More actions · Answer 3

The reason for your error was not translated because Google says your error is out of memory exception which may have made my answer different. Here is a support article to that problem but I also think your migration was wrong so you need to look at the out of memory issue and find out why your migration is not working. check my migration related threads for pointer on migration related issues.

http://support.microsoft.com/kb/909678

Kind regards,
Gift Peddie

sebastian.streiger SSC Rookie Points: 42 More actions · Answer 4

I can´t see where my exception details point to an memory error.

The exception detail was copied from the IDE, while I was debugging.

As our servers are nstalled in Spanish, error descriptions show up in spanish.

Best regards

Sebastián Streiger

Argentina

Gift Peddie SSC Guru Points: 73570 More actions · Answer 5

Se inició una excepción de tipo Microsoft.ReportingServices.ReportRendering.ReportRenderingException

This is what I posted in Google so you have to investigate out of memory exception and the many known issues of moving reporting services from one server to another server. There are many things that can go wrong, if all your reports are not running it may be migration related.

Kind regards,
Gift Peddie

sebastian.streiger SSC Rookie Points: 42 More actions · Answer 6

Finally I managed to find what teh problem was.

The report has an image control that was linked to an external source.

The link for the external source is passed as a parameter to RS, and in the new instalation it wos wrongly configured.

The fac that when generating to EXCEL was working OK is cause the excel format doesn´t render images.

Anyway, thanks for your help.

Sebastián Streiger

Argentina