Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod

Hi Steven,

I have sent you an email.

Thanks,
Alex

"Steven Cheng [MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:JDems5YsIHA.1900@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi EF,

After some further discussing with the dev engineer, we think the problem
you encounter should involve something else that maynot be easy to locate
from appearance. I'm currently planning to allocate some further resource
to help you. Would you send me an email via the following address so that
I
can ask you for further information offline:

"stcheng" @ "microsoft.com"

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
From: <EF@xxxxxxxxxxxxx>
Subject: Re: Upgrading Windows SharePoint Services 2.0 scalable hosting
mod
Date: Tue, 6 May 2008 13:45:33 +0800


Hi Steven,

I am use WSS 3.0 with SP1 and it said that setting the HH property is not
needed for SP1. Anyway, I tried your method and it is still not working
as
expected.

When you says

Step 2 Attach a content database for upgrade STSADM -o addcontentdb -url
http://hostheaderwebapplication -databaseserver databaseserver
-databasename databasename

Is the url http://hostheaderwebapplication the url of the web application
that I have created?


Thanks,
Alex

"Steven Cheng [MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Gh2vM9yrIHA.4284@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Alex,

I've just got some update from the engineer who wrote the blog entry I
provided you previously. Here is his comments to your original 4
questiosn:

1) After installing a new WSS 3.0 farm do I need to first create a new
web
application prior to adding the content db? I am asking because the
command
"stsadm -o addcontentdb" needs a web application URL.
======================
Correct, you will need to create a new Web application to host your
content
databases which will require a content database, you can remove the
content
database when the Web application has been created.


2) If creating a web application is required before adding the content
db,
what should be the database name for the web application?
=========================
Database naming is irrelevant if you will be removing the content
database
created when the Web application was provisioned.


3) In WSS 2.0, I have 1 content db to 1 site collection and thus 1 unique
URL each. When I use the addcontentdb, how does it knows what is the URL
since I am only providing the web application URL?
=====================
You'll need to specify the -hh command when adding the content database
to
the server farm for example:

Step 1 Set the Web application HH property: STSADM -o setproperty -pn
V2UsedHostHeaderMode -pv true.
Step 2 Attach a content database for upgrade STSADM -o addcontentdb -url
http://hostheaderwebapplication -databaseserver databaseserver
-databasename databasename


4) It says when adding the content db, make sure the root site for the
web
application is included in the first content db you add? What does this
means?
===============
Can be disregarded when performing v2 HH to v3.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you.
Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.


--------------------
References: <44340996-6B54-4180-916B-735133293D59@xxxxxxxxxxxxx>
<RcVe$3nqIHA.1788@xxxxxxxxxxxxxxxxxxxxxx>
<1966D94E-E823-452E-A9BB-7DD5DE49D5E5@xxxxxxxxxxxxx>
<h#uCYd1qIHA.4284@xxxxxxxxxxxxxxxxxxxxxx>
<O1itRgGrIHA.1872@xxxxxxxxxxxxxxxxxxxx>
<08AB3898-3631-4AC8-B4B7-04C691065F8B@xxxxxxxxxxxxx>
Subject: Re: Upgrading Windows SharePoint Services 2.0 scalable hosting
mod
Date: Mon, 5 May 2008 00:00:01 -0700


Hi Daniel,

Thanks for information. I have tried your method but it doesn't solve my
problem.

It seems like I need to create web application for each of the site
collection I want to migrate. This migration is really giving me a pain.

Thanks,
Alex


"Daniel Bugday" wrote:

I wrote an how to on this issue.. works perfect!

http://www.sharepointforum.com/en-US/Wiki/Forms/DispForm.aspx?ID=7

/Daniel Bugday
http://www.sharepointforum.com/
http://www.sharepointforum.com/en-US/Blog/default.aspx

<EF@xxxxxxxxxxxxx> wrote in message
news:O1itRgGrIHA.1872@xxxxxxxxxxxxxxxxxxxxxxx
Hi Steven,

I having trying this out on a test environment for the past 2 days and
I
don't seem to get it work as expected.

My current WSS 2.0 is using scalable hosting mode.
I have only 1 web site (or also known as virtual server) with 1 IP
address.
I create all my site collection using createsiteinnewdb.
All site collections have their own url (e.g. sales.domain.com,
marketing.domain.com, it.domain.com).
Each site collection has its own content database.

Now I am trying out the content database migration to WSS 3.0.
I setup a new WSS 3.0 farm in VM.
I backup the content databases from the WSS 2.0 SQL Server.
Restore the content databases to the WSS 3.0 SQL Server.
Create a new web application in WSS 3.0 using the
servername.domain.com
as
the URL.
Delete the content database created during the creation of web
application.
I run the following to add the content database.
stsadm -o addcontentdb -url http://servername.domain.com -databasename
STS_DB1.
Now if I try to add another content database to the same web
application,
it failed.
Now the site collection in STS_DB1 is suppose to be having the url
sales.domain.com. But I can't use that url, instead I have to use
servername.domain.com.

