I'm doing something really dumb (I think) - Publishing to local PC with IIS and FP extensions

D

Dan

On my local PC I have XP Pro with IIS 5.1 and FP extensions version
6.0.2.5516 running. My normal development site is internet based. When I
try to publish to my local PC so I can work faster, and open Remote Web Site
Properties in FP2003, then change the radio button to "Frontpage or
Sharepoint Services" so that I can run stuff needing the FP extensions,
browse to a web on my PC and click OK, the dialog box does nothing - won't
allow me to change the destination in other words. Computer management etc.
shows IIS and FP extensions both running, and I've TRIED to follow exactly
the instructions for installing IIS and extensions, but I'm clearly doing
something wrong... Would some kind soul please help a pretty new person?

TIA
 
R

Randy Birch

ouch.

Personally, I think you're doing things totally backwards. The web site you
normally edit should exist on your local pc, not on the server. You edit
*only* the local version of the site ('cause you know the one on the web is
working!), and publish those changes when desired. There is no way to have a
site on a remote server work in conjunction with files on your PC, and still
work for all other visitors to your site.

I've used FP since version 1 back in 1995 or so, and have tried both
intentionally and unintentionally to do just about everything right and
wrong that FP will allow. I not a FP MVP, but I did learn early on that
attempting to maintain a remote site as the "master" (rather than a local
version) was a recipe for disaster. Other's mileage may vary, of course ...
I guess you could call this 'my best practice'.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: On my local PC I have XP Pro with IIS 5.1 and FP extensions version
: 6.0.2.5516 running. My normal development site is internet based. When I
: try to publish to my local PC so I can work faster, and open Remote Web
Site
: Properties in FP2003, then change the radio button to "Frontpage or
: Sharepoint Services" so that I can run stuff needing the FP extensions,
: browse to a web on my PC and click OK, the dialog box does nothing - won't
: allow me to change the destination in other words. Computer management
etc.
: shows IIS and FP extensions both running, and I've TRIED to follow exactly
: the instructions for installing IIS and extensions, but I'm clearly doing
: something wrong... Would some kind soul please help a pretty new person?
:
: TIA
: --
: Dan E
: webbie(removethis)@preferredcountry.com
:
:
 
D

Dan

You're right, and I agree Randy, however where I'm developing is a test (not
public)area on my host, plus I've had little choice since I've been unable
to get IIS/FP extensions up and running on my local machine, and plus
there's no point developing the stuff I'm doing in an environment where FP
extensions aren't available, SO - to repeat - how do I get IIS/Extensions
working agreeably on my PC? :)

TIA

Dan Ellis
 
R

Randy Birch

I've never had problems "installing FP extensions" on any of my NT-based
machines (NT/2000/XP) that ran local copies of IIS ... I just installed IIS
as one of the first things after installing Windows, and then installed
FrontPage. Everything seemed to work fine.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: You're right, and I agree Randy, however where I'm developing is a test
(not
: public)area on my host, plus I've had little choice since I've been unable
: to get IIS/FP extensions up and running on my local machine, and plus
: there's no point developing the stuff I'm doing in an environment where FP
: extensions aren't available, SO - to repeat - how do I get IIS/Extensions
: working agreeably on my PC? :)
:
: TIA
:
: Dan Ellis
:
: --
: Dan Ellis
: webbie(removethis)@preferredcountry.com
: : > ouch.
: >
: > Personally, I think you're doing things totally backwards. The web site
: you
: > normally edit should exist on your local pc, not on the server. You edit
: > *only* the local version of the site ('cause you know the one on the web
: is
: > working!), and publish those changes when desired. There is no way to
have
: a
: > site on a remote server work in conjunction with files on your PC, and
: still
: > work for all other visitors to your site.
: >
: > I've used FP since version 1 back in 1995 or so, and have tried both
: > intentionally and unintentionally to do just about everything right and
: > wrong that FP will allow. I not a FP MVP, but I did learn early on that
: > attempting to maintain a remote site as the "master" (rather than a
local
: > version) was a recipe for disaster. Other's mileage may vary, of course
: ...
: > I guess you could call this 'my best practice'.
: >
: > --
: >
: > Randy Birch
: > MVP Visual Basic
: > http://vbnet.mvps.org/
: > Please respond only to the newsgroups so all can benefit.
: >
: >
: > : > : On my local PC I have XP Pro with IIS 5.1 and FP extensions version
: > : 6.0.2.5516 running. My normal development site is internet based.
When
: I
: > : try to publish to my local PC so I can work faster, and open Remote
Web
: > Site
: > : Properties in FP2003, then change the radio button to "Frontpage or
: > : Sharepoint Services" so that I can run stuff needing the FP
extensions,
: > : browse to a web on my PC and click OK, the dialog box does nothing -
: won't
: > : allow me to change the destination in other words. Computer
management
: > etc.
: > : shows IIS and FP extensions both running, and I've TRIED to follow
: exactly
: > : the instructions for installing IIS and extensions, but I'm clearly
: doing
: > : something wrong... Would some kind soul please help a pretty new
: person?
: > :
: > : TIA
: > : --
: > : Dan E
: > : webbie(removethis)@preferredcountry.com
: > :
: > :
: >
: >
:
:
 
