Question Unable to connect to the remote server

[MarieRaye]

Hello,

I have a web application that connects to a webservice. Usually I can step through the webservice and my start page loads up just fine. But starting a few days ago this was not the case. Now I am getting the message "Unable to connect to the remote server." As an inner exception I get "No connection could be made because the target machine actively refused it 127.0.0.1:3236”. If I change the webservice to the one we have on our development server then it runs just fine, but I cant run it locally on my machine without getting this error.

Any ideas? I have run out of things to try!

Thanks!

 

[JohnH]

"127.0.0.1" is "localhost", ie a shortcut IP to your own PC. Make sure you have configured the web service proxy to connect to correct address, this is done when you add the web service reference, like http://yourdomain.com/service.asmx?wsdl.

 

[MarieRaye]

Good Morning JohnH,

I do have my web service reference set to my localhost: "http://localhost:3236/ESRA_Service/Service.asmx". I have also tried substituting localhost: 3236 with my computer name, but both ways I end up with the same error message.

Any other ideas????

Thanks!

 

[JohnH]

You have configured this web service application to run at your local machine at port 3236, and verified no firewall is blocking that port?
Or have you included the webservice source in your web application to run along it during debugging?

 

[MarieRaye]

I have a WebService Address in my web.user.config in my application. the WebService Address is set to: "http://localhost:3236/ESRA_Service/Service.asmx".

I have checked my firewall and the settings have not changed from when it was working until now.

Any other ideas?

 

[JohnH]

A hosting service have to be running your service application, either IIS or the lightweight VS debugging server that otherwise hosts the web applications when you debug, the latter may change port from "day to day" (or when service is closed and new free port is needed) if your running the webservice as external application from your consumer.