Troubleshooting ASP.Net Application Pools on IIS6

I have several sites running on Windows 2003 Server in true IIS 6 mode
with Application pools. One site has about 9 Virtual Directories in
it that are all configured to run as applications. Each of these have
a dedicated application pool with all different memory settings in the
Memory Recycling area.
The applications are all .Net based applications. They are all pretty
frequently used apps and as a rule of thumb, we assigned more memory
in the app pools to the busier sites and less to the least busy sites.
Here's the deal. Every once in a while, the application will hang up
and not respond. Once I recycle the application, it's fine.
I don't really get a whole lot of info from the developers other than
"The site is hung up" The only thing I see is stuff like this in the
eventlog. This is usually AFTER I recycle the application and it
start working again.
----
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 11/18/2004
Time: 2:37:21 PM
User: N/A
Computer: <server name>
Description:
A process serving application pool <app name>' exceeded time limits
during shut down. The process id was '344'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----
I'd like to know what I can do to troubleshoot this. Is there any
other logs I can check? Are there any diagnostic tools that I can
check?Hello,
Please take a look at following articles. These might be helpful in your
case.
828222 How to generate a dump file when ASP.NET deadlocks in IIS 6.0
http://support.microsoft.com/?id=828222
821268 PRB: Contention, poor performance, and deadlocks when you make Web
http://support.microsoft.com/?id=821268
HTH.
Thanks.
Ganesh Anekar
Microsoft Developer Support
Internet Information Server
****************************************
*****************************red">
account name for newsgroup participation only.<<
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
2004 Microsoft Corporation. All rights reserved.
****************************************
*****************************
"dreamlinetheater" <dreamlinetheater@.hotmail.com> wrote in message
news:e153da91.0411181313.145fa674@.posting.google.com...
>I have several sites running on Windows 2003 Server in true IIS 6 mode
> with Application pools. One site has about 9 Virtual Directories in
> it that are all configured to run as applications. Each of these have
> a dedicated application pool with all different memory settings in the
> Memory Recycling area.
> The applications are all .Net based applications. They are all pretty
> frequently used apps and as a rule of thumb, we assigned more memory
> in the app pools to the busier sites and less to the least busy sites.
> Here's the deal. Every once in a while, the application will hang up
> and not respond. Once I recycle the application, it's fine.
> I don't really get a whole lot of info from the developers other than
> "The site is hung up" The only thing I see is stuff like this in the
> eventlog. This is usually AFTER I recycle the application and it
> start working again.
> ----
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1013
> Date: 11/18/2004
> Time: 2:37:21 PM
> User: N/A
> Computer: <server name>
> Description:
> A process serving application pool <app name>' exceeded time limits
> during shut down. The process id was '344'.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----
>
> I'd like to know what I can do to troubleshoot this. Is there any
> other logs I can check? Are there any diagnostic tools that I can
> check?

Troubleshooting ASP.Net Application Pools on IIS6

I have several sites running on Windows 2003 Server in true IIS 6 mode
with Application pools. One site has about 9 Virtual Directories in
it that are all configured to run as applications. Each of these have
a dedicated application pool with all different memory settings in the
Memory Recycling area.

The applications are all .Net based applications. They are all pretty
frequently used apps and as a rule of thumb, we assigned more memory
in the app pools to the busier sites and less to the least busy sites.

Here's the deal. Every once in a while, the application will hang up
and not respond. Once I recycle the application, it's fine.
I don't really get a whole lot of info from the developers other than
"The site is hung up" The only thing I see is stuff like this in the
eventlog. This is usually AFTER I recycle the application and it
start working again.

----------------
Event Type:Warning
Event Source:W3SVC
Event Category:None
Event ID:1013
Date:11/18/2004
Time:2:37:21 PM
User:N/A
Computer:<server name>
Description:
A process serving application pool <app name>' exceeded time limits
during shut down. The process id was '344'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

----------------

I'd like to know what I can do to troubleshoot this. Is there any
other logs I can check? Are there any diagnostic tools that I can
check?Hello,

Please take a look at following articles. These might be helpful in your
case.

828222 How to generate a dump file when ASP.NET deadlocks in IIS 6.0
http://support.microsoft.com/?id=828222

821268 PRB: Contention, poor performance, and deadlocks when you make Web
http://support.microsoft.com/?id=821268

HTH.
Thanks.
Ganesh Anekar
Microsoft Developer Support
Internet Information Server
************************************************** *******************
>>Please do not send email directly to this alias. This is an online
account name for newsgroup participation only.<<

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

2004 Microsoft Corporation. All rights reserved.
************************************************** *******************
"dreamlinetheater" <dreamlinetheater@.hotmail.com> wrote in message
news:e153da91.0411181313.145fa674@.posting.google.c om...
>I have several sites running on Windows 2003 Server in true IIS 6 mode
> with Application pools. One site has about 9 Virtual Directories in
> it that are all configured to run as applications. Each of these have
> a dedicated application pool with all different memory settings in the
> Memory Recycling area.
> The applications are all .Net based applications. They are all pretty
> frequently used apps and as a rule of thumb, we assigned more memory
> in the app pools to the busier sites and less to the least busy sites.
> Here's the deal. Every once in a while, the application will hang up
> and not respond. Once I recycle the application, it's fine.
> I don't really get a whole lot of info from the developers other than
> "The site is hung up" The only thing I see is stuff like this in the
> eventlog. This is usually AFTER I recycle the application and it
> start working again.
> ----------------
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1013
> Date: 11/18/2004
> Time: 2:37:21 PM
> User: N/A
> Computer: <server name>
> Description:
> A process serving application pool <app name>' exceeded time limits
> during shut down. The process id was '344'.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----------------
>
> I'd like to know what I can do to troubleshoot this. Is there any
> other logs I can check? Are there any diagnostic tools that I can
> check?

