i've inherited an ancient wss2 sp2 installation and been tasked with upgrading it to MOSS 2007 (and then to 2010 next year). i've been fairly successful migrating the data (content database migration, 80 gig database) in the DEV environment. no prescan errors only custom templates (3 different in use on 95% of the sites) and unghosted pages (44 ish). On upgrade to 2007 via stsadm the upgrade log file reports no errors, just warnings (could not find custom template) because i did not create an upgrade.xml file for my custom templates. after the database upgrade is complete i open the site(s) in Sharepoint Designer, i can see ALL data, documents pictures etc. i do however get an error 404 when trying to view in a browser, and SD says default.aspx, allitems etc does not exist for all sites. if i create a default.aspx and copy in the code from a generic page i can view some top level content, but will error 404 on entrance to any libraries or lists. i do not want my old customizations, or my old webparts, all i want is to be able to view the old data in MOSS 2007. do you think this is possible? how? can i elaborate to make my situation clearer? i'd like to think i'm well versed in wss2 and sp2007, so please feel free to be technical in your replies. i have spent the last few months searching the web, and have had good success with the database upgrade, albeit not being able to "see" anything. do i have to do the upgrade with my customizations? it looks to me like the custom templates were minimally changed, could i reset all sites to default or original templates via the database (i've got no issue doing that, would just need some guidance)? any and all comments, URLs etc are greatly appreciated thanx in advance marc.

Hi marc nagainis, Prescan utility creates three different files. The one you need to check is that whose name begins with “PreupgradeReport” prefix and finishes with the “Log” suffix. Open this file, find that the value of "Number of sites using custom template" is greater than zero. This tells us that the "branding" of one of our sites has been modified and set up by us, so we must save these customizations in order to implement them later when WSS 3.0 is installed. The steps for migrating an SPS 2003 content database is as follows: 1. Install Office server in a new farm. 2. Manually reapply configuration settings. a. Ensure that all inclusions are recreated in the MOSS environment. b. Deploy all custom site definitions in the new environment. c. Deploy your custom Web parts to the GAC or Bin. d. Configure your email server in the new environment. e. Recreate quota templates, if any. 3. Migrate the content database from SPS 2003 or WSS 2.0. a. Backup the content databases used in the SPS 2003 or WSS 2.0 environment. b. Restore the content databases to the SQL server used in your Office Serve environment. You can also use the stsadm command line tool to add your SPS 2003 or WSS 2.0 content database to Office Server. To syntax to add a content database is stsadm –o addcontentdb <databasename>. Could you tell us the exact error (404)? Review the upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log. The number of errors and warnings is listed at the end of the upgrade log file. You can follow the instructions given in the KB article <http://support.microsoft.com/kb/918744/> to detect and delete the orphan entries. Then check the effect. Note: Before you delete the orphan entries remember to back up your site. Regards, Rock Wang Microsoft Online Community Support

Hi Rock! thanx for replying, i appreciate it. my migration process was very similar to what you outline above. i'll elaborate a bit. migrating from WSS2.0 SP2 > MOSS 2007 SP2 WSS2.0 Server: Ran Prescan. results are below Number of sites skipped (already scanned): 0 Number of sites scanned: 79 Number of broken sites: 0 Number of webs scanned: 467 Number of broken webs: 0 Number of webs using custom template: 447 (95.72% of total). Number of pages scanned: 24794 Number of unghosted pages: 46 (0.19% of total). created a backup of the content database and copied to my new SQL server, did a restore. MOSS 2007 Server: Installed 2007. Created a web application via Central Admin, had it create a new content database. used STSADM to add old content database and upgrade. removed new content database via Central Admin. old (upgraded) content database is still associated with new Web Application. following is final line of Upgrade.log Inplace Upgrade session finishes. root object = SPContentDatabase Name=DEV_InfoSite Parent=SPDatabaseServiceInstance, recursive = True. 0 errors and 77 warnings encountered. Warnings are all to do with missing templates... i also did not install the French language pack on my moss2007, but i will. [SPContentDatabaseSequence] [WARNING] [6/9/2010 11:05:58 AM]: WebTemplate ID 11001 (lcid: 1033), provisioned in ContentDatabase DEV_InfoSite, is missing. [SPContentDatabaseSequence] [WARNING] [6/9/2010 11:05:58 AM]: WebTemplate ID 11002 (lcid: 1033), provisioned in ContentDatabase DEV_InfoSite, is missing. [SPContentDatabaseSequence] [WARNING] [6/9/2010 11:05:58 AM]: WebTemplate ID 11004 (lcid: 1033), provisioned in ContentDatabase DEV_InfoSite, is missing. [SPContentDatabaseSequence] [WARNING] [6/9/2010 11:05:58 AM]: Could not GetWebTemplates for LCID 1036. my questions would be 1: do i HAVE to create a custom site definition upgrade file etc in order to migrate my data to 2007? 2: if i do HAVE to, thats fine, i can do that. i have already created custom XML files based on WSSUpgrade.xml. in that file, do i have to change <File FromPath="{LocaleId}\STS\default.aspx" ToPath="SiteTemplates\STS\default.aspx" /> the file from path to be my custom template folder? 3: i have read that there are 2 parts to a custom site definition upgrade, the files contained in "web server extensions\12\TEMPLATE\SiteTemplates\NAME" and the renamed upgrade xml file in 12\Config\Upgrade. i am fuzzy on what needs to me in SiteTemplates. i have created the Upgrade file. sorry if this is too long, any and all help is appreciated. marc.