I have been testing an IIS 7 server recently and it was working correctly for a while but now every time I do a publish from VS 2008, I loose the default document and get a security exception when I click on the Browse *.80(http) link: "
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory."
I can go in and enable browsing or I can add my default page to the top of the default document list and it works again. The same thing happened on two different servers that I am trying to ready for a IIS6 to 7 migration. On one of the servers I deleted
the application and reconfigured it and it seems to be working. I don't like going into production not knowing what I may have done that caused it so I am leaving the second server as is until I can try and find a solution that doesn't involve deleting and
rebuilding. Any suggestions as to what I might try would be appreciated.
It is probably the default document setting had been overwritten in the web.config file, and the default document’s list on the parent level is empty. Please open IIS Manager, navigate to the default document on the server level, then add the default files.
Please mark the replies as answers if they help or unmark if not.
Feedback to us
Leo, Thanks, I have added the website default document to the parent level and that seems to have worked. I am a little worried that I don't understand exactly how this happened and why it needs to be done. You say "the default document setting had been
overwritten in the web.config file". Do you mean the web sites web.conig? I have never had an entry in the web.cofig file for default document although I do remember configuring it in IIS 6 once I published.
As for entering it in IIS 7. II had some help setting it up and it worked fine until I started having this overwrite issue. Are yopu saying that if the parent level doesn't have my websites default document listed, every time I re publish I will overwrite
all my settings? I will close this and research the subject some more. Thanks for the help.
Marked as answer by AkAlan on Jul 30, 2010 04:02 PM
AkAlan
11 Posts
Publishing Application overwrites settings
Jul 22, 2010 10:02 PM|LINK
I have been testing an IIS 7 server recently and it was working correctly for a while but now every time I do a publish from VS 2008, I loose the default document and get a security exception when I click on the Browse *.80(http) link: "
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory."
I can go in and enable browsing or I can add my default page to the top of the default document list and it works again. The same thing happened on two different servers that I am trying to ready for a IIS6 to 7 migration. On one of the servers I deleted the application and reconfigured it and it seems to be working. I don't like going into production not knowing what I may have done that caused it so I am leaving the second server as is until I can try and find a solution that doesn't involve deleting and rebuilding. Any suggestions as to what I might try would be appreciated.
Leo Tang - M...
4161 Posts
Microsoft
Re: Publishing Application overwrites settings
Jul 28, 2010 06:57 AM|LINK
Hi,
It is probably the default document setting had been overwritten in the web.config file, and the default document’s list on the parent level is empty. Please open IIS Manager, navigate to the default document on the server level, then add the default files.
Feedback to us
Develop and promote your apps in Windows Store
AkAlan
11 Posts
Re: Publishing Application overwrites settings
Jul 30, 2010 04:01 PM|LINK
Leo, Thanks, I have added the website default document to the parent level and that seems to have worked. I am a little worried that I don't understand exactly how this happened and why it needs to be done. You say "the default document setting had been overwritten in the web.config file". Do you mean the web sites web.conig? I have never had an entry in the web.cofig file for default document although I do remember configuring it in IIS 6 once I published.
As for entering it in IIS 7. II had some help setting it up and it worked fine until I started having this overwrite issue. Are yopu saying that if the parent level doesn't have my websites default document listed, every time I re publish I will overwrite all my settings? I will close this and research the subject some more. Thanks for the help.