D

Dan

Randy - I think it's just I'm not doing something I should. Here's what
happens. I do have http://localhost available in My Network Places as
\\localhost, and I also have in My Network Places localhost (2) as
http://localhost/, and it is coming from C:\inetpub\wwwroot.

FP2003 can open C:\inetpub\wwwroot OK as a local disk-based web, but when I
try to open it from FP2003 as http://localhost, it comes up with a dialog
box "Web site setp", with http://localhost/ in the web site location, and
with WebDAV pre-chosen as the file transfer method. When I choose Frontpage
Server Extensions or Sharepoint Services instead of WebDAV and click next, I
get the message "You are unable to import a web site from http://localhost.
Verify the location and try again." Then I set the dialog back to Webdav
and it offers to put a copy of the files in Documents and settings... etc..
I then cancel out of that and get a message from FP "The Web server at
http://localhost does not appear to have Windows Sharepoint Services
installed.", which puzzles me - does it mean I have the wrong version FP
Extensions installed? (I have version 6.0.2.5516). And I don't know where
to ge from there... Any suggestions? It's possible I guess I have
something set wrongly in IIS or FP extensions - maybe uninstall those, then
re-install both and start again with their default settings? Any
suggestions received with gratitude... I'm a physicist, not a webbie :)

Dan Ellis
webbie(removethis)@preferredcountry.com
 
R

Randy Birch

If you can navigate to http://localhost/yourwebname and get the index page
with all data and FP-specific items intact, the extensions are present and
running so your difficulty lies elsewhere. I confess I am still evaluating
the upgrade to 2003 (I use 2002 now), so can not comment on specific menu
items or options that may be present in that version.

If you can't navigate to http://localhost/yourwebname try substituting your
local machine name ... ie on my box http://vbnetdev/mywebname and
http://localhost/mywebname opens the same web.

Another thought ... what happens when you go to control panel >
administrative tools > Server Extensions Administrator. On my box it opens
FP server extensions, then my local machine name, then the server extension
folder /LM/W3SVC/1:. Tee property sheet for that item has the 'enable
authoring' option checked.

Under the /LM/W3SVC/1: item are my local webs, each identified as a subweb,
a vdir, or nothing. For those identified as subwebs, selecting and
right-clicking presents a menu with All Tasks, one of which is Check Server
Extensions. Where the folder is not identified as a specific type (no
extensions applied), the option is Configure Server Extensions.

You can try creating a new FP web by selecting the parent (/LM/W3SVC/1:),
right-click and select New > Server Extensions Web, then create a new dummy
test web (any name, no spaces). If this web is successfully created and has
the classification subweb, and if you can subsequently open that web using
FrontPage's File > Open Web option (typing the web as
http://localhost/dummywebname), and you can create and view pages containing
FP items (ie an include page), try repeating this same process specifying
the web you're having problems with (if it's not listed as a subweb
already). You'll get a notice that the folder already exists ... say OK and
continue. Of course, you will want to back up the files first just in case.

If it is a subweb, choose the Check Server Extensions option.

--------------

I've created a tiny web site (2 pages, 5 images) you can download to check
the server extensions ... http://www.mvps.org/rgbfptest

Go to New > Web > Empty web. Give it a name, then when created go to File >
Import > From Web > and enter http://www.mvps.org/rgbfptest. It will haul
the works down to create a local copy of the site. Open the index.html page
in FP and view the included content, and preview in the browser to determine
all works as it should.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.
 
D

