RS Web Service

Hi,
I am getting the following error when tries to call any web method of ReportExecution2005 Web Service from a 2003 Web application.

"Server did not recognize the value of HTTP Header SOAPAction: http://schemas.microsoft.com/sqlserver/2005/01/12/reporting/reportingservices/LoadReport."

Please someone suggest me how to fix this issue.

Thanks
AnobeJust wondering if you have tried with VS 2005? It shouldn't matter but it would tell us if it was specific to the generated proxy.|||Hi,
It was working with VS 2005. It was giving problem with VS 2003 only, is there any additional settings to be done?
And this is happening only to ReportExecution2005 Webservice, it not happeing to Reportservice webservice, which is also hosted on the same 2005 reporting service.

Regards,
Anobe|||Did you try rebuiding your proxy against the ReportExecution2005 webservice endpoint. I believe this error has occurrs if you generated a proxy built on a pre-RTM version of the server and tried to use it against an RTM server.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
I have not yet installed the RTM server, still working on the pre-RTM server. Both proxy and service are on pre-RTM server.

Anobe|||Can you try with RTM? I don't have any CTP builds running to check it out.|||HI,
I don't have a RTM version. Is there no way that i can call a web method of 2005 Web Service from 2003 Web Application?

Thanks
Anobe|||Let's back track -
First what is your environment:
Your web application - is it using .Net Framework 1.1?
Did you use Visual Studio .Net 2003 to build your web application?
Are you running your web application and report server on the same computer?
If yes, are you running your web application and report server on the same website?
If yes, are the report server and web application virutal directories configured to use teh same application pool (Windows 2003 only)?
Second, how did you generate your proxy:
Did you add a web reference in Visual Studio to your project? If so, did you do this on the same build of SQL Server as you are now encountering problems?
What URL did you supply to the proxy when building your web application?
Third, when invoking the proxy in code:
What URL do you supply to the ReportExecutionService .URL property?
What credentials do you supply to the ReportExecutionService .Credentials property?
Thanks,
-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Web Application: Its build on VS 2003.
Report Server: Its RS 2005, which is deployed on a different machine on the same network.

I am adding a Web reference to the ReportExecution2005 web service in my Web Application.

I am passing the credentials as 'System.Net.CredentialCache.DefaultCredentials'.

Suppose 'http://localhost/reportserver/testreport/test1' is the path i use to call my report through IE, then the URL that i am passing for the .Url property is '/testreport/test1'

But How all the above settings relates to in getting a problem like 'Server is not able to recoganize the HTTP SOAP header'

|||The URL property is either set in code or if not, the value used when generating the proxy is used. The value can be found either directly in your code (usually where you instantiate your ReportExecutionService class). Alternatively you can find out the static one by right clicking the proxy under web references in solution explorer.
Can you verify that the Url property of the proxy is in the form:
http://myserver/reportserver/ReportExecution2005.asmx

And that the value for 'myserver' is correct for your production server?
-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.