« Previous Next »

• 01-06-2009, 6:38 PM

  adam_right Joined on 01-22-2008, 3:27 PM Posts 3

  FrontPage Server Extensions problem on Windows 2008 Reply Contact I am workinh with a VS 2008 (c#) project on Windows XP Pro. os. I am trying to publish that application using "Publish Web" wizard to a remote server which is Windows Web Server 2008 os. But the publishing fails every time with following error: ---------------- Connecting to http://XX.XXX.XXX.XX/... Unable to create the Web site 'http://XX.XXX.XXX.XX/'. The Web server does not appear to have FrontPage Server Extensions installed. ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ========== ========== Publish: 0 succeeded, 1 failed, 0 skipped ========== ---------------- I use these links. http://learn.iis.net/page.aspx/134/install-frontpage-server-extensions/ http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1630  http://www.rtr.com/fpse/ I have installed FrontPage Server extensions from above links without any problems on the remote server. And extend the Virtual Server ( the "Default Web Site").  However, the problem remains. I cannot find any solution to this issue. Many thanks for any suggestions

• 01-07-2009, 12:02 AM

  In reply to

  ganeshanekar Joined on 11-15-2006, 12:29 AM India Posts 532

  Re: FrontPage Server Extensions problem on Windows 2008 Reply Contact Did it ever worked? Can you check if the remote website (on WS2008) has a Host-header? If yes, remove it and try. Take a backup of ApplicationHost.Config before you make changes.In applicationHost.config you will see the following line: <section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Deny" /> Can you change that to the following : <section name="modules" overrideModeDefault="Allow" /> If it does not help, restore original applicationhost.config. BTW, do you have SP1 of VS2008 installed? HTH. ~ Ganesh

• 01-07-2009, 4:22 AM

  In reply to

  adam_right Joined on 01-22-2008, 3:27 PM Posts 3

  Re: FrontPage Server Extensions problem on Windows 2008 Reply Contact Hi Ganesh,  there isn't an ApplicationHost.Config  file in the remote server's IIS folder ( which name is wwwroot ). Just web.config file. And it hasn't Host-header line. And yes i have SP1 for VS2008 in my developing machine. Do you know any alternative way for deploying an asp.net project to the remote server, instead publish wizard of VS2008  ?   Thanks..

• 01-07-2009, 5:44 AM

  In reply to

  ganeshanekar Joined on 11-15-2006, 12:29 AM India Posts 532	Re: FrontPage Server Extensions problem on Windows 2008 Reply Contact You can find applicationhost.config file in c:\windows\system32\inetsrv\config folder. To check host-header, on remote machine, open IIS manager and look for Bindings in Actions Pane. Select the website which are publishing too and check if there is any host value defined. HTH. ~ Ganesh

• 01-07-2009, 10:18 AM

  In reply to

  adam_right Joined on 01-22-2008, 3:27 PM Posts 3

  Re: FrontPage Server Extensions problem on Windows 2008 Reply Contact in Site Binding" section of site there is only one row and its values are : Type: Http Host Name : Port: 80 Ip Address : * Binding İnfo : i add a screen capture of site binding   and i have changed the applicationHost.config file on remote server. But still same error. The Web server does not appear to have FrontPage Server Extensions installed.   Could you see any problem ?

• 01-16-2009, 4:19 PM

  In reply to

  robmcm Joined on 05-26-2006, 9:05 PM Redmond, WA Posts 125

  Re: FrontPage Server Extensions problem on Windows 2008 Reply Contact Removing a Host Header is not necessary - the FrontPage Server Extensions will work fine with Host Headers. I would be more concerned with how FPSE is set up and configured on the server and whether some configuration setting is preventing FPSE from working. Here are a few additional things to check: 1. From your initial post I can see that you've already gone through the walkthrough for installing FPSE on your WS2008 computer, but did you use the web-based or command-line-based installation for FPSE on your Default Web Site? Either way should work, but using the web-based installation allows you to administer FPSE on your Default Web Site and I'm curious if that succeeds. 2. Can you browse to the following URL? http://yourserver/_vti_inf.html That file is used by a remote computer to discover FPSE capabilities on a server, so if you can't browse that file then there's an issue. 3. Can you browse to the following URL? http://yourserver/_vti_bin/shtml.dll You should see the following message displayed in your browser: Cannot run the FrontPage Server Extensions on this page: "" That error message actually means that FPSE is working correctly, but it's a great test for basic functionality. 4. Does your web site have a custom HTTP header for MS-Author-Via: MS-FP/4.0 configured? (This would be under HTTP Response Headers in IIS7's IIS Manager.) Robert McMurray (MSFT, IIS)