|
Home > Archive > IIS Server > June 2005 > Web Service Fails to Load on Reboot
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Web Service Fails to Load on Reboot
|
|
| grahamwert@gmail.com 2005-06-24, 5:59 pm |
| We have some web applications with web services and are having some
issues with IIS. Sometimes when we reboot the server, some of the web
services fail to come back up (i.e. none of the WebMethods are
available to client apps and a default page with no WebMethods is
listed if you type the .asmx URLs in a browser). The current solution
we've come up with is to cut all of the .dlls out of the bin directory
of the app and paste them back in. Once we do this, the web services
come back up. Sometimes (but rarely) the web services will go down
even without a server reboot. The same solution applies for this
scenario as well.
We're running IIS 5.1 on Windows 2000 Server with .NET Framework
Version:1.1.4322.2032 and ASP.NET Version:1.1.4322.2032.
Does anyone have an idea?
| |
| David Wang [Msft] 2005-06-25, 5:50 pm |
| Your question is related to ASP.Net and not IIS, and I'd suggest asking
microsoft.public.dotnet.framework.aspnet or Forums on www.asp.net.
Right now, it sounds like your WebMethods cause a failure and crash/hang on
the server. And when you touch the /bin directory, it causes ASP.Net to
recompile/reload your WebMethods and sometimes get past the bug in your
WebMethod.
So, the problem is not that Web Service fails to load on reboot -- it is
definitely loading on reboot -- it is that something in the WebMethod is
causing problems and that recycling the WebMethod by touching /bin is
solving it.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<grahamwert@gmail.com> wrote in message
news:1119629013.874377.204590@g49g2000cwa.googlegroups.com...
We have some web applications with web services and are having some
issues with IIS. Sometimes when we reboot the server, some of the web
services fail to come back up (i.e. none of the WebMethods are
available to client apps and a default page with no WebMethods is
listed if you type the .asmx URLs in a browser). The current solution
we've come up with is to cut all of the .dlls out of the bin directory
of the app and paste them back in. Once we do this, the web services
come back up. Sometimes (but rarely) the web services will go down
even without a server reboot. The same solution applies for this
scenario as well.
We're running IIS 5.1 on Windows 2000 Server with .NET Framework
Version:1.1.4322.2032 and ASP.NET Version:1.1.4322.2032.
Does anyone have an idea?
| |
| grahamwert@gmail.com 2005-06-26, 8:47 pm |
| I did post the same issue to
microsoft.public.dotnet.framework.aspnet.webservices but didn't get a
response. Anyway, I created a monitoring application that runs every
15 minutes to check the web services (it just searches the http
responses from the various .asmx pages for the web methods) and haven't
had one crash or go down once it comes up. The only time I've had any
of them fail once up is when updates were applied to the web service's
application domain, which of course generally forces a
recompile/reload. So it would seem that the issue is at the
compilation and/or linking stage. Until I can get to the root of the
issue, is there a way to manually force IIS to recompile an ASP.Net
application (command line utility, etc.) other than by modifying files
within the application?
| |
| David Wang [Msft] 2005-06-27, 7:55 am |
| Not an IIS question -- forcing recompilation of ASP.Net is dependent on
ASP.Net behavior, so I would check with their support forums.
I'm not certain about the activity in the forum you posted to, but the
following two definitely have a lot of traffic as well as ASP.Net product
team members monitoring:
http://www.asp.net
microsoft.public.dotnet.framework.aspnet
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<grahamwert@gmail.com> wrote in message
news:1119833408.923195.107390@g49g2000cwa.googlegroups.com...
I did post the same issue to
microsoft.public.dotnet.framework.aspnet.webservices but didn't get a
response. Anyway, I created a monitoring application that runs every
15 minutes to check the web services (it just searches the http
responses from the various .asmx pages for the web methods) and haven't
had one crash or go down once it comes up. The only time I've had any
of them fail once up is when updates were applied to the web service's
application domain, which of course generally forces a
recompile/reload. So it would seem that the issue is at the
compilation and/or linking stage. Until I can get to the root of the
issue, is there a way to manually force IIS to recompile an ASP.Net
application (command line utility, etc.) other than by modifying files
within the application?
|
|
|
|
|