Web Service stops responding

[Dan S]

I have a .NET web service running on a 2K box and IIS 5. We've experienced
it twice now where the service stops responding to any type of request after
running succesfully for a month or so. The service does not respond to the
consumer or to my browser pointing to the asmx file. An IIS restart fixed
the problem once but has also not fixed the problem. We had to go as far as
restarting Windows. Any ideas? Some configuration tweak that might help to
prevent something like this. As far as I know we are using the default
configuration values.

Thanks,
--
Dan S

[jabailo]

Dan S wrote:

I have a .NET web service running on a 2K box and IIS 5. We've experienced
it twice now where the service stops responding to any type of request after
running succesfully for a month or so. The service does not respond to the
consumer or to my browser pointing to the asmx file. An IIS restart fixed
the problem once but has also not fixed the problem. We had to go as far as
restarting Windows. Any ideas? Some configuration tweak that might help to
prevent something like this. As far as I know we are using the default
configuration values.

Thanks,

I think we're having similar problems ( see my post just before yours ).

I am also using IIS5;2K

Do you ever see any errors or 500 (Server Unavailable) messages?

I don't. From my client's side, it looks as if the web method is being
called just fine. From the server side, it looks as if the method was
never called!

[jabailo]

Dan S wrote:

I have a .NET web service running on a 2K box and IIS 5. We've experienced
it twice now where the service stops responding to any type of request after
running succesfully for a month or so. The service does not respond to the
consumer or to my browser pointing to the asmx file. An IIS restart fixed
the problem once but has also not fixed the problem. We had to go as far as
restarting Windows. Any ideas? Some configuration tweak that might help to
prevent something like this. As far as I know we are using the default
configuration values.

Thanks,

I think we're having similar problems ( see my post just before yours ).

I am also using IIS5;2K

Do you ever see any errors or 500 (Server Unavailable) messages?

I don't. From my client's side, it looks as if the web method is being
called just fine. From the server side, it looks as if the method was
never called!

[Dan S]

Sounds similar. But the consumer just hangs and never succeeds. However,
the service is returning some data - is your return type just a void? And
yes, I never get a 500 error, the logs for the service are empty as if it is
never called, and I don't see anything in the IIS logs either. Very strange.
What bothers me the most is that restarting IIS hasn't helped in some cases.
We've had to do a full reboot, which can potentially effect hundreds of
people.
--
Dan S
"ja*****@texeme.com" wrote:

Dan S wrote:

I have a .NET web service running on a 2K box and IIS 5. We've experienced
it twice now where the service stops responding to any type of request after
running succesfully for a month or so. The service does not respond to the
consumer or to my browser pointing to the asmx file. An IIS restart fixed
the problem once but has also not fixed the problem. We had to go as far as
restarting Windows. Any ideas? Some configuration tweak that might help to
prevent something like this. As far as I know we are using the default
configuration values.

Thanks,

I think we're having similar problems ( see my post just before yours ).

I am also using IIS5;2K

Do you ever see any errors or 500 (Server Unavailable) messages?

I don't. From my client's side, it looks as if the web method is being
called just fine. From the server side, it looks as if the method was
never called!

[Dan S]

Sounds similar. But the consumer just hangs and never succeeds. However,
the service is returning some data - is your return type just a void? And
yes, I never get a 500 error, the logs for the service are empty as if it is
never called, and I don't see anything in the IIS logs either. Very strange.
What bothers me the most is that restarting IIS hasn't helped in some cases.
We've had to do a full reboot, which can potentially effect hundreds of
people.
--
Dan S
"ja*****@texeme.com" wrote:

Dan S wrote:

I have a .NET web service running on a 2K box and IIS 5. We've experienced
it twice now where the service stops responding to any type of request after
running succesfully for a month or so. The service does not respond to the
consumer or to my browser pointing to the asmx file. An IIS restart fixed
the problem once but has also not fixed the problem. We had to go as far as
restarting Windows. Any ideas? Some configuration tweak that might help to
prevent something like this. As far as I know we are using the default
configuration values.

Thanks,

