Hi to all forum members

I got this problem. When I try to run a test project I receive "Page not found" in browser opened by ASP.NET Development server. I am logged as administrator to my WIN XP. And I am using VS2005. I had VWD and ASP.NET 2.0 before but  removed everything before installing VS2005. Do you hav eany idea why is this happening.

p.s. I do not use any firewall only nod32 as antivirus program

I will be very glad is someone can help me.

Try stopping your AV software.  Most common issue is blocking ports that the development web server might use.

Jeff

I turned ogg my AV program and (nod 32) again no result. When I try to run any page no matter how simple it is the development server starts and afte ra long time (some minutes) show no page found. Only one tme the page showed correctly. It has only onelabel on it no more complicated elements. I am using VPN to get Internet but after I turned it off again no change :(

Any event log entries?

Jeff

No event log at my disposal righ tnow. But I will take a look when I have access to my PC at home later today. Could the problem be in PC hardware cause I am using one old machine: Duron 650Mhz, 3MB20 SDRAM 100Mhz, 15Gb HDD. Is this enough to run VS 2005. Actually yesterday I manage to get the page run one time after message "Page not found" in web browser I refreshed IE and got  page correctly displayed and after that everything ruined again :( I think that something is impeding VS2005 work but now sure what. 

That's a minimal configuration for Visual Studio, so you may be having hardware issues.

Jeff

An update to my problem. I reinstalled Windows XP SP2 and VS 2005 and still cannot open any test page using web dev server. The most strange thing is that when I select site ASP.NET configuration in VS 2005 menu it opens new IE and new instance of  WebDev server and everything is OK. So only my test page does not open :( or to be more precise not everytime. Yesterday I succeeded to open the test page after refreshing IE content (F5) but only one time. So what do you think the problem might be?

P.S. Where can I see error log file for my test application. No log file found. Only in VS 2005 in "server" tab not sure about name I saw some logging for all sort of things - system, apache, and so on.

Did you disable the firwall?  Did you use a Hello World app?

Jeff

No firewall activated. and I only put one label on the page. I think this is  simple enough for a test application.

jeff@zina.com:

Did you disable the firwall?  Did you use a Hello World app?

Jeff

So does someone has decision for my problem ? I do not have any ideas what more can I do to make this VS 2005 to work :(

No decisions, just suggestions.  Post in the VS forums, there may be more help.  Beyond that I'm still leaning to a hardware issue.  Check the event logs for anything.  Check drive space, RAM, etc.

Jeff

i had the same problem and here is its fix,

as u have Eset nod32 antivirus v3.0.621 (same as me) , the problem is from this AV that dont allow connections to be made to Visual Studio ASP.NET Server .

now follow these steps to solve this issue:

1. DoubleClick on Nod32 icon on tray and Open it up.
2. if it is not in "Advanced Mode" , switch to Advanced Mode. ( you can do it by clicking on the bottom-left link "Display:Standard Mode" and then click on "Toggle Advanced Mode" )
3. then goto SETUP section. then on the Right Pane click on "Antivirus and Antispyware protection". the panel should be opened.
4. now in the "Web Access protection" click on "Configure..."
5. from the left Tree go to path : "Web access protection > HTTP > Web Browsers"
6. now you should see visual studio 8 "devenv.exe" in the list .
7. click on it twice till you see a cross sign in the box. ( Note on CROSS sign , not mark sign ! )
8. with this cross sign you tell the Nod32 that this program should not be scanned and filtered for web access.

due to this steps , my problem solved and now i can access my page from localhost:<portNumber> .

Thanks a lot, your solution resolve all my problems.!!!

Thank you for this resolution. After having to restore my computer multiple times to an earlier point, I was finally able to isolate the NOD32 3.0 "upgrade" as a likely culprit. Microsoft wanted me to pay them over $250 for help with this issue! Do you think we can bill ESET for lost productivity time?

Thanks guys for the valuable info.  It almost worked for me, too :)  You certainly helped me along the right direction (whew!)  I had to take it a little further when using ESET's Smart Security (3.0.6210.0).

In addition to the settings above with the Web browsers, I had to go to Personal Firewall, Protocol filtering, and select "HTTP and POP3 ports" instead of the other two options.  Now it works for me.