Troubleshooting ASP.NET

when i turn on visual studio.net i got , asp.net project i got thr following message
The specified server is not runnung ASP.NET ...version...
using help i did aspnet_regiis/i
but it does not work

please help
thanks.Well is it saying you are not running ASP.NET version 1.1?

If so make sure you go to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 in the cmd window and run aspnet_regiis.exe -i . That will install version 1.1.

troubleshooting conflicting DLL references.

Here's the scenario:
We've purchased DTSearch search engine.
It ships with a .net api dll that we can add to our project.
Adding this DLL as a new reference, however, kills my project and spits out
a seemingly irrelevant error:
----
C:\Inetpub\wwwroot\userControls\cioPosti
ngDisplay.ascx.vb(58) : error
BC30392: 'Catch' cannot catch type 'exception' because it is not
'System.Exception' or a class that inherits from 'System.Exception'.
C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(106) : error
BC30392: 'Catch' cannot catch type 'exception' because it is not
'System.Exception' or a class that inherits from 'System.Exception'.
C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(108) : error
BC30456: 'Message' is not a member of 'exception'.
C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(108) : error
BC30456: 'Source' is not a member of 'exception'.
----
What are things that could possibly cause this? The vendor (rightfully so)
finds this behavior odd...as do I.
-DarrelIt looks pretty clear to me:
error BC30392: 'Catch' cannot catch type 'exception' because it is not
'System.Exception' or a class that inherits from 'System.Exception'.
Your catch needs to be:
Try
' ... code
Catch(exception As System.Exception)
' ... code
Finally
' ... code
EndCatch
The remaining errors are because you're attempting to access member
properties and methods of System.Exception from a class that isn't derived
from System.Exception. Once you fix your catch statement, the rest ought to
work.
"darrel" wrote:

> Here's the scenario:
> We've purchased DTSearch search engine.
> It ships with a .net api dll that we can add to our project.
> Adding this DLL as a new reference, however, kills my project and spits ou
t
> a seemingly irrelevant error:
> ----
> C:\Inetpub\wwwroot\userControls\cioPosti
ngDisplay.ascx.vb(58) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(106) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(108) : error
> BC30456: 'Message' is not a member of 'exception'.
> C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(108) : error
> BC30456: 'Source' is not a member of 'exception'.
> ----
> What are things that could possibly cause this? The vendor (rightfully so)
> finds this behavior odd...as do I.
> -Darrel
>
>

