FrontPage 2002 Server Extensions Problem During SharePoint Service 2.0 Installation ON Server 2003
Hi, All,When I installSharePoint Service 2.0, got:Windows SharePoint Services has detected that this virtual server is running SharePoint Team Services or FrontPage 2002 Server Extensions. To extend this virtual server with Windows SharePoint Services, you must move the site content to a different virtual server, and then remove SharePoint Team Services or FrontPage 2002 Server Extensions from this virtual server. For more information about moving data from SharePoint Team Services or FrontPage 2002 Server Extensions, see the Administrator's Guide for Windows SharePoint Services.So, how to remove theFrontPage 2002 Server Extensions?For your reference, I did as following: I installed theFrontPage 2002 Server Extensions before and published a website on the server 2003. I removed IIS and reinstalled it withoutFrontPage 2002 Server Extensions. Usingowsadm.exe-o fulluninstall -p 80, gotError: There is no web named "".The version (unknown) of the server extensions you are trying to uninstall cannot be uninstalled with this tool. You must upgrade this virtual server to the current version, and then use owsadm.exe to uninstall. Forllowinghttp://support.microsoft.com/kb/823378, but there isn'tServer Administration page in myWindows SharePoint Services Central Administration.Thanks, Andrew Huang andrew.huang@ymail.com
February 12th, 2009 8:55pm

Are you sure that you want to install WSS 2.0?The latest version is WSS 3.0 and it's been out for over 2 years already. There are NO advantages of having WSS 2.0 compared to WSS 3.0.WSS FAQ sites: WSS 2.0: http://wssv2faq.mindsharp.com WSS 3.0 and MOSS 2007: http://wssv3faq.mindsharp.com Total list of WSS 3.0 and MOSS 2007 Books (including foreign language titles) http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/V%20Books.aspx
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2009 9:31pm

Hi, Mike,With TFS installation guide (071210):Install Windows SharePoint Services with Service Pack 2 for use with Team Foundation Server, select the Server Farm option, and restart the computer.I'm not sure if I can install WSS 3.0 or not.Thanks, Andrew Huang andrew.huang@ymail.com
February 13th, 2009 5:21pm

Hi, Mike,FromTN1501,Team Foundation Server requires the installation of WSS 2.0 on the Team Foundation Server application tier for installation and serviceability.I think, I can upgrade to WSS 3.0 after TFS installation.Thanks, Andrew Huang andrew.huang@ymail.com
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2009 6:17pm

You should be aware that uninstalling FrontPage Extensions will remove all the "services.cnf" files from all of the _vti_pvt folders under each of your designated web sites. Thereafter any attempt to open such web sites using Microsoft tools such as Expression Web will fail with the message "There is no web site at: <whatever your address is>". Another symptom is that any attempt to open such a site using Internet Explorer (using your local system URL) will suddenly start issuing a popup requiring you to provide authentication before proceeding to the site. t took me several hours to figure out what had happened. I was tempted at various times to use the "convert to web" feature in Expression Web (which appears when you right-click on the home folder name when navigating to it via the file system), which no doubt would have made some attempt to replace the services.cnf file and probably would have altered other things that I didn't want altered. Fortunately I resisted and finally restored all my "services.cnf" files from a backup. Apparently the FrontPage uninstaller believes that in uninstalling FrontPage Extensions it is your intent to entirely de-commission all your web sites (!). If you do not have a backup from which to restore your services.cnf files, then you can reconstruct them. A site with no subsites will have a "services.cnf" file containing one line with one character, namely the forward slash (/). A site that has subsites will contain the forward-slash line, and additionally will have one line for each subsite of the form "/path-to-subsite-home-folder". That is, the line representing each subsite will consist of a slash followed by the relative path to the home folder of the subsite. Such a file might look like this (without the indentation): / /SubsiteDirectlyUnderTopSite /SubFolder/SubSiteTwoLevelsBelowTopSite I hope this will save someone else the three hours I spent on this.
January 8th, 2011 1:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics