locked
SPS 2003 to MOSS (Database Attach) Upgrade: Site Collections not migrated RRS feed

  • Question

  • Afternoon all,

    I'd be interested in getting your views on.  I've got a SharePoint 2003 SP2 / SQL 2000 SP 2 deployment thay I've been asked to migrate into SharePoint 2010  We don't need the central portal, just the site collections, so I've identified the SPCON_Site SQL Database that we need to work with.  Please note that I don't have a SharePoint 2003 test farm, only the live one, which itself has recently crashed.  The 2010 deployment was installed and confgured by another team.  S, my intended approach was: -

    1. Run the prescan.exe on the WSS2 databases.  Take appropriate action
    2. Export the DB from SQL 2000, import into SQL 2008 R2 (as part of my intermediate MOSS 2007 virtual build)
    3. Attach the content db to a new SharePoint 2007 web application.  Fix any issues

     

    The problem I'm having is getting from SharePoint 2003 to SharePoint 2007.  I've created a web application, deleted the content DB and used STSADM to attach the migrated WSS 2 DB to the application.  IIS has been restarted but no Site Collections are showing within the Admin GUI or via an STSADM enumsites.  I've not tried this before, so there's no GUID issues to worry about.  Checking against the Web Application doesn't show the WSS2.0 DB as being attached.

    I'm not againt tearing everything up and trying again, but I'd rather get to the bottom of the particular issues before doing so.

    Any pointers are appreciated.


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/

    • Edited by Mike Walsh FIN Tuesday, June 28, 2011 7:57 PM Step 4 is off-topic here (sp 2010)
    Tuesday, June 28, 2011 11:07 AM
    Answerer

All replies

  • Just to confirm that you arent running 2003 and 2007 side by side?  Also, do the site collections depend on a URL and a managed path that is itself supplied by the "other" content database, or do they live under a different web application?  I would double check the managed path settings i the new web app to be safe.

    Chris


    Chris McNulty MCSE/MCTS/MSA/MVTSP http://www.kma-llc.net | blog http://blogs.kma-llc.net/microknowledge | twitter @cmcnulty2000 Microsoft Community Contributor Award 2011
    Tuesday, June 28, 2011 11:22 AM
  • Hi Chris,

    Just to add I didn't bother setting up a root site collection on the 2007 application.

    They're not running side by side no, the VM has just 2007 installed.  The site collections didn't rely on a managed path as far as I knew but I'll check this.  Would you suggest re-attaching the database if I make a change to the managed path?

    Thanks
    Steven


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/
    Tuesday, June 28, 2011 12:03 PM
    Answerer
  • An update

    The managed paths appear fine.  In SP03, the root site was under <SERVERNAME>/sites/SiteName.  I've got no root application in the intended SharePoint 2007 application but the ../Sites managed path is present.

    I've also tried swapping out the content databases in a NEW application rather than editing a current one.  This does attach to the application but still shows no site collections


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/
    Tuesday, June 28, 2011 12:25 PM
    Answerer
  • Ok, I've gone back to the current deployment and have run the preupgrade checker

    06/28/2011 16:33:41 Scan finished with failure.
    06/28/2011 16:33:41 ===============================Logs===============================
    06/28/2011 16:33:41 Log file: C:\DOCUME~1\sandrews\LOCALS~1\Temp\1\PreupgradeReport_634448755560124237_Log.txt
    06/28/2011 16:33:41 Summary file: C:\DOCUME~1\sandrews\LOCALS~1\Temp\1\PreupgradeReport_634448755560124237_Summary.xml
    06/28/2011 16:33:41 ==============================Totals==============================
    06/28/2011 16:33:41 Number of sites skipped (already scanned):   0
    06/28/2011 16:33:41 Number of sites scanned:   50
    06/28/2011 16:33:41 Number of broken sites:   1 (2.00% of total).
    06/28/2011 16:33:41 Number of webs scanned:   1613
    06/28/2011 16:33:41 Number of broken webs:   65 (4.03% of total).
    06/28/2011 16:33:41 Number of webs using custom template:   65 (4.03% of total).
    06/28/2011 16:33:41 Number of pages scanned:   34348
    06/28/2011 16:33:41 Number of unghosted pages:   3849 (11.21% of total).


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/
    Tuesday, June 28, 2011 3:56 PM
    Answerer
  • Steven:

    What did you find as an outcome of your PRESCAN check???
    The trail went cold... and I am having a similar problem - attach DB has no site collections.

    However, when I went back and re-ran PRESCAN, it was skipping the WSSv2 WebApp entirely due to the NeedUpgrade state.  I found this posting:  http://cwsharepointdesign.blogspot.com/2009/03/sharepoint-prescan-utility-hiccups.html

    Ran the following on the WSSv2 box:
    stsadm -o upgrade -url http://WSSv2_WebApp

    This was successful and we got a good PRESCAN, but still no-joy on the DB Attach.

    Thanks,
    Bill Correa
    Arcanum Group, Inc.

    Thursday, April 12, 2012 4:49 AM
  • Hi Bill

    I found the link in that blog post to Joel Olseson's old blog a lot more useful.

    I didn't resolve this manually I'm afraid, I ended up getting a third party tool, which allowed me to get the double-hop bypassed.

    Can you post the results of your prre-scan?


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/

    Thursday, April 12, 2012 9:17 AM
    Answerer