|
Home > Archive > FrontPage Server Extensions for Windows > December 2005 > How do I enable the FP SE?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How do I enable the FP SE?
|
|
|
| I developed an extended 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 SBS 2003. 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
appear to be disabled. I checked that the FP server extensions were
installed (shtml.dll in several places, as expected). Do I need to enable
something?
I noticed that the default web on the new server does not have some of the
files in the C:\inetpub\www.root directory, particularly the _vti_inf.html
file. Should I put this file (and maybe the other files and folders from
www.root) in the default web, and then republish to the new server?
--
Lynn Hart
| |
| Thomas A. Rowe 2005-12-21, 8:49 pm |
| Do not copy any of the extension file between machines, the extensions on the server will manage the
files on the server. You new server is running the FP2002 extensions that are specific for the OS,
and you can not update or change them.
--
========================================
======
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.
========================================
======
"Lynn" <Lynn@discussions.microsoft.com> wrote in message
news:8D220584-393B-4F29-BDD9-A448B2EEBBED@microsoft.com...
>I developed an extended 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 SBS 2003. 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
> appear to be disabled. I checked that the FP server extensions were
> installed (shtml.dll in several places, as expected). Do I need to enable
> something?
> I noticed that the default web on the new server does not have some of the
> files in the C:\inetpub\www.root directory, particularly the _vti_inf.html
> file. Should I put this file (and maybe the other files and folders from
> www.root) in the default web, and then republish to the new server?
> --
> Lynn Hart
| |
|
| I followed your advice. I copied the wwwroot files on the new server into
the (initially empty) Default Web Site home directory on the new server, then
published the old server to the new. The FP SE still don't work. To double
check, I added a hit counter on a page on the new server, but it doesn't
update. I just don't have access to the FP SE. I noticed an odd thing,
however. When I check "Properties" of every directory on C:, the "Read only"
attribute has a greyed-out check mark by it. I clear the check mark, apply
the change, ask that it apply to all sub-folders, then exit. I open the
directory again, and the greyed-out check mark is back! If I make a "new
folder", it also has the greyed-out "Read only" property, and this is the
case for all directories on D:, my other drive. This is obviously a global
setting that I don't know how to turn off, and might be part of the problem,
since the working website on the old server does not have these properties.
Can you help? Any other suggestions would be appreciated.
--
Lynn Hart
"Thomas A. Rowe" wrote:
> Do not copy any of the extension file between machines, the extensions on the server will manage the
> files on the server. You new server is running the FP2002 extensions that are specific for the OS,
> and you can not update or change them.
>
> --
> ========================================
======
> 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.
> ========================================
======
>
> "Lynn" <Lynn@discussions.microsoft.com> wrote in message
> news:8D220584-393B-4F29-BDD9-A448B2EEBBED@microsoft.com...
>
>
>
| |
| Thomas A. Rowe 2005-12-23, 5:54 pm |
| You didn't follow my advice as I did NOT tell you to copy anything from the old machine to the new
machine. You must configure the extensions on the new machine, and then you need to publish the web
from the old machine to the new machine via FP's http mode.
--
========================================
======
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.
========================================
======
"Lynn" <Lynn@discussions.microsoft.com> wrote in message
news:2F67EB93-5C77-46BE-958E-527A893B74D9@microsoft.com...[vbcol=seagreen]
>I followed your advice. I copied the wwwroot files on the new server into
> the (initially empty) Default Web Site home directory on the new server, then
> published the old server to the new. The FP SE still don't work. To double
> check, I added a hit counter on a page on the new server, but it doesn't
> update. I just don't have access to the FP SE. I noticed an odd thing,
> however. When I check "Properties" of every directory on C:, the "Read only"
> attribute has a greyed-out check mark by it. I clear the check mark, apply
> the change, ask that it apply to all sub-folders, then exit. I open the
> directory again, and the greyed-out check mark is back! If I make a "new
> folder", it also has the greyed-out "Read only" property, and this is the
> case for all directories on D:, my other drive. This is obviously a global
> setting that I don't know how to turn off, and might be part of the problem,
> since the working website on the old server does not have these properties.
> Can you help? Any other suggestions would be appreciated.
> --
> Lynn Hart
>
>
> "Thomas A. Rowe" wrote:
>
| |
|
| I did do what you said. Please read my last post carefully. The only
transfer of files from the old server to the new was by publishing the web
from the old machine to the new via FP's http mode. But first, on the new
machine only, I copied and pasted the files from the wwwroot directory to
the (initially empty) Default Web Site home directory on the new server, in
order to get things initialized. Sorry about any confusion. I still don't
have access to the FP SE. Can you comment on my second question, which I
repeat here:
I noticed an odd thing, when I check "Properties" of every directory on C:,
the "Read only" attribute has a greyed-out check mark by it. I clear the
check mark, apply the change, ask that it apply to all sub-folders, then
exit. When I open the directory again, the greyed-out check mark is back!
If I make a "new folder" on C:, it also has the greyed-out "Read only"
property, and this is the case for all directories on D:, my other drive.
This is obviously a global setting that I don't know how to turn off, and
might be part of the problem, since the working website on the old server
does not have these properties. Can you help? Any suggestions would be
appreciated.
--
Lynn Hart
"Lynn" wrote:
> I developed an extended 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 SBS 2003. 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
> appear to be disabled. I checked that the FP server extensions were
> installed (shtml.dll in several places, as expected). Do I need to enable
> something?
> I noticed that the default web on the new server does not have some of the
> files in the C:\inetpub\www.root directory, particularly the _vti_inf.html
> file. Should I put this file (and maybe the other files and folders from
> www.root) in the default web, and then republish to the new server?
> --
> Lynn Hart
| |
| Thomas A. Rowe 2005-12-23, 8:48 pm |
| Ok, sorry. However you can not just copy files extension related file from one folder to another
(wwwroot to default web), you must set the FP extensions up via the IIS MMC, and then the Server
Extensions Admin application under Control Panel | Admin Tools, if running Windows 2003 Server or
the FP2002 extensions under Windows XP or 2000.
The FP extensions become unique to the machine and folder/web they are install on and used with, so
they can not be copied between location. FP never publishing the hidden _vti folder and any other
extensions related files or folders between location, etc.
The grayed out check mark means that the folder contains some hidden Windows System files/folders.
--
========================================
======
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.
========================================
======
"Lynn" <Lynn@discussions.microsoft.com> wrote in message
news:958240F9-6530-4A3D-9832-1234EF269141@microsoft.com...[vbcol=seagreen]
>I did do what you said. Please read my last post carefully. The only
> transfer of files from the old server to the new was by publishing the web
> from the old machine to the new via FP's http mode. But first, on the new
> machine only, I copied and pasted the files from the wwwroot directory to
> the (initially empty) Default Web Site home directory on the new server, in
> order to get things initialized. Sorry about any confusion. I still don't
> have access to the FP SE. Can you comment on my second question, which I
> repeat here:
> I noticed an odd thing, when I check "Properties" of every directory on C:,
> the "Read only" attribute has a greyed-out check mark by it. I clear the
> check mark, apply the change, ask that it apply to all sub-folders, then
> exit. When I open the directory again, the greyed-out check mark is back!
> If I make a "new folder" on C:, it also has the greyed-out "Read only"
> property, and this is the case for all directories on D:, my other drive.
> This is obviously a global setting that I don't know how to turn off, and
> might be part of the problem, since the working website on the old server
> does not have these properties. Can you help? Any suggestions would be
> appreciated.
>
> --
> Lynn Hart
>
>
> "Lynn" wrote:
>
| |
|
| I understand the principle you are talking about, but can you be more
specific about how to implement it? When IIS is first installed on the new
server, the Default Web Site is set up with all necessary virtual directories
(_vti_bin, etc), but no path to the home directory of the Default Web site.
When I first specify a path to the (disk-based) home directory of the Default
Web Site, there is initially nothing in this home directory. I can't even
publish to it because it lacks the file "frontpage.lck" file in folder
_vti_pvt, which is, of course, missing. (You get an error message if you try
to publish without this file.) The question is how to get physical folders
such as_vti_pvt and physical files like _vti_inf.html installed in the home
directory without just copying them, which is illegal. I see no way to
follow your advice, "you must set the FP extensions up via the IIS MMC, and
then the Server Extensions Admin application under Control Panel | Admin
Tools." Everything appears to already be set up. I see nothing to
configure.
Maybe the solution is as follows: When I open _vti_inf.html in
FrontPage, it states, "Comment: This page is placed into the root directory
of your FrontPage web when FrontPage is installed. It contains information
used by the FrontPage client to communicate with the FrontPage server
extensions installed on this web server. You should not delete this file."
It also states, "In the HTML comments, this page contains configuration
information that the FrontPage Explorer and FrontPage Editor need to
communicate with the FrontPage server extensions installed on this web
server. Do not delete this page." Maybe I need to uninstall FrontPage and
reinstall it after the path to the (empty) home directory of the Default Web
Site is set up in IIS. In other words, maybe I need to configure the Default
Web Site first, before reinstalling FrontPage and before publishing to it.
(In my case, I installed FrontPage first before there existed a path to the
home directory of the Default Web Site.) If I do it this way, I hope that
the Default Web Site will be chosen during the install as the "FrontPage web"
mentioned above. Maybe I should also delete "companyweb" (a small prototype
website) which exists in the default IIS install, before I reinstall FP, just
to be safe. What do you think? I welcome any comments, especially if I am
way off base.
--
Lynn Hart
"Thomas A. Rowe" wrote:
> Ok, sorry. However you can not just copy files extension related file from one folder to another
> (wwwroot to default web), you must set the FP extensions up via the IIS MMC, and then the Server
> Extensions Admin application under Control Panel | Admin Tools, if running Windows 2003 Server or
> the FP2002 extensions under Windows XP or 2000.
>
> The FP extensions become unique to the machine and folder/web they are install on and used with, so
> they can not be copied between location. FP never publishing the hidden _vti folder and any other
> extensions related files or folders between location, etc.
>
> The grayed out check mark means that the folder contains some hidden Windows System files/folders.
> --
> ========================================
======
> 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.
> ========================================
======
>
> "Lynn" <Lynn@discussions.microsoft.com> wrote in message
> news:958240F9-6530-4A3D-9832-1234EF269141@microsoft.com...
>
>
>
| |
| Thomas A. Rowe 2005-12-24, 5:55 pm |
| When you first install IIS under Windows XP Pro, and then install the FP extensions on the root web
via the IIS MMC, you then open http://localhost directly in FP, then create a folder for each site
(select each folder, right click and select convert to web / site), thereafter directly in FP you
would either open http://localhost and then double click to open each subweb / site or open
http://localhost/subweb.
As long as the FP extensions are installed and you are using them, you will rarely (if ever) have a
need to access the web / site via it's disk-based location, and you should never have a need to
touch any of the _vti folders and the files contained within them, which are managed as needed by
FP.
========================================
======
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.
========================================
======
"Lynn" <Lynn@discussions.microsoft.com> wrote in message
news:D4F1F17F-E24E-486F-BFAA-21296FA089AD@microsoft.com...[vbcol=seagreen]
> I understand the principle you are talking about, but can you be more
> specific about how to implement it? When IIS is first installed on the new
> server, the Default Web Site is set up with all necessary virtual directories
> (_vti_bin, etc), but no path to the home directory of the Default Web site.
> When I first specify a path to the (disk-based) home directory of the Default
> Web Site, there is initially nothing in this home directory. I can't even
> publish to it because it lacks the file "frontpage.lck" file in folder
> _vti_pvt, which is, of course, missing. (You get an error message if you try
> to publish without this file.) The question is how to get physical folders
> such as_vti_pvt and physical files like _vti_inf.html installed in the home
> directory without just copying them, which is illegal. I see no way to
> follow your advice, "you must set the FP extensions up via the IIS MMC, and
> then the Server Extensions Admin application under Control Panel | Admin
> Tools." Everything appears to already be set up. I see nothing to
> configure.
> Maybe the solution is as follows: When I open _vti_inf.html in
> FrontPage, it states, "Comment: This page is placed into the root directory
> of your FrontPage web when FrontPage is installed. It contains information
> used by the FrontPage client to communicate with the FrontPage server
> extensions installed on this web server. You should not delete this file."
> It also states, "In the HTML comments, this page contains configuration
> information that the FrontPage Explorer and FrontPage Editor need to
> communicate with the FrontPage server extensions installed on this web
> server. Do not delete this page." Maybe I need to uninstall FrontPage and
> reinstall it after the path to the (empty) home directory of the Default Web
> Site is set up in IIS. In other words, maybe I need to configure the Default
> Web Site first, before reinstalling FrontPage and before publishing to it.
> (In my case, I installed FrontPage first before there existed a path to the
> home directory of the Default Web Site.) If I do it this way, I hope that
> the Default Web Site will be chosen during the install as the "FrontPage web"
> mentioned above. Maybe I should also delete "companyweb" (a small prototype
> website) which exists in the default IIS install, before I reinstall FP, just
> to be safe. What do you think? I welcome any comments, especially if I am
> way off base.
>
> --
> Lynn Hart
>
>
> "Thomas A. Rowe" wrote:
>
|
|
|
|
|