« Previous Next »

Thread: Problems with NETWORK SERVICE and slow AppPool Startup

Last post 07-19-2009 8:56 PM by steve schofield. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

  • 07-19-2009, 7:04 PM

    • rstrahl
    • Top 150 Contributor
    • Joined on 08-20-2003, 1:08 PM
    • Paia, Hawaii
    • Posts 45

    Problems with NETWORK SERVICE and slow AppPool Startup

    I've run into a problem with my development machine where application startup will take 90-120 seconds. It doesn't matter whether the page accessed is a static HTML page or dynamic ASPX content.

    This problem started recently - I'm guessing after installation of .NET 4.0 and VS 2010 but I'm not certain - and appears to be related to the NETWORK SERVICE account. I'm running on Vista SP1 and when using NETWORK SERVICE as the account any application on the server starts slow.

    If I switch to another account (Local System or ApplicationPoolIdentity) the same application will start fast (3-5 seconds startup time) which is normal.

    I've checked permissions on the application folder for NETWORK SERVICE (full rights) and also on the Temporary ASP.NET folder in the .NET framework folder. All that seems fine. Yet if I run under NETWORK SERVICE any startup is dog slow. Any other account it's fine.

    What else I did:

    * I ran through ProcMon to check for errors - nothing jumps out beyond normal probing

    It also appears that my live site (running Server 2008) has the same issue and it's also started just recently. Very sure this is a recent occurrence with everything having worked properly very recently.

    Any idea what else I can check on?

    +++ Rick ---


     
    Rick Strahl [MVP]
    West Wind Technologies
    Making waves on the Web
    www.west-wind.com/weblog
  • 07-19-2009, 8:56 PM In reply to

    Re: Problems with NETWORK SERVICE and slow AppPool Startup

    The network service is 'really' the machine account under the covers.  Is there a DNS issue where it can't authenticate to a domain controller(s)?  I'd not recommend you run it under network service anyway vs. a custom account or ApplicationPoolIdentity.   It's more secure. 

    Let me add

    Check to see if both DC's that are configured for DNS resolution are up and available. 

    Make sure your primary NIC is listed at the top vs. a loopback adapter.  (do this inside network connections, advanced, bindings). 

    Is windows firewall enabled somewhere preventing communication to a DC?

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
Page 1 of 1 (2 items)
Microsoft Communities