Re: Host Headers after Migration - Help!!!

Result: After the database restore, the user cannot access the site via the
URL that Original Web App was Created in. Root Site Collection has URL of Host Header of WSS2 Content DB. '
Should have URL of /

Resolution: A bit more info on what I did, Had to make it 10 steps. (-:
1. Set the Host Header in the table of the WSS2 content database to the URL that you used to Create the WSS3 Web App
2. Remove Content DB that was Created with WSS3 Web App
3. set Parameter V2UsedHostHeaderMode to True
4. -o addcontentdb WSS2 DB (it gets Upgraded) (Root site Collection has URL of Host Header)
5. set Parameter V2UsedHostHeaderMode to False
6. Remove Upgraded WSS3 Content DB
7. Edit Site table and replace Host Header URL with NULL
8. -o addcontentdb WSS3 Upgraded and modified DB (Root site Collection has URL of /)
9. The site using Web App URL works (no again, it never worked in WSS3)
10. Bug and we will report it to product team.



RE" As to the upgrade issue: "Parent=SPDatabaseServiceInstance could not be accessed" you posted in a different post, I have responded to you in that post. To further discuss this upgrade issue, let's continue our mmunications in that post."

I do not see that reply to that post thread. I see several other messages that have been posted since your reply to this post.



"Alex Xie [MSFT]" <v-alxie@xxxxxxxxxxxxxxxxxxxx> wrote in message news:BYDyrH%23iHHA.3528@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Scott,

Thank you for your update and feedback.

From your reply, I understand that you have resolved this host header issue
by manually modifying the table in the content database. I appreciate your
efforts and time put into this issue.

It seems to be a bug in WSS 3.0 admin tools that leaded to this issue. I
will report this issue to our product team so that we will put this issue
on to schedule to fix. I am truly sorry for the inconvenience you have
experienced.

Here, I want to list a summary of this issue.

ARCR
-------------
Action: Migrate a WSS 2.0 content database to WSS 3.0

Result: After the database restore, the user cannot access the site via the
URL with Host Header

Cause: There is a bug that the parameter V2UsedHostHeaderMode and WSS 3.0
stsadm.exe admin tool haven't addressed.

Resolution:
1. Set the Host Header in the table of the content database.
2. Remove the site content database and then re-add the modified one
3. The site using Host Header in URL works again.
4. Bug and we will report it to product team.

As to the upgrade issue: "Parent=SPDatabaseServiceInstance could not be
accessed" you posted in a different post, I have responded to you in that
post. To further discuss this upgrade issue, let's continue our
communications in that post.

In the meantime, I would like to inform you that I will close the post of
which the subject is "Very Disappointed in WSS Phone Support" as duplicated
post since you are talking about the same issue as this one. If you have
any concerns, please feel free to let me know.

Regards,

Alex Xie
Microsoft Online Partner Support

======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.

We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

.

Relevant Pages