B
Brian Boguhn
I posted this over in the IIS group, but thought perhaps someone over
here might have some insight as well...
Any assistance with the following is appreciated.
I installed a brand new clean Windows Server 2003 Standard system. I
then went through the Manage Your Server wizard and installed IIS and
the FPSE. So far, so good. Going to a web browser, I can open the
default page for http://myserver.
Here's where the fun starts. There's actually two parts, but I think
solving one would probably fix the other as well, so here goes...
- After doing the above, I used the IIS 6.0 migration tool to move an
existing IIS 5.0 installation to the new server. The tool told me the
migration was successful, and indeed, I could access my pages. The
issue arose, however, when trying to access pages that used FrontPage
components (in this case, specifically, a search page). If I entered
something into the search, I would get a page not found error back
listing a script that wasn't on the system. However, this script does
exist on the old IIS installation.
- After fooling with the above for a while and getting nowhere, I
uninstalled IIS and FPSE completely and then did a fresh install. At
this point, I created a new web and created several pages, including a
search page. I browsed to the web, went to the search page, tried to
search, and...I'm told I'm trying to use a component that requires
FPSE installed on the server. However, the FPSE ARE installed.
What am I missing here? I've been digging through Technet and going
through newsgroups and such trying to figure this out, and finding a
lot of stuff, but never getting to the answer. The two instances
above are streamlined down to the essentials; this has been over a
week of work and still no success in having a working site. I don't
recall my IIS 4.0 and 5.0 sites being difficult to get going at all.
Thank you in advance.
here might have some insight as well...
Any assistance with the following is appreciated.
I installed a brand new clean Windows Server 2003 Standard system. I
then went through the Manage Your Server wizard and installed IIS and
the FPSE. So far, so good. Going to a web browser, I can open the
default page for http://myserver.
Here's where the fun starts. There's actually two parts, but I think
solving one would probably fix the other as well, so here goes...
- After doing the above, I used the IIS 6.0 migration tool to move an
existing IIS 5.0 installation to the new server. The tool told me the
migration was successful, and indeed, I could access my pages. The
issue arose, however, when trying to access pages that used FrontPage
components (in this case, specifically, a search page). If I entered
something into the search, I would get a page not found error back
listing a script that wasn't on the system. However, this script does
exist on the old IIS installation.
- After fooling with the above for a while and getting nowhere, I
uninstalled IIS and FPSE completely and then did a fresh install. At
this point, I created a new web and created several pages, including a
search page. I browsed to the web, went to the search page, tried to
search, and...I'm told I'm trying to use a component that requires
FPSE installed on the server. However, the FPSE ARE installed.
What am I missing here? I've been digging through Technet and going
through newsgroups and such trying to figure this out, and finding a
lot of stuff, but never getting to the answer. The two instances
above are streamlined down to the essentials; this has been over a
week of work and still no success in having a working site. I don't
recall my IIS 4.0 and 5.0 sites being difficult to get going at all.
Thank you in advance.