Hey guys, I could use your help. One of the things I'm doing before departing Project Awesome is transferring it to the .NET 2.0 post SP1 compilation model. I have been sucessful thus far moving the projects over to the new solution. I, however, am having trouble with the webservices.
Now, the origional developer created a local webservice to get around the issues the compilation model created. There is also another webservice that communicates with a local 3rd party tool. After I publish the site when I open it in IE the page loads (the actual website) however, when it tries to hit the webservice (the one he places his BO in) I am getting an exception that says ""No connection could be made because the target machine actively refused it 127.0.0.1:2438" My first instinct was to check permissions on the folders, everything looks good. Then, I checked IIS, everything looks good there. In the event viewer I'm getting the same exception I get on the page. When I step through it's obvious that it conks out as soon as it tries to talk to the web service. I did a netstat command in cmd prompt and there is nothing running on the 2438 port. Is it possible the port has changed? What is the best way to see what the new port number is?
All help is greatly appreciated. I hope I explained my problem in detail enough. Sorry this post isn't more entertaining.
In more important news I have blue hair, pictures to follow.
UPDATE - This has been fixed, partially because of the issue with the ports (thank you for your help) and partially because of the deployment of the project. I appreciate it guys, this wonjt be the last time. :)
Blue hair? That's hot.
ReplyDeleteMy first instinct is that the webservice isn't running at all. However, if you're convinced that it's out there somewhere, you could just use a port scanner on localhost.
You can pass flags to netstat so it will output the PID and executable name for connections:
ReplyDeletenetstat -anob
Then look for the new port number in the output by scanning connections looking for LISTENING state with an appropriate executable or PID.
That said 2348 is an odd port number. Like @Gustav it makes me suspect that the web service is configured in a separate site/container that isn't running. That would be a good place to check next.
Good luck!