Application/ODP does not restart after network failure
32784Mar 2 2006 — edited Mar 6 2006Hi, it looks like our .Net webapplication (using ODP) does not come up anymore after a network failure. When you enter the url of the start-page, it immediately redirects to the custom error-page, and seems to hang there. Most likely is no db-connection possible.
We have to manually restart IIS to get it going again. Could it be a problem with pooled connections that have become invalid by the failure, or is there maybe a setting in IIS 6.0 (on Windows server 2003) that should be corrected? Any advice is welcome.