Re: First request to ASP.NET application completely hangs Windows 2003 Server

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 04:37:57 -0700

Strange. We are running all versions of ASP.Net against Windows Server 2003
which have all patches and do not observe such problems.

What do you mean by "the server freezes"
-- Can you move the mouse cursor
-- Can you observe CPU utilization
-- Can you create any new processes like notepad.exe

What other changes are you making to your servers other than clean OS
installation? If your machines are part of a domain, I'd start looking at
domain policies that are mucking around with system-wide privileges. I am
suspecting a global setting specific to your machines since no one else has
ever reported this.

When you do get this lockup, please run IIS State on the affected w3wp.exe
and inetinfo.exe and post the log here:
http://www.iisfaq.com/default.aspx?view=P197 

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Artur Jedynak" <artur.jedynak@integral-tech.pl> wrote in message
news:eqME68lnEHA.132@TK2MSFTNGP09.phx.gbl...
Hello,
I have very strange problem - first request to ANY ASP.NET application hangs
completely W2003 Server. The server freeezes in unusual way - I cannot start
ANY new process (or stop), processor utilization is very low (~2-3 %). Thi
happens only during request to ASP.NET application. STatic HTML and .ASP
applications work fine.
Complete reinstallation of IIS did not help. After installing .NET 2.0
Beta - result is the same. It seems to be problem in .NET, not IIS, but it
only manifests in ASP.NET application.
I receive ths behavior on 2 systems - one is development server and it
happened after 4 months of hard work, but the same effect is on production
server with PURE installation and another set of ASP. NET application (just
one simple app.)
The problem started ~4 weeks ago after one of critical updates install.
It seems quite serious, I have no idea, especially that the problem seems to
go deep into internals, in fact there is no possibility to start any
process, so it looks like deadlock at the kernel level.
Artur Jedynak

Relevant Pages