Reputation: 9568
I have a own web service that wrapped the geo bing maps geocode web service. This geocode web service is hosted in a Azure web role. When I try to make the call, I get the following error:
There was no endpoint listening at http://dev.virtualearth.net/webservices/v1/geocodeservice/GeocodeService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.. Unable to connect to the remote server
When I test it from a winforms testapp, using the same created WS client proxy the result is correct.
It looks that a call from my own webservice to the Bing maps webservice is not allowed somehow...
Any clue what is wrong.... ?
Upvotes: 0
Views: 2354
Reputation: 17954
Just a tip, the Bing Maps REST services has much better geocoding than the SOAP services. They are also faster and lighter weight. I have a blog post on how to use the REST services in .NET here: http://rbrundritt.wordpress.com/2012/01/06/bing-maps-rest-service-net-libraries/
just a tip though, when using the REST services from server side code you can set the user ip address information in the REST request. Set this to 127.0.0.1. This will trick the geocoder into using the default geocoding algorithm rather than using a localized algrothim for what ever country your server is hosted in.
Upvotes: 1
Reputation: 9568
Problem solved. We use a proxy here in the office (set to 'Automatically detect settings'). The proxy doesn't allow calling from Azure web role to external web services. When using direct internet connection, it worked perfectly.
Upvotes: 0