locked
Unhandled exception has occurred RRS feed

  • Question

  • User-18758192 posted

    Sporadic crash led to impacting some web functionality on my web/app server following the below event in the AppLog.  Any insight on how I can go about finding some root cause of this exception event?  Running IIS v8.5 on Windows Server 2012 R2.

    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 5/20/2019 12:10:36 PM
    Event time (UTC): 5/20/2019 4:10:36 PM
    Event ID: 810a23d2614b471c810a938c505a181a
    Event sequence: 34
    Event occurrence: 1
    Event detail code: 0

    Application information:
    Application domain: /LM/W3SVC/1/ROOT-8-132028422366972836
    Trust level: Full
    Application Virtual Path: /
    Application Path: C:\inetpub\wwwroot\
    Machine name: <hostname>

    Process information:
    Process ID: 2940
    Process name: w3wp.exe
    Account name: IIS APPPOOL\DefaultAppPool

    Exception information:
    Exception type: HttpException
    Exception message: External component has thrown an exception.
    at System.Web.Handlers.TraceHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
    at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)



    Request information:
    Request URL: http://<IP_address>/trace.axd
    Request path: /trace.axd
    User host address: <IP_address>
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: IIS APPPOOL\DefaultAppPool

    Thread information:
    Thread ID: 43
    Thread account name: IIS APPPOOL\DefaultAppPool
    Is impersonating: False
    Stack trace: at System.Web.Handlers.TraceHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
    at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


    Custom event details:

    Monday, May 20, 2019 5:40 PM

All replies

  • User-2114649853 posted

    Hi khallowe,

    Custom event details:

    According to your code, it seems that error details is not complete,I hope that you could share the details of custom event details ,it will help us to find which error you met and help us to solve it. 

    Best Regards

    Able

    Tuesday, May 21, 2019 2:58 AM
  • User-18758192 posted

    Here was the follow-up AppLog error:

    Log Name:      Application

    Source:        Application Error

    Date:          5/20/2019 12:11:33 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      PrivateWeb4.l1office.local

    Description:

    Faulting application name: svchost.exe, version: 6.3.9600.17415, time stamp: 0x54504177

    Faulting module name: ntdll.dll, version: 6.3.9600.18969, time stamp: 0x5aa29ff0

    Exception code: 0xc0000409

    Fault offset: 0x00000000000816e8

    Faulting process id: 0x394

    Faulting application start time: 0x01d50f0454337327

    Faulting application path: C:\Windows\system32\svchost.exe

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: ef1e51e0-7b19-11e9-80e2-0050568e1c1c

    Faulting package full name:

    Faulting package-relative application ID:

    Not exactly sure which code you wish to see.

    Thanks.

    Tuesday, May 21, 2019 3:34 PM
  • User-2114649853 posted

    Hi khallowell,

    According to your description, could you please tell me which type of application pool you are using?Classic or integrated.If your mode is integrated ,change it to classic.You could see as below:

    Best Regards

    Able

    Wednesday, May 22, 2019 9:35 AM
  • User-18758192 posted

    Thanks for your feedback, much appreciated.  But, why would I wish to change the app pool mode back to classic mimicking IIS6 and below, and it's duplication of authentication/authorization?  What other scenarios would dictate moving back to Classic mode?  Our application works, but this one anomaly that occurred in the middle of the day broke a process call to an external source to present a PDF file from history.  How would Classic mode help versus the Integrated mode?

    Thanks!

    Wednesday, May 22, 2019 11:54 AM
  • User-2114649853 posted

    Hi khallowell,

    So ,have it solved your problem? Firstly,for iis classic and Integrated mode,you could see the links as below:

    https://stackoverflow.com/questions/716049/what-is-the-difference-between-classic-and-integrated-pipeline-mode-in-iis7

    Then if you use classic mode,it will set asp.net or other tools processed as a separate module.I doubt that the application is compatible with the integration mode. You should only add an application to an application pool in Classic mode if the application fails to work in Integrated mode.

    Since I still couldn't see the error details,if you still has problem. I hope that you could use FRT to get logs of error.

    Here is the link, I hope it could help you.

    https://docs.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis

    Best Regards

    Able

    Thursday, May 23, 2019 9:00 AM