> Here's the scenario:
> a seemingly irrelevant error:
> ----
> C:\Inetpub\wwwroot\userControls\cioPosti
ngDisplay.ascx.vb(58) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(106) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(108) : error
> BC30456: 'Message' is not a member of 'exception'.
> C:\Inetpub\wwwroot\userControls\staticCo
ntentDisplay.ascx.vb(108) : error
> BC30456: 'Source' is not a member of 'exception'.
> ----
> finds this behavior odd...as do I.
bit late, but first use system.exception instead of plain exception.
if u use Crystal Reports btw, there is your possible problem.
it uses also Exception, dunno why, but they do it
User submitted from AEWNET (http://www.aewnet.com/)

troubleshooting conflicting DLL references.

Here's the scenario:

We've purchased DTSearch search engine.

It ships with a .net api dll that we can add to our project.

Adding this DLL as a new reference, however, kills my project and spits out
a seemingly irrelevant error:
-----------------
C:\Inetpub\wwwroot\userControls\cioPostingDisplay. ascx.vb(58) : error
BC30392: 'Catch' cannot catch type 'exception' because it is not
'System.Exception' or a class that inherits from 'System.Exception'.
C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(106) : error
BC30392: 'Catch' cannot catch type 'exception' because it is not
'System.Exception' or a class that inherits from 'System.Exception'.
C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(108) : error
BC30456: 'Message' is not a member of 'exception'.
C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(108) : error
BC30456: 'Source' is not a member of 'exception'.
-----------------

What are things that could possibly cause this? The vendor (rightfully so)
finds this behavior odd...as do I.

-DarrelIt looks pretty clear to me:
error BC30392: 'Catch' cannot catch type 'exception' because it is not
'System.Exception' or a class that inherits from 'System.Exception'.

Your catch needs to be:
Try
' ... code
Catch(exception As System.Exception)
' ... code
Finally
' ... code
EndCatch

The remaining errors are because you're attempting to access member
properties and methods of System.Exception from a class that isn't derived
from System.Exception. Once you fix your catch statement, the rest ought to
work.

"darrel" wrote:

> Here's the scenario:
> We've purchased DTSearch search engine.
> It ships with a .net api dll that we can add to our project.
> Adding this DLL as a new reference, however, kills my project and spits out
> a seemingly irrelevant error:
> -----------------
> C:\Inetpub\wwwroot\userControls\cioPostingDisplay. ascx.vb(58) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(106) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(108) : error
> BC30456: 'Message' is not a member of 'exception'.
> C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(108) : error
> BC30456: 'Source' is not a member of 'exception'.
> -----------------
> What are things that could possibly cause this? The vendor (rightfully so)
> finds this behavior odd...as do I.
> -Darrel
>

> Here's the scenario:
> > We've purchased DTSearch search engine.
> > It ships with a .net api dll that we can add to our project.
> > Adding this DLL as a new reference, however, kills my project and spits out
> a seemingly irrelevant error:
> -----------------
> C:\Inetpub\wwwroot\userControls\cioPostingDisplay. ascx.vb(58) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(106) : error
> BC30392: 'Catch' cannot catch type 'exception' because it is not
> 'System.Exception' or a class that inherits from 'System.Exception'.
> C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(108) : error
> BC30456: 'Message' is not a member of 'exception'.
> C:\Inetpub\wwwroot\userControls\staticContentDispl ay.ascx.vb(108) : error
> BC30456: 'Source' is not a member of 'exception'.
> -----------------
> > What are things that could possibly cause this? The vendor (rightfully so)
> finds this behavior odd...as do I.
> > -Darrel

bit late, but first use system.exception instead of plain exception.

if u use Crystal Reports btw, there is your possible problem.
it uses also Exception, dunno why, but they do it

User submitted from AEWNET (http://www.aewnet.com/)

Troubleshooting asp.net on XP Pro

I'm working out of some asp.net books. The examples aren't working on my XP Pro system.
I know it's not my code because the files will work if I move them to my company's web server (Shhh, don't tell).

I set up IIS and made a virtual directory that points to a partition where I'm putting the files.
I have the .NET Framework 1.1 and ran a windows update today.

Here is an example of a problem. This For...Next statement is supposed to write a sentence 7 times in different sizes. If I load the page in my browser it displays:
> Hello and Welcome!

Here is my code:

<%@dotnet.itags.org.Page Language="VB" Debug="True" %>
<html>
<head>
<title>Hello and Welcome Page</title>
</head>
<body>
<center>
<% Dim TextSize As Integer %>
<% For TextSize = 1 To 7 %>
<font size = <%=TextSize%>>
Hello and Welcome!<br>
</font>
<% Next %>
</center>
</body>
</html

1. run aspnet_regiis.exe
2. make sure you're requesting the page via HTTP and not just from the filesystem.
When I try to run Aspnet_regiis.exe I get an error message:
The application Failed to initialize properly. (0xc0000142)

Wonder if this is my problem?
Oh, I see I have to run that command from a Visual Studio command prompt. I will try that.
aspnet_regiis.exe -i fixed the problem!
Did you tried with -i ?

Troubleshooting ASP.Net memory usage issues?

I'm responsible for a pair of IIS 6 webservers that run our production
ASP.Net application. We push code on a monthly basis, and about two ws
after our October code push, we started to run into occasional webserver
errors.
The application pool is configured to run as a domain user which has
permissions to the web code. When we have issues, the webserver will return
the ASP.Net "Server Application Unavailable" page, and our app pool memory
usage is really high (anywhere from 2 to 4 times our normal usage). Non
asp.net content is served up just fine. If I recycle the application pool
or do an iisreset, memory usage drops back to normal and the site starts
working again.
Nothing is logged to the eventlog or http error log, and the only errors we
see from our application has been the occasional "Exception of type
System.OutOfMemoryException was thrown." The same page doesn't error every
time, and the function I've seen throw exceptions is incredibly generic and
used heavily throughout our entire application (or so our devs have told
me). Our application doesn't even log an error every time this has
happened.
How should I go about troubleshooting this? Our devs are saying it's a
server issue, but I'm leaning towards a code issue. These servers are
running Windows 2003 Server standard, fully updated as of this last wend.What session management are you using. InProc sessions are major memory
consumers.
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
"Daniel Peterson" <pythas@.hotmail.com> wrote in message
news:CB009C9F-B38F-4937-8AF9-256502E90CDE@.microsoft.com...
> I'm responsible for a pair of IIS 6 webservers that run our production
> ASP.Net application. We push code on a monthly basis, and about two ws
> after our October code push, we started to run into occasional webserver
> errors.
> The application pool is configured to run as a domain user which has
> permissions to the web code. When we have issues, the webserver will
> return the ASP.Net "Server Application Unavailable" page, and our app pool
> memory usage is really high (anywhere from 2 to 4 times our normal usage).
> Non asp.net content is served up just fine. If I recycle the application
> pool or do an iisreset, memory usage drops back to normal and the site
> starts working again.
> Nothing is logged to the eventlog or http error log, and the only errors
> we see from our application has been the occasional "Exception of type
> System.OutOfMemoryException was thrown." The same page doesn't error
> every time, and the function I've seen throw exceptions is incredibly
> generic and used heavily throughout our entire application (or so our devs
> have told me). Our application doesn't even log an error every time this
> has happened.
> How should I go about troubleshooting this? Our devs are saying it's a
> server issue, but I'm leaning towards a code issue. These servers are
> running Windows 2003 Server standard, fully updated as of this last
> wend.
Hi Daniel,
It's a code issue. It will be one of 2 possible reasons: 1. Memory Leak.
Yes, .Net applications can leak memory, if they use unmanaged resources that
are not disposed properly. 2. Memory Fragmentation. If the same block of
memory is re-used as, for example, an application-level collection that has
members added and removed over a long period of time, that memory can become
fragmented, necessitating the allocation of more memory to create contiguous
blocks when they are needed.
HTH,
Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP
"Daniel Peterson" <pythas@.hotmail.com> wrote in message
news:CB009C9F-B38F-4937-8AF9-256502E90CDE@.microsoft.com...
> I'm responsible for a pair of IIS 6 webservers that run our production
> ASP.Net application. We push code on a monthly basis, and about two ws
> after our October code push, we started to run into occasional webserver
> errors.
> The application pool is configured to run as a domain user which has
> permissions to the web code. When we have issues, the webserver will
> return the ASP.Net "Server Application Unavailable" page, and our app pool
> memory usage is really high (anywhere from 2 to 4 times our normal usage).
> Non asp.net content is served up just fine. If I recycle the application
> pool or do an iisreset, memory usage drops back to normal and the site
> starts working again.
> Nothing is logged to the eventlog or http error log, and the only errors
> we see from our application has been the occasional "Exception of type
> System.OutOfMemoryException was thrown." The same page doesn't error
> every time, and the function I've seen throw exceptions is incredibly
> generic and used heavily throughout our entire application (or so our devs
> have told me). Our application doesn't even log an error every time this
> has happened.
> How should I go about troubleshooting this? Our devs are saying it's a
> server issue, but I'm leaning towards a code issue. These servers are
> running Windows 2003 Server standard, fully updated as of this last
> wend.
We're using the session state db.
"Eliyahu Goldin" <REMOVEALLCAPITALSeEgGoldDinN@.mMvVpPsS.org> wrote in
message news:e0N$Dc2JIHA.2064@.TK2MSFTNGP06.phx.gbl...
> What session management are you using. InProc sessions are major memory
> consumers.
> --
> Eliyahu Goldin,
> Software Developer
> Microsoft MVP [ASP.NET]
> http://msmvps.com/blogs/egoldin
> http://usableasp.net
>
> "Daniel Peterson" <pythas@.hotmail.com> wrote in message
> news:CB009C9F-B38F-4937-8AF9-256502E90CDE@.microsoft.com...
>
So what's the best route to troubleshoot, just bust out debugdiag and go
from there?
If it's option #2 as you mention below, would cycling the application pool
more frequently solve that? I think we're using the 1740 minute default
right now.
"Kevin Spencer" <unclechutney@.nothinks.com> wrote in message
news:#YiaFK4JIHA.5360@.TK2MSFTNGP03.phx.gbl...
> Hi Daniel,
> It's a code issue. It will be one of 2 possible reasons: 1. Memory Leak.
> Yes, .Net applications can leak memory, if they use unmanaged resources
> that are not disposed properly. 2. Memory Fragmentation. If the same block
> of memory is re-used as, for example, an application-level collection that
> has members added and removed over a long period of time, that memory can
> become fragmented, necessitating the allocation of more memory to create
> contiguous blocks when they are needed.
> --
> HTH,
> Kevin Spencer
> Chicken Salad Surgeon
> Microsoft MVP
> "Daniel Peterson" <pythas@.hotmail.com> wrote in message
> news:CB009C9F-B38F-4937-8AF9-256502E90CDE@.microsoft.com...
>
Hi Daniel,
You could set up some performance counters, but the first thing I think I
would do is look for evidence of the 2 conditions I specified in the code.
It might very well show up rather easily if you know what you're looking
for.
HTH,
Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP
"Daniel Peterson" <pythas@.hotmail.com> wrote in message
news:0323BA74-E5C3-4FEA-9C05-38B520DA602D@.microsoft.com...
> So what's the best route to troubleshoot, just bust out debugdiag and go
> from there?
> If it's option #2 as you mention below, would cycling the application pool
> more frequently solve that? I think we're using the 1740 minute default
> right now.
> "Kevin Spencer" <unclechutney@.nothinks.com> wrote in message
> news:#YiaFK4JIHA.5360@.TK2MSFTNGP03.phx.gbl...
I agree with Kevin, it's a code issue. Too many coders think they don't have
to worry about memory management anymore since "DotNet does it for me!".
Personally, I would start by looking at the Session and/or Application
object. It's likely that some coder decided it would be convenient to stuff
a huge collection of search results (or some such thing) into the session
object and now it's being held there until the session expires.

> You could set up some performance counters, but the first thing I think I
> would do is look for evidence of the 2 conditions I specified in the code.
> It might very well show up rather easily if you know what you're looking
> for.
Another culprit could be IDisposable objects not being disposed. You
doing anything with the graphics object maybe?
Dave Bush
http://blog.dmbcllc.com
--Original Message--
From: Scott Roberts [mailto:sroberts@.no.spam.here-webworks-software.com]
Posted At: Friday, November 16, 2007 9:34 AM
Posted To: microsoft.public.dotnet.framework.aspnet
Conversation: Troubleshooting ASP.Net memory usage issues?
Subject: Re: Troubleshooting ASP.Net memory usage issues?
I agree with Kevin, it's a code issue. Too many coders think they don't
have
to worry about memory management anymore since "DotNet does it for me!".
Personally, I would start by looking at the Session and/or Application
object. It's likely that some coder decided it would be convenient to
stuff
a huge collection of search results (or some such thing) into the
session
object and now it's being held there until the session expires.

> You could set up some performance counters, but the first thing I
think I
> would do is look for evidence of the 2 conditions I specified in the
code.
> It might very well show up rather easily if you know what you're
looking
> for.
Thanks for your help everyone. We found a 3rd party component with
debugdiag that appears to be leaking memory, although our devs seemed to
dismiss that as the issue, and they're still pointing to the servers. If
they don't want to look, I'm not sure how much more I can do.
They think that
http://support.microsoft.com/defaul...268&Product=asp
this is what's going on, although we're not seeing any of those errors or
eventlog messages.
Ugh.
"Scott Roberts" <sroberts@.no.spam.here-webworks-software.com> wrote in
message news:etWOA3FKIHA.5208@.TK2MSFTNGP04.phx.gbl...
> I agree with Kevin, it's a code issue. Too many coders think they don't
> have to worry about memory management anymore since "DotNet does it for
> me!".
> Personally, I would start by looking at the Session and/or Application
> object. It's likely that some coder decided it would be convenient to
> stuff a huge collection of search results (or some such thing) into the
> session object and now it's being held there until the session expires.
>
>
> Thanks for your help everyone. We found a 3rd party component with
> debugdiag that appears to be leaking memory, although our devs seemed to
> dismiss that as the issue, and they're still pointing to the servers. If
> they don't want to look, I'm not sure how much more I can do.
In your original post you mentioned that the problem started after a new
version was published, right? Was this 3rd party component used in the old
version of the site? Was it upgraded for the new version? Does the new
version use some features of this component that were previously unused?

> They think that
> http://support.microsoft.com/defaul...268&Product=asp
> this is what's going on, although we're not seeing any of those errors or
> eventlog messages.
I don't see anything pertaining to large memory usage in that KB. Is it a
memory problem or a thread pool problem?

Troubleshooting ASP.Net memory usage issues?

I'm responsible for a pair of IIS 6 webservers that run our production
ASP.Net application. We push code on a monthly basis, and about two weeks
after our October code push, we started to run into occasional webserver
errors.

The application pool is configured to run as a domain user which has
permissions to the web code. When we have issues, the webserver will return
the ASP.Net "Server Application Unavailable" page, and our app pool memory
usage is really high (anywhere from 2 to 4 times our normal usage). Non
asp.net content is served up just fine. If I recycle the application pool
or do an iisreset, memory usage drops back to normal and the site starts
working again.

Nothing is logged to the eventlog or http error log, and the only errors we
see from our application has been the occasional "Exception of type
System.OutOfMemoryException was thrown." The same page doesn't error every
time, and the function I've seen throw exceptions is incredibly generic and
used heavily throughout our entire application (or so our devs have told
me). Our application doesn't even log an error every time this has
happened.

How should I go about troubleshooting this? Our devs are saying it's a
server issue, but I'm leaning towards a code issue. These servers are
running Windows 2003 Server standard, fully updated as of this last weekend.What session management are you using. InProc sessions are major memory
consumers.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
"Daniel Peterson" <pythas@dotnet.itags.org.hotmail.comwrote in message
news:CB009C9F-B38F-4937-8AF9-256502E90CDE@dotnet.itags.org.microsoft.com...

Quote:

Originally Posted by

I'm responsible for a pair of IIS 6 webservers that run our production
ASP.Net application. We push code on a monthly basis, and about two weeks
after our October code push, we started to run into occasional webserver
errors.
>
The application pool is configured to run as a domain user which has
permissions to the web code. When we have issues, the webserver will
return the ASP.Net "Server Application Unavailable" page, and our app pool
memory usage is really high (anywhere from 2 to 4 times our normal usage).
Non asp.net content is served up just fine. If I recycle the application
pool or do an iisreset, memory usage drops back to normal and the site
starts working again.
>
Nothing is logged to the eventlog or http error log, and the only errors
we see from our application has been the occasional "Exception of type
System.OutOfMemoryException was thrown." The same page doesn't error
every time, and the function I've seen throw exceptions is incredibly
generic and used heavily throughout our entire application (or so our devs
have told me). Our application doesn't even log an error every time this
has happened.
>
How should I go about troubleshooting this? Our devs are saying it's a
server issue, but I'm leaning towards a code issue. These servers are
running Windows 2003 Server standard, fully updated as of this last
weekend.

Hi Daniel,

It's a code issue. It will be one of 2 possible reasons: 1. Memory Leak.
Yes, .Net applications can leak memory, if they use unmanaged resources that
are not disposed properly. 2. Memory Fragmentation. If the same block of
memory is re-used as, for example, an application-level collection that has
members added and removed over a long period of time, that memory can become
fragmented, necessitating the allocation of more memory to create contiguous
blocks when they are needed.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Daniel Peterson" <pythas@dotnet.itags.org.hotmail.comwrote in message
news:CB009C9F-B38F-4937-8AF9-256502E90CDE@dotnet.itags.org.microsoft.com...

Quote:

Originally Posted by

I'm responsible for a pair of IIS 6 webservers that run our production
ASP.Net application. We push code on a monthly basis, and about two weeks
after our October code push, we started to run into occasional webserver
errors.
>
The application pool is configured to run as a domain user which has
permissions to the web code. When we have issues, the webserver will
return the ASP.Net "Server Application Unavailable" page, and our app pool
memory usage is really high (anywhere from 2 to 4 times our normal usage).
Non asp.net content is served up just fine. If I recycle the application
pool or do an iisreset, memory usage drops back to normal and the site
starts working again.
>
Nothing is logged to the eventlog or http error log, and the only errors
we see from our application has been the occasional "Exception of type
System.OutOfMemoryException was thrown." The same page doesn't error
every time, and the function I've seen throw exceptions is incredibly
generic and used heavily throughout our entire application (or so our devs
have told me). Our application doesn't even log an error every time this
has happened.
>
How should I go about troubleshooting this? Our devs are saying it's a
server issue, but I'm leaning towards a code issue. These servers are
running Windows 2003 Server standard, fully updated as of this last
weekend.

We're using the session state db.

"Eliyahu Goldin" <REMOVEALLCAPITALSeEgGoldDinN@dotnet.itags.org.mMvVpPsS.orgwrote in
message news:e0N$Dc2JIHA.2064@dotnet.itags.org.TK2MSFTNGP06.phx.gbl...

Quote:

Originally Posted by

What session management are you using. InProc sessions are major memory
consumers.
>
--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
>
>
"Daniel Peterson" <pythas@dotnet.itags.org.hotmail.comwrote in message
news:CB009C9F-B38F-4937-8AF9-256502E90CDE@dotnet.itags.org.microsoft.com...

Quote:

Originally Posted by

>I'm responsible for a pair of IIS 6 webservers that run our production
>ASP.Net application. We push code on a monthly basis, and about two
>weeks after our October code push, we started to run into occasional
>webserver errors.
>>
>The application pool is configured to run as a domain user which has
>permissions to the web code. When we have issues, the webserver will
>return the ASP.Net "Server Application Unavailable" page, and our app
>pool memory usage is really high (anywhere from 2 to 4 times our normal
>usage). Non asp.net content is served up just fine. If I recycle the
>application pool or do an iisreset, memory usage drops back to normal and
>the site starts working again.
>>
>Nothing is logged to the eventlog or http error log, and the only errors
>we see from our application has been the occasional "Exception of type
>System.OutOfMemoryException was thrown." The same page doesn't error
>every time, and the function I've seen throw exceptions is incredibly
>generic and used heavily throughout our entire application (or so our
>devs have told me). Our application doesn't even log an error every time
>this has happened.
>>
>How should I go about troubleshooting this? Our devs are saying it's a
>server issue, but I'm leaning towards a code issue. These servers are
>running Windows 2003 Server standard, fully updated as of this last
>weekend.

>
>

So what's the best route to troubleshoot, just bust out debugdiag and go
from there?

If it's option #2 as you mention below, would cycling the application pool
more frequently solve that? I think we're using the 1740 minute default
right now.

"Kevin Spencer" <unclechutney@dotnet.itags.org.nothinks.comwrote in message
news:#YiaFK4JIHA.5360@dotnet.itags.org.TK2MSFTNGP03.phx.gbl...

Quote:

Originally Posted by

Hi Daniel,
>
It's a code issue. It will be one of 2 possible reasons: 1. Memory Leak.
Yes, .Net applications can leak memory, if they use unmanaged resources
that are not disposed properly. 2. Memory Fragmentation. If the same block
of memory is re-used as, for example, an application-level collection that
has members added and removed over a long period of time, that memory can
become fragmented, necessitating the allocation of more memory to create
contiguous blocks when they are needed.
>
--
HTH,
>
Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP
>
"Daniel Peterson" <pythas@dotnet.itags.org.hotmail.comwrote in message
news:CB009C9F-B38F-4937-8AF9-256502E90CDE@dotnet.itags.org.microsoft.com...

Quote:

Originally Posted by

>I'm responsible for a pair of IIS 6 webservers that run our production
>ASP.Net application. We push code on a monthly basis, and about two
>weeks after our October code push, we started to run into occasional
>webserver errors.
>>
>The application pool is configured to run as a domain user which has
>permissions to the web code. When we have issues, the webserver will
>return the ASP.Net "Server Application Unavailable" page, and our app
>pool memory usage is really high (anywhere from 2 to 4 times our normal
>usage). Non asp.net content is served up just fine. If I recycle the
>application pool or do an iisreset, memory usage drops back to normal and
>the site starts working again.
>>
>Nothing is logged to the eventlog or http error log, and the only errors
>we see from our application has been the occasional "Exception of type
>System.OutOfMemoryException was thrown." The same page doesn't error
>every time, and the function I've seen throw exceptions is incredibly
>generic and used heavily throughout our entire application (or so our
>devs have told me). Our application doesn't even log an error every time
>this has happened.
>>
>How should I go about troubleshooting this? Our devs are saying it's a
>server issue, but I'm leaning towards a code issue. These servers are
>running Windows 2003 Server standard, fully updated as of this last
>weekend.

>
>

Hi Daniel,

You could set up some performance counters, but the first thing I think I
would do is look for evidence of the 2 conditions I specified in the code.
It might very well show up rather easily if you know what you're looking
for.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Daniel Peterson" <pythas@dotnet.itags.org.hotmail.comwrote in message
news:0323BA74-E5C3-4FEA-9C05-38B520DA602D@dotnet.itags.org.microsoft.com...

Quote:

Originally Posted by

So what's the best route to troubleshoot, just bust out debugdiag and go
from there?
>
If it's option #2 as you mention below, would cycling the application pool
more frequently solve that? I think we're using the 1740 minute default
right now.
>
"Kevin Spencer" <unclechutney@dotnet.itags.org.nothinks.comwrote in message
news:#YiaFK4JIHA.5360@dotnet.itags.org.TK2MSFTNGP03.phx.gbl...

Quote:

Originally Posted by

>Hi Daniel,
>>
>It's a code issue. It will be one of 2 possible reasons: 1. Memory Leak.
>Yes, .Net applications can leak memory, if they use unmanaged resources
>that are not disposed properly. 2. Memory Fragmentation. If the same
>block of memory is re-used as, for example, an application-level
>collection that has members added and removed over a long period of time,
>that memory can become fragmented, necessitating the allocation of more
>memory to create contiguous blocks when they are needed.
>>
>--
>HTH,
>>
>Kevin Spencer
>Chicken Salad Surgeon
>Microsoft MVP
>>
>"Daniel Peterson" <pythas@dotnet.itags.org.hotmail.comwrote in message
>news:CB009C9F-B38F-4937-8AF9-256502E90CDE@dotnet.itags.org.microsoft.com...

Quote:

Originally Posted by

>>I'm responsible for a pair of IIS 6 webservers that run our production
>>ASP.Net application. We push code on a monthly basis, and about two
>>weeks after our October code push, we started to run into occasional
>>webserver errors.
>>>
>>The application pool is configured to run as a domain user which has
>>permissions to the web code. When we have issues, the webserver will
>>return the ASP.Net "Server Application Unavailable" page, and our app
>>pool memory usage is really high (anywhere from 2 to 4 times our normal
>>usage). Non asp.net content is served up just fine. If I recycle the
>>application pool or do an iisreset, memory usage drops back to normal
>>and the site starts working again.
>>>
>>Nothing is logged to the eventlog or http error log, and the only errors
>>we see from our application has been the occasional "Exception of type
>>System.OutOfMemoryException was thrown." The same page doesn't error
>>every time, and the function I've seen throw exceptions is incredibly
>>generic and used heavily throughout our entire application (or so our
>>devs have told me). Our application doesn't even log an error every
>>time this has happened.
>>>
>>How should I go about troubleshooting this? Our devs are saying it's a
>>server issue, but I'm leaning towards a code issue. These servers are
>>running Windows 2003 Server standard, fully updated as of this last
>>weekend.

>>
>>

I agree with Kevin, it's a code issue. Too many coders think they don't have
to worry about memory management anymore since "DotNet does it for me!".

Personally, I would start by looking at the Session and/or Application
object. It's likely that some coder decided it would be convenient to stuff
a huge collection of search results (or some such thing) into the session
object and now it's being held there until the session expires.

Quote:

Originally Posted by

You could set up some performance counters, but the first thing I think I
would do is look for evidence of the 2 conditions I specified in the code.
It might very well show up rather easily if you know what you're looking
for.

Another culprit could be IDisposable objects not being disposed. You
doing anything with the graphics object maybe?

Dave Bush
http://blog.dmbcllc.com
--Original Message--
From: Scott Roberts [mailto:sroberts@dotnet.itags.org.no.spam.here-webworks-software.com]

Posted At: Friday, November 16, 2007 9:34 AM
Posted To: microsoft.public.dotnet.framework.aspnet
Conversation: Troubleshooting ASP.Net memory usage issues?
Subject: Re: Troubleshooting ASP.Net memory usage issues?

I agree with Kevin, it's a code issue. Too many coders think they don't
have
to worry about memory management anymore since "DotNet does it for me!".

Personally, I would start by looking at the Session and/or Application
object. It's likely that some coder decided it would be convenient to
stuff
a huge collection of search results (or some such thing) into the
session
object and now it's being held there until the session expires.

Quote:

Originally Posted by

You could set up some performance counters, but the first thing I

think I

Quote:

Originally Posted by

would do is look for evidence of the 2 conditions I specified in the

code.

Quote:

Originally Posted by

It might very well show up rather easily if you know what you're

looking

Quote:

Originally Posted by

for.

Thanks for your help everyone. We found a 3rd party component with
debugdiag that appears to be leaking memory, although our devs seemed to
dismiss that as the issue, and they're still pointing to the servers. If
they don't want to look, I'm not sure how much more I can do.

They think that
http://support.microsoft.com/defaul...268&Product=asp
this is what's going on, although we're not seeing any of those errors or
eventlog messages.

Ugh.

"Scott Roberts" <sroberts@dotnet.itags.org.no.spam.here-webworks-software.comwrote in
message news:etWOA3FKIHA.5208@dotnet.itags.org.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

I agree with Kevin, it's a code issue. Too many coders think they don't
have to worry about memory management anymore since "DotNet does it for
me!".
>
Personally, I would start by looking at the Session and/or Application
object. It's likely that some coder decided it would be convenient to
stuff a huge collection of search results (or some such thing) into the
session object and now it's being held there until the session expires.
>

Quote:

Originally Posted by

>You could set up some performance counters, but the first thing I think I
>would do is look for evidence of the 2 conditions I specified in the
>code. It might very well show up rather easily if you know what you're
>looking for.

>

Thanks for your help everyone. We found a 3rd party component with

Quote:

Originally Posted by

debugdiag that appears to be leaking memory, although our devs seemed to
dismiss that as the issue, and they're still pointing to the servers. If
they don't want to look, I'm not sure how much more I can do.

In your original post you mentioned that the problem started after a new
version was published, right? Was this 3rd party component used in the old
version of the site? Was it upgraded for the new version? Does the new
version use some features of this component that were previously unused?

Quote:

Originally Posted by

They think that
http://support.microsoft.com/defaul...268&Product=asp
this is what's going on, although we're not seeing any of those errors or
eventlog messages.

I don't see anything pertaining to large memory usage in that KB. Is it a
memory problem or a thread pool problem?
To answer your questions:

1. Yes, we noticed the issues about 2 weeks after a release. The 3rd party
component was updated in that release, I don't think we're using any new
features, but I'll check.

2. I don't see anything in that KB article that describes the symptoms
we're seeing either. We're not getting any of the error messages that would
suggest a thread pool issue, I'm not quite sure how they ended up at that kb
article.

"Scott Roberts" <sroberts@dotnet.itags.org.no.spam.here-webworks-software.comwrote in
message news:O1RhfZ5KIHA.4688@dotnet.itags.org.TK2MSFTNGP06.phx.gbl...

Quote:

Originally Posted by

Quote:

Originally Posted by

>Thanks for your help everyone. We found a 3rd party component with
>debugdiag that appears to be leaking memory, although our devs seemed to
>dismiss that as the issue, and they're still pointing to the servers. If
>they don't want to look, I'm not sure how much more I can do.

>
In your original post you mentioned that the problem started after a new
version was published, right? Was this 3rd party component used in the old
version of the site? Was it upgraded for the new version? Does the new
version use some features of this component that were previously unused?
>

Quote:

Originally Posted by

>They think that
>http://support.microsoft.com/defaul...268&Product=asp
>this is what's going on, although we're not seeing any of those errors or
>eventlog messages.

>
I don't see anything pertaining to large memory usage in that KB. Is it a
memory problem or a thread pool problem?

Troubleshooting IIS "Hang" / Postback Not Working

I have recently added some code to a web application and now I find it
hanging after I do about 2 or 3 postbacks within the application. It hangs
after
doing different things (I cannot find anything in common) and when I run in
Debug mode, it doesn't even appear to be within my code when it hangs (I put
breakpoints all over the place and it doesn't stop at any of them during the
hang).
It hangs after I click a button on the page... but it never reaches the
Page_Load event of the page it is posting back to.. it is like the PostBack
isn't working.
How do I figure out what is going on? What really confuses me is the fact
that the code works the first time but not the second time I run it.. even
with the exact same input data...
It does seem to be related to uploading images... so I went through my code
and made sure I was disposing of all of the image objects in Finally
statements.
Any thoughts on how I can find the problem?
I have ANTS profiler by Red Gate software and I tried doing a memory profile
but it didn't seem to get me anywhere (either that or I wasn't doing it
right).
It is not causing IIS to crash... just to "spin" for a long time. This is
on my development Win XP Pro machine.
After quite some time, I get the following errors when I debug... but I
think they are more a symptom of the non-response to the application as
opposed to the cause of my problem.
--
A first chance exception of type 'System.Net.Sockets.SocketException'
occurred in system.dll
Additional information: An existing connection was forcibly closed by the
remote host
A first chance exception of type 'System.IO.IOException' occurred in
system.dll
Additional information: Unable to read data from the transport connection.
LoriHi Lori ,
Welcome to ASP.NET newsgroup.
From your description, one of your asp.net always run into hanging after
you do some modification recently. I'm not quite sure what's your orginally
code logic and what's your modification on them. However, have you been
able to isolate the problem to a certain or some certain individule pages?
Also, based on your error message, I think you're doing some network
transfering task , using Socket or httpwebrequest? Generally, if your
server's CPU utilization is not high and application hangs, it's likely
that there are some thread deadlock in your app or there are some longrun
task in your page's exectution steps which block the server's workthreads.
Would provide some further description on your code logic?
In addition, I suggest you turn on the ASP.NET's trace and use Trace.Write
or Warn to output some trace info in the different stage of those page's
execution lifecycle. For example, before page_load and after Page_Load or
before a method call and after a method call. Then, we can use the
application's trace.axd to view which stage consumes most of the times.
If there are any further findings, please feel free to post here also. Good
Luck!
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Troubleshooting IIS "Hang" / Postback Not Working

I have recently added some code to a web application and now I find it
hanging after I do about 2 or 3 postbacks within the application. It hangs
after
doing different things (I cannot find anything in common) and when I run in
Debug mode, it doesn't even appear to be within my code when it hangs (I put
breakpoints all over the place and it doesn't stop at any of them during the
hang).

