G
Graham Wert
We have some web applications with web services and are having some
issues. Sometimes when we reboot the server, restart IIS, or update
the applications, 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). It's
almost as if the .asmx file can't find its codebehind when
recompiling/reloading. 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. The fact
that they work fine and stay up once we can get them to come up is very
strange since, from what I understand, asp.net applications are
periodically recompiled/reloaded. Is there something special about the
initial compile/load of the application when it's restarted and where
could things be breaking down? None of the other pages or files in our
applications seem to be impacted by this problem, just the web
services.
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 any ideas?
issues. Sometimes when we reboot the server, restart IIS, or update
the applications, 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). It's
almost as if the .asmx file can't find its codebehind when
recompiling/reloading. 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. The fact
that they work fine and stay up once we can get them to come up is very
strange since, from what I understand, asp.net applications are
periodically recompiled/reloaded. Is there something special about the
initial compile/load of the application when it's restarted and where
could things be breaking down? None of the other pages or files in our
applications seem to be impacted by this problem, just the web
services.
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 any ideas?