IIS Server - UNC Website

Author

UNC Website

Padraic Lavin

2005-06-25, 7:47 am

Hi,

I searched the newsgroups and have already tried a few things which haven't
resolved my problem.

My setup is this;

W2003 Standard Server acting as a file server (holding centralised content
for one website - asp files and a lot of images)
W2003 Web Edition Server using IIS to serve the website from a UNC share on
the server above.

During high traffic periods sessions get screwed up e.g. a visitor logs into
the website but
sees data relating to another user (not good at all).

I have tried various things from the following article with no success.

http://www.microsoft.com/technet/pr...s/remstorg.mspx

I am convinced its a problem with the file server not being able to cope
with requests.

Neither server seems to be under any stress and I know I can solve the
problem by serving the website from one
server instead of two however this would be a short term solution. I really
need to have centralised content
served by multiple servers.

Any suggestions?

--
Regards,

Padraic Lavin

David Wang [Msft]

2005-06-25, 5:50 pm

If your problem is with sessions, then I'm not certain UNC is involved --
because session state is usually stored on the webserver itself (it is NOT
stored on the filesystem nor involved with UNC). I would start looking at
how you create and maintain session state -- are you using your own, one
that is built into the web application platform, or ??

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Padraic Lavin" <win2k@utvinternet.com> wrote in message
news:eMHccNYeFHA.2124@TK2MSFTNGP14.phx.gbl...
Hi,

I searched the newsgroups and have already tried a few things which haven't
resolved my problem.

My setup is this;

W2003 Standard Server acting as a file server (holding centralised content
for one website - asp files and a lot of images)
W2003 Web Edition Server using IIS to serve the website from a UNC share on
the server above.

During high traffic periods sessions get screwed up e.g. a visitor logs into
the website but
sees data relating to another user (not good at all).

I have tried various things from the following article with no success.

http://www.microsoft.com/technet/pr...s/remstorg.mspx

I am convinced its a problem with the file server not being able to cope
with requests.

Neither server seems to be under any stress and I know I can solve the
problem by serving the website from one
server instead of two however this would be a short term solution. I really
need to have centralised content
served by multiple servers.

Any suggestions?

--
Regards,

Padraic Lavin

Padraic

2005-06-30, 7:49 am

Sorry, I should have been a bit clearer. The problem isn't with sessions,
users are being
tracked using cookies. When traffic to this unc website reaches a certain
level, IIS
appears to stop responding presumably because it is waiting for the asp
files to be served
from the file server. CPU is about 10% and there is loads of available
memory. Other weird things happen, for example when a logged in user writes
to the database (via web application) the event is credited to another user
(the previous user to write to the database). SQL Server 2000 SP4 (on another
machine) is not under any stress either.

I have increased the max work items, etc. as suggested in the earlier
article with no success. I'm beginning to think its some other limit built
into IIS by default.

"David Wang [Msft]" wrote:

> If your problem is with sessions, then I'm not certain UNC is involved --
> because session state is usually stored on the webserver itself (it is NOT
> stored on the filesystem nor involved with UNC). I would start looking at
> how you create and maintain session state -- are you using your own, one
> that is built into the web application platform, or ??
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Padraic Lavin" <win2k@utvinternet.com> wrote in message
> news:eMHccNYeFHA.2124@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I searched the newsgroups and have already tried a few things which haven't
> resolved my problem.
>
> My setup is this;
>
> W2003 Standard Server acting as a file server (holding centralised content
> for one website - asp files and a lot of images)
> W2003 Web Edition Server using IIS to serve the website from a UNC share on
> the server above.
>
> During high traffic periods sessions get screwed up e.g. a visitor logs into
> the website but
> sees data relating to another user (not good at all).
>
> I have tried various things from the following article with no success.
>
> http://www.microsoft.com/technet/pr...s/remstorg.mspx
>
> I am convinced its a problem with the file server not being able to cope
> with requests.
>
> Neither server seems to be under any stress and I know I can solve the
> problem by serving the website from one
> server instead of two however this would be a short term solution. I really
> need to have centralised content
> served by multiple servers.
>
> Any suggestions?
>
> --
> Regards,
>
> Padraic Lavin
>
>
>
>

David Wang [Msft]

2005-07-01, 2:48 am

Then you really want to look at that URL to make sure you have properly
tuned both the file server and IIS web server to handle your distinctive
user load. (CPU and RAM are not the only indication of resource-contention
on the server -- you are talking about UNC shares accessed by distinct
users, which involve yet another sort of resource -- read the URL for
details).

http://www.microsoft.com/technet/pr...s/remstorg.mspx