It hangs after I click a button on the page... but it never reaches the
Page_Load event of the page it is posting back to.. it is like the PostBack
isn't working.

How do I figure out what is going on? What really confuses me is the fact
that the code works the first time but not the second time I run it.. even
with the exact same input data...

It does seem to be related to uploading images... so I went through my code
and made sure I was disposing of all of the image objects in Finally
statements.

Any thoughts on how I can find the problem?

I have ANTS profiler by Red Gate software and I tried doing a memory profile
but it didn't seem to get me anywhere (either that or I wasn't doing it
right).

It is not causing IIS to crash... just to "spin" for a long time. This is
on my development Win XP Pro machine.

After quite some time, I get the following errors when I debug... but I
think they are more a symptom of the non-response to the application as
opposed to the cause of my problem.
-----------
A first chance exception of type 'System.Net.Sockets.SocketException'
occurred in system.dll

Additional information: An existing connection was forcibly closed by the
remote host

A first chance exception of type 'System.IO.IOException' occurred in
system.dll

Additional information: Unable to read data from the transport connection.

LoriHi Lori ,

Welcome to ASP.NET newsgroup.
From your description, one of your asp.net always run into hanging after
you do some modification recently. I'm not quite sure what's your orginally
code logic and what's your modification on them. However, have you been
able to isolate the problem to a certain or some certain individule pages?

