Can not publish after reinstall



I'm been using FP2000 for 2-3 years. My laptop hard drive crashed and I've
restored the FP application and web (as in the past under the default
inetpub/wwwroot) on the newly installed replacement drive. Unfortunately I
don't remember all the settings etc from the original setup (FP, IIS, etc)
that was working great before the crash.

As part of the restore I "re"-installed FP extensions 2002 ( from
the MS web site. The web host has FP entensions turned on (FP-2002 ext.also).

I've made changes to a couple of pages but unable to successfully publish
since the restore. The Publish Web pop-up window is displayed after clicking
on the publish button and I enter "" as the
publish to location. After OK the site logon popup window is displayed and I
enter our web site name and webmaster's password. A progress pop-up window
shows the local pages listing message followed by host pages begin listed
message. The pop-up window closes without any message of pages overwritten or
published and Front Page itself closes out/terminates without any action/info.

Any thoughts on what where to start researching?

Jim T.


You might want to check what extensions you have installed:

The only extensions available for download from Microsoft are FP2002
extensions for 64bit operating systems.
Extensions for 32 bit OS have not been available for download for several
years (except for IIS7).
Extensions for Windows 2003 (32bit) server are on the Windows 2003 CD.
Extensions for Vista (IIS7) are downloaded from, not from

Extensions version are FP 2000 extensions (the leading 4
denotes 2000) - of course, the 4 may be a typo.

Start researching by looking at the Event Logs for errors.


The extensions version is displayed on the Front Page tool/web
settings/general tab. In the control panel add/remove programs window the
list has Microsoft FrontPage Server Extensions 2002. Clicking on the support
info link the version is listed as 10.0.2701.0. I'm not sure what version my
host is running other than it is a 2002 version.

Additional info
IIS ver. 5.1
MMC console ver 3.0

Also on the FP web settings show
Server Version: "No server currently in use"

I believe I set up a virtual server on my pre-crash disk but I don't
remember the details/settings.

Would any of the above be part of the problem? You indicated to research the
event error log. I tried publishing again and looked at the event log in the
Adm Tools/Event Viewer. Is this the error viewer you were talking about? The
viewer did not list any errors for the time I published or any entries that
looks like it would be associated with the FP publish event.

Jim T.


FrontPage extensions versions:
3.x.x.xxxx = FP98
4.x.x.xxxx = FP2000
5.x.x.xxxx = FP2002
6.x.x.xxxx = either FP2003 run time extensions (used only in disc based
webs) OR SharePoint Services

The version number 10.0.2710 is about right for a (possibly old) version
for Win XP - the current version for Windows 2003 is 10.0.6790

Version coupled with "No server in use" indicates you have a
disc based web open - opened using the file system location such as

This could have a bearing on the Publishing failure if the web was created
as a server based web - it should be opened as http://localhost.

Also, are you running a 64bit version of Windows XP? If not, when did you
download the extensions? - as I said earlier, they have not been available
on Microsoft's site for several years for 32bit systems.



Thanks for the help. I'm finding it difficult to research my problems with
my mixed bag of systems. I'm running XP pro SP3. The crashed disk was SP2.

My web for my town was created 3 years ago so my memory is not the greatest
of all the details. You are correct in that the web is server based. If
memory serves me with XP you can not use the Personal Web Server that comes
with FP-2000. I've also looked at the FP help on converting the disk-based
web to the server based web but the help references the PWS.

Any suggestion on setting up a server in XP pro and converting the web to
the server?The old system also had Sharepoint installed. Is this needed?

Jim T.

PS: learned my lesson; I've installed image back-up software instead of just
file back ups.

Steve Easton

You can install Internet Information Services using the XP Pro CD,
it is done via Control Panel Add or Remove programs, add or remove windows features.
There is also a version of the extensions on the CD.

When you are in the administrators portion of the control panel, although you see SharePoint Services, it is
FrontPage Extensions.


Steve Easton
Microsoft MVP FrontPage
FP Cleaner
Hit Me FP


Current Config.
IIS version 5.1 installed
MMC 3.0 / Server Extension Adm. version 5.02.4803

After my hard disk crash and new drive installed with XP Pro (update to SP3)
I copied the wwwroot and subfolders from a CD back up to the C:\Inetpub
directory. This evidently made the web a disk based instead of the previously
configured web-based folders. I've tried to follow the FP help to convert
these folder to web based. However the option is not available for the
wwwroot folder and trying to convert any of the subfolders results in 2
warning/error popup windows. The first indicate some of the hyperlink/nav.
bar my be removed and the second is an error window
"Server error: Unable to create a disk-based web at
C:\Inetpub\wwwroot\photos" because its parent web would not be a disk based
web. Create the disk based web elsewhere, outside of you web server's
document hierarchy".

Somehow as a newbie 3 years ago I stumbled through making it work but with
recovering from the disk crash I'm not having same kind of luck.

Do I need to copy the web folder to a location outside the wwwroot folder
and then convert those folders to web-base? Then how do these folders get to
wwwroot as web-base? Where do I find info on "localhost"?

Jim T.


The errors are consistent with opening a server based web as a disc based
web. You already have have the server based web in place, but you must
open it in FrontPage using a http:// URL, not a file system location.

Open the Microsoft SharePoint Administrator from Control
Panel->Administration tools and run a Server Health Check on the default
web site..

Run Steve's FP Cleaner ( and
delete the hidden Web Cache Files, and Hidden Temporary Files.

Then ALWAYS open the website (and subwebs, if any) using http://localhost -
NEVER use C:\inetpub\wwwroot.


Thanks to all for your continued support. I was in IT for over 20 years
(Application Dev. & Mgmt) and the recovery from my hard drive failure has
been one of the most frustrating and challenging I've ever faced. Data
recovery is a piece of cake; settings etc. not so lucky. As a newbie (guess I
still am) the rebuild has been a harder and longer learning curve that the
original setup.

Where I'm at.
1. Removed FP extensions and reinstalled FP-2002 extension successfully
( The FP-2002 configuration screen is now available and tested

2. Moved the files and folders from c:\Inetpub\wwwroot to an external drive.
I can successfully open this web as a disk-based web.

3. In IIS (5.1) renamed the Default Web to stonehamme (same name as the www
site) under:
- JIMT (local computer)
- Web Sites
- stonehamme

This menu also now show the following sub-folders
+ IISHelp
+ Printers
+ vti_bin
+ _sharepoint

However I do not see an action/menu option to create an empty web in IIS.
There is an option for creating a virtual directory. Is this what I should do?
Or should I create a new web in wwwroot using FP and then publish to it?

Many Thanks Again!
Jim T.

Steve Easton

You shouldn't have renamed default web site in IIS, that needs to be there.

How I do it:
Right click My computer and select Manage.
Click the Plus signs by services and applications, then Internet Information services, then Web sites.

Default web site will be listed.
Right click Default Web Site and scroll to New.
Select Server Extensions 2002 Web.
Follow the instructions
When done you can access this new web via http://localhost/websitename

However you might need to edit / change permissions in IIS.

So, right click Default Web Site and select Properties.
Click the Directory security tab.
Click the Edit Button.
On the Authentication Methods dialog, at the very bottom check: Integrated Windows authentication.
Click OK all of the way out.

Stop and Restart IIS, or simply reboot the machine.


Steve Easton
Microsoft MVP FrontPage
FP Cleaner
Hit Me FP


Continued thanks. A step closer but ...

I reset the web site to the original name of Default Web

I then followed you procedures below; however once on the on the IIS new
menu the only option is to create a sub-web. Should I be able to create a web
or just a sub-web?

I created a sub-web named stonehamme which created a folder under wwwroot
with that name. After stopping and starting the server exited and rebooted. I
then opened the files/folders on the external drive (as a disk web) with the
open web option in FP. Clicked on the publish icon and got the publish web
popup window where I entered:
http://localhost/stonehamme. The progress showed the pages being listed.
After maybe 30 seconds the FP application did crash but simple closed without
completing the publish.

Currently the wwwroot directory has:
+ stonehamme

The subdirectories under stonehamme are empty except for _vti_pvt which has
some of the files from the external drive

I'm totally lost. Would it be better somehow start over. Also on the old
disk all of the files and folders was directly under www.root. Don't remember
how I did it but there were no sub-webs or "other folders".

Any help will be greatly appreciated. One of the best features for me in FP
is the change management of the publishing action.

Jim T.

Steve Easton

When browsing via the file system you will see C:\Inetpub\wwwroot
C:\Inetpub\wwwroot is the same as Default Web site when viewed via computer management.

When opening it via front page, http://localhost is the same as C:\Inetpub\wwwroot.

If you don't have the option to create a new "extensions web" when right clicking Default Web site in computer
management, the extensions are not properly installed.


Steve Easton
Microsoft MVP FrontPage
FP Cleaner
Hit Me FP



Thanks for the help

Save you some time, see last two paragraph first (below the *** marker).

I followed your instructions opening FP
1. file, new, web
2. change the location from my documents \ my web to

FP created the testweb and in the folder list pane the newly created
web is shown as +http://localhost/testweb

In windows explorer the testweb folder is under wwwroot and is
at the same level as stonehamme. Also in explorer the testweb
has the same subfolders and files as stonehamme.

I then tried to publish to testweb and the same results as stonehamme,
the "listing pages in ..." ran, in this case just a few seconds, and then
FP close, no warnings, no errors no etc.

Some odds-n-ends
1) In the external disk web in the _vti_pvt folder there is a file named
frontpg.lck. Is this a FP lock such that this file have to be renamed or
deleted in order to publish for the first time?

2) When using the open web in FP the following folders reflect the small
globe on the folder (signifying a web folder?)

