Link to home
Start Free TrialLog in
Avatar of bmilli
bmilli

asked on

Running ASP.Net in VS 2008 - get Error: WebDev.WebServer.exe has encountered a problem and needs to close.

I recently installed Visual Studio 2008 Standard Edition (that I received free from the "Heroes happen here" event) on a machine that already had Visual Studio 2005 Professional edition.  The OS is XP Pro.  The installation appeared to finish without errors.  When I created a "Hello World" website and hit F5, it built just fine, but fails after that with the error:
WebDev.WebServer.exe has encountered a problem and needs to close.  

I verified that I can still run web apps in the older version of Visual Studio 2005.  I verified I can run windows applications in the newer 2008 version.

My coworker has the same setup (Visual Studio 2005 Pro and Visual Studio 2008 Standard).  He is able to run web apps under both versions.  

Thanks for any help you can provide.
Avatar of Bob Learned
Bob Learned
Flag of United States of America image

Is there anything in the Event Log that would indicate a reason?  I wonder if there are any logs that would help explain?  I haven't seen this error specifically, so finding a solution may prove to be pretty impossible.
Avatar of bmilli
bmilli

ASKER

TheLearnedOne,
Thanks for the response.  I do indeed get three Application errors as follows:

1. Source: Microsoft Visual Studio
Faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module vsdebug.dll, version 9.0.21022.8, stamp 47317c84, debug? 0, fault address 0x0013d402.

2. Source: .NET Runtime
.NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (7A06491A) (0)

3. Source: .NET Runtime 2.0 Error Reporting
Faulting application webdev.webserver.exe, version 9.0.21022.8, stamp 4731664b, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x001f491a.


I will look for other logs and investigate the two dll's referenced above.  Do these errors ring any bells with you?

Thanks
Those appear to be configuration problems that usually don't occur, which would explain why someone else could have the same setup and not have the problem.  Unfortunately, these are difficult to find, since the sky is the limit, and reference material is scarce.
Avatar of bmilli

ASKER

Thanks very much for your comments.  I am not suprised by your answer.   I figured it was obscure and my only hope was to find someone who had the exact same problem and figured it out.

I am new to the Experts Exchange.  Though the problem was not solved, your answers were helpful.  Would it be normal/acceptable to click on "Accept as Solution" and give partial/full credit at this point?
That comment was meant to say that it would be difficult to find, but not necessarily impossible.  If you still need help to find a resolution, I am willing to help point you in the right direction.
Avatar of bmilli

ASKER

I appreciate that.  I have not given up yet.  

Besides looking for other log files, I was thinking about looking for differences between my machine and my coworkers machine (the successful install).  I suppose I would start looking for differences with the files mentioned in the errors.  If you have other ideas, I am listening and will do my best to check them out.
What is your environment like?

1) Windows XP Professional SP2?

2) Visual Studio.NET 2005 Professional SP1?

3) 2008 is not a Beta, right?
Avatar of bmilli

ASKER


1) Windows XP Professional SP2?
  Correct

2) Visual Studio.NET 2005 Professional SP1?
  Correct???
  Microsoft Visual Studio 2005 - Version 8.0.50727.762 (SP .050727-7600)
  Microsoft .NET Framework - Version 2.0.50727 SP1

3) 2008 is not a Beta, right?
  Correct
What is the setting for:

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

2) HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings\JITDebug

3) Tools | Options | Debugging | Just-In-time
Avatar of bmilli

ASKER

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
"C:\WINDOWS\system32\vsjitdebugger.exe" -p %ld -e %ld

2) HKEY_CURRENT_USER\Software\Microsoft\Windows Script\Settings\JITDebug
0

3) Tools | Options | Debugging | Just-In-time
Managed, Native, and Script are all checked.


Try repairing the install for Visual Studio.NET 2005.
4) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgJITDebugLaunchSetting

5) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
Avatar of bmilli

ASKER

In case I did not mention it earlier, 2005 works just fine, but if you think it will help, I will give it a try.  

A quick question.  I installed VS 2008, using the same product key, on my home machine several months ago.  I installed my personal copy at work while waiting for the paperwork to go through for the 2008 licenses.  I suppose I could uninstall from my home machine until we get the licenses at work.  I would think if there was a licensing issue it would surface in a different way.  Do you think this might be related?

Try repairing the install for Visual Studio.NET 2008--don't think that they are related.
Avatar of bmilli

ASKER

Sorry for the delay, I was stuck in meetings all afternoon.

4) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgJITDebugLaunchSetting
10
5) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
"C:\WINDOWS\system32\vsjitdebugger.exe" PID %d APPDOM %d EXTEXT "%s" EVTHDL %d

I tried uninstalling and reinstalling a few days ago.  No difference.
I just tried the repair option this morning.  No difference.

Regarding the license issue that we both suspected was not related...I verified it was not a problem by installing 2008 on my old work machine using the same product key.  I am able to run a website on the old machine.

Thanks  
Sorry, that was my brain going down the wrong track.  The JIT debugger is only for your code, not a system problem.

Avatar of bmilli

ASKER

