« Previous Next »

Thread: Application pool 'webhosting(client)(2.0)(pool)' is being automatically disabled.

Last post 03-13-2009 6:14 PM by fabioy. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

  • 01-26-2009, 1:52 AM

    Application pool 'webhosting(client)(2.0)(pool)' is being automatically disabled.

    Hi.

     Dear Friends

    We have found 'service unavaliable' error on few asp based websites after check evet viewer we found following error,

    Application pool 'webhosting(client)(2.0)(pool)' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

     

    After detailed we found few error's of Evet ID: 1310

     

    Event code: 3008

    Event message: A configuration error has occurred.

    Event time: 1/24/2009 8:00:10 PM

    Event time (UTC): 1/24/2009 3:00:10 PM

    Event ID: 2906c38b77a7487790395fda36ea9e3d

    Event sequence: 8

    Event occurrence: 7

    Event detail code: 0

     

    Application information:

    Application domain: /LM/W3SVC/11854/Root-2-128772817301718750

    Trust level: Full

    Application Virtual Path: /

    Application Path: C:\Inetpub\\hum.tv\httpdocs\

    Machine name: SERVER

     

    Process information:

    Process ID: 3232

    Process name: w3wp.exe

    Account name: SERVER\IWPC_2(webhosting)

     

    Exception information:

    Exception type: ConfigurationErrorsException

    Exception message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\Inetpub\vhosts\hum.tv\httpdocs\careers\web.config line 42)

     

    Request information:

    Request URL: http://www.hum.tv/careers/careers.aspx

    Request path: /careers/careers.aspx

    User host address: 116.71.30.37

    User:

    Is authenticated: False

    Authentication Type:

    Thread account name: SERVER\IWPC_2(webhosting)

     

    Thread information:

    Thread ID: 7

    Thread account name: SERVER\IWPC_2(webhosting)

    Is impersonating: False

    Stack trace: at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)

    at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)

    at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)

    at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)

    at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)

    at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)

    at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)

    at System.Web.Configuration.RuntimeConfig.get_Identity()

    at System.Web.HttpContext.get_ImpersonationToken()

    at System.Web.ClientImpersonationContext.Start(HttpContext context, Boolean throwOnError)

    at System.Web.HttpApplication.ThreadContext.Enter(Boolean setImpersonationContext)

    at System.Web.HttpApplication.OnThreadEnterPrivate(Boolean setImpersonationContext)

    at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)

     

     

     

  • 03-13-2009, 6:14 PM In reply to

    • fabioy
    • Top 500 Contributor
    • Joined on 05-06-2008, 11:04 PM
    • Posts 17

    Re: Application pool 'webhosting(client)(2.0)(pool)' is being automatically disabled.

    There are a couple of ways to solve the problem:

    1. If the ASP.Net application expects to be running under an application node, then go to the IIS MMC and mark the virtual directory as an "Application" directory and ASP.Nets should be happy again.  This is especially important if the app contains a "global.asax" file, since those can only be at an application directory.
    2. If you don't need an app directory, then you can either remove the offending config section from the web.config file; or alternatively, go to the root web.config (or machine.config) and change the "allowDefinition" property to "Everywhere" (note some configuration sections don't work properly if below an app level).

    Hope this helps.

    -- Fabio Yeon
    Senior Software Design Engineer
    IIS
Page 1 of 1 (2 items)
Microsoft Communities