3) When using the open web in FP the open web dialog window has:

Look in: "Web Folders" (drop down list places this under My Computer)
Selection list: "localhost"
Folder Name: http://localhost/

Double click on localhost in selection box and the following is displayed
private (folder)
images (folder)
stonehamme (web folder)
testweb (web folder)

Click on OK and the web (wwwroot) opens with the above folders in the folder

Closing FP and selecting http;//localhost/stonehamme opens that web and
two folders "_private" and "images".
Same for testweb

All three are blank webs at this point (i.e. folder no pages)

One of the problems may be I opened the web as a disk base web on the
drive and did tools/web settings. The FP server extensions on this is
(and obviously no server running). However opening the http://localhost webs
the FP extension is version 5.02.6738.

So since there is a difference between the two; is there a way to resolve?
Is there a way to set the extensions on the external disk web to the 5.02
I hate to think of opening the stonehamme web and importing all the files and
folders if that is even possible.

Continued Thanks
Jim T.


In Windows XP Pro you cannot open a new extensions web in IIS - there is
only one web site. You can create subwebs.
In FrontPage you can create new websites, which will be subwebs of the
default web in IIS.


The extensions versions are correct and do not need to be changed.
is correct for a disc-based web running under FP2000, is correct for FP 2002 extensions on IIS (and also for disc-based web
running on FP2002).

Since you "moved" the original site to an external disc, there may be a
problem with the _vti_* folder contents.
Open the web in FrontPage and run Tools->Recalculate Hyperlinks. See if
this makes a difference in publishing to IIS.

If not, then there is a drastic step:
With FrontPage closed, use Windows explorer to delete every folder in the
site on the external disc with names starting _vti - note that there is a
_vti_cnf folder in almost every folder in the web.
Then in FrontPage use File->Open Web
Browse to the folder containing the web site and click open - this folder
will no longer have the blue globe on it.
FrontPage will add back the _vti* folders.
Try publishing again.



Thanks for hanging in there with me. I followed your procedure of
recalculating the hyperlinks and then republishing. No go, same problem; FP
starts listing the files on the disk base web and after a time FP closes
without any updates as far as I can tell. The folders on web-based web
consist of:
but no files under the folders except _vti_pvt. The disk-based _vti_pvt
folder has more files than the web-based folder.

If you are still up for the challenge, I'll try another approach you might

The last ditch choice, I assume, is to create the folders in the web-based
web and import the files into the appropriate folders. I have about 25
folders under the root and and probably and average of 3 subfolders under
each or about 75-100 folders. I assume importing function, although time
consuming, will work to import all the files into the appropriate web
folders. Do you see any pit-falls in this approach if no other option works?

Jim T.


The contents of the _vti_* folders are different for each web site, and for
each type of website - even if the pages and images are identical.
FrontPAge NEVER publishes the _vti* folders - they are unique to the
website they are in, and this is why they should never be copied from site
to site, and why I keep saying these files *may* be causing your problems.
It could be something else entirely.

I recently had a problem with a web that crashed Expression Web when being
published - similar problem to yours, except it was a crash.
I resorted to copying the web to another location on the hard disc,
deleting all the _vti_* files. Opening it in EW, then publishing it back
to its original location. Cured the problem.

I explained the method in a previous post in this thread, using your
external drive.

If you going the Import route, I would open FrontPage and Windows explorer
and tile them so both can be seen at once.
In FrontPage, open the web site you wish to move all the files to in Folder
In Windows Explorer open the web site on your external drive - it would be
best to delete all the _vt* folders.
Drag the folders one by one from Windows Explorer to the FrontPage window.
This is the same as Importing, but easier to do. FrontPage should warn you
about any _vti_* folder that may be caught up.
DO NOT move any _vti* folders such as _cti_pvt etc. or you will be back to
square one again.
You will have to redo the navigation.


Thank to all who helped me recover from my disk crash. I was not successful
in using the publish meithod (deleting _vit's, etic). I'm using the import
function in the web-based version to load the folders and files from the
external drive. So far so good.
A few little glitches along the way but I'm able to open the disk-based web
to verify image locations etc.

I have another question but will start a new thread for it.

Thanks again to all
Jim T.

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