Dan

Randy - a number of things.

1. I didn't know I could have subwebs under inetpub/wwwroot - I tjhought
the XP Pro version of IIS was limited to one web - no? So I had basic web
pages including a
Default.htm directly in wwwroot.

2. I do get the same structure as you under Admin Tools > Server Extensions
Administrator (Front Page Server Extensions >MAIN (computer name)
/LM/W3SVC/1:. And yes the properties sheet for /LM/W3SVC/1: does have
authoring checked. It shows version 6.0.2.5516, and I do wonder about that.
My internet host says they have FP2002 extensions installed, and when I take
a look there, the version of extensions is 5.something. Now, when I right
click on LM/W3SVC?1: and choose All Tasks > Check Server Properties, I get a
message from Microsoft Server Extensions saying "The server administration
programs and the server extensions on the web server are not compqatible.
The administration program is too old to use with this server.", and there's
an OK box, which, when I click it, makes that message go away, and
apparently the web check happens anyway, and a box "Check Web" has the
message "Checking web http://", and in the box it says "No problems found
End check 2/22/2004 5:18:44 PM" If I try to Recalculate web after right
clicking, I get the same error message about the admin programs and the
server extensions being incompatible. OK - now I right clicked on
/LM/W3SVC/1: and chose New > Server Extensions Web, gave it a directory name
test, and name test, and the folder test was created beneath /LM/W3SVC/1:,
and was identified as a subweb. When I right click on THAT, choose All
Tasks > Check Server Extensions, I get the same error message about
incompatible admin programs. server extensions. I remember once I did try
to go from FP extensions version 200 to version 2002, and that may have
something to do with this...

3. In your suggestion about testing using http://www.mvps.org/rgbfptest -
where did you mean for me to create the test web - as a disk-based web (i.e.
C:/inetpub/wwwroot/something, or as http://localhost/something? In FP2003,
when I go New > One page web site, I have to browse to the location of the
new web site, and I can browse to anywhere in My Network Places, or my
computer, or whatever. If I browse to localhost, then try to enter a new
name (i.e. a folder that doesn't exist), I get a creation error. If I
browse to an existing subweb (test), from Web Site Templates then click OK,
I get a Web Site Setup dialog which wants me to create a local copy on my
computer, edit the local copy, then publish changes to my Web server using
Remote Site View. The default is WebDAV - if I click to use FP Server
Extensions as the method, I get a message "You are unable to import a Web
site from http://localhost/test. Verify the location and then try again."
If I click WebDAV then Next, it gives a local copy default location in
C:\Documents and Settings\Dan\My Documents\My Webs. Clicking next gives a
congratulations from the wizard message, then I click Finish and I get a new
FP2003 window with Remote web site view, showing local as c:\Documents etc.
and Remote as http://localhost/test. Now I REALLY don't know if this is
what I should have or not. I wanted to have a local (i.e. on my computer)
version of my internet development site,but have server extensions working
locally on the local copy, so that all the stuff that needs the extensions
would work during building. I'm now confused... Any suggestions - VETY
gratefully received.

TIA,
 
R

Randy Birch

1) I've never used the default folder under wwwroot for my pages ... I
always create new webs using File>New Web, and enter the name. When browsing
the local machine you just add the web to the end, ie
http://localhost/myweb/, ensuring the default file name for the opening file
is as expected under IIS config (eg default.htm). These webs you create ...
ie myweb ... are subwebs in relation to the wwwroot web. You can have as
many as you want ... I've got 20 or so for different projects on the go.

2) My IIS version is 5.1. My server extensions (at least under properties
for /LM/W3SVC/1 I assume this is the SE version number) are 4.0.2.5322. I
suspect this version is reported because I don't have XP SPs on this
machine --- I'm behind a hardware firewall and virus-protected.

This page talks about your server extension error, though in the context of
sharepoint. http://support.microsoft.com/default.aspx?scid=kb;EN-US;823376.
Might find something that clicks.

There is something definitely whacky with your setup, and it may have to do
with service packs you have that I don't have installed. Perhaps others can
chime in here if there are issues, or if they have further suggestions
concerning your error.

If not, there is the second last resort ... following a backup in case
things go awry, I would do the following in an attempt to resolve the
problem:

a) open Administrative Programs > Internet Information Services, and
right-click on 'default web site', ... there you should have an option under
Tasks to 'Remove server extensions". Do so.