I think we're having similar problems ( see my post just before yours ).

I am also using IIS5;2K

Do you ever see any errors or 500 (Server Unavailable) messages?

I don't. From my client's side, it looks as if the web method is being
called just fine. From the server side, it looks as if the method was
never called!

[jabailo]

My return is void.

But here's the wierd thing on my side.

Knowing about this problem, what I do is a retry.

If there are 800 lines in the source, and I only see 500 web service
completes (by checking the database ) I run it again after waiting 3
minutes.

It usually works by at least the 3rd try!

Again the part that I find most bothersome is that to the code, those
calls look as if they were never made! They just disappear into the ether!

Dan S wrote:

Sounds similar. But the consumer just hangs and never succeeds. However,
the service is returning some data - is your return type just a void? And
yes, I never get a 500 error, the logs for the service are empty as if it is
never called, and I don't see anything in the IIS logs either. Very strange.
What bothers me the most is that restarting IIS hasn't helped in some cases.
We've had to do a full reboot, which can potentially effect hundreds of
people.

[jabailo]

My return is void.

But here's the wierd thing on my side.

Knowing about this problem, what I do is a retry.

If there are 800 lines in the source, and I only see 500 web service
completes (by checking the database ) I run it again after waiting 3
minutes.

It usually works by at least the 3rd try!

Again the part that I find most bothersome is that to the code, those
calls look as if they were never made! They just disappear into the ether!

Dan S wrote:

Sounds similar. But the consumer just hangs and never succeeds. However,
the service is returning some data - is your return type just a void? And
yes, I never get a 500 error, the logs for the service are empty as if it is
never called, and I don't see anything in the IIS logs either. Very strange.
What bothers me the most is that restarting IIS hasn't helped in some cases.
We've had to do a full reboot, which can potentially effect hundreds of
people.

[Deepak]

Have you observed anything in IIS logs?
Normally there is a file called W3SVC which has all the entries for the HTTP
web requests.
When you experience this situation next time, Please open the asmx file in
the browser and then look at the IIS log file.
Also look at eventviewer to find anything about the web service.
What is this web service supposed to do?
How is the memory consumption and CPU utliziation on that computer when this
kind of situation happens?
I know this is a very tricky situation.
We first have to find what the problem is and then go look for a solution.
Thanks
Deepak

"Dan S" wrote:

I have a .NET web service running on a 2K box and IIS 5. We've experienced
it twice now where the service stops responding to any type of request after
running succesfully for a month or so. The service does not respond to the
consumer or to my browser pointing to the asmx file. An IIS restart fixed
the problem once but has also not fixed the problem. We had to go as far as
restarting Windows. Any ideas? Some configuration tweak that might help to
prevent something like this. As far as I know we are using the default
configuration values.

Thanks,
--
Dan S

[kntcnrg]

I'm experiencing this problem and found that when using the SoapHeader, it needs to be initialized during the web service class constructor. This solved the issue for part of the problem, but I still get the same error.

[code]
public class SoapHeaderMessage : SoapHeader
{
public string UserName;
public string PassWord;
}

[WebServiceAttribute(Namespace="http://mylocalhostingsite")]
public class WebServiceClass : WebService
{
public SoapHeaderMessage soapHeader;

public WebServiceClass()
{
soapHeader = new SoapHeaderMessage();
soapHeader.MustUnderstand = true;
soapHeader.UserName = ConfigurationSettings.AppSettings["soapUserName"];
soapHeader.PassWord = ConfigurationSettings.AppSettings["soapPassWord"];

...
}

[WebMethod, SoapHeaderAttribute("soapHeader")]
public void myWebMethod()
{
...
}
}

Let me know what other solutions anyone comes across.

[kntcnrg]

I have found by using Ethereal's Network Analyzer that the packets changed from one namespace to another using my local machine for references to a live version of the app. Since the app uses SSL, I installed the certificate from the web server and the problem was fixed.

1. Use Ethereal Network Protocol Analyzer
2. Ensure that when using SSL, that the end-user computer has the certificate from the web server installed.

Hope this helps!