I am having this ridiculously frustrating problem, migrating an existing web app to VS.2005.

 

Initially I was able to successfully convert my VS 2002 app, by opening the Localhost site using the new ‘Local IIS’ option (File -> Add Existing Web Site ->. Local IIS -> Select the Localhost site) and everything was OK. However, when I shut down and reboot, I was unable to open the same project and got the following error:

 

“Unable to open the Web ‘http://localhost’. The Web server does not appear to have the FrontPage server extensions installed. If the FrontPage Server extensions are installed, this error may occur because the _vti_bin virtual directory is not marked executable. To correct his problem, run the Internet Services Manager, select the Web server having the problem and use the Check Server Extensions task”

 

I have attempted to resolve this problem using the Internet Service Manager as the error message suggests, but this creates additional FrontPage errors, and at the end of the day, I don’t want to use FrontPage for this application.

 

I have found that if I run the Repair/Reinstall module on the VS 2005 Professional installation disk, and reboot my PC I am able to re-open my project using localhost, however as soon as I reboot my PC, the FrontPage error returns.

 

Repair/Reinstall and the problem goes away, until I reboot. What on is going???

 

Hello,

that error message can be misleading, and in Fwk2 the FP extensions are obsolete and unneeded.

I guess you have not registered the Fwk to IIS after installing. To do this, open the shell (cmd), cd to the C:\Windows\Framework.NET\v2.0 folder (or something like that, just chose the right folder for the right version), and run:

aspnet_regiis -i -enable

That should make it run...

Hope this helps. -LV

Hi,

Thanks for this, however it hasn't corrected my problem.

As suggested I executed the command "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i –enable" and it ran a through a DOS process to install ASP.NET 2.0.50727. After it completed, I attempted to load the project and got the same FrontPage error. I rebooted and the error persisted.

I then ran through the Repair/Reinstall in the Maintenance Mode module on the VS 2005 Pro Install CD and rebooted as required and was able to load my project. I rebooted again, and then started to get the FrontPage error message.

I have been able to consistently repeat this behaviour. Interestingly, the PC must be rebooted after running the Repair/Reinstall for Localhost to work correctly. If I select the reboot later option an attempt to load the project I gat the same FrontPage error. Does this suggest that there is a dependent process running on reboot that aspnet_regiis does not use?

As additional information, I am logged onto the PC with Administrator privileges and my Web App is located at the root of Localhost. It is essential that I load it under Localhost, because the app is dependent on virtual directories.

Thanks,

Stephen

> I executed the command "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i –enable"

Unless you have set Fwk related environment viriables before doing this (wihch requires running another script), this shouldn't indeed work. The procedure i've depicted is just what Microsoft suggests, and requires you: 1) open cmd; 2) cd to the right folder; 3) execute the script (locally, so to say). Then check back your root app folder configuration, Asp.net version above all...

If *this* doesn't work, then i'm afraid i wouldn't know what else to try other than reinstalling everything from scratch... so hope someone else can shed light in that case.

-LV

I only gave the full path to show the actual location and version number. Running it this way does work, but I may have put the file path in double quotes. At any rate, this is not my problem...

Also, while reinstalling does temporarily resolve this issue, it is hardly a solution, because as I have documented, I would need to do this each day.

However, I have worked out additional some additional behaviour. The trigger appears to be when I compile my web app.

If I run the repair/reinstall process and reboot my PC, I am able to open my web app using localhost in VS 2005 Pro. I can then shut down and reopen in VS without any problem. I can also reboot and reopen my web app without any problem.

However, if I open my web app and then compile my app, and close VS, I am then unable to reopen the same application.

What is changing when I compiling my web app, that is then triggering this phoney FrontPage error? 

Thanks,

Stephen

Why not simply install FrontPage Extensions?  Assuming you're running this on an IIS system and not with the internal web server.

Jeff

Because I don't use FrontPage, I don't understand why I need to be dependent on FrontPage and I hate that it populates my server with its own directory structure that adds no value. However, as mentioned in my original post I did follow the advice of the error message and installed FrontPage extensions to see if that fixed he problem, but I got more phoney errors related to permissions of directories.

Also, this is an upgrade project from VS 2002. It works in that environment and I see no reason why it shouldn’t in VS 2005.

Finally, I tend to agree with the first poster that the FrontPage is probably phoney and hides another error condition. I have been able to describe clear and repeatable behaviour that is bug like and deserves a proper solution.

 

Has this post now become unanswerable?

I'm having the exact same problem, glad to hear I'm not alone. Not glad to hear it hasn't been resolved.

 

 

Actually, my error stems from creating a website with 'http://localhost/website'.

If however, I change the name of the website to one that definitely does not exist, like

'http://localhost/websitea', then the website is successfully created.

 

Seems VS 2005 is unable to communicate with the IIS metadatabase on existing iis applications, and the duplicate application error bubbles up and is somehow caught to this error.

 

 

I'm now getting this error on Vista. BEen running it two months now (RTM Version) and just 2 days ago (29 January 2007) it was brought down for Patch Tuesday. Tuesday morning came up and I can't run any Website. (Web application projects work fine).

 Here's my Topic post: http://forums.asp.net/thread/1556295.aspx

Hi All,

 

I have fond the answer just look : http://msdn.microsoft.com/en-us/library/aa984224(VS.71).aspx

 

or u can use this:

 

start ==> run ==> iismgr ==> right click on your web site ==> All tasks ==> click on Check server extensions ==> write your account info (username and passwod)

 

then this will work perfectly

 

please if this work mark it as an answer

thx in advance