b) uninstall FrontPage

c) through control panes>add/remove programs/windows, uninstall IIS.

d) reboot

e) ensure all folders directories under C:\Program Files\microsoft FrontPage
are empty, and if not, delete it. Also delete the entire inetpub folder --
this will delete your local ftp and wwwroot folder and all contents.

f) delete the FrontPage temp folders under your temp folder(s). I have 2
.... one under c:\temp, where my environment variable points as the tmp
location, and one under c:\windows\temp.

g) delete C:\Documents and Settings\birchr\Application
Data\Microsoft\FrontPage

h) rename the folder C:\WINDOWS\system32\inetsrv if it still exists

i) delete C:\WINDOWS\inf\iis.inf and C:\WINDOWS\inf\iis.pnf if it still
exists

j) delete or rename C:\WINDOWS\system32\adsiis.dll , adsiisex.dll,
iisext.dll , iismap.dll, iismui.dll , iisreset.exe , iisrstap.dll ,
iisRtl.dll , iissuba.dll, and spiisupd.exe if they still exist

k) do a registry search for 'FrontPage and examine any results found to
determine if they appear 'harmless' to a subsequent reinstall.

l) reboot ... there should be no startup errors. If there are note them and
try to resolve the error by inspecting the registry. There should be no IIS
entry under administrative tools, nor a Server extension entry. In addition,
if you open mmc and go to file>add/remove snap in>add the IIS and FP server
extensions should not be listed.

m) get a coffee

n) install IIS from add/remove programs/windows. Reboot.

o) install FrontPage

p) open fp ... go to file > new web and try to create a dummy web site of
any name. If you can and you can add and open a page, you're fixed. If not,
get a second coffee, or perhaps a scotch.

I've only had one machine (a win2000 box) that did not "take" the server
extensions. I tried to debug the problems for about a half-hour, but as I
had installed those immediately following an install of Windows 2000,
instead of dicking around further I decided that nuking the drive,
reformatting and reinstalling Windows and IIS again would be better in the
long run. Although a PITA, at least in this instance no data needed to be
preserved.

My last resort suggestion would be to do this, especially if you have no
problem with XP/IIS on other machines.

