WSS 3.0 upgrade to MOSS 2007 RRS feed

  • Question

  • Can someone please help me? I am in the middle of  a migration from WSS 3.0 to SharePoint 2007 SP2. I am doing this through the database attach method. After making a full backup form the old environment and restored it on the new environment.

    Everything goes swell, but it seems that I cannot open the website after attaching the database with the stsadm –o –addcontentdb command line.

    I received the following error:


     "The Web Cannot display the page

     Mostly likley Causes:

     • The website is under maintenance

     • The Website Has A programming error”



     Can anyone help me?  I’ve been hitting this wall for quite some time now.

    On Google, I cannot find any solution

     Server Info:

    Windows Server 2003 SP2 x64bit (Vitrual)

    SQL Server 2005

     Thank you.

    • Edited by Kurt Lourens Friday, January 6, 2012 2:46 PM
    • Moved by Xue-Mei Chang-MSFTModerator Monday, January 9, 2012 8:47 AM sharepoint 2007 issue (From:SharePoint 2010 - General Questions and Answers)
    Friday, January 6, 2012 2:31 PM

All replies

  • Hi Kurt,

    the first step is to run ststadm -o preupgrade check and ensure you have reslved all of the errors, the second is after you create the new wep app remove the default content database prior to adding the content database you plan to upgrade.


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

    Wednesday, February 22, 2012 6:37 PM
  • Hi Kurt

    Please try the below:

    • Detach and reattach the content db

    Is this issue with all the site collection in the respective content db, if not the try the below:

    • Run the below command if there is any orphan entries stsadm -o enumsites -url New_Web_App_URL >C:\Sites.txt. Check the output if there the site is listed.
    • Databaserepair: http://technet.microsoft.com/en-us/library/cc288636%28v=office.12%29.aspx

    Regards Ram

    Thursday, February 23, 2012 9:18 AM
  • HI,

    As you have already attached the database first execute one configuration wizard and then try again.

    I hope this will help you out.

    Thanks, Rahul Rashu

    Thursday, February 23, 2012 7:50 PM