IIS doesn't have any "limits" from a UNC perspective because it can handle
thousands of concurrent connections from the client. The problem, of course,
is that you must tune SMB on both the file server and on the web server to
support that many concurrent connections, especially if each is using a
distinct user identity (each user identity will need its own copy of the SMB
resources -- wasteful, yes, but that's how its security model works).

For example, IIS uses file change notification to detect if a file has
changed (to flush its response cache) -- this applies to both static files
and ASP files (this behavior is configurable -- find the IIS 6 Registry Keys
Full disclosure on MSDN for the details). Other ISAPIs/CGIs may implement
the same thing (for example, I know ASP.Net has the same problem with UNC
that ASP had on IIS5 -- IIS6 and ASP on IIS6 uses different strategy for
UNC). This change notification consume SMB resources if the vdir is UNC and
effectively double the number of SMB required per unique authenticated user.

Of course, this really isn't a "problem" of the Windows File Server. Sure,
there are file servers out there without this problem, but they also don't
support change notifications -- a real performance drag because the web
server MUST connect over UNC to check the file stats every request instead
of having the filesystem asynchronous tell the webserver when/if the file
ever changes). Centralized storage isn't free; it drags in its own set of
problems that you must be aware of and tune. You will have to decide the cac
hing scheme, user authentication scheme, etc that work for your scenario,
and tune it all.

