Re: Host Headers after Migration - Help!!!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi Scott,
\par
\par Thank you for the supplemental information you added.
\par
\par With these detailed information given, I am pretty sure we will soon get this issue fixed in our MOSS 2007 and WSS 3.0 products. We highly appreciate your efforts and time put into this issue.
\par
\par As for the second problem, please find that post in this newsgroup and let's discuss that issue in that post. I look forward to hearing from you in that post.
\par
\par Regards,
\par
\par Alex Xie
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par \pard\li720 --------------------
\par Reply-To: "Scott Townsend" <scooter133@xxxxxxxxxxxxxxxx>
\par From: "Scott Townsend" <scooter133@xxxxxxxxxxxxxxxx>
\par References: <AC8FCD73-7A76-4F28-9DCB-92A16AFEA7F2@xxxxxxxxxxxxx> <CeGUMV7iHHA.1144@xxxxxxxxxxxxxxxxxxxxxx> <3B87A437-B662-4176-91C6-A53AB058FEDB@xxxxxxxxxxxxx> <BYDyrH#iHHA.3528@xxxxxxxxxxxxxxxxxxxxxx>
\par In-Reply-To: <BYDyrH#iHHA.3528@xxxxxxxxxxxxxxxxxxxxxx>
\par Subject: Re: Host Headers after Migration - Help!!!
\par Date: Tue, 1 May 2007 12:04:51 -0700
\par Lines: 100
\par Message-ID: <F562CE80-445B-4296-84BA-536785245FA5@xxxxxxxxxxxxx>
\par MIME-Version: 1.0
\par Content-Type: text/plain;
\par \tab format=flowed;
\par \tab charset="iso-8859-1";
\par \tab reply-type=original
\par Content-Transfer-Encoding: 7bit
\par X-Priority: 3
\par X-MSMail-Priority: Normal
\par X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
\par X-MS-CommunityGroup-PostID: \{F562CE80-445B-4296-84BA-536785245FA5\}
\par X-MS-CommunityGroup-ThreadID: 85CE5BF0-5F1F-4926-B5EF-09D22D4035CB
\par X-MS-CommunityGroup-ParentID: 3CE1E920-899B-442B-AFA0-91D6E7BA1B61
\par Newsgroups: microsoft.public.sharepoint.windowsservices
\par Path: TK2MSFTNGHUB02.phx.gbl
\par Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sharepoint.windowsservices:4422
\par NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
\par X-Tomcat-NG: microsoft.public.sharepoint.windowsservices
\par
\par Result: After the database restore, the user cannot access the site via the
\par URL that Original Web App was Created in. Root Site Collection has URL of
\par Host Header of WSS2 Content DB. '
\par Should have URL of /
\par
\par Resolution: A bit more info on what I did, Had to make it 10 steps. (-:
\par 1. Set the Host Header in the table of the WSS2 content database to the URL
\par that you used to Create the WSS3 Web App
\par 2. Remove Content DB that was Created with WSS3 Web App
\par 3. set Parameter V2UsedHostHeaderMode to True
\par 4. -o addcontentdb WSS2 DB (it gets Upgraded) (Root site Collection has
\par URL of Host Header)
\par 5. set Parameter V2UsedHostHeaderMode to False
\par 6. Remove Upgraded WSS3 Content DB
\par 7. Edit Site table and replace Host Header URL with NULL
\par 8. -o addcontentdb WSS3 Upgraded and modified DB (Root site Collection has
\par URL of /)
\par 9. The site using Web App URL works (no again, it never worked in WSS3)
\par 10. Bug and we will report it to product team.
\par
\par
\par
\par RE" As to the upgrade issue: "Parent=SPDatabaseServiceInstance could not be
\par accessed" you posted in a different post, I have responded to you in that
\par post. To further discuss this upgrade issue, let's continue our mmunications
\par in that post."
\par
\par I do not see that reply to that post thread. I see several other messages
\par that have been posted since your reply to this post.
\par
\par
\par
\par "Alex Xie [MSFT]" <v-alxie@xxxxxxxxxxxxxxxxxxxx> wrote in message
\par news:BYDyrH%23iHHA.3528@xxxxxxxxxxxxxxxxxxxxxxxxx
\par > Hi Scott,
\par >
\par > Thank you for your update and feedback.
\par >
\par > From your reply, I understand that you have resolved this host header
\par > issue
\par > by manually modifying the table in the content database. I appreciate your
\par > efforts and time put into this issue.
\par >
\par > It seems to be a bug in WSS 3.0 admin tools that leaded to this issue. I
\par > will report this issue to our product team so that we will put this issue
\par > on to schedule to fix. I am truly sorry for the inconvenience you have
\par > experienced.
\par >
\par > Here, I want to list a summary of this issue.
\par >
\par > ARCR
\par > -------------
\par > Action: Migrate a WSS 2.0 content database to WSS 3.0
\par >
\par > Result: After the database restore, the user cannot access the site via
\par > the
\par > URL with Host Header
\par >
\par > Cause: There is a bug that the parameter V2UsedHostHeaderMode and WSS 3.0
\par > stsadm.exe admin tool haven't addressed.
\par >
\par > Resolution:
\par > 1. Set the Host Header in the table of the content database.
\par > 2. Remove the site content database and then re-add the modified one
\par > 3. The site using Host Header in URL works again.
\par > 4. Bug and we will report it to product team.
\par >
\par > As to the upgrade issue: "Parent=SPDatabaseServiceInstance could not be
\par > accessed" you posted in a different post, I have responded to you in that
\par > post. To further discuss this upgrade issue, let's continue our
\par > communications in that post.
\par >
\par > In the meantime, I would like to inform you that I will close the post of
\par > which the subject is "Very Disappointed in WSS Phone Support" as
\par > duplicated
\par > post since you are talking about the same issue as this one. If you have
\par > any concerns, please feel free to let me know.
\par >
\par > Regards,
\par >
\par > Alex Xie
\par > Microsoft Online Partner Support
\par >
\par > ======================================================
\par > PLEASE NOTE: The partner managed newsgroups are provided to assist with
\par > break/fix issues and simple how to questions.
\par >
\par > We also love to hear your product feedback!
\par > Let us know what you think by posting
\par > from the web interface: Partner Feedback
\par > from your newsreader: microsoft.private.directaccess.partnerfeedback.
\par > We look forward to hearing from you!
\par > ======================================================
\par > When responding to posts, please "Reply to Group" via your newsreader so
\par > that others may learn and benefit from this issue.
\par > ======================================================
\par > This posting is provided "AS IS" with no warranties, and confers no
\par > rights.
\par > ======================================================
\par
\par \pard
\par
\par }
Quantcast