As I said earlier, others may have additional hints specific to service
packs you may have installed and the error message the extensions are
generating.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: Randy - a number of things.
:
: 1. I didn't know I could have subwebs under inetpub/wwwroot - I tjhought
: the XP Pro version of IIS was limited to one web - no? So I had basic web
: pages including a
: Default.htm directly in wwwroot.
:
: 2. I do get the same structure as you under Admin Tools > Server
Extensions
: Administrator (Front Page Server Extensions >MAIN (computer name)
: >/LM/W3SVC/1:. And yes the properties sheet for /LM/W3SVC/1: does have
: authoring checked. It shows version 6.0.2.5516, and I do wonder about
that.
: My internet host says they have FP2002 extensions installed, and when I
take
: a look there, the version of extensions is 5.something. Now, when I right
: click on LM/W3SVC?1: and choose All Tasks > Check Server Properties, I get
a
: message from Microsoft Server Extensions saying "The server administration
: programs and the server extensions on the web server are not compqatible.
: The administration program is too old to use with this server.", and
there's
: an OK box, which, when I click it, makes that message go away, and
: apparently the web check happens anyway, and a box "Check Web" has the
: message "Checking web http://", and in the box it says "No problems found
: End check 2/22/2004 5:18:44 PM" If I try to Recalculate web after right
: clicking, I get the same error message about the admin programs and the
: server extensions being incompatible. OK - now I right clicked on
: /LM/W3SVC/1: and chose New > Server Extensions Web, gave it a directory
name
: test, and name test, and the folder test was created beneath /LM/W3SVC/1:,
: and was identified as a subweb. When I right click on THAT, choose All
: Tasks > Check Server Extensions, I get the same error message about
: incompatible admin programs. server extensions. I remember once I did try
: to go from FP extensions version 200 to version 2002, and that may have
: something to do with this...
:
: 3. In your suggestion about testing using http://www.mvps.org/rgbfptest -
: where did you mean for me to create the test web - as a disk-based web
(i.e.
: C:/inetpub/wwwroot/something, or as http://localhost/something? In
FP2003,
: when I go New > One page web site, I have to browse to the location of the
: new web site, and I can browse to anywhere in My Network Places, or my
: computer, or whatever. If I browse to localhost, then try to enter a new
: name (i.e. a folder that doesn't exist), I get a creation error. If I
: browse to an existing subweb (test), from Web Site Templates then click
OK,
: I get a Web Site Setup dialog which wants me to create a local copy on my
: computer, edit the local copy, then publish changes to my Web server using
: Remote Site View. The default is WebDAV - if I click to use FP Server
: Extensions as the method, I get a message "You are unable to import a Web
: site from http://localhost/test. Verify the location and then try again."
: If I click WebDAV then Next, it gives a local copy default location in
: C:\Documents and Settings\Dan\My Documents\My Webs. Clicking next gives a
: congratulations from the wizard message, then I click Finish and I get a
new
: FP2003 window with Remote web site view, showing local as c:\Documents
etc.
: and Remote as http://localhost/test. Now I REALLY don't know if this is
: what I should have or not. I wanted to have a local (i.e. on my computer)
: version of my internet development site,but have server extensions working
: locally on the local copy, so that all the stuff that needs the extensions
: would work during building. I'm now confused... Any suggestions - VETY
: gratefully received.
:
: TIA,
: --
: Dan Ellis
: webbie(removethis)@preferredcountry.com
: : > If you can navigate to http://localhost/yourwebname and get the index
page
: > with all data and FP-specific items intact, the extensions are present
and
: > running so your difficulty lies elsewhere. I confess I am still
evaluating
: > the upgrade to 2003 (I use 2002 now), so can not comment on specific
menu
: > items or options that may be present in that version.
: >
: > If you can't navigate to http://localhost/yourwebname try substituting
: your
: > local machine name ... ie on my box http://vbnetdev/mywebname and
: > http://localhost/mywebname opens the same web.
: >
: > Another thought ... what happens when you go to control panel >
: > administrative tools > Server Extensions Administrator. On my box it
opens
: > FP server extensions, then my local machine name, then the server
: extension
: > folder /LM/W3SVC/1:. Tee property sheet for that item has the 'enable
: > authoring' option checked.
: >
: > Under the /LM/W3SVC/1: item are my local webs, each identified as a
: subweb,
: > a vdir, or nothing. For those identified as subwebs, selecting and
: > right-clicking presents a menu with All Tasks, one of which is Check
: Server
: > Extensions. Where the folder is not identified as a specific type (no
: > extensions applied), the option is Configure Server Extensions.
: >
: > You can try creating a new FP web by selecting the parent
(/LM/W3SVC/1:),
: > right-click and select New > Server Extensions Web, then create a new
: dummy
: > test web (any name, no spaces). If this web is successfully created and
: has
: > the classification subweb, and if you can subsequently open that web
using
: > FrontPage's File > Open Web option (typing the web as
: > http://localhost/dummywebname), and you can create and view pages
: containing
: > FP items (ie an include page), try repeating this same process
specifying
: > the web you're having problems with (if it's not listed as a subweb
: > already). You'll get a notice that the folder already exists ... say OK
: and
: > continue. Of course, you will want to back up the files first just in
: case.
: >
: > If it is a subweb, choose the Check Server Extensions option.
: >
: > --------------
: >
: > I've created a tiny web site (2 pages, 5 images) you can download to
check
: > the server extensions ... http://www.mvps.org/rgbfptest
: >
: > Go to New > Web > Empty web. Give it a name, then when created go to
File
: >
: > Import > From Web > and enter http://www.mvps.org/rgbfptest. It will
haul
: > the works down to create a local copy of the site. Open the index.html
: page
: > in FP and view the included content, and preview in the browser to
: determine
: > all works as it should.
: >
: > --
: >
: > Randy Birch
: > MVP Visual Basic
: > http://vbnet.mvps.org/
: > Please respond only to the newsgroups so all can benefit.
: >
: >
: >
: >
:
:
 
R

Ronx

Is "(I have version 6.0.2.5516)" a typo? As far as I know, FPSE 6.xxx are
Windows Sharepoint Services, which do not run on IIS5.1 - they need Win2003
and IIS6.

FPSE2000 are 4.xxx
FPSE2002 are 5.xxx
 
D

Dan

No, Ron, no typo. IIS is version 5.1, Server extensions 6.0.2.5516 is what
is reported by right-clicking on my top level local web site and choosing
Server Extensions. Therein may lie the problem. I followed directions from
Jim Buyens' Inside Out (FP2003 - in the Appendices) for getting the 2002
extensions. By that time, I had IIS and Extensions for FP2000 installed,
but I did uninstall the FP 2000 extensions before installing what I thought
was FP2002 extensions. Must admit I have had some hints from prompts etc.
that Shaerpoint services may be involved... Hmmm. Somewhere there was a
piece telling me how I could find out which version was actually installed -
involved looking for different versions of a dll I think - anyway, when I
looked, I had both.

More later - and thanks a million for your help - I really appreciate it.
 
D

Dan

Many thanks Randy for your involvement - I really appreciate it. As you'll
see from my reply to Ronx, it look as if somehow I have Sharepoint Services
extensions installed, so before I do anything else much (and I have to work
today!), I'll try to figure out the best way to remove all trace of those,
then get FP2002 extensions installed.

More later - have a good day.
--
Dan Ellis
webbie(removethis)@preferredcountry.com
Randy Birch said:
1) I've never used the default folder under wwwroot for my pages ... I
always create new webs using File>New Web, and enter the name. When browsing
the local machine you just add the web to the end, ie
http://localhost/myweb/, ensuring the default file name for the opening file
is as expected under IIS config (eg default.htm). These webs you create ....
ie myweb ... are subwebs in relation to the wwwroot web. You can have as
many as you want ... I've got 20 or so for different projects on the go.

2) My IIS version is 5.1. My server extensions (at least under properties
for /LM/W3SVC/1 I assume this is the SE version number) are 4.0.2.5322. I
suspect this version is reported because I don't have XP SPs on this
machine --- I'm behind a hardware firewall and virus-protected.

