.NET Webservice running, half 404's
I have a .NET web service running as a Windows service on a Windows Server 2003 R2 machine. I have a separate .NET / C # 2.0 application that calls this web service from elsewhere on our local network. The webservice has 2 methods - 1 of these method calls works flawlessly. However, the other method always returns a 404 "not found" error. I can visit the webservice url and see both methods. I did a "web link update" in my project and it ended up fine. The generated web proxy saw that the method is just fine. But it never works at runtime, while it works very well.
There are no web settings in the service config file - just your standard connection string and a few applications.
What can call 1 method up to 404 and another works fine?
EDIT: Both the web service and the calling code are .NET 2.0, C #. This is not WCF, but just an old school "web link". In fact, it is based on System.Web.Services.Protocols.SoapHttpClientProtocol and not Microsoft.Web.Services3.WebServicesClientProtocol.
I have confirmed that the webservice url is not dynamically set.
a source to share
You don't say which technology you are using, so I will consider it WCF. You don't say which version of .NET you are using on the service side, so I am assuming .NET 3.5 SP1.
I recommend you take a close look. In particular, turn on tracking and see what he has to say about it. Are you getting the request? At what point is the response generated? The service may have been found, but there is something wrong with the SOAP "action", so this second operation was not actually found. Remember that what you see in the web proxy is not the same as what the proxy will actually request. It should be, but it may not be. Turn on tracking and find out.
You can also consider debugging the service to see if the operation has actually been achieved. Perhaps an exception in an operation translates to 404?
Also, look at the event logs to see if anything interesting happened around the same time.
a source to share
Some code will really help us understand your problem better. May I ask if the application calling the web service is a web application or a desktop application or a Windows service?
If it is a web application, one suggestion would be to call the web service manually and run fiddler or firebug to see what the server response is and what data is being sent and returned. This can be the starting point for fixing your problem.
a source to share