Prev: Service Unavailable
Next: Cannot start IIS
From: Eva Skakalova on 18 Oct 2005 05:17
Hello,

after upgrade to WIN2k3 with IIS 6.0 our ASP.NET application hangs twice a
day. Clients receive error message 'service uavailable or page cannot be
found'.
Error text from httperr.log:
'HTTP/1.1 GET /ISZV_WebPortal/ - 1 Connection_Dropped DefaultAppPool'
This requires always the restart of IIS Admin Service. What changed so
dramatically between IIS 5.i and IIS 6.0 that causes these problems ? Is it
a problem of the configuration of IIS 6.0 on S2K3?
Please tell me what to do.

Eva



From: David Wang [Msft] on 18 Oct 2005 06:37
IIS5 and IIS6 are totally different underneath the covers
- IIS6 is complete rewrite from IIS5 for many reasons, security being one of
them
- Process Model is completely different, though we added in a "IIS5
Compatibility Mode"
- Networking stack is completely different. IIS6 uses custom kernel mode
driver HTTP.SYS, IIS5 uses Winsock
- You may have moved .Net Framework from 1.0 to 1.1 on Windows Server 2003

Connection_Dropped can be easily treated by simply recycling the affected
Application Pool. On IIS6, you should NEVER need to restart IIS - no need to
ever use IISRESET, no need to ever stop IISADMIN, no need to ever stop
W3SVC - unless you are making a couple of obvious global configuration
changes. Recycling an Application Pool should be the most you ever need to
do.

Seeing problems when upgrading to a new OS is expected, so the only thing
you can do is debug to determine the cause and then have the responsible
party take action. According to
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/http/http/types_of_errors_logged_by_the_http_api.asp ,
"Connection_Dropped" indicates client-side behavior. Though you can certain
use a tool like DebugDiag from Microsoft to diagnose such "hangs" on the
server side.

Finally - if you upgraded the OS to Windows Server 2003, you should consider
reinstalling clean and migrating your website to get full security and
reliability enhancements of IIS6 on Windows Server 2003. Upgraded settings
are simply not as functional nor secure as the clean-install settings.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Eva Skakalova" <skakalova(a)spirit.sk> wrote in message
news:%23Pq%232S80FHA.736(a)tk2msftngp13.phx.gbl...
Hello,

after upgrade to WIN2k3 with IIS 6.0 our ASP.NET application hangs twice a
day. Clients receive error message 'service uavailable or page cannot be
found'.
Error text from httperr.log:
'HTTP/1.1 GET /ISZV_WebPortal/ - 1 Connection_Dropped DefaultAppPool'
This requires always the restart of IIS Admin Service. What changed so
dramatically between IIS 5.i and IIS 6.0 that causes these problems ? Is it
a problem of the configuration of IIS 6.0 on S2K3?
Please tell me what to do.

Eva




 | 
Pages: 1
Prev: Service Unavailable
Next: Cannot start IIS