No problem.  Thanks for your ideas.
One thing that occurred to me...
On my old machine, when I inherited it, it had VB6 installed on it.  I installed VS 2005...then VS 2008.
On the new machine, when I inherited it, it had VS 2005 installed on it.  I installed VB6....then VS 2008.
I doubt it has anything to do with it, but maybe installing VB6 after VS2005 is causing me grief.
I suppose I could try to repair VS 2005, and then repair VS 2008.  Not sure what else to try.
Thanks again for your time,
bmilli
Do you have IIS installed on the local machine?
Avatar of bmilli

ASKER

I think the answer is No.  At least, not the full blown IIS.
I am running on Windows XP Pro.  Under Administrative Tools, there is an Internet Information Services icon, but when I run it, I see the WebSites folder and I cannot add any websites beyond the existing Default Web Site.

When I run websites in VS 2005, I get that ASP.Net Development Server icon in my tray.

Does that answer your question?
Yes, in a roundabout way you did.  You have the full-blown IIS 5.1 installed on your Windows XP machine.  You might want to see if you can create an IIS web site, and see if you have the same problems with the debugger.
Avatar of bmilli

ASKER


I was not sure exactly what you meant.  This is what I did:

I loaded VS 2008 and chose Create Website.
For Location, I chose HTTP
Clicked on Browse
Clicked on the root folder
Clicked on Create New Web Application
Clicked on OK  
Opened Default.aspx
Type Hello World.
Hit F5.

I was prompted to enable debugging.  Leaving "Modify the Web.Config file to enable debugging." selected I hit OK.
I actually get a slightly different behavior with this type of website.  

I see the "Microsoft Visual Studio has encountered a problem and needs to close" error.
I look at the Application Log and see one error:
  Faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module vsdebug.dll, version 9.0.21022.8, stamp 47317c84, debug? 0, fault address 0x0013d402.

I uncheck "Restart Microsoft Visual Studio" and I click on "Send Error Report".
I briefly see a window indicating it is sending the information, then it goes away.

Looking at the application log, I see 1 info and 2 error messages
  The info message: Bucket 568751753, bucket table 1, faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module vsdebug.dll, version 9.0.21022.8, stamp 47317c84, debug? 0, fault address 0x0013d402.
  Error #1: .NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (7A06491A) (0)
  Error #2: aspnet_wp.exe  (PID: 3016) stopped unexpectedly.


The original website/problem (Create Website with Location of File System)
Hit F5.
I see the "Microsoft Visual Studio has encountered a problem and needs to close" error.
Checking the Application log, I see 1 error:
  Faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module vsdebug.dll, version 9.0.21022.8, stamp 47317c84, debug? 0, fault address 0x0013d402.

I uncheck "Restart Microsoft Visual Studio" and I click on "Send Error Report".
I see a window indicating it is sending the information, then it goes away.

Then, I would see "WebDeb.WebServer.exe has encountered a problem and needs to close.  We are sorry for the inconvenience." error.
Looking at the application log, I see 1 info and 2 error messages
  The info message: Bucket 568751753, bucket table 1, faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module vsdebug.dll, version 9.0.21022.8, stamp 47317c84, debug? 0, fault address 0x0013d402.
  Error #1: .NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (7A06491A) (0)
  Error #2: Faulting application webdev.webserver.exe, version 9.0.21022.8, stamp 4731664b, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x001f491a.
I click on Send Error Report for the second message
I see a window indicating it is sending the information, then it goes away.
Looking at the Application log, I see 1 information message
  The info message: Bucket 568752135, bucket table 1, faulting application webdev.webserver.exe, version 9.0.21022.8, stamp 4731664b, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x001f491a.
What kind of machine are you running?  32- or 64-bit machine?
Avatar of bmilli

ASKER

32 bit
OS: Windows XP Professional Version 2002 Service Pack 2
Processor: x86 Family 15 Model 4 Stepping 10
Machine: HP workstation: xw6200 Intel Xeon CPU 3.2 GHz.  2GB RAM
Avatar of bmilli

ASKER

I found a site where a person was seeing the same errors in the application log.  Though, it was a problem with VS 2005 I think.  There is supposedly a patch for this, but that person was unable to install the patch (I tried and was stopped as well).  Finally the person solved their problem by uninstalling .Net Framework 2.0 and reinstalling.  So, I tried uninstalling 3.5, 3.0, and 2.0, reinstalling 2.0, then repairing VS 2008 to get the 2.0 SP 1, 3.0 and 3.5 installed again.  Sadly, it did not help me get past this problem.
ASKER CERTIFIED SOLUTION
Avatar of Bob Learned
Bob Learned
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bmilli

ASKER

I appreciate your efforts.  I my resolve is beginning to fade...I suspect I will revisit someday... contact Microsoft at some point.  I would like to award you points for your effort, can I do this without breaking any rules?  How would I go about doing it?  I presume "Accept as Solution" and "Accept Multiple Solutions" would mark the text as a successful solution, which I don't want to do.  Is there a way to award points without marking it as solved?

Thanks again.

Yes, I believe you can post a question in Community Support to give partial credit to the expert for their effort.

Give them the URL for this question.
Avatar of bmilli

ASKER

While the problem is yet to be solved, the "pointing in the right direction" and the "above and beyond effort" are worthy of points.