Failed to execute web request for specified URL mscorlib
-
Wednesday, February 08, 2012 7:53 PM
Hi everyone,
I have been trying to build a report using an xml query to get data from a web service. The query is:
<Query>
<Method Namespace="http://tempuri.org/" Name="GetMatchingStrategyOuputDataRequest">
<Parameters>
<Parameter Name="StrategyId" Type="XML">
<DefaultValue>
<Name>Address</Name>
</DefaultValue>
</Parameter>
</Parameters>
</Method>
<SoapAction>
http://tempuri.org/IService/GetMatchingStrategyOuputData
</SoapAction>
<ElementPath IgnoreNamespaces="True">
GetMatchingStrategyOuputDataResponse{}/Data
</ElementPath>
</Query>I am sure everything on the query is right except the namespace. However, I am not sure whether the error that I am getting (see title) is related to the namespace itself or something else. On our code, we have http://tempuri.org/ URI as our namespace, but we have another one (a proper one). I have tried to substitute that one into the code and the query, but when I do, I get a mismatch at EndpointDispatcher error.
I am running out of options, so any help is welcome. Thanks.
All Replies
-
Wednesday, February 15, 2012 2:10 AMModerator
Hi becool12,
Thanks for the question. Since you haven't post the detail error message here, so based on my past experiences, I would suggest you to check if your issue caused by the authentication of the web services. This is related thread that I had handled, please check it:
Passing SOAP Header with XML Query
Thanks,
Sharp WangPlease remember to mark the replies as answers if they help you and unmark them if they provide no help.
-
Wednesday, February 15, 2012 4:07 PM
Hi Sharp,
Thanks for replying. The error I am getting is the title of the post. Maybe I should rephrase my question. Will my query work with the namespace http://tempuri.org/ ? Should I use another namespace since http://tempuri.org/ is just a temporary URI? Or the error "Failed to execute web request for specified URL (mscorlib)" has nothing to do with the namespace?
Thanks.
P.S.: I checked the link you posted. Unfortunately, it wasn't much help.
-
Thursday, April 12, 2012 6:30 PM
Hi Sharp,
I was able to solve this issue. It had to do with the namespace. I used the correct namespace (my company's namespace), and solved the Endpoint mismatch error with one of my colleagues's help.
Thanks,
becool12.

