Hi. I am preparing for migration to MOSS2007 from SP2003 SP2. I ran the prescan tool over the database, and it has come back with errors (below) at the very beginning of the log file. C:/>prescan /all 05/13/2010 09:21:58 Cannot locate the list definition required for upgrade. Check to ensure you have all templates and language packs installed. 05/13/2010 09:21:58 Error: Exception scanning web: http://address 05/13/2010 09:21:58 System.Runtime.InteropServices.COMException (0x80004005): Cannot complete this action. Please try again. at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateSchemaAllListsOfWeb(String bstrUrl) at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPWeb(SqlConnection connection, String vsUrl, SPVirtualServer vs, SPSite site, SPWeb web) So far, I have done the following to try and get it the prescan to complete successfully. Ran STSADM -o enumtemplates to determine number and ID of templates to add to preupgradescanconfig.xml C:\>stsadm -o enumtemplates There are no items matching the criteria specified. Ran STSADM -0 databaserepair to determine any orphaned lists or sites. C:\>stsadm -o databaserepair -url http://address -databasename Address1_SITE <OrphanedObjects Count="0" /> Thought I'd go ahead and try delete any corruptions anyway: C:\>stsadm -o databaserepair -url http://address -databasename Address1_SITE deletecorruption Command line error. "deletecorruption" not listed as an operation that can be used. Decided to detach and reattach the Content database via CA to make sure those sites are not stuck in the config db as they are not showing as active on the portal site: (CA) SPS > Remove Content Database Returned to Manage Content Databases and Content database is still listed, where normally, the content database is not displayed if it has been detached successfully. Ok, I'll detach the content database using STSADM C:/>STSADM -o deletecontentdatabase -databasename Address1_SITE -databaseserver DEV-SQL -url http://address Lo, the same result. Cannot detach the database. Ok, time for SPSADM: Made the content DB on DEV-SQL readonly and ran SPSADM "repairorphans". (Even though the databaserepair indicated none) C:\Program Files\SharePoint Portal Server\Bin>spsadm repairorphans http://address Repairing... Done. The repair process happened quite quickly, (considering it had to detach and reattach the content database), so I assumed it hadn't run successfully at all even though the SPSADM had indicated it did. I reviewed the log file output from Sharepoint Portal Server which indicated everything went well, (including the detach/reattach, but also indicated a Leak: 00000678 UNK 00000000 00000E10 Successfully repaired orphans<BR> 00000688 CRI 00000000 00000E10 CResourceManager::ObjectMain unloading with a non-zero refcount. (1)<BR> 00000688 CRI 00000000 00000E10 CResourceManager::ObjectMain Unloaded.<BR> >>> 00000688 CRI 00000000 00000E10 CUrlMap::ObjectMain Leak detected! Unloading with a non-zero refcount. (1)<BR> 00000688 CRI 00000000 00000E10 CUrlMap::ObjectMain Unloaded.<BR> So, I detached the Content DB from the SQL server manually, restarted IIS on Portal Server, and reattached the Content DB. Run prescan again using the /all switch c:/temp/prescan>prescan /all No change. Prescan failed, with the same error results. I've run the prescan with custom templates listed in the preupgradescanconfig.xml file: c/ prescanupgradeconfig.xml - same issues I've run the prescan with url indicated: /v http://address - same issues. The reports have not indicated any orphaned objects. I haven't yet tried to detach and reattach the config db. I'm running out of ideas. Can anyone give me some advice on what to try next? Thanks for looking

This issue was finally resolved so I thought I would share, although because of the cause, its unlikely to be replicated by anyone else. After many weeks trying many different things with the help of MS Support, I took a copy of the 1033 from a fresh install and overwrote the one on my problem server. This kept all my customised folders intact, but replaced the files in the SPS and STS folders. I then ran the prescan and got a successful result. After comparing the two directories (new 1033 and problem 1033) there was only one file that was showing any differences, and that was in the default.aspx in the SPS directory. In 2007, it appears a "cleanup" of the SPSWC:Toolbar was made by someone, so all ToolBarButton id references were added to the same line. So instead of: <SPSWC:SubmitLinkToolBarButton runat="server" id="TBBNewListing" /> it was modified to: <SPSWC:SubmitLinkToolBarButton runat="server" id="TBBNewListing" /> I confirmed this was the cause of my prescan issues by running prescans against both versions and the one with single lines failed. thanks