> Hi Dilip,
>
> I have added the wse 2.0 references to my client project and changed
> the web service proxy to derive from
> Microsoft.Web.Services2.WebServicesClientProtocol as per the
> documentation and samples, still giving me the same error though, The
> 'Routing' sample that ships with the sdk doesn't seem to do anything
> that special. Any ideas on what I am missing?
>
> Thanks!
>
> ~Quag
>
> "Dilip Krishnan" wrote:
>
>> Hello Quagmire,
>> You would need to set up the addressing headers in your client code.
>> It
>> would be simple if you were to use WSE
>> HTH
>> Regards,
>> Dilip Krishnan
>> MCAD, MCSD.net
>> dkrishnan at geniant dot com
>> http://www.geniant.com
>>> Hi,
>>>
>>> I am using the ms reporting services webservice to supply reports to
>>> my winforms client. I would like to set up an intermediate server
>>> that takes requests from the winform client and routes them to the
>>> reporting services webservice. From the documentation it looks like
>>> ws-addressing will do this. So far I have setup the soap router as
>>> per the documentation, however when the client is pointed at the
>>> soap-router I get the following exception
>>>
>>> Microsoft.Web.Services2.Addressing.AddressingFault: Message
>>> Information Header Required
>>>
>>> I am assuming I have to change something on my client code so that
>>> it knows how to talk to the soap router properly. I noticed that the
>>> visual studio web references once updated include a extra class with
>>> the letters 'wse' appended to the name, I have tried using this
>>> version of the proxy but continue to get the same problem.
>>>
>>> Any ideas on what is wrong, or any pointers to the proper setup of a
>>> soap router with 3rd party webservices would be much appreciated.
>>>
>>> Thanks!
>>> ~Quag