System.Runtime.InteropServices.SEHException in WebDev.WebServer.ex

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • =?Utf-8?B?VGhvbWFzIFR1dGtv?=

    System.Runtime.InteropServices.SEHException in WebDev.WebServer.ex

    An ASP.NET web project has recently began crashing WebDev.WebServe r.exe with
    a System.Runtime. InteropServices .SEHException. The EventLog for the crash
    looks like this:

    Application ID: WebDev.WebServe r.EXE

    Process ID: 1552

    Exception: System.Runtime. InteropServices .SEHException

    Message: External component has thrown an exception.

    StackTrace: at
    Microsoft.Visua lStudio.WebHost .Host.ProcessRe quest(Connectio n conn)
    at Microsoft.Visua lStudio.WebHost .Server.OnSocke tAccept(Object
    acceptedSocket)
    at System.Threadin g._ThreadPoolWa itCallback.Wait Callback_Contex t(Object
    state)
    at System.Threadin g.ExecutionCont ext.Run(Executi onContext
    executionContex t, ContextCallback callback, Object state)
    at
    System.Threadin g._ThreadPoolWa itCallback.Perf ormWaitCallback Internal(_Threa dPoolWaitCallba ck tpWaitCallBack)
    at System.Threadin g._ThreadPoolWa itCallback.Perf ormWaitCallback (Object
    state)

    This occurs if I launch the site from VS2005 or VS2008. It works fine on
    other machines and when hosted in IIS but this is driving me crazy trying to
    figure out why it won't run in the Development web host that is part of VS on
    my machine. This site used to work in the current problem environment and I
    do not recall any major changes. The box is a Vista SP1 box running both VS
    2005 Team Suite and VS 2008 Team Suite. I have messed around with the windows
    debugging tools and using adplus have created crash dumps but I haven't been
    able to gather anything from them as I am a complete beginner when it comes
    to analyzing crash dumps. Is anyone willing to look at the crash dumps or
    have any suggestions? Please note that when I create a new web project and
    launch that, it works fine.

    Thanks for any help, this has been driving me crazy for the past 2 days
    staring at crash dumps and trying to figure this out.
Working...