This page talks about your server extension error, though in the context of
http://support.microsoft.com/default.aspx?scid=kb;EN-US;823376.
Might find something that clicks.

There is something definitely whacky with your setup, and it may have to do
with service packs you have that I don't have installed. Perhaps others can
chime in here if there are issues, or if they have further suggestions
concerning your error.

If not, there is the second last resort ... following a backup in case
things go awry, I would do the following in an attempt to resolve the
problem:

a) open Administrative Programs > Internet Information Services, and
right-click on 'default web site', ... there you should have an option under
Tasks to 'Remove server extensions". Do so.

b) uninstall FrontPage

c) through control panes>add/remove programs/windows, uninstall IIS.

d) reboot

e) ensure all folders directories under C:\Program Files\microsoft FrontPage
are empty, and if not, delete it. Also delete the entire inetpub folder --
this will delete your local ftp and wwwroot folder and all contents.

f) delete the FrontPage temp folders under your temp folder(s). I have 2
... one under c:\temp, where my environment variable points as the tmp
location, and one under c:\windows\temp.

g) delete C:\Documents and Settings\birchr\Application
Data\Microsoft\FrontPage

h) rename the folder C:\WINDOWS\system32\inetsrv if it still exists

i) delete C:\WINDOWS\inf\iis.inf and C:\WINDOWS\inf\iis.pnf if it still
exists

j) delete or rename C:\WINDOWS\system32\adsiis.dll , adsiisex.dll,
iisext.dll , iismap.dll, iismui.dll , iisreset.exe , iisrstap.dll ,
iisRtl.dll , iissuba.dll, and spiisupd.exe if they still exist

k) do a registry search for 'FrontPage and examine any results found to
determine if they appear 'harmless' to a subsequent reinstall.

l) reboot ... there should be no startup errors. If there are note them and
try to resolve the error by inspecting the registry. There should be no IIS
entry under administrative tools, nor a Server extension entry. In addition,
if you open mmc and go to file>add/remove snap in>add the IIS and FP server
extensions should not be listed.

m) get a coffee

n) install IIS from add/remove programs/windows. Reboot.

o) install FrontPage

p) open fp ... go to file > new web and try to create a dummy web site of
any name. If you can and you can add and open a page, you're fixed. If not,
get a second coffee, or perhaps a scotch.

I've only had one machine (a win2000 box) that did not "take" the server
extensions. I tried to debug the problems for about a half-hour, but as I
had installed those immediately following an install of Windows 2000,
instead of dicking around further I decided that nuking the drive,
reformatting and reinstalling Windows and IIS again would be better in the
long run. Although a PITA, at least in this instance no data needed to be
preserved.

