webdev.webserver fails to start

  • Thread starter Thread starter oaksong
  • Start date Start date
O

oaksong

I had a problem with this a couple months ago and managed to get it
working. This included poking a few holes in BlackIce and disabling a
feature (BOP) in McAfee Virus Scan. This was a test case, and the
ports were blocked until permission was granted to use this solution.

Now I've got the ports open, and what was working two months ago no
longer works. BlackIce was disabled to no noticeable effect. We've
been on the phone with MS Tech Support and they're not getting us
anywhere. Any suggestions, clues, etc. would be appreciated.

tia
Chris
 
Can you switch to IIS development? It would solve all of these problems. If
you are on XP Pro or Vista Business, Enterprise or Ultimate, you can add IIS
to your dev box.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************
 
Can you switch to IIS development? It would solve all of these problems. If
you are on XP Pro or Vista Business, Enterprise or Ultimate, you can add IIS
to your dev box.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBAhttp://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
Click to expand...

In my environment IIS is not an option.
 
re:
In my environment IIS is not an option.
Click to expand...

You might want to try Cassiniv2 to host your test development.

Direct link to the source files:
http://blogs.msdn.com/dmitryr/attachment/548131.ashx

You also need the v2.0 version of GACUTIL which should
be installed by default with VWD Express or VS 2005.

Make sure you read the "ReadMe.txt" file included in the zipped source.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
It turned out that there was another BOP (buffer overflow protection)
in operation. It was in services under ISS (aka Black Ice). BOP
effectively busies out the ports, which was what I recognized was the
problem but didn't know what was causing the problem. By turning that
off, webdev.webserver became operational.
 
Interesting!

Thanks for the update!




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
It turned out that there was another BOP (buffer overflow protection)
in operation. It was in services under ISS (aka Black Ice). BOP
effectively busies out the ports, which was what I recognized was the
problem but didn't know what was causing the problem. By turning that
off, webdev.webserver became operational.
 
Back
Top