471,344 Members | 1,512 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,344 software developers and data experts.

verify that ASP.NET or ATL Server is correctly installed on the server.....

I keep getting this silly Error since installing the lastest Windows
XP updates...

Error while trying to run project: Unable to start debugging on the
web server. Could not start ASP.NET or ATL Server Debugging.

Verify that ASP.NET or ATL Server is correctly installed on the server
Everything is configured correctly and should work fine as it was
before...
I done a system restore and fixed it the first time but I want to know
what actually is causing it???

The other strange thing is that now when I try to view the pages
without debugging I get a 404 error saying it can't find the pages
which I know are there!!!

Any ideas bar wiping my machine or doing a system restore each time it
happens???
Jul 21 '05 #1
2 5275
I'm getting the same ASP.NET debugging problem after the latest
automatic Windows Update. It was working just fine before it.

I checked the Windows Firewall and noticed security entries in the
event log about blocking inetpub.exe. So I added it to the firewall
exceptions list, but no luck.

I did try all the usual things like running aspnet_regiis /i,
restarting, etc.

Anyone else seeing this problem since being "upgraded" by Microsoft?
Any clues?

Jul 21 '05 #2
I ad the same problem after the automatic Windows update installed last
night. I did a system restore to the previous day and everything
started working again. I turned off automatic updates so I won't have
the same problem tomorrow.

Scott
tn******@pobox.com wrote:
I'm getting the same ASP.NET debugging problem after the latest
automatic Windows Update. It was working just fine before it.

I checked the Windows Firewall and noticed security entries in the
event log about blocking inetpub.exe. So I added it to the firewall
exceptions list, but no luck.

I did try all the usual things like running aspnet_regiis /i,
restarting, etc.

Anyone else seeing this problem since being "upgraded" by Microsoft?
Any clues?


Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

9 posts views Thread by Steve Buster | last post: by
1 post views Thread by Mythran | last post: by
9 posts views Thread by David Thielen | last post: by
1 post views Thread by Grey | last post: by
reply views Thread by Ronak mishra | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.