My last resort suggestion would be to do this, especially if you have no
problem with XP/IIS on other machines.

As I said earlier, others may have additional hints specific to service
packs you may have installed and the error message the extensions are
generating.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: Randy - a number of things.
:
: 1. I didn't know I could have subwebs under inetpub/wwwroot - I tjhought
: the XP Pro version of IIS was limited to one web - no? So I had basic web
: pages including a
: Default.htm directly in wwwroot.
:
: 2. I do get the same structure as you under Admin Tools > Server
Extensions
: Administrator (Front Page Server Extensions >MAIN (computer name)
: >/LM/W3SVC/1:. And yes the properties sheet for /LM/W3SVC/1: does have
: authoring checked. It shows version 6.0.2.5516, and I do wonder about
that.
: My internet host says they have FP2002 extensions installed, and when I
take
: a look there, the version of extensions is 5.something. Now, when I right
: click on LM/W3SVC?1: and choose All Tasks > Check Server Properties, I get
a
: message from Microsoft Server Extensions saying "The server administration
: programs and the server extensions on the web server are not compqatible.
: The administration program is too old to use with this server.", and
there's
: an OK box, which, when I click it, makes that message go away, and
: apparently the web check happens anyway, and a box "Check Web" has the
: message "Checking web http://", and in the box it says "No problems found
: End check 2/22/2004 5:18:44 PM" If I try to Recalculate web after right
: clicking, I get the same error message about the admin programs and the
: server extensions being incompatible. OK - now I right clicked on
: /LM/W3SVC/1: and chose New > Server Extensions Web, gave it a directory
name
: test, and name test, and the folder test was created beneath /LM/W3SVC/1:,
: and was identified as a subweb. When I right click on THAT, choose All
: Tasks > Check Server Extensions, I get the same error message about
: incompatible admin programs. server extensions. I remember once I did try
: to go from FP extensions version 200 to version 2002, and that may have
: something to do with this...
:
: 3. In your suggestion about testing using
http://www.mvps.org/rgbfptest -
 
D

Dan

Hi Randy - worked solidly from 4pm to 1 am yesterday trying to remove all
traces of FP IIS and FP extensions as in your detailed help above. BTW,
Add/Remove Windows components won't start without iis.inf, so I put that
back, and the pnf. Reinstalled IIS, installed FP 2002 extensions from
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservext/html/fpse02win.asp,
that wouldn't work at all, so went through it all again to get rid of FP2002
extensions and IIS, re-installed IIS - this time with FP 2000 extensions -
then FP2003 - lo and behold I can't open a new web locally under /localhost.
Tries to create it, then I get an error message "The web server at
http://MAIN does not appear to have Windows Sharepoint Services installed."
So - I'm gonna roll back to before I started yesterday, try to get my
production web finished and running, then I'll nuke the drive and start
afresh - all those apps to install! (Sob!) :)

Thanks for all your help - REALLY appreciate it.

Dan Ellis
webbie(removethis)@preferredcountry.com

--
Dan Ellis
webbie(removethis)@preferredcountry.com
Randy Birch said:
1) I've never used the default folder under wwwroot for my pages ... I
always create new webs using File>New Web, and enter the name. When browsing
the local machine you just add the web to the end, ie
http://localhost/myweb/, ensuring the default file name for the opening file
is as expected under IIS config (eg default.htm). These webs you create ....
ie myweb ... are subwebs in relation to the wwwroot web. You can have as
many as you want ... I've got 20 or so for different projects on the go.

2) My IIS version is 5.1. My server extensions (at least under properties
for /LM/W3SVC/1 I assume this is the SE version number) are 4.0.2.5322. I
suspect this version is reported because I don't have XP SPs on this
machine --- I'm behind a hardware firewall and virus-protected.

This page talks about your server extension error, though in the context of
http://support.microsoft.com/default.aspx?scid=kb;EN-US;823376.
Might find something that clicks.

There is something definitely whacky with your setup, and it may have to do
with service packs you have that I don't have installed. Perhaps others can
chime in here if there are issues, or if they have further suggestions
concerning your error.

If not, there is the second last resort ... following a backup in case
things go awry, I would do the following in an attempt to resolve the
problem:

a) open Administrative Programs > Internet Information Services, and
right-click on 'default web site', ... there you should have an option under
Tasks to 'Remove server extensions". Do so.

