|
Home > Archive > FrontPage Server Extensions for Windows > May 2004 > Frustrations with IIS 6.0 and FPSE continue
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 |
Frustrations with IIS 6.0 and FPSE continue
|
|
| Brian Boguhn 2004-05-20, 5:42 pm |
| OK, I've done everything below and I'm still having issues. This is
what is going on:
1. I start with a clean installation of IIS 6.0 on Windows Server
2003, with FPSE 2002 installed.
2. I do a migration from a Windows 2000 Server with IIS 5.0 and FPSE
2002 to the new server, using the IIS Migration tool and this command:
C:\>iismt pavlov "Default Web Site" /siteid replace /verbose /path
d:\inetpub\wwwroot /fpse. The migration runs through completely and
reports that it was successful. I then do an edit of the metabase
through Notebook and change all instances of c:\winnt (the old server)
to c:\windows (the new server). One more very important thing to note
here: On the old server, I can't get my FPSE administration stuff to
work, even though FPSE are installed. If I right-click and try to
recalculate or pull of admin stuff, I just get page not found errors.
I've never been able to resolve this, and haven't been able to find
anything on it from Microsoft. Note that even though this occurs, all
FrontPage functions work on all the sites and subdirectories on the
server.
3. After #2 above, I try to access various pages on the server, and I
get HTTP 500 errors. I can't access anything. And if I try, on the
new server, to run FPSE functions that worked before the migration
(ie. Recalculate site, etc.), I get the same page not found errors I
get on the old server. So I'm hosed.
Besides the above, I've also tried doing the migration simply by using
Robocopy to copy the directories from the old server to the new
server. When I do this, I can at least access the pages, and I can
even get as far in a search as being told there is no catalog, but the
FPSE admin functions only partially work. I can bring up the admin
screen, but if I try to do a recalculate, it runs forever and never
ends.
Any further thoughts on how to fix this?
Brian
From: boguhn@entelos.com (Brian Boguhn)
Newsgroups: microsoft.public.frontpage.extensions.windowsnt
Subject: Re: Getting ready to pull my hair out with IIS 6.0 and FPSE
References: <2cdfba4a.0405191013.7042920@posting.google.com>
<VA.00001a13.01e68e5c@obts-outlookdev.outlookbythesound.mukwoods>
NNTP-Posting-Host: 12.22.57.200
Message-ID: <2cdfba4a.0405200648.26ae1c5b@posting.google.com>
Hollis,
Thanks for the info. This is definitely getting me closer. I had the
indexing service installed, but not allowed in IIS. I went through
your steps and did it. That at least got me to the point where when I
tried to do a search, I got back a message of 'No Catalog'. I had
done a recalculation, but I guess it didn't work.
There are some other issues with the site and the migration. I'm
going to run the migration and post a follow-up with what I'm running
into.
Brian
"Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message news:<VA.00001a13.01e68e5c@obts-outlookdev.outlookbythesound.mukwoods>...
> In article <2cdfba4a.0405191013.7042920@posting.google.com>, Brian
> Boguhn wrote:
> With Win2K3 and IIS6, in addition to installing and configuring the
> sites, and giving them their own application pool, you have to look in
> that third folder under your IIS server (in the IIS Manager console).
>
> Double click that folder and look at the list of extensions that are
> allowed in the left hand pane. From your description, I would guess
> that FPSE, FPSE2K2 are there and allowed, but that the Internet
> Service is not. You have to install this as a component of IIS, and
> it is not installed by default.
>
> http://www.experts-exchange.com/App...FrontPage/Q_207
> 7
> 8551.html
>
> "By default, Windows 2003 Server does not install the indexing server.
> You should actually see an option in the IIS console to "allow" or
> "prohibit" the indexing service under the Web Service Extension
> section.
>
> The solution:
> 1) Go to "add/remove components" - "Windows Components" and uncheck
> the indexing service so it can be uninstalled.
> 2) Reboot the system
> 3) Go back to "add/remove components" and reinstall the indexing
> service.
> 4) In the IIS console, under "Web Service Extension", "allow" the
> indexing service.
> 5) Recalculate the website
>
> The search should function properly!"
>
>
> The link to this info in a page on my site:
> http://www.outlookbythesound.com/SB...ch_component.ht
> m
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
> Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
> http://search.support.microsoft.com...D=TECH&LN=EN-US
>
> Mukilteo, WA USA
| |
| Hollis D. Paul 2004-05-20, 5:42 pm |
| In article <2cdfba4a.0405200919.421ba5a2@posting.google.com>, Brian
Boguhn wrote:
> Any further thoughts on how to fix this?
>
Are you migrating this to a Virtual Web Server that you created, or is
it going to the default web site?
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com...D=TECH&LN=EN-US
Mukilteo, WA USA
| |
| Brian Boguhn 2004-05-21, 5:55 pm |
| Hollis -
The Default Web Site.
I found a link to an article detailing the same type of error I am
encountering:
http://groups.google.com/groups?hl=...UTF-8%26selm%3D
ef1f2f53.0307240817.323e239b%2540posting.google.com%26rnum%3D1
I haven't tried the workaround suggested, but it looks like a security
risk.
Brian
"Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message news:<VA.00001a18.017e1670@obts-outlookdev.outlookbythesound.mukwoods>...
> In article <2cdfba4a.0405200919.421ba5a2@posting.google.com>, Brian
> Boguhn wrote:
> Are you migrating this to a Virtual Web Server that you created, or is
> it going to the default web site?
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
> Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
> http://search.support.microsoft.com...D=TECH&LN=EN-US
>
> Mukilteo, WA USA
| |
| Hollis D. Paul 2004-05-21, 5:55 pm |
| In article <2cdfba4a.0405210732.65cc2c45@posting.google.com>, Brian Boguhn wrote:
> The Default Web Site.
>
> I found a link to an article detailing the same type of error I am
> encountering:
> http://groups.google.com/groups?hl=...3DUTF-8%26selm%
3Def1f2f53.0307240817.323e239b%2540posting.google.com%26rnum%3D1
>
> I haven't tried the workaround suggested, but it looks like a security
> risk.
>
Well, I had a similar problem when I migrated from SBS2000 to SBS2003. The
website was still there, as I was migrating from one partition to another.
The site was listed in the IIS Manager, but it was stopped and couldn't be
started. It turned out that the migration had not set up a listener on the
IPs of the Virtual Web Servers. There is a Win2K3 utility that I used to
add the VWS's IP to the IPListen list, and I was then able to browse the sites.
However, I could never connect to them with FrontPage to update it, because
they were not properly entered in the IIS metadata. I ended up deleting the
migrated sites and files, re-creating the Virtual Web Servers and publishing
the pages again from a backup disk-based web. They are now live and I can
update them with FrontPage.
You might be interested in the following KB article: 813368 IIS 6.0: Setting
Metabase Property Disable Socket Pooling Has No Effect
You will be interested in the resolution part where it talks about installing
running the utility named httpcfg.
The logon to the server issue is side-stepped in the SBS world, because,
normally, all clients are logged on to the server. Doesn't seem to be a
security risk there. We just don't tell the users what it might mean.
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com...D=TECH&LN=EN-US
Mukilteo, WA USA
| |
| Tom Pepper Willett 2004-05-21, 8:53 pm |
| Brian: Some of the FP MVPs have experienced a lot of problems with the FP
2002 extensions being used with Win2003 server, and have pretty well given
up, and are installing the FP 2000 extensions.
--
========================================
=============
Tom Pepper Willett [Microsoft MVP - FrontPage]
----------------------------------------------------------------------------
-------------------
Microsoft FrontPage:
http://www.microsoft.com/office/fro...fo/default.mspx
http://msdn.microsoft.com/office/un...ding/frontpage/
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
========================================
=============
"Brian Boguhn" <boguhn@entelos.com> wrote in message
news:2cdfba4a.0405210732.65cc2c45@posting.google.com...
| Hollis -
|
| The Default Web Site.
|
| I found a link to an article detailing the same type of error I am
| encountering:
|
http://groups.google.com/groups?hl=...UTF-8%26selm%3D
ef1f2f53.0307240817.323e239b%2540posting.google.com%26rnum%3D1
|
| I haven't tried the workaround suggested, but it looks like a security
| risk.
|
| Brian
|
| "Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message
news:<VA.00001a18.017e1670@obts-outlookdev.outlookbythesound.mukwoods>...
| > In article <2cdfba4a.0405200919.421ba5a2@posting.google.com>, Brian
| > Boguhn wrote:
| > > Any further thoughts on how to fix this?
| > >
| > Are you migrating this to a Virtual Web Server that you created, or is
| > it going to the default web site?
| >
| > Hollis D. Paul [MVP - Outlook]
| > Hollis@outhousebythesound.com
| > Mukilteo, WA USA
| >
| > Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
| > http://search.support.microsoft.com...D=TECH&LN=EN-US
| >
| > Mukilteo, WA USA
|
|
|
|
|