Re: FPSE2002 migration to WSS2.0

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Lawrence Garvin (onsitechsolutions_at_news.postalias)
Date: 07/08/04 

Date: Thu, 8 Jul 2004 11:37:09 -0500

"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:OhYqJ3KZEHA.384@TK2MSFTNGP10.phx.gbl...
> All I can say is that the Admin Guide clearly states that you cannot have
> both front-end and back-end (database) of WSS running on Web Edition.

This is true. And I believe this is based on an earlier version of MSDE that
would not load on the Web Edition; however, MSDERelA has removed that
restriction and /is/ certified for use on the Web Edition.

> So I would say based on that is that your problems are being caused by
> attempting a non-supported (and as far as I know non-working) set-up.

I would disagree. Check the release nodes for MSDE Rel A. :-)

Furthermore, I /DO/ have a successful Sharepoint site running on that
server. The issue is with /migrating/ previously existing sites, not with
establishing basic functionality.

> Mike Walsh, Helsinki, Finland
> WSS FAQ at wss.collutions.com
> Please post questions to the newsgroup only.
>
>
> "Lawrence Garvin" <onsitechsolutions@news.postalias> wrote in message
> news:ucxaRpKZEHA.648@TK2MSFTNGP10.phx.gbl...
> > Several weeks ago I completed the installation of WSS on my Web Edition
> > server, but ran into some challenges getting the config database
> connected.
> > Over the weekend I found the necessary instructions in the Sharepoint
> Admin
> > guide, and so proceeded to create a WSS website. (Note: To confirm, I do
> > have WSS2.0 and MSDE running on Windows Server 2003, Web Edition.)
> >
> > I did successfully create a WSS website, configure host headers, and
that
> > website is off to the content development process.
> >
> > Then, I discovered the Usage Analysis capabilities of WSS, and decided
> that
> > would be useful to have on my other websites published from this same
> > server. So I proceeded to migrate my sites from FPSE2002 to WSS2.0.
> >
> > A couple of items immediately struck me as odd. One, the statement that
> > FPSE2002 and WSS2.0 cannot coexist on the same server. Not only were
they
> > coexisting on my Web Edition server, but they're also /designed/ to
> coexist
> > on SBS2003. Go figger.
> >
> > In accordance with the instructions in the Sharepoint Admin Guide, I did
> the
> > following:
> >
> > 1. Backed up my existing web sites using smigrate. There are eight of
> them.
> >
> > 2. Removed FPSE2002 from each of the servers, and then uninstalled
> FPSE2002
> > from my Web Edition server.
> >
> > The next steps, install/enable ASP.NET and configure IIS6 to run in
worker
> > process isolation mode are already accomplished. Again, this goes to the
> > coexistence question. I skipped these steps.
> >
> > Then, the instructions are to use the smigrate tool to restore the
backed
> up
> > website.
> >
> > And it was at this point that I readily determined that some steps were
> > missing from these instructions.
> >
> > In another part of the Sharepoint Admin Guide, I found some of the
missing
> > steps. The most significant of these include creating a new top-level
site
> > without applying a template -- but I had significant difficulties with
> this
> > step. If I removed the old site from IIS Manager and removed the
original
> > data folders, then stsadm complains that the virtual server doesn't
exist.
> > If I put back the virtual server definition with a blank content folder,
> > then stsadm complains that the server is not extended.
> >
> > If I attempted to extend the existing virtual server (with the intention
> of
> > aborting the selection of a template), the extension completes
> successfully,
> > but Sharepoint Central Administration refuses to recognize the virtual
> site
> > as extended, and no further actions can take place -- but the site does
> get
> > a blank home page -- and effectively obliterates any original content.
> > Attempting to do a restore on top of this site, of course, is
ineffective
> > because the 'blank home page' is not part of the original content.
> >
> > After some trial and error, this is what I found works (sort of), but
I'm
> > not sure why. Also, I'd like to compare what I did to what I /should/
have
> > done and to what is /written/ (or not, as the case may be), so that for
> > future reference, I'll be better prepared.
> >
> > Here's what I did:
> >
> > 1. Extend the previously existing virtual server with Sharepoint Central
> > Administration. (My guess is this created the necessary references in
the
> > config database that were, heretofore, nonexistent.)
> >
> > 2. Then, immediately DELETE the site collection for that virtual server.
> > (Which takes away the undesirable 'new' content containing the blank
home
> > page.)
> >
> > 3. Delete the virtual server from IIS Manager.
> >
> > 4. Recreate the virtual server in IIS Manager. At this point, Sharepoint
> > Central Administration now recognizes this site as an 'extended' site,
but
> > it retains the original content in the original web folder structure.
> >
> > However, this is only about halfway to what I expected to have
> accomplished
> > as a result of the migration.
> >
> > I had expected that migrating the sites from a standard web environment
> > (with or without FPSE2002) to WSS2.0 would have resulted in the
migration
> of
> > the content into the MSDE databases. Perhaps this would have happened as
a
> > function of the smigrate restore, which I've not had the need to
perform.
> >
> > Also, I find myself asking about the expected use of non-Sharepoint
sites
> on
> > a multi-site web server, that were created/managed with FPSE, or that
are
> > intended to continue to be managed via FrontPage. Since FPSE2002 and WSS
> > allegedly do not coexist -- how exactly is FrontPage expected to
interact
> > with a web server running WSS, but containing virtual servers that do
not
> > contain WSS-type content if FPSE2002 cannot remain?
> >
> > Also, unfortunately, the Usage Analysis does not work for these sites,
so
> it
> > seems I've done this for naught.
> > Does anybody have any ideas/thoughts on why the Usage Analysis isn't
> > working? Are my sites actually extended as SCA reports, or is something
> > being misreported between the config database and SCA?
> >
> > Perhaps once I understand the whole process, it'll all make better
sense.
> >
> > Thanks in advance to anybody who can enlighten me.
> >
> >
>
>

Relevant Pages

  • Deployment Planning Questions
    ... The "One domain-name site per virtual server" - (TechNet ... Admin Guide - WSS Architecture) seems to be the best fit: ... Can shared web applications be installed when using ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Share Point Services
    ... money in WSS and you could use it in a virtually free server system? ... install WSS on Web Edition, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: wss onwindows 2003 webedition
    ... if you install WSS on web edition you must ... So it's not usually cheaper - unless you already have another server running ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Cannot upload documents to a Document Library in WSS.
    ... I never changed any setting on the WSS site. ... different server from the main site. ... > If you use Web Edition you MUST use a second server running either SQL ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Win2003 Web Edition
    ... WSS will only run in Web Edition if the database it uses (then typically ... SQL Server2K) is on a different server. ... Usually this makes it not worthwhile to use Web Edition unless you are load ... Please ask about SPS in the SPS newsgroup ...
    (microsoft.public.sharepoint.windowsservices)