b) uninstall FrontPage

c) through control panes>add/remove programs/windows, uninstall IIS.

d) reboot

e) ensure all folders directories under C:\Program Files\microsoft FrontPage
are empty, and if not, delete it. Also delete the entire inetpub folder --
this will delete your local ftp and wwwroot folder and all contents.

f) delete the FrontPage temp folders under your temp folder(s). I have 2
... one under c:\temp, where my environment variable points as the tmp
location, and one under c:\windows\temp.

g) delete C:\Documents and Settings\birchr\Application
Data\Microsoft\FrontPage

h) rename the folder C:\WINDOWS\system32\inetsrv if it still exists

i) delete C:\WINDOWS\inf\iis.inf and C:\WINDOWS\inf\iis.pnf if it still
exists

j) delete or rename C:\WINDOWS\system32\adsiis.dll , adsiisex.dll,
iisext.dll , iismap.dll, iismui.dll , iisreset.exe , iisrstap.dll ,
iisRtl.dll , iissuba.dll, and spiisupd.exe if they still exist

k) do a registry search for 'FrontPage and examine any results found to
determine if they appear 'harmless' to a subsequent reinstall.

l) reboot ... there should be no startup errors. If there are note them and
try to resolve the error by inspecting the registry. There should be no IIS
entry under administrative tools, nor a Server extension entry. In addition,
if you open mmc and go to file>add/remove snap in>add the IIS and FP server
extensions should not be listed.

m) get a coffee

n) install IIS from add/remove programs/windows. Reboot.

o) install FrontPage

p) open fp ... go to file > new web and try to create a dummy web site of
any name. If you can and you can add and open a page, you're fixed. If not,
get a second coffee, or perhaps a scotch.

I've only had one machine (a win2000 box) that did not "take" the server
extensions. I tried to debug the problems for about a half-hour, but as I
had installed those immediately following an install of Windows 2000,
instead of dicking around further I decided that nuking the drive,
reformatting and reinstalling Windows and IIS again would be better in the
long run. Although a PITA, at least in this instance no data needed to be
preserved.

My last resort suggestion would be to do this, especially if you have no
problem with XP/IIS on other machines.

As I said earlier, others may have additional hints specific to service
packs you may have installed and the error message the extensions are
generating.

--

Randy Birch
MVP Visual Basic
http://vbnet.mvps.org/
Please respond only to the newsgroups so all can benefit.


: Randy - a number of things.
:
: 1. I didn't know I could have subwebs under inetpub/wwwroot - I tjhought
: the XP Pro version of IIS was limited to one web - no? So I had basic web
: pages including a
: Default.htm directly in wwwroot.
:
: 2. I do get the same structure as you under Admin Tools > Server
Extensions
: Administrator (Front Page Server Extensions >MAIN (computer name)
: >/LM/W3SVC/1:. And yes the properties sheet for /LM/W3SVC/1: does have
: authoring checked. It shows version 6.0.2.5516, and I do wonder about
that.
: My internet host says they have FP2002 extensions installed, and when I
take
: a look there, the version of extensions is 5.something. Now, when I right
: click on LM/W3SVC?1: and choose All Tasks > Check Server Properties, I get
a
: message from Microsoft Server Extensions saying "The server administration
: programs and the server extensions on the web server are not compqatible.
: The administration program is too old to use with this server.", and
there's
: an OK box, which, when I click it, makes that message go away, and
: apparently the web check happens anyway, and a box "Check Web" has the
: message "Checking web http://", and in the box it says "No problems found
: End check 2/22/2004 5:18:44 PM" If I try to Recalculate web after right
: clicking, I get the same error message about the admin programs and the
: server extensions being incompatible. OK - now I right clicked on
: /LM/W3SVC/1: and chose New > Server Extensions Web, gave it a directory
name
: test, and name test, and the folder test was created beneath /LM/W3SVC/1:,
: and was identified as a subweb. When I right click on THAT, choose All
: Tasks > Check Server Extensions, I get the same error message about
: incompatible admin programs. server extensions. I remember once I did try
: to go from FP extensions version 200 to version 2002, and that may have
: something to do with this...
:
: 3. In your suggestion about testing using
http://www.mvps.org/rgbfptest -
 
S

Steve Easton

Not dumb, you can publish to a local pc with IIS and extensions. However it's easier to just create
the web in IIS

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top