migration to new server

[Lynn]

I developed a working website on my old server in Windows 2000 Professional
using FP 2000 components such as search, submit forms, hit counter, forum,
etc. I just purchased a new Dell Windows 2003 (small business server,
standard edition). I use FP 2000 on both machines. I used FP to publish the
website from the old server (now the client) to the new server, but now none
of the FP 2000 components work on the new server (even though all of them
worked fine on the old machine). [However, all of my .asp pages written in
VB Script work fine, and the html links all work on the new server.] The
Microsoft FrontPage 2000 Server Extensions Resource Kit states that a FP
extended web developed on a client computer should be published to the web
server using the Publish Web command in the FP client. It also states that
when you do this, "all FP-based components in the FP extended web are
regenerated to take advantage of platform-specific functionality." I did all
this, but the FP components do not work. I checked that the FP server
extensions were installed (shtml.dll in several places, as expected). The FP
server extensions appear to be disabled. Do I need to enable something? Help!

 

[Thomas A. Rowe]

Did you install the FP extensions and then configure the site to use them. Windows 2003 Server comes
locked down, meaning functions/services, etc. that worked under Windows 2000 must now be enabled.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================