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

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

David
Mon Sep 20 06:37:57 CDT 2004

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




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

Artur
Mon Sep 20 06:56:20 CDT 2004

Hello,

"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:ek81lZwnEHA.608@TK2MSFTNGP09.phx.gbl...
> 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
>

I can move the cursor, CPU utilization is low, but I CANNOT create new
process, when I try to do this,
the system becomes unresponsive. I can observe CPU utilization when I start
tak manager or process explorer BEFORE requesting ASP.NET page.
The strange thing is, that creation of new process hangs the system.
However, even before this, after first ASP.NET request, the network
subsystem is unresponsive immediately. The computer responds to ping, but it
seems like RPC is unavailable and file sharing also.
Machine is part of domain, but no specific policy is applied.
regards
Artur Jedynak

> 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.
>



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

David
Wed Sep 22 03:41:39 CDT 2004

Hmm. Well, no one has reported what you have seen, and we do not see it on
Windows Server 2003 with all patches. So, it seems like a problem specific
to you.

I doubt it has anything to do with ASP.Net since it has nothing in
kernel-mode -- Certainly not anything involving process creation. I have
seen behavior like you describe only under low memory conditions or virus
attacks.

If you can narrow down your behavior to saying "if I do not apply patch X /
Y, this problem doesn't happen", that could be helpful (assuming that you
have some series of bad patch interactions). If you can open a support case
with PSS to have it debugged, that is even better.

--
//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:eHF%23MjwnEHA.3564@tk2msftngp13.phx.gbl...
Hello,

"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:ek81lZwnEHA.608@TK2MSFTNGP09.phx.gbl...
> 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
>

I can move the cursor, CPU utilization is low, but I CANNOT create new
process, when I try to do this,
the system becomes unresponsive. I can observe CPU utilization when I start
tak manager or process explorer BEFORE requesting ASP.NET page.
The strange thing is, that creation of new process hangs the system.
However, even before this, after first ASP.NET request, the network
subsystem is unresponsive immediately. The computer responds to ping, but it
seems like RPC is unavailable and file sharing also.
Machine is part of domain, but no specific policy is applied.
regards
Artur Jedynak

> 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.
>





Re: First request to ASP.NET application completely hangs Windows by DemirSelmanovic

DemirSelmanovic
Fri Feb 11 08:11:02 CST 2005

Hi,
I'm having EXACT the same problem on my computer. I've had it on w2k pro sp4
fully pached, and I've also installed win xp with pre sp2 paches and same
thing happened.
At first I thought that the problem is with my GForce display adapter
because WDM service stoped responding when I run application (by clicking run
in VS.NET 2003, or by compiling it and runing from IE. I even tried mozilla
and the same thnig hapened). I've noticed this in Event viewer.
But, I've replaced display adapter with ATI and same thing hapened, on both
systems (win2k and xp), but now I dont get any problems loged in Event viewer.

Since everything works on another computer my guess is that it's a hardware
problem.
I have ASUS P4SP-MX motherboard and I guess the problem is there, but I
would be thankfull if some could tell me why is this hapening and is there a
way to fix it.

Demir

"David Wang [Msft]" wrote:

> Hmm. Well, no one has reported what you have seen, and we do not see it on
> Windows Server 2003 with all patches. So, it seems like a problem specific
> to you.
>
> I doubt it has anything to do with ASP.Net since it has nothing in
> kernel-mode -- Certainly not anything involving process creation. I have
> seen behavior like you describe only under low memory conditions or virus
> attacks.
>
> If you can narrow down your behavior to saying "if I do not apply patch X /
> Y, this problem doesn't happen", that could be helpful (assuming that you
> have some series of bad patch interactions). If you can open a support case
> with PSS to have it debugged, that is even better.
>
> --
> //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:eHF%23MjwnEHA.3564@tk2msftngp13.phx.gbl...
> Hello,
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:ek81lZwnEHA.608@TK2MSFTNGP09.phx.gbl...
> > 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
> >
>
> I can move the cursor, CPU utilization is low, but I CANNOT create new
> process, when I try to do this,
> the system becomes unresponsive. I can observe CPU utilization when I start
> tak manager or process explorer BEFORE requesting ASP.NET page.
> The strange thing is, that creation of new process hangs the system.
> However, even before this, after first ASP.NET request, the network
> subsystem is unresponsive immediately. The computer responds to ping, but it
> seems like RPC is unavailable and file sharing also.
> Machine is part of domain, but no specific policy is applied.
> regards
> Artur Jedynak
>
> > 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.
> >
>
>
>
>
>