I'm somewhat new to reporting services and have used a web service call to
render my reports in my asp.net applications in the past. All the reports
thus far have been Excel, and I've used the same method for calling these
reports from some sample code I found online. This has worked great up till
now.
I have a report I want to render in PDF. I've plugged in the correct values
in my code and the browser will try and download the PDF but returns a "File
is damaged and could not be displayed". I tried rending in Excel and I get
"This file is not in a recognizable format". I've compared my code to past
projects and everything looks good. The only difference with this report is
I used a list control with textboxes instead of a table which I've used on
all past reports. If anyone has a suggestion on what causes these error
message, please reply. Thanks.I figured it out. There was a <httpModules> tag in my web.config that was
causing this problem. I built another project to call my report with a
"clean" web.config and it works fine.
"jweesies" wrote:
> I'm somewhat new to reporting services and have used a web service call to
> render my reports in my asp.net applications in the past. All the reports
> thus far have been Excel, and I've used the same method for calling these
> reports from some sample code I found online. This has worked great up till
> now.
> I have a report I want to render in PDF. I've plugged in the correct values
> in my code and the browser will try and download the PDF but returns a "File
> is damaged and could not be displayed". I tried rending in Excel and I get
> "This file is not in a recognizable format". I've compared my code to past
> projects and everything looks good. The only difference with this report is
> I used a list control with textboxes instead of a table which I've used on
> all past reports. If anyone has a suggestion on what causes these error
> message, please reply. Thanks.
Monday, March 26, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment