This weekend, I had this bright idea to install Virtual Server 2005 R2 on my Vista dev box at home to test a theory.
Well, it seems to break Visual Studio's WebServer. When trying to run or debug an ASP.Net application, I was hit by a "
WebDev.WebServer.exe has stopped working".
I tried many things, as you can imagine, but a few were:
- Reboot
- Un-installed Virtual Server 2005
- Un-installed/re-installed the Web Development Feature from the VS installation.
- Re-ran the various combinations of aspnet_regiis.exe
There was an entry in the Event Log's Application Logs:
Fault bucket 118476878, type 5
Event Name: CLR20r3
Response: None
Cab Id: 0
Problem signature:
P1: webdev.webserver.exe
P2: 9.0.0.0
P3: 4731664b
P4: System
P5: 2.0.0.0
P6: 471ebf0d
P7: 2c04
P8: 40
P9: System.Net.Sockets.Socket
P10:
System.Net.Sockets.Socket...
I tried running webdev.webserver.exe manually from the command line:
C:\Program Files\Common Files\microsoft shared\DevServer\9.0
C:\Windows\Microsoft.NET\Framework\v2.0.50727
both worked (I tried port 8080 and 8888) (see note at the end)
Anyway, what seems to have fixed the problem was the following:
Disable IPv6 from your network adapters
Control Panel -> Network Connections -> for each adapter/connection: disable the TCP/IPv6
notes:
- When running the webDev exe manually, I didn't (and should have) try to run it with the same port that VS was trying with.
- I didn't try disabling IPv6 one connection at a time. Maybe 1 did the trick, not sure.
Ho yes, one weird thing: the web based admin configuration page worked when the Web page launched by VS didn't
Anyway, I'm fixed for now and need to move on.
If this article helps you, woohoo...
If it doesn't, you'll find an answer in google ;)
Pat