I also tried resetting up a new WSS 3.0.
Create a new web application using the servername.domain.com as the
URL.
Add new content database.
Create new site collection with host header.
stsadm -o createsite -owneremail myemail@xxxxxxxxxx -url
http://sales.domain.com -ownerlogin domain\mylogin -hhurl
http://servername.domain.com
Add another new content database.
Create new site collection with host header.
stsadm -o createsite -owneremail myemail@xxxxxxxxxx -url
http://marketing.domain.com -ownerlogin domain\mylogin -hhurl
http://servername.domain.com
Now this match what I have in my current WSS 2.0. However, this is
creating new site collections. How can I migrate the content database
and
get the same result?

Please help.....

Thanks,
Alex


"Steven Cheng [MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:h%23uCYd1qIHA.4284@xxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your reply Alex,

Regarding on the further questions you mentioned, I'll do some
further
research on it. I'll update you if I can some new information.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments
and
suggestions about how we can improve the support we provide to you.
Please
feel free to let my manager know what you think of the level of
service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to


http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
Thread-Topic: Upgrading Windows SharePoint Services 2.0 scalable
hosting
mod
Subject: RE: Upgrading Windows SharePoint Services 2.0 scalable
hosting
mod
Date: Tue, 29 Apr 2008 22:52:02 -0700

Hi Steven,

Okay, I am now trying out the content db migration. I am trying to
follow
the "Upgrading to Windows SharePoint Services 3.0 technology"
document.
The
chapter I am looking at is "Deploy a new farm, then migrate
databases".

There are a few things that I am not sure of as it is not mention in
the
document.

1) After installing a new WSS 3.0 farm do I need to first create a
new
web
application prior to adding the content db? I am asking because the
command
"stsadm -o addcontentdb" needs a web application URL.

2) If creating a web application is required before adding the
content
db,
what should be the database name for the web application?

3) In WSS 2.0, I have 1 content db to 1 site collection and thus 1
unique
URL each. When I use the addcontentdb, how does it knows what is the
URL
since I am only providing the web application URL?

4) It says when adding the content db, make sure the root site for
the
web
application is included in the first content db you add? What does
this
means?

Thanks,
Alex


"Steven Cheng [MSFT]" wrote:

Hi Alex,

As for WSS 2.0 scalable hosting upgrade, based on my research, seems
most
one will recommend content db based migration on a new WSS 3.0 web
application. Here are two blog entries from some SPS engineers:

#Upgrading Windows SharePoint Services 2.0 Scalable Hosting Mode
Server
Farms



http://blogs.technet.com/wbaer/archive/2007/03/31/upgrading-windows-sharepoi
nt-services-2-0-scalable-hosting-mode-server-farms.aspx

#WSS 2.0 to WSS 3.0 Farm Host Header Upgrade FYI



http://blogs.msdn.com/joelo/archive/2007/05/30/wss-2-0-to-wss-3-0-farm-host-
header-upgrade-fyi.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your
comments
and
suggestions about how we can improve the support we provide to you.
Please
feel free to let my manager know what you think of the level of
service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to



http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent
issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each
follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to
reach
the
most efficient resolution. The offering is not appropriate for
situations
that require urgent, real-time or phone-based interactions or
complex
project analysis and dump analysis issues. Issues of this nature are
best
handled working with a dedicated Microsoft Support Engineer by
contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.



--------------------
Thread-Topic: Upgrading Windows SharePoint Services 2.0 scalable
hosting
mode
thread-index: AciqERuv5/OXhhPORjqNE372boi/GQ==
X-WBNR-Posting-Host: 207.46.19.168
From: =?Utf-8?B?QWxleA==?= <EF@xxxxxxxxxxxxx>
Subject: Upgrading Windows SharePoint Services 2.0 scalable hosting
mode
Date: Tue, 29 Apr 2008 08:53:03 -0700


Hi,

What is the best option to upgrade WSS 2.0 scalable hosting mode to
WSS
3.0?

In the upgrade document from MS, I can only either perform In-Place
or
Content DB migration. For the content db migration, if I understand
correctly which is actually like a manual in-place upgrade since I
have
to
complete the migrating of all content databases before I can start
creating
new sites.

Is there a better way of doing this?

Thanks,
Alex











.

Relevant Pages

  • Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
    ... Step 2 Attach a content database for upgrade STSADM -o addcontentdb -url ... After installing a new WSS 3.0 farm do I need to first create a new web ... Upgrading Windows SharePoint Services 2.0 scalable hosting ... I create all my site collection using createsiteinnewdb. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
    ... I create all my site collection using createsiteinnewdb. ... Now I am trying out the content database migration to WSS 3.0. ... Upgrading Windows SharePoint Services 2.0 scalable hosting ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
    ... I create all my site collection using createsiteinnewdb. ... Now I am trying out the content database migration to WSS 3.0. ... Upgrading Windows SharePoint Services 2.0 scalable hosting mod ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Upgrading Windows SharePoint Services 2.0 scalable hosting mod
    ... database when the Web application has been created. ... Upgrading Windows SharePoint Services 2.0 scalable hosting ... My current WSS 2.0 is using scalable hosting mode. ... I create all my site collection using createsiteinnewdb. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Error Event ID 27745
    ... However, it looks like WSS is trying to index your content, but cannot find, ... Office SharePoint Server 2007 ... Event Source: Windows SharePoint Services 3 ... Unable to connect to the database WSS_Content on. ...
    (microsoft.public.sharepoint.portalserver)
Loading