server administration page

[Harry]

I am running XP pro and IIS 6 with FP 2002 extensions
installed. When I try to administer my site using the
sharepoint administrator I get to the
http://.../_sharepoint/fpadmdll.dll page ok, but when I
try to administer the server to extend it the
http://.../_vti_bin/_vti_adm/fpadmdll.dll?
page=webadmin.htm page does not load.
This means that I am unable to use the FP extensions and
hence can't test the functional pages.
Can anybody help?

 

[Jim Buyens]

Define "does not load". For example:

o Are you getting a 404 Not Found?
o A 500 Internal Server Error?
o An Access Denied error?
o Something else?

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

Sorry Jim,
I am getting a 404 Not found message.
I am actually running IIS 5.1 not 6 as previously stated.
I have reinstalled the extensions and upon completion I
get the message "The server Administration programs and
the server extensions on the web server are not
compatible. The Administration program is too old to use
with this server"
Yet I get a message saying the extensions were installed
successfully.
Also when I select the option in IIS to open my default
website with FP I get told that I need to have the FP
client installed, which I have!
I am totally baffled.

 

[Tom Pepper Willett]

The server administration program and the server extensions on the Web
server are not compatible. The server is too old to use with this
administration program:

Try this: Start | Control Panel | Administrative Tools | Microsoft
SharePoint Administrator

It brings up a web based FrontPage Server Extensions 2002 Server
Administration page.

Also see:
http://support.microsoft.com/?kbid=319476
--
Tom Pepper Willett
Microsoft MVP - FrontPage
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
http://msdn.microsoft.com/frontpage
-----

 

[Guest]

Thanks Tom,
If you read my original message you will see that I when
I use the sharepoint administrator page and click on my
default website I get the 404 Not found error.

 

[Jim Buyens]

Somehow, you've ended up with an incompatible set of IIS and FPSE
software.

I would try first removing any and all versions of the FrontPage
Server Extensions, then removing IIS. If, along the way, you get
any dialog boxes asking whether to retain something, choose not
to retain it.

Then, install IIS from Control Panel, Add/Remove Programs,
Add/Remove Windows components, but *don't* install the
included server extensions. Instead, after IIS setup completes,
install the extensions from:

http://msdn.microsoft.com/library/en-us/dnservext/html/fpse02win.asp

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

Thanks Jim,
I have done this and it appears to work.
It seems that I had the previous extensions supplied with
IIS installed and they were causing conflicts.
One further question:
Do I need to point my IIS default website to a location
if I publish my site to the server?
eg default website = d:\website
and I publish to http://localhost
Is the default website location where the published site
will be stored?

Thanks for your help

 

[Jim Buyens]

Thanks Jim,
I have done this and it appears to work.
It seems that I had the previous extensions supplied with
IIS installed and they were causing conflicts.
One further question:
Do I need to point my IIS default website to a location
if I publish my site to the server?
eg default website = d:\website
and I publish to http://localhost
Is the default website location where the published site
will be stored?

If you publish d:\website to http://localhost, the files will end up
at c:\inetpub\wwwroot\.

If you publish d:\website to http://localhost/website, the files will
end up at c:\inetpub\wwwroot\website.

However, it's best not to think too much about physical file locations
like c:\inetpub\wwwroot\website, and to work through the http://
address instead. Messing with a server-based FrontPage Web site via
the file system is one of the surest ways to get yourself in trouble.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------