Re: VS2005 Remote Web - FPSE Not Installed???

Hi Scott,

It's nothing to do with remote debugging or which FrameWork version you set. Either the extensions are installed and properly configured or they're not.

On Windows 2000/FP2000 extensions there's a suite of command line tools you can use to check the extensions:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\40\bin

You should find a similar folder on Server 2003. Make sure you've read all the extensions help files, make sure you've enabled the extensions in the IIS configuration tab for "server extensions"

Otherwise, re-install the extensions if you have to. Then use these tools above to "check" the extensions before trying to use a client box.

Scott F K Hooper wrote: 
Repost from 6-Jan-2006

I have VS2005 installed on my XP Pro SP2 workstation and am trying to create a new web on my 2003 Server. On the VS Start Page I select Create:Web Site, then in the New Web Site dialog I select ASP.NET Web Site, HTTP as the location type, VB as the laguage and finally I key the location as "http://<servername>/DOTNET2_Test", where <serverName> is appropriately substituted with the name of our 2003 Server domain controller. The error I get back upon clicking OK, after about 5-10 seconds of activity on the server with the "creating..." dialog on the workstation, is "Unable to create the Web 'http://<servername>/DOTNET2_Test'. The Web server does not appear to have the FrontPage server extensions installed.

Now then, on the server the FrontPage 2002 server extensions are most definately installed as checked in Add/Remove Programs->Windows Setup. I have also setup the VS 2005 Remote Debugger on the server.Using IIS6 on the server the empty web DOTNET2_Test also exists, mapped to a folder of same name off the webroot$ location. I read somewhere that I should be able to right-click the web in IIS6 and see FP2002 options in All Tasks, but all I see is "Save Configuration to a File". Sounds like the server extensions aren't installed doesn't it? But You can see the tick box there in Windows Setup stating the contrary. In the properties for the Web I have set the ASP.NET version to 2.0.50727

I have been through the How To at http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx to setup remote debugging so I'm sure it's not a firewall issue. I have even tried lowering the firewall on both machines to be sure. Incidentally, remote debugging works fine with VS2003/.NET1.1 between these two PC's. Sometime ago I had quite a lot of hassle getting that going, but it turned out to be a DCOM security issue - easily fixed when you know how :)

So that's where I'm at. I have tried providing VS2005 with a non-existent web name on the same remote server in hope that it would create it, but I get the same error referencing FrontPage. 

TIA to anybody who can shed any light for me
SFK





--
Gerry Hickman (London UK)
.

Relevant Pages

  • Re: VS2005 Remote Web - FPSE Not Installed???
    ... I can't give a proper answer right now because when I looked at my server today I realized I was testing SharePoint instead of Frontpage Extensions, but if you expand IIS in Computer Management you should see a folder called something like "server extensions". ... Remote Debugging does not need Frontpage Extensions if you are on a LAN, you only need the extensions if you are trying to speak to a server using the HTTP protocol. ...
    (microsoft.public.vsnet.general)
  • Re: VS2005 Remote Web - FPSE Not Installed???
    ... use the FP extensions whereas VS2005 does? ... In VS2005 the default is to use a "File Share" project on the local box, debug it in the built-in web server, and then use the tedious "Copy Web" command to copy the files to the production server. ... I have also setup the VS 2005 Remote Debugger on the server.Using IIS6 on the server the empty web DOTNET2_Test also exists, mapped to a folder of same name off the webroot$ location. ... I have been through the How To at http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx to setup remote debugging so I'm sure it's not a firewall issue. ...
    (microsoft.public.vsnet.general)
  • Re: Server Extensions Administrator
    ... the extensions do not work. ... To avoid using a subweb set up a virtual server, ... FrontPage Support: http://www.frontpagemvps.com/ ... have not been installed - click Extend to install the extensions. ...
    (microsoft.public.frontpage.extensions.windowsnt)
  • Re: VS2005 Remote Web - FPSE Not Installed???
    ... A FileSystem website was a bit pointless on VS2003 because you needed IIS to run it; only a fool would try to run a FileSystem website with IIS so most pros used FrontPage extensions. ... It's much easier to set up for the developer who does not have an expert server guy on hand. ... If I develop all my apps this way now, is there any need at all for remote debugging on the server? ...
    (microsoft.public.vsnet.general)
  • Re: front page 2003 running on small business server 2003 r2 issue
    ... Tick FrontPage 2002 Server Extensions ... > FrontPage will create sub webs in an existing web site that has FP ...
    (microsoft.public.frontpage.programming)
Loading