Also, based on your error message, I think you're doing some network
transfering task , using Socket or httpwebrequest? Generally, if your
server's CPU utilization is not high and application hangs, it's likely
that there are some thread deadlock in your app or there are some longrun
task in your page's exectution steps which block the server's workthreads.
Would provide some further description on your code logic?

In addition, I suggest you turn on the ASP.NET's trace and use Trace.Write
or Warn to output some trace info in the different stage of those page's
execution lifecycle. For example, before page_load and after Page_Load or
before a method call and after a method call. Then, we can use the
application's trace.axd to view which stage consumes most of the times.

If there are any further findings, please feel free to post here also. Good
Luck!

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

troubleshooting markup SQLDataSource with a bunch of session variables?

I've got a page with Formview that has a sqldatasource doing a
compicated select with a bunch of session parameter variables set in a
calling page.
1. Is there anyway to response.write all session variables without
having to specify each one?
2. How can I see the actual SQL that is being passed to the Formview?
I've tried
response.write(ChargeDataSource.SelectCommand.ToString()) but that just
what I set originally.
Thanks.For (1):
foreach (string o in Session.Keys)
{
Response.Write (o + ": " + Session[o] + "<br/>");
}
"jobs" <jobs@.webdos.com> wrote in message
news:1161382144.231799.326450@.b28g2000cwb.googlegroups.com...
I've got a page with Formview that has a sqldatasource doing a
compicated select with a bunch of session parameter variables set in a
calling page.
1. Is there anyway to response.write all session variables without
having to specify each one?
2. How can I see the actual SQL that is being passed to the Formview?
I've tried
response.write(ChargeDataSource.SelectCommand.ToString()) but that just
what I set originally.
Thanks.

troubleshooting markup SQLDataSource with a bunch of session variables?

I've got a page with Formview that has a sqldatasource doing a
compicated select with a bunch of session parameter variables set in a
calling page.

1. Is there anyway to response.write all session variables without
having to specify each one?
2. How can I see the actual SQL that is being passed to the Formview?
I've tried
response.write(ChargeDataSource.SelectCommand.ToSt ring()) but that just
what I set originally.

Thanks.For (1):
foreach (string o in Session.Keys)
{
Response.Write (o + ": " + Session[o] + "<br/>");
}

"jobs" <jobs@.webdos.comwrote in message
news:1161382144.231799.326450@.b28g2000cwb.googlegr oups.com...
I've got a page with Formview that has a sqldatasource doing a
compicated select with a bunch of session parameter variables set in a
calling page.

1. Is there anyway to response.write all session variables without
having to specify each one?
2. How can I see the actual SQL that is being passed to the Formview?
I've tried
response.write(ChargeDataSource.SelectCommand.ToSt ring()) but that just
what I set originally.

Thanks.