Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
I configured this web service and it was working fine but due to some changes at vendor side who created this web service and now when I tried to update or configure service references I am getting following error.
Metadata contains a reference that cannot be resolved: 'http://vm-dev-mes:8000/MESService/AXMESService.svc'.
There was no endpoint listening at http://vm-dev-mes:8000/MESService/AXMESService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (404) Not Found.
If the service is defined in the current solution, try building the solution and adding the service reference again.
Can anyone please give me any pointer which I can look into or have to inform other third party vendor so they can also check at their side.
Can you access the service by other means, e.g. in web browser? If not, the service is unavailable by some reason. If it works, try to remove the existing service reference and add a new one.
Yes I can access web service in browser. I also tried to add same webservice again into my visual studio project and got same error.
It could also be one of your references to that WebService being broken now. This means the Service is up and listening, and your application can reach the Service Address, but the Contract is broken. Look at the inner exception and see if it reveals what Service Entrypoint it is unable to locate.
Hi Tommy, How can I check contract is broken or still established ? Where can I find this inner exception as I am getting only one error thrown on screen which I pasted as question.
If you can hit the breakpoint where the exception is thrown in Visual Studio, you should be able to use the Locals Window to open the exception variable and peek inside the InnerException, but you are probably getting this error when compiling your solution, or?
My guess is that your solution refers to a previous version of the Contract (the description of available Service Entrypoints and their signature) and this breaks building. Can you add the reference to your solution over again?
I just noticed that you have already tried to add it again.
The service could actually be broken due to a flawed SOAP return message.
Feel free to send the WSDL output in a private message and I could have a quick look. :-)
I am not getting any error in compliation I am still trying to configure or update service references and getting this error.
Did you have this service up and running ok before the third party vendor changed it?
You could also be bit by the service account you are using not having sufficient access to the Temp-folders.