In our load/reliability tests (we basically just install using default
values, figure out and tweak certain values, and run our simulations --
closest situation to what you'd be doing) -- if you do not calculate those
SMB values correctly, you get very strange behavior from the fileserver that
result in unexpected 200s, 401s, or 500s.

And you did change the values on both "SMB client" (i.e. the web server) and
"SMB server" (i.e. the file server) and reboot them to take effect?

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Padraic" <Padraic@discussions.microsoft.com> wrote in message
news:55E4728A-B01D-4F39-A69E-CE3DC7CD66D4@microsoft.com...

Sorry, I should have been a bit clearer. The problem isn't with sessions,
users are being
tracked using cookies. When traffic to this unc website reaches a certain
level, IIS
appears to stop responding presumably because it is waiting for the asp
files to be served
from the file server. CPU is about 10% and there is loads of available
memory. Other weird things happen, for example when a logged in user writes
to the database (via web application) the event is credited to another user
(the previous user to write to the database). SQL Server 2000 SP4 (on
another
machine) is not under any stress either.

I have increased the max work items, etc. as suggested in the earlier
article with no success. I'm beginning to think its some other limit built
into IIS by default.

"David Wang [Msft]" wrote:

> If your problem is with sessions, then I'm not certain UNC is involved --
> because session state is usually stored on the webserver itself (it is NOT
> stored on the filesystem nor involved with UNC). I would start looking at
> how you create and maintain session state -- are you using your own, one
> that is built into the web application platform, or ??
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Padraic Lavin" <win2k@utvinternet.com> wrote in message
> news:eMHccNYeFHA.2124@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I searched the newsgroups and have already tried a few things which
haven't
> resolved my problem.
>
> My setup is this;
>
> W2003 Standard Server acting as a file server (holding centralised content
> for one website - asp files and a lot of images)
> W2003 Web Edition Server using IIS to serve the website from a UNC share
on
> the server above.
>
> During high traffic periods sessions get screwed up e.g. a visitor logs
into
> the website but
> sees data relating to another user (not good at all).
>
> I have tried various things from the following article with no success.
>
>
http://www.microsoft.com/technet/pr...s/remstorg.mspx
>
> I am convinced its a problem with the file server not being able to cope
> with requests.
>
> Neither server seems to be under any stress and I know I can solve the
> problem by serving the website from one
> server instead of two however this would be a short term solution. I
really
> need to have centralised content
> served by multiple servers.
>
> Any suggestions?
>
> --
> Regards,
>
> Padraic Lavin
>
>
>
>

Padraic

2005-07-01, 7:53 am

Thanks David for the replies.

I have already read the document you suggest and applied the registry
changes (see my first post).

I have ruled out UNC at this stage. I made changes to the code so that only
a fraction of
the asp files were accessed over a share (about 180). Performance increased
but the same problem occurred.
I then moved the asp files to the server so that UNC cannot be the cause as
it isn't used anymore.
About 12 hours later the same problem occurred.

When I mentioned limits I was referring to W2003 pre SP1 where the max ports
limit caused timeout
errors when trying to access SQL Server in certain cases. It was a simple
registry change but took
a lot of investigating to identify the problem. At least the problem was
addressed in SP1.

I don't think that IIS is able to use all the memory available to it. I have
IIS setup
to cache the 180 or so asp files in memory and application variables are
used quite a lot.
When the problem occurs there's about 512mb free ram but the asp files
cannot load the
application variables into memory. At this stage I haven't a clue what could
be causing the
problem or how to fix it short of reinstalling IIS.

Great blog btw.

"David Wang [Msft]" wrote:

> Then you really want to look at that URL to make sure you have properly
> tuned both the file server and IIS web server to handle your distinctive
> user load. (CPU and RAM are not the only indication of resource-contention
> on the server -- you are talking about UNC shares accessed by distinct
> users, which involve yet another sort of resource -- read the URL for
> details).
>
> http://www.microsoft.com/technet/pr...s/remstorg.mspx
>
> IIS doesn't have any "limits" from a UNC perspective because it can handle
> thousands of concurrent connections from the client. The problem, of course,
> is that you must tune SMB on both the file server and on the web server to
> support that many concurrent connections, especially if each is using a
> distinct user identity (each user identity will need its own copy of the SMB
> resources -- wasteful, yes, but that's how its security model works).
>
> For example, IIS uses file change notification to detect if a file has
> changed (to flush its response cache) -- this applies to both static files
> and ASP files (this behavior is configurable -- find the IIS 6 Registry Keys
> Full disclosure on MSDN for the details). Other ISAPIs/CGIs may implement
> the same thing (for example, I know ASP.Net has the same problem with UNC
> that ASP had on IIS5 -- IIS6 and ASP on IIS6 uses different strategy for
> UNC). This change notification consume SMB resources if the vdir is UNC and
> effectively double the number of SMB required per unique authenticated user.
>
> Of course, this really isn't a "problem" of the Windows File Server. Sure,
> there are file servers out there without this problem, but they also don't
> support change notifications -- a real performance drag because the web
> server MUST connect over UNC to check the file stats every request instead
> of having the filesystem asynchronous tell the webserver when/if the file
> ever changes). Centralized storage isn't free; it drags in its own set of
> problems that you must be aware of and tune. You will have to decide the cac
> hing scheme, user authentication scheme, etc that work for your scenario,
> and tune it all.
>
> In our load/reliability tests (we basically just install using default
> values, figure out and tweak certain values, and run our simulations --
> closest situation to what you'd be doing) -- if you do not calculate those
> SMB values correctly, you get very strange behavior from the fileserver that
> result in unexpected 200s, 401s, or 500s.
>
> And you did change the values on both "SMB client" (i.e. the web server) and
> "SMB server" (i.e. the file server) and reboot them to take effect?
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Padraic" <Padraic@discussions.microsoft.com> wrote in message
> news:55E4728A-B01D-4F39-A69E-CE3DC7CD66D4@microsoft.com...
>
> Sorry, I should have been a bit clearer. The problem isn't with sessions,
> users are being
> tracked using cookies. When traffic to this unc website reaches a certain
> level, IIS
> appears to stop responding presumably because it is waiting for the asp
> files to be served
> from the file server. CPU is about 10% and there is loads of available
> memory. Other weird things happen, for example when a logged in user writes
> to the database (via web application) the event is credited to another user
> (the previous user to write to the database). SQL Server 2000 SP4 (on
> another
> machine) is not under any stress either.
>
> I have increased the max work items, etc. as suggested in the earlier
> article with no success. I'm beginning to think its some other limit built
> into IIS by default.
>
>
> "David Wang [Msft]" wrote:
>
> rights.
> haven't
> on
> into
> http://www.microsoft.com/technet/pr...s/remstorg.mspx
> really
>
>
>

Padraic

2005-07-04, 7:49 am

Thread ID: 40
System Thread ID: f8c
Kernel Time: 0:0:3.750
User Time: 0:7:26.46
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04f7fdcc 7c822114 ntdll!KiFastSystemCallRet
01 04f7fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04f7fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04f7fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04f7fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04f7ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04f7ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04f7ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 41
System Thread ID: ae0
Kernel Time: 0:0:4.890
User Time: 0:7:40.328
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04fbfdcc 7c822114 ntdll!KiFastSystemCallRet
01 04fbfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04fbfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04fbfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04fbfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04fbff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04fbffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04fbffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 42
System Thread ID: 8a0
Kernel Time: 0:0:4.62
User Time: 0:8:7.843
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0503fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0503fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0503fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0503fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0503fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0503ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0503ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0503ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 43
System Thread ID: 44c
Kernel Time: 0:0:4.484
User Time: 0:7:22.46
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0529fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0529fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0529fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0529fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0529fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0529ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0529ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0529ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 44
System Thread ID: bf0
Kernel Time: 0:0:4.937
User Time: 0:8:14.812
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 052dfdcc 7c822114 ntdll!KiFastSystemCallRet
01 052dfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 052dfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 052dfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 052dfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 052dff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 052dffb8 77e66063 msvcrt!_endthreadex+0xa3
07 052dffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 45
System Thread ID: 2e4
Kernel Time: 0:0:5.46
User Time: 0:8:9.265
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0531fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0531fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0531fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0531fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0531fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0531ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0531ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0531ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 46
System Thread ID: ef4
Kernel Time: 0:0:4.46
User Time: 0:7:24.515
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0535fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0535fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0535fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0535fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0535fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0535ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0535ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0535ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 47
System Thread ID: a94
Kernel Time: 0:0:4.859
User Time: 0:7:59.203
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04fffdcc 7c822114 ntdll!KiFastSystemCallRet
01 04fffdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04fffe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04fffed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04fffef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04ffff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04ffffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04ffffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 48
System Thread ID: be8
Kernel Time: 0:0:4.765
User Time: 0:9:8.671
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0539fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0539fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0539fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0539fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0539fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0539ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0539ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0539ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 49
System Thread ID: bc4
Kernel Time: 0:0:4.390
User Time: 0:8:5.421
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 053dfdcc 7c822114 ntdll!KiFastSystemCallRet
01 053dfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 053dfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 053dfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 053dfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 053dff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 053dffb8 77e66063 msvcrt!_endthreadex+0xa3
07 053dffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 50
System Thread ID: 4e8
Kernel Time: 0:0:4.78
User Time: 0:7:39.875
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0541fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0541fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0541fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0541fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0541fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0541ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0541ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0541ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 51
System Thread ID: 6f4
Kernel Time: 0:0:4.296
User Time: 0:8:40.468
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0545fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0545fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0545fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0545fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0545fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0545ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0545ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0545ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 52
System Thread ID: d6c
Kernel Time: 0:0:13.484
User Time: 0:7:23.921
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0555fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0555fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0555fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0555fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0555fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0555ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0555ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0555ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 53
System Thread ID: c94
Kernel Time: 0:0:4.140
User Time: 0:7:47.421
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0559fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0559fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0559fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0559fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0559fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0559ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0559ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0559ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 54
System Thread ID: c28
Kernel Time: 0:0:4.578
User Time: 0:7:27.921
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 055dfdcc 7c822114 ntdll!KiFastSystemCallRet
01 055dfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 055dfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 055dfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 055dfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 055dff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 055dffb8 77e66063 msvcrt!_endthreadex+0xa3
07 055dffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 55
System Thread ID: e5c
Kernel Time: 0:0:4.500
User Time: 0:8:15.359
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0561fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0561fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0561fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0561fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0561fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0561ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0561ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0561ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 56
System Thread ID: e74
Kernel Time: 0:0:4.390
User Time: 0:7:26.453
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0460fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0460fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0460fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0460fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0460fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0460ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0460ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0460ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 57
System Thread ID: d10
Kernel Time: 0:0:4.875
User Time: 0:8:3.265
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0549fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0549fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0549fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0549fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0549fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0549ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0549ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0549ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 58
System Thread ID: 8e4
Kernel Time: 0:0:6.843
User Time: 0:7:23.484
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0551fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0551fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0551fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0551fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0551fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0551ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0551ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0551ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 59
System Thread ID: 9ac
Kernel Time: 0:0:4.359
User Time: 0:7:33.656
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0565fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0565fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0565fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0565fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0565fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0565ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0565ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0565ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 60
System Thread ID: 9d0
Kernel Time: 0:0:3.984
User Time: 0:7:8.234
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0569fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0569fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0569fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0569fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0569fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0569ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0569ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0569ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 61
System Thread ID: b00
Kernel Time: 0:0:5.15
User Time: 0:7:36.31
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 056dfdcc 7c822114 ntdll!KiFastSystemCallRet
01 056dfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 056dfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 056dfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 056dfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 056dff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 056dffb8 77e66063 msvcrt!_endthreadex+0xa3
07 056dffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 62
System Thread ID: e9c
Kernel Time: 0:0:4.625
User Time: 0:8:3.718
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 05cafdcc 7c822114 ntdll!KiFastSystemCallRet
01 05cafdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 05cafe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 05cafed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 05cafef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 05caff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 05caffb8 77e66063 msvcrt!_endthreadex+0xa3
07 05caffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 63
System Thread ID: ebc
Kernel Time: 0:0:4.171
User Time: 0:8:6.62
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 05d2fdcc 7c822114 ntdll!KiFastSystemCallRet
01 05d2fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 05d2fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 05d2fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 05d2fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 05d2ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 05d2ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 05d2ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 64
System Thread ID: b64
Kernel Time: 0:0:4.796
User Time: 0:8:6.125
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 05d6fdcc 7c822114 ntdll!KiFastSystemCallRet
01 05d6fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 05d6fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 05d6fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 05d6fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 05d6ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 05d6ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 05d6ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 65
System Thread ID: c3c
Kernel Time: 0:0:5.156
User Time: 0:7:16.265
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 05dafdcc 7c822114 ntdll!KiFastSystemCallRet
01 05dafdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 05dafe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 05dafed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 05dafef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 05daff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 05daffb8 77e66063 msvcrt!_endthreadex+0xa3
07 05daffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 66
System Thread ID: a34
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 0d38fe18 7c821c54 ntdll!KiFastSystemCallRet
01 0d38fe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
02 0d38ff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0
x198
03 0d38ff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
04 0d38ffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
05 0d38ffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
06 0d38ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 67
System Thread ID: ef0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: Unable to locate ASP page

No remote call being made

# ChildEBP RetAddr
00 0571fe18 7c821c54 ntdll!KiFastSystemCallRet
01 0571fe1c 77c7538c ntdll!ZwReplyWaitReceivePortEx+0xc
02 0571ff84 77c5778f RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0
x198
03 0571ff8c 77c5f7dd RPCRT4!RecvLotsaCallsWrapper+0xd
04 0571ffac 77c5de88 RPCRT4!BaseCachedThreadRoutine+0x9d
05 0571ffb8 77e66063 RPCRT4!ThreadStartRoutine+0x1b
06 0571ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 68
System Thread ID: 9b4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0750ff70 7c821bf4 ntdll!KiFastSystemCallRet
01 0750ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 0750ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 0750ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 69
System Thread ID: ec0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0754ff70 7c821bf4 ntdll!KiFastSystemCallRet
01 0754ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 0754ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 0754ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 70
System Thread ID: ee8
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 041bff70 7c821bf4 ntdll!KiFastSystemCallRet
01 041bff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 041bffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 041bffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 71
System Thread ID: a6c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0575ff70 7c821bf4 ntdll!KiFastSystemCallRet
01 0575ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 0575ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 0575ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 72
System Thread ID: 9d8
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 06ebff70 7c821bf4 ntdll!KiFastSystemCallRet
01 06ebff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 06ebffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 06ebffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 73
System Thread ID: fc0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 06efff70 7c821bf4 ntdll!KiFastSystemCallRet
01 06efff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 06efffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 06efffec 00000000 kernel32!BaseThreadStart+0x34

Padraic

2005-07-04, 7:49 am

I've re-installed IIS since and the problem still happens.

This is the output from IIS State. ( I have to post it in two replies)

Starting new log output
IISState version 3.3.1

Mon Jul 04 03:21:59 2005

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 2328

Thread ID: 0
System Thread ID: 9e4
Kernel Time: 0:0:0.31
User Time: 0:0:0.46
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 0006fc08 7c822124 ntdll!KiFastSystemCallRet
01 0006fc0c 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0006fc7c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0006fc90 5a36467a kernel32!WaitForSingleObject+0x12
04 0006fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10
05 0006fca8 5a3af41d w3dt!UlAtqStartListen+0x2d
06 0006fcb8 5a3bc259 w3core!W3_SERVER::StartListen+0xbd
07 0006ff0c 0100187c w3core!UlW3Start+0x26e
08 0006ff44 01001a23 w3wp!wmain+0x22a
09 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x12b
0a 0006fff0 00000000 kernel32!BaseProcessStart+0x23

Thread ID: 1
System Thread ID: da4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 009eff9c 7c821364 ntdll!KiFastSystemCallRet
01 009effa0 7c81fe26 ntdll!NtDelayExecution+0xc
02 009effb8 77e66063 ntdll!RtlpTimerThread+0x47
03 009effec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 2
System Thread ID: 658
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00a2ff70 7c821bf4 ntdll!KiFastSystemCallRet
01 00a2ff74 7c83ad75 ntdll!NtRemoveIoCompletion+0xc
02 00a2ffb8 77e66063 ntdll!RtlpWorkerThread+0x3d
03 00a2ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 3
System Thread ID: dd8
Kernel Time: 0:0:3.578
User Time: 0:0:5.718
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00caff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00caff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00caff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00caff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x33
04 00caffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x24
05 00caffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread
+0x39
06 00caffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 4
System Thread ID: 6c8
Kernel Time: 0:0:5.984
User Time: 0:0:11.62
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00ceff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00ceff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00ceff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00ceff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x33
04 00ceffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x24
05 00ceffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread
+0x39
06 00ceffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 5
System Thread ID: 29c
Kernel Time: 0:0:3.406
User Time: 0:0:5.562
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d2ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d2ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d2ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d2ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x33
04 00d2ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x24
05 00d2ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread
+0x39
06 00d2ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 6
System Thread ID: 964
Kernel Time: 0:0:0.187
User Time: 0:0:0.625
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d6ff24 7c821bf4 ntdll!KiFastSystemCallRet
01 00d6ff28 77e6611a ntdll!NtRemoveIoCompletion+0xc
02 00d6ff54 5a30249e kernel32!GetQueuedCompletionStatus+0x29
03 00d6ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x33
04 00d6ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+
0x24
05 00d6ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread
+0x39
06 00d6ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 7
System Thread ID: f54
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00e2fcec 7c822114 ntdll!KiFastSystemCallRet
01 00e2fcf0 7c83acfd ntdll!NtWaitForMultipleObjects+0xc
02 00e2ffb8 77e66063 ntdll!RtlpWaitThread+0x161
03 00e2ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 8
System Thread ID: 844
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 017afa84 7c822124 ntdll!KiFastSystemCallRet
01 017afa88 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 017afaf8 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 017afb0c 5a3b8147 kernel32!WaitForSingleObject+0x12
04 017affb8 77e66063 w3core!HTTP_COMPRESSION::CompressionThre
ad+0x126
05 017affec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 9
System Thread ID: c70
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: ASP
Executing Page: Unable to locate ASP page

# ChildEBP RetAddr
00 024bff0c 7c822124 ntdll!KiFastSystemCallRet
01 024bff10 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 024bff80 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 024bff94 709fc91b kernel32!WaitForSingleObject+0x12
04 024bffb4 709fc8f3 asp!CApplnCleanupMgr::ApplnCleanupDoWork
+0x1e
05 024bffb8 77e66063 asp!CApplnCleanupMgr::ApplnCleanupThread
+0xa
06 024bffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 10
System Thread ID: f80
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: ASP
Executing Page: Unable to locate ASP page

# ChildEBP RetAddr
00 0257fe1c 7c822114 ntdll!KiFastSystemCallRet
01 0257fe20 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0257fec8 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0257ff24 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0257ff40 709fbcbe USER32!MsgWaitForMultipleObjects+0x1f
05 0257ff84 77bcb530 asp!CMTACallbackThread::Thread+0x4f
06 0257ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0257ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 11
System Thread ID: 9f4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: ASP
Executing Page: Unable to locate ASP page

# ChildEBP RetAddr
00 025bfef4 7c822124 ntdll!KiFastSystemCallRet
01 025bfef8 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 025bff68 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 025bff7c 709fe9b7 kernel32!WaitForSingleObject+0x12
04 025bffb8 77e66063 asp!CViperReqManager::WatchThread+0x68
05 025bffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 12
System Thread ID: c74
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0261fee8 7c822124 ntdll!KiFastSystemCallRet
01 0261feec 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0261ff5c 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0261ff70 75bd4dc8 kernel32!WaitForSingleObject+0x12
04 0261ff84 77bcb530 comsvcs!CSTAThreadPool::LoadBalanceThrea
dControlLoop+0x29
05 0261ffb8 77e66063 msvcrt!_endthreadex+0xa3
06 0261ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 13
System Thread ID: d84
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0265fee0 7c822124 ntdll!KiFastSystemCallRet
01 0265fee4 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 0265ff54 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 0265ff68 75bd4843 kernel32!WaitForSingleObject+0x12
04 0265ff84 77bcb530 comsvcs!CSTAThreadPool::KillThreadContro
lLoop+0x25
05 0265ffb8 77e66063 msvcrt!_endthreadex+0xa3
06 0265ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 14
System Thread ID: e6c
Kernel Time: 0:0:4.640
User Time: 0:7:23.421
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0269fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0269fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0269fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0269fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0269fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0269ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0269ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0269ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 15
System Thread ID: e54
Kernel Time: 0:0:5.250
User Time: 0:8:29.421
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 026dfdcc 7c822114 ntdll!KiFastSystemCallRet
01 026dfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 026dfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 026dfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 026dfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 026dff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 026dffb8 77e66063 msvcrt!_endthreadex+0xa3
07 026dffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 16
System Thread ID: a08
Kernel Time: 0:0:5.890
User Time: 0:8:34.46
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0271fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0271fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0271fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0271fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0271fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0271ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0271ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0271ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 17
System Thread ID: 4d8
Kernel Time: 0:0:4.718
User Time: 0:8:48.78
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0275fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0275fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0275fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0275fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0275fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0275ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0275ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0275ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 18
System Thread ID: 824
Kernel Time: 0:0:0.0
User Time: 0:0:0.15
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 030ffd00 7c822124 ntdll!KiFastSystemCallRet
01 030ffd04 77e6baa8 ntdll!NtWaitForSingleObject+0xc
02 030ffd74 77e6ba12 kernel32!WaitForSingleObjectEx+0xac
03 030ffd88 75bb250b kernel32!WaitForSingleObject+0x12
04 030fffb8 77e66063 comsvcs!PingThread+0xf6
05 030fffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 19
System Thread ID: b48
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 032cff88 7c822114 ntdll!KiFastSystemCallRet
01 032cff8c 71c6df01 ntdll!NtWaitForMultipleObjects+0xc
02 032cffb8 77e66063 NETAPI32!NetbiosWaiter+0x73
03 032cffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 20
System Thread ID: 5e8
Kernel Time: 0:0:4.718
User Time: 0:8:10.234
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 038cfdcc 7c822114 ntdll!KiFastSystemCallRet
01 038cfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 038cfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 038cfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 038cfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 038cff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 038cffb8 77e66063 msvcrt!_endthreadex+0xa3
07 038cffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 21
System Thread ID: b78
Kernel Time: 0:0:5.62
User Time: 0:8:11.468
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0422fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0422fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0422fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0422fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0422fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0422ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0422ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0422ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 22
System Thread ID: c68
Kernel Time: 0:0:4.625
User Time: 0:7:31.750
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0426fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0426fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0426fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0426fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0426fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0426ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0426ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0426ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 23
System Thread ID: 604
Kernel Time: 0:0:15.921
User Time: 0:7:48.890
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 042afdcc 7c822114 ntdll!KiFastSystemCallRet
01 042afdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 042afe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 042afed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 042afef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 042aff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 042affb8 77e66063 msvcrt!_endthreadex+0xa3
07 042affec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 24
System Thread ID: 8a8
Kernel Time: 0:0:4.890
User Time: 0:7:59.593
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 042efdcc 7c822114 ntdll!KiFastSystemCallRet
01 042efdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 042efe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 042efed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 042efef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 042eff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 042effb8 77e66063 msvcrt!_endthreadex+0xa3
07 042effec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 25
System Thread ID: 32c
Kernel Time: 0:0:5.281
User Time: 0:8:19.906
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0442fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0442fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0442fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0442fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0442fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0442ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0442ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0442ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 26
System Thread ID: c38
Kernel Time: 0:0:4.796
User Time: 0:7:38.953
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0446fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0446fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0446fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0446fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0446fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0446ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0446ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0446ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 27
System Thread ID: fb4
Kernel Time: 0:0:4.453
User Time: 0:7:36.109
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 044afdcc 7c822114 ntdll!KiFastSystemCallRet
01 044afdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 044afe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 044afed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 044afef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 044aff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 044affb8 77e66063 msvcrt!_endthreadex+0xa3
07 044affec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 28
System Thread ID: 730
Kernel Time: 0:0:5.250
User Time: 0:8:12.296
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0464fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0464fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0464fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0464fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0464fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0464ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0464ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0464ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 29
System Thread ID: 990
Kernel Time: 0:0:5.0
User Time: 0:8:21.625
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0468fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0468fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0468fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0468fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0468fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0468ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0468ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0468ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 30
System Thread ID: 2d8
Kernel Time: 0:0:12.250
User Time: 0:8:3.156
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 047cfdcc 7c822114 ntdll!KiFastSystemCallRet
01 047cfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 047cfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 047cfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 047cfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 047cff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 047cffb8 77e66063 msvcrt!_endthreadex+0xa3
07 047cffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 31
System Thread ID: 8f8
Kernel Time: 0:0:4.93
User Time: 0:7:0.328
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0484fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0484fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0484fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0484fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0484fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0484ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0484ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0484ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 32
System Thread ID: fec
Kernel Time: 0:0:4.656
User Time: 0:7:51.390
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 0488fdcc 7c822114 ntdll!KiFastSystemCallRet
01 0488fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 0488fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 0488fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 0488fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 0488ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 0488ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 0488ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 33
System Thread ID: f90
Kernel Time: 0:0:4.875
User Time: 0:7:34.296
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 048cfdcc 7c822114 ntdll!KiFastSystemCallRet
01 048cfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 048cfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 048cfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 048cfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 048cff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 048cffb8 77e66063 msvcrt!_endthreadex+0xa3
07 048cffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 34
System Thread ID: 56c
Kernel Time: 0:0:4.843
User Time: 0:7:52.828
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04b4fdcc 7c822114 ntdll!KiFastSystemCallRet
01 04b4fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04b4fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04b4fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04b4fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04b4ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04b4ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04b4ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 35
System Thread ID: 8f0
Kernel Time: 0:0:4.687
User Time: 0:8:9.796
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04b8fdcc 7c822114 ntdll!KiFastSystemCallRet
01 04b8fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04b8fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04b8fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04b8fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04b8ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04b8ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04b8ffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 36
System Thread ID: 954
Kernel Time: 0:0:14.593
User Time: 0:7:37.218
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04bcfdcc 7c822114 ntdll!KiFastSystemCallRet
01 04bcfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04bcfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04bcfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04bcfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04bcff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04bcffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04bcffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 37
System Thread ID: 380
Kernel Time: 0:0:4.578
User Time: 0:8:9.687
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04dbfdcc 7c822114 ntdll!KiFastSystemCallRet
01 04dbfdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04dbfe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04dbfed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04dbfef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04dbff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04dbffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04dbffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 38
System Thread ID: 240
Kernel Time: 0:0:4.921
User Time: 0:8:10.953
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04effdcc 7c822114 ntdll!KiFastSystemCallRet
01 04effdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04effe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04effed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04effef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04efff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04efffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04efffec 00000000 kernel32!BaseThreadStart+0x34

Thread ID: 39
System Thread ID: 4c0
Kernel Time: 0:0:4.390
User Time: 0:7:26.609
Thread Status: Thread is in a WAIT state.
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 04f3fdcc 7c822114 ntdll!KiFastSystemCallRet
01 04f3fdd0 77e6711b ntdll!NtWaitForMultipleObjects+0xc
02 04f3fe78 7739cd08 kernel32!WaitForMultipleObjectsEx+0x11a
03 04f3fed4 7738e381 USER32!RealMsgWaitForMultipleObjectsEx+0
x141
04 04f3fef0 75bd88b6 USER32!MsgWaitForMultipleObjects+0x1f
05 04f3ff84 77bcb530 comsvcs!CSTAThread::WorkerLoop+0x1e5
06 04f3ffb8 77e66063 msvcrt!_endthreadex+0xa3
07 04f3ffec 00000000 kernel32!BaseThreadStart+0x34

David Wang [Msft]

2005-07-05, 5:57 pm

You can repost use "IIS State Log Analysis" as the subject so that more
people are aware of it.

The errors you noted about symbols are not the problem. They just indicate
that symbol files could not be located for DLLs loaded in the process --
which prevent correct stack resolution.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Padraic Lavin" <win2k@utvinternet.com> wrote in message
news:O9FuPDTgFHA.1284@TK2MSFTNGP14.phx.gbl...
Hi again,

I think I caught it while the crash was happening.
CPU was at a constant 50% for a small period so I ran IISSTATE
The result is iisstate-812.log

Afterwards when the asp pages were unusable I ran IISSTATE again.
The result of this is iisstate-812-2.log (too large to post)

I noticed these errors

"*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\OLEAUT32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\vbscript.dll - "

Any assistance would be greatly appreciated.

--
Regards,

Padraic

"Padraic" <Padraic@discussions.microsoft.com> wrote in message
news:62E5601D-3832-4E65-AAFE-81B4CEBBE410@microsoft.com...[vbcol=seagreen]
> Thanks David for the replies.
>
> I have already read the document you suggest and applied the registry
> changes (see my first post).
>
> I have ruled out UNC at this stage. I made changes to the code so that
> only
> a fraction of
> the asp files were accessed over a share (about 180). Performance
> increased
> but the same problem occurred.
> I then moved the asp files to the server so that UNC cannot be the cause
> as
> it isn't used anymore.
> About 12 hours later the same problem occurred.
>
> When I mentioned limits I was referring to W2003 pre SP1 where the max
> ports
> limit caused timeout
> errors when trying to access SQL Server in certain cases. It was a simple
> registry change but took
> a lot of investigating to identify the problem. At least the problem was
> addressed in SP1.
>
> I don't think that IIS is able to use all the memory available to it. I
> have
> IIS setup
> to cache the 180 or so asp files in memory and application variables are
> used quite a lot.
> When the problem occurs there's about 512mb free ram but the asp files
> cannot load the
> application variables into memory. At this stage I haven't a clue what
> could
> be causing the
> problem or how to fix it short of reinstalling IIS.
>
> Great blog btw.
>
> "David Wang [Msft]" wrote:
>
http://www.microsoft.com/technet/pr...s/remstorg.mspx[vbcol=seagreen]
http://www.microsoft.com/technet/pr...s/remstorg.mspx[vbcol=seagreen]