SSRS Report Viewer Intercepting Request Object Values

[BLKeller]

I'm having a problem with a site I'm working on which contains links to Reporting Services reports. The pages are written in HTML and classic ASP. The links to the reports are in the following format:

http://ServerName/ReportServer?Repor...Command=Render

The problem occurs after I open a report from the site. Prior to opening any reports, the forms I've created on the site work fine, but after a report is run, the values sent across by the Post method are no longer sent to the receiving page, which should be processing the values sent to it. If I change the report URL to view the report in Report Manager (http://ServerName/Reports/Pages/Report.aspx?ItemPath=...) the forms do work correctly, however, I don't really want to do it this way because I don't want users to be able to access other reports on the Report Manager.

I've looked around for the past couple of days and have not found anything regarding why this problem would occur. I'm thinking the issue might be due to the fact that the SQL Server and the web server are running on the same machine. I have done this type of development in the past without running into this issue, however, in those other cases, the SQL Server was running on one machine, while the web server was running on another.

My knowledge of what goes on behind the scenes with web pages and the Reporting Services Report Viewer is somewhat limited, so hopefully I'm not asking a very obvious question and hopefully I can comprehend any answers that anyone can supply.

I'm using:

SQL Server 2005
Visual Studio 2005 (for report development)
IIS 5.1
Window XP (SP2)
Dreamweaver MX (for web development)

Any ideas anyone can provider would be appreciated.

Thanks!

[sp4tech]

That's good.

But can you please tell me how can I use this SSRS report viewer control in classic ASP? This is the main problem I am facing. I had used crystal reports in classic ASP.

Regards,

[paul1035]

Well how we are using it is we are just opening up the reports in a iframe within our app, and we are just linking to the report with http://ourserver:81/reportserver and then making the reports look like they are embedded into the app. Otherwise, you can actually embed your reports following something similar to this link: http://www.codeproject.com/KB/report...iewer2005.aspx
They have a good walk through of embedding reports into your ASP.NET app.

[sp4tech]

So you trying to display the whole Report server admin page to all the users. Correct? I think that could be one of the drawback we need to use report viewer. Is it?
Ya. using .NET for report viewer is easy than using in classic ASP.

Regards,

[paul1035]

Well when you view the reports using the reportserver links, then you aren't quite linking to the admin page as they can't change anything from that view, they only view the report itself with no other options, other than parameters. So that is why this issue came to be, because we didn't want to link to the pages under the reports manager, instead we wanted to link to them using reportserver because it only shows the reports that way.