Unable to publish via http, broken site

[Mike Edwards]

After my post yesterday about inability to show database results, further
inspection found underlying problems.

Running IIS 5.1 on WinXP Professional
FP Server Extensions 2002
FP 2000
Website database is Jet (MS Access .mdb) in the fpdb folder
Windows update installed IE7 (which broke my machine)
I uninstalled IE7 and rolled back to IE6

If I try to publish the web site via http, I get an error message "The
server you are publishing to does not have the Front Page Server Extensions
installed, and therefore does not support publishing via HTTP. To continue
publishing, specify a location that will work with FTP."

I get the same message whether I publish to http://localhost or
http://www.kingmuddfish.com/.

I go to Server Extensions Manager FPMMC and it shows Microsoft Server
Extensions in the snap in. If I try to add FrontPage Server Extensions -- it
shows up as a second instance of Microsoft Server Extensions.

I go to Internet Information Services manager, and it shows the default web
site as "(Stopped)". I choose menu option to start, but I get an error
message "The Service did not respond to the start or control request in a
timely fashion."

Does anyone see possible causes? I can't figure this one out.

Sincerely,
Mike Edwards

 

[Mike Edwards]

Also, if I try to publish the site directly to the web subdirectory, I get
an error message "The folder "C:\Inetpub\wwwroot" is contained by a server
based Web. To access the folder, you must use the http://url for the web
server."

I'm pretty much out of business at this point.

I haven't found anything addressing this on MSDN.

Mike

 

[Thomas A. Rowe]

Have you tried removing the Extensions, then IIS, then rebooting, then re-installing IIS with the
FP2000 extensions from the Windows XP Pro CD, then configuring and testing the FP2002 extensions,
and if everything is ok, then upgrade to the FP2002 extensions?

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

 

[Mike Edwards]

I removed IIS, rebooted, reinstalled IIS with the FP2000 extensions from the
XP CD.

Same results as before.

When I open the IIS console, it says "Error" "Default Web Site (Stopped)"
and when I try to start it, it returns a different error message now
"Unexpected error 0x8ffe2740 occurred."

When I try to publish via http -- the error message said there was no
website at that location. I then copied the web site directly to the machine
folder and it published, but the behavior of the asp pages is the same where
either no records are displayed or I get the "save or open" dialog box. If I
tell it to open, it doesn't.

If I try to update the published web site via http, I get the error message
that says the front page extensions are not installed and to use FTP. If I
try to update via machine folder -- it says there is a website at that
location and I have to use http.

I opened up the Services console to make sure IIS showed up and noticed that
some Apache services were running -- aparently some stuff got installed when
I installed MySQL. I killed the Apache services, the error message
disappeared from the IIS Console Default Web Site. I started the Default
Website successfully, and now the asp pages work correctly.

However, I cannot update the site via Frontpage. If I use
http://www.kingmuddfish.com -- it says Frontpage Server extensions are not
installed. If I use http://localhost method -- it says it cannot find a web
server. If I use file:///C:/Inetpub/wwwroot it says it is a web site and I
must use http.

Has anyone had this problem before?

Thanks,
Mike Edwards

 

[Thomas A. Rowe]

You have to first get the default web site running, for this I suggest your post to the Windows or
IIS newsgroup, before you can extend the web with FP extensions

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

 

[Mike Edwards]

Thanks Tom,

The site was working, it was authentication that was screwed up.

I found the answer by looking on the frontpage.exensions news group.

The solution is in this KB http://support.microsoft.com/kb/896861

I did the regedit and all works perfectly.

Sincerely,
Mike Edwards