|
Home > Archive > FrontPage Server Extensions for Windows > April 2005 > configuring frontpage server extensions
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 |
configuring frontpage server extensions
|
|
| Shadowrift 2005-04-04, 5:55 pm |
| OK, so after following up, it looks like the frontpage server extensions for
the Windows server 2003 was installed through add/remove programs.
Heres the problem again:
In IIS Manager
I left click on Default Website and select All Tasks, and then select
Configure Server Extentions 2002
I then Specify an administrator account for this virtual server and then hit
Submit.
which brings me to this page:
http://cbscc-m3-iis01:5188/fpadmdll.dll
which looks like a webpage and in the center it reads: "Please wait while
your changes are processed." but nothing happens, it just sits there.
any ideas?
| |
| Shadowrift 2005-04-04, 5:55 pm |
| Interesting, i just tried to extend again but from my machine and not
remotely connected and i got the following error message:
Unable to create a web at the URL "/" because FrontPage information was
unexpectedly encountered beneath the corresponding directory
("E:\inetpub\wwwroot\"). If you are certain that there is no FrontPage web at
" E:\inetpub\wwwroot\AdministrationFinance
", you should delete the file
" E:\inetpub\wwwroot\AdministrationFinance
\_vti_pvt\services.cnf" or rename it
to "services.org".
there are numerous websites under wwwroot.
any ideas?
"Shadowrift" wrote:
> OK, so after following up, it looks like the frontpage server extensions for
> the Windows server 2003 was installed through add/remove programs.
>
> Heres the problem again:
> In IIS Manager
> I left click on Default Website and select All Tasks, and then select
> Configure Server Extentions 2002
>
> I then Specify an administrator account for this virtual server and then hit
> Submit.
>
> which brings me to this page:
> http://cbscc-m3-iis01:5188/fpadmdll.dll
>
> which looks like a webpage and in the center it reads: "Please wait while
> your changes are processed." but nothing happens, it just sits there.
>
> any ideas?
| |
| Roy Chastain 2005-04-05, 5:50 pm |
| Each virtual site has to be in a separate directory tree.
They can all be under INETPUB for instance, but you can not put one inside another site which is what is happening if you try to
put them under WWWRoot.
On Mon, 4 Apr 2005 13:53:05 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Interesting, i just tried to extend again but from my machine and not
>remotely connected and i got the following error message:
>
>Unable to create a web at the URL "/" because FrontPage information was
>unexpectedly encountered beneath the corresponding directory
>("E:\inetpub\wwwroot\"). If you are certain that there is no FrontPage web at
>" E:\inetpub\wwwroot\AdministrationFinance
", you should delete the file
>" E:\inetpub\wwwroot\AdministrationFinance
\_vti_pvt\services.cnf" or rename it
>to "services.org".
>
>there are numerous websites under wwwroot.
>any ideas?
>
>"Shadowrift" wrote:
>
-------------------------------------------
Roy Chastain
KMSystems, Inc.
| |
| Shadowrift 2005-04-05, 5:50 pm |
| the directory is setup as follows:
inetpub
|
|---------|-----------|
ftproot wwwroot scripts
|
|---------|-----------|
website1 website2 website3
Each virtual site has its own directory. There is no virtual site in a
directory within a virtual site directory.
"Roy Chastain" wrote:
> Each virtual site has to be in a separate directory tree.
> They can all be under INETPUB for instance, but you can not put one inside another site which is what is happening if you try to
> put them under WWWRoot.
>
> On Mon, 4 Apr 2005 13:53:05 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
>
>
> -------------------------------------------
> Roy Chastain
> KMSystems, Inc.
>
| |
| Roy Chastain 2005-04-05, 5:50 pm |
| That will work as long as WWWROOT is NOT the root directory of a site, but since the default installation of IIS creates a site in
WWWROOT, I would expect that there is one there.
On Tue, 5 Apr 2005 08:27:05 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>the directory is setup as follows:
>
> inetpub
> |
> |---------|-----------|
>ftproot wwwroot scripts
> |
> |---------|-----------|
>website1 website2 website3
>
>Each virtual site has its own directory. There is no virtual site in a
>directory within a virtual site directory.
>
>"Roy Chastain" wrote:
>
-------------------------------------------
Roy Chastain
KMSystems, Inc.
| |
| Shadowrift 2005-04-05, 5:50 pm |
| ok thanks, any idea what the default site's name would be?
Im also going to go through these existing sites that have been slapped on
here. It looks like some sites with frontpage functionality were put onto a
server that did not have frontpage extensions installed in the first place.
Could it be that FPSE cannot install when there is existing frontpage data in
the virtual directories?
"Roy Chastain" wrote:
> That will work as long as WWWROOT is NOT the root directory of a site, but since the default installation of IIS creates a site in
> WWWROOT, I would expect that there is one there.
>
> On Tue, 5 Apr 2005 08:27:05 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
>
>
> -------------------------------------------
> Roy Chastain
> KMSystems, Inc.
>
| |
| Roy Chastain 2005-04-05, 5:50 pm |
| Don't know about the install question.
As far as the default site is concerned.
Start the IIS Administration Console
Right click each web site in Web Sites and see if the "Local Path" on the Home Directory tab points to the WWWROOT folder. (I
would start with the one labeled Default Web Site.
Basically the Local Path of one site can not be nested within the Local Path of another site.
On Tue, 5 Apr 2005 10:53:02 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>ok thanks, any idea what the default site's name would be?
>
>Im also going to go through these existing sites that have been slapped on
>here. It looks like some sites with frontpage functionality were put onto a
>server that did not have frontpage extensions installed in the first place.
>Could it be that FPSE cannot install when there is existing frontpage data in
>the virtual directories?
>
>"Roy Chastain" wrote:
>
-------------------------------------------
Roy Chastain
KMSystems, Inc.
| |
| Shadowrift 2005-04-06, 5:54 pm |
| Your'e right.
http://rich.toogeek.com/IISshot1.jpg
http://rich.toogeek.com/IISshot2.jpg
The local path for default website is E:\inetpub\wwwroot
and the local path for processtoolbox is E:\Inetpub\wwwroot\processtoolbox
I have sucessfully configured server extensions 2002 for default website.
but it is processtoolbox that i need the frontpage web set up for so i can
connect to it via frontpage. Any ideas what i should do next?
"Roy Chastain" wrote:
> Don't know about the install question.
>
> As far as the default site is concerned.
> Start the IIS Administration Console
> Right click each web site in Web Sites and see if the "Local Path" on the Home Directory tab points to the WWWROOT folder. (I
> would start with the one labeled Default Web Site.
>
> Basically the Local Path of one site can not be nested within the Local Path of another site.
>
> On Tue, 5 Apr 2005 10:53:02 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
>
>
> -------------------------------------------
> Roy Chastain
> KMSystems, Inc.
>
| |
| Tom Pepper Willett 2005-04-06, 5:54 pm |
| wwwroot is your default web site.
You must create the processtoolbox so that it appears as
E:\Inetpub\processtoolbox
Use the IIS console to build your new site.
--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/of...etid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/fro...fo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/un...ding/frontpage/
FrontPage 2002 Server Extensions Support Center:
http://support.microsoft.com/defaul...fh;en-us;fp10se
===
"Shadowrift" <Shadowrift@discussions.microsoft.com> wrote in message
news:4EAD5DD3-DB38-497E-BC68-97C5098910F3@microsoft.com...
| Your'e right.
| http://rich.toogeek.com/IISshot1.jpg
| http://rich.toogeek.com/IISshot2.jpg
|
| The local path for default website is E:\inetpub\wwwroot
| and the local path for processtoolbox is E:\Inetpub\wwwroot\processtoolbox
|
| I have sucessfully configured server extensions 2002 for default website.
| but it is processtoolbox that i need the frontpage web set up for so i can
| connect to it via frontpage. Any ideas what i should do next?
|
|
| "Roy Chastain" wrote:
|
| > Don't know about the install question.
| >
| > As far as the default site is concerned.
| > Start the IIS Administration Console
| > Right click each web site in Web Sites and see if the "Local Path" on
the Home Directory tab points to the WWWROOT folder. (I
| > would start with the one labeled Default Web Site.
| >
| > Basically the Local Path of one site can not be nested within the Local
Path of another site.
| >
| > On Tue, 5 Apr 2005 10:53:02 -0700, "Shadowrift"
<Shadowrift@discussions.microsoft.com> wrote:
| >
| > >ok thanks, any idea what the default site's name would be?
| > >
| > >Im also going to go through these existing sites that have been slapped
on
| > >here. It looks like some sites with frontpage functionality were put
onto a
| > >server that did not have frontpage extensions installed in the first
place.
| > >Could it be that FPSE cannot install when there is existing frontpage
data in
| > >the virtual directories?
| > >
| > >"Roy Chastain" wrote:
| > >
| > >> That will work as long as WWWROOT is NOT the root directory of a
site, but since the default installation of IIS creates a site in
| > >> WWWROOT, I would expect that there is one there.
| > >>
| > >> On Tue, 5 Apr 2005 08:27:05 -0700, "Shadowrift"
<Shadowrift@discussions.microsoft.com> wrote:
| > >>
| > >> >the directory is setup as follows:
| > >> >
| > >> > inetpub
| > >> > |
| > >> > |---------|-----------|
| > >> >ftproot wwwroot scripts
| > >> > |
| > >> > |---------|-----------|
| > >> >website1 website2 website3
| > >> >
| > >> >Each virtual site has its own directory. There is no virtual site in
a
| > >> >directory within a virtual site directory.
| > >> >
| > >> >"Roy Chastain" wrote:
| > >> >
| > >> >> Each virtual site has to be in a separate directory tree.
| > >> >> They can all be under INETPUB for instance, but you can not put
one inside another site which is what is happening if you try to
| > >> >> put them under WWWRoot.
| > >> >>
| > >> >> On Mon, 4 Apr 2005 13:53:05 -0700, "Shadowrift"
<Shadowrift@discussions.microsoft.com> wrote:
| > >> >>
| > >> >> >Interesting, i just tried to extend again but from my machine and
not
| > >> >> >remotely connected and i got the following error message:
| > >> >> >
| > >> >> >Unable to create a web at the URL "/" because FrontPage
information was
| > >> >> >unexpectedly encountered beneath the corresponding directory
| > >> >> >("E:\inetpub\wwwroot\"). If you are certain that there is no
FrontPage web at
| > >> >> >" E:\inetpub\wwwroot\AdministrationFinance
", you should delete the
file
| > >> >> >" E:\inetpub\wwwroot\AdministrationFinance
\_vti_pvt\services.cnf"
or rename it
| > >> >> >to "services.org".
| > >> >> >
| > >> >> >there are numerous websites under wwwroot.
| > >> >> >any ideas?
| > >> >> >
| > >> >> >"Shadowrift" wrote:
| > >> >> >
| > >> >> >> OK, so after following up, it looks like the frontpage server
extensions for
| > >> >> >> the Windows server 2003 was installed through add/remove
programs.
| > >> >> >>
| > >> >> >> Heres the problem again:
| > >> >> >> In IIS Manager
| > >> >> >> I left click on Default Website and select All Tasks, and then
select
| > >> >> >> Configure Server Extentions 2002
| > >> >> >>
| > >> >> >> I then Specify an administrator account for this virtual server
and then hit
| > >> >> >> Submit.
| > >> >> >>
| > >> >> >> which brings me to this page:
| > >> >> >> http://cbscc-m3-iis01:5188/fpadmdll.dll
| > >> >> >>
| > >> >> >> which looks like a webpage and in the center it reads: "Please
wait while
| > >> >> >> your changes are processed." but nothing happens, it just sits
there.
| > >> >> >>
| > >> >> >> any ideas?
| > >> >>
| > >> >> -------------------------------------------
| > >> >> Roy Chastain
| > >> >> KMSystems, Inc.
| > >> >>
| > >>
| > >> -------------------------------------------
| > >> Roy Chastain
| > >> KMSystems, Inc.
| > >>
| >
| > -------------------------------------------
| > Roy Chastain
| > KMSystems, Inc.
| >
| |
| Shadowrift 2005-04-06, 5:54 pm |
| sorry, are you saying I should just move the location of processtoolbox and
change it's local path, or to create a new website that is not under default
website?
"Tom Pepper Willett" wrote:
> wwwroot is your default web site.
> You must create the processtoolbox so that it appears as
> E:\Inetpub\processtoolbox
> Use the IIS console to build your new site.
> --
> ===
> Tom "Pepper" Willett
> Microsoft MVP - FrontPage
> ---
> About FrontPage 2003:
> http://office.microsoft.com/home/of...etid=FX01085802
> FrontPage 2003 Product Information:
> http://www.microsoft.com/office/fro...fo/default.mspx
> Understanding FrontPage:
> http://msdn.microsoft.com/office/un...ding/frontpage/
> FrontPage 2002 Server Extensions Support Center:
> http://support.microsoft.com/defaul...fh;en-us;fp10se
> ===
> "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote in message
> news:4EAD5DD3-DB38-497E-BC68-97C5098910F3@microsoft.com...
> | Your'e right.
> | http://rich.toogeek.com/IISshot1.jpg
> | http://rich.toogeek.com/IISshot2.jpg
> |
> | The local path for default website is E:\inetpub\wwwroot
> | and the local path for processtoolbox is E:\Inetpub\wwwroot\processtoolbox
> |
> | I have sucessfully configured server extensions 2002 for default website.
> | but it is processtoolbox that i need the frontpage web set up for so i can
> | connect to it via frontpage. Any ideas what i should do next?
> |
> |
> | "Roy Chastain" wrote:
> |
> | > Don't know about the install question.
> | >
> | > As far as the default site is concerned.
> | > Start the IIS Administration Console
> | > Right click each web site in Web Sites and see if the "Local Path" on
> the Home Directory tab points to the WWWROOT folder. (I
> | > would start with the one labeled Default Web Site.
> | >
> | > Basically the Local Path of one site can not be nested within the Local
> Path of another site.
> | >
> | > On Tue, 5 Apr 2005 10:53:02 -0700, "Shadowrift"
> <Shadowrift@discussions.microsoft.com> wrote:
> | >
> | > >ok thanks, any idea what the default site's name would be?
> | > >
> | > >Im also going to go through these existing sites that have been slapped
> on
> | > >here. It looks like some sites with frontpage functionality were put
> onto a
> | > >server that did not have frontpage extensions installed in the first
> place.
> | > >Could it be that FPSE cannot install when there is existing frontpage
> data in
> | > >the virtual directories?
> | > >
> | > >"Roy Chastain" wrote:
> | > >
> | > >> That will work as long as WWWROOT is NOT the root directory of a
> site, but since the default installation of IIS creates a site in
> | > >> WWWROOT, I would expect that there is one there.
> | > >>
> | > >> On Tue, 5 Apr 2005 08:27:05 -0700, "Shadowrift"
> <Shadowrift@discussions.microsoft.com> wrote:
> | > >>
> | > >> >the directory is setup as follows:
> | > >> >
> | > >> > inetpub
> | > >> > |
> | > >> > |---------|-----------|
> | > >> >ftproot wwwroot scripts
> | > >> > |
> | > >> > |---------|-----------|
> | > >> >website1 website2 website3
> | > >> >
> | > >> >Each virtual site has its own directory. There is no virtual site in
> a
> | > >> >directory within a virtual site directory.
> | > >> >
> | > >> >"Roy Chastain" wrote:
> | > >> >
> | > >> >> Each virtual site has to be in a separate directory tree.
> | > >> >> They can all be under INETPUB for instance, but you can not put
> one inside another site which is what is happening if you try to
> | > >> >> put them under WWWRoot.
> | > >> >>
> | > >> >> On Mon, 4 Apr 2005 13:53:05 -0700, "Shadowrift"
> <Shadowrift@discussions.microsoft.com> wrote:
> | > >> >>
> | > >> >> >Interesting, i just tried to extend again but from my machine and
> not
> | > >> >> >remotely connected and i got the following error message:
> | > >> >> >
> | > >> >> >Unable to create a web at the URL "/" because FrontPage
> information was
> | > >> >> >unexpectedly encountered beneath the corresponding directory
> | > >> >> >("E:\inetpub\wwwroot\"). If you are certain that there is no
> FrontPage web at
> | > >> >> >" E:\inetpub\wwwroot\AdministrationFinance
", you should delete the
> file
> | > >> >> >" E:\inetpub\wwwroot\AdministrationFinance
\_vti_pvt\services.cnf"
> or rename it
> | > >> >> >to "services.org".
> | > >> >> >
> | > >> >> >there are numerous websites under wwwroot.
> | > >> >> >any ideas?
> | > >> >> >
> | > >> >> >"Shadowrift" wrote:
> | > >> >> >
> | > >> >> >> OK, so after following up, it looks like the frontpage server
> extensions for
> | > >> >> >> the Windows server 2003 was installed through add/remove
> programs.
> | > >> >> >>
> | > >> >> >> Heres the problem again:
> | > >> >> >> In IIS Manager
> | > >> >> >> I left click on Default Website and select All Tasks, and then
> select
> | > >> >> >> Configure Server Extentions 2002
> | > >> >> >>
> | > >> >> >> I then Specify an administrator account for this virtual server
> and then hit
> | > >> >> >> Submit.
> | > >> >> >>
> | > >> >> >> which brings me to this page:
> | > >> >> >> http://cbscc-m3-iis01:5188/fpadmdll.dll
> | > >> >> >>
> | > >> >> >> which looks like a webpage and in the center it reads: "Please
> wait while
> | > >> >> >> your changes are processed." but nothing happens, it just sits
> there.
> | > >> >> >>
> | > >> >> >> any ideas?
> | > >> >>
> | > >> >> -------------------------------------------
> | > >> >> Roy Chastain
> | > >> >> KMSystems, Inc.
> | > >> >>
> | > >>
> | > >> -------------------------------------------
> | > >> Roy Chastain
> | > >> KMSystems, Inc.
> | > >>
> | >
> | > -------------------------------------------
> | > Roy Chastain
> | > KMSystems, Inc.
> | >
>
>
>
| |
| Roy Chastain 2005-04-07, 6:03 pm |
| IN GENERAL just move the E:\Inetpub\wwwroot\processtoolbox directory to
E:\Inetpub\processtoolbox. Then change the local path in the ProcessToolBox site to point to the new location.
Then you should be able to extend the site correctly.
If anyone has hard coded paths in the web site to files, then you will have fix that after you move the site.
Again, you can NOT have one site within the root of another site.
On Wed, 6 Apr 2005 12:59:01 -0700, "Shadowrift" <Shadowrift@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>sorry, are you saying I should just move the location of processtoolbox and
>change it's local path, or to create a new website that is not under default
>website?
>
>"Tom Pepper Willett" wrote:
>
-------------------------------------------
Roy Chastain
KMSystems, Inc.
|
|
|
|
|