Re-attaching the content database gives error while trying to do migration based upgrade from TFS 2005 to TFS 2010
This is one of the interesting issues that I came across while trying a migration upgrade of TFS 2005 to TFS 2010, we have to reattach the old SharePoint content database to the new Windows SharePoint Services 3.0 instance on the TFS 2010 machine by running the following command:
stsadm.exe -o addcontentdb -url https://servername -databasename <content_database_name>.
While performing the above mentioned command we may get the following error message:
"The pre-upgrade scan tool has not yet been run on this database SPContentDatabaseName=sts_content_tfs Parent=SPDatabaseServiceInstance. You must run the pre-upgrade scan tool before you can continue with the upgrade process. Run the tool from the following path c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\prescan.exe."
When you try to run the prescan tool on the new TFS 2010 machine, you will get the following error message:
"This program requires Windows SharePoint Services V2.”
We found that we get these messages as the prescan tool command needs to run against the WSS 2.0 content database that is attached to a WSS 2.0 virtual server on the TFS 2005 machine before upgrading the database to the WSS 3.0 schema on the TFS 2010 machine by using the stsadm –o addcontentdb command.
Hence, to resolve this issue we performed the following steps
1. Download and install the pre-upgrade scan tool from the Microsoft Download center (https://go.microsoft.com/fwlink/?LinkId=92383) to your original TFS 2005 machine.
2. On the command line, change to the folder that contains the downloaded file, and then run the following command to run scan on the original/source server:
prescan.exe /all
After the scan has completed, a summary report is displayed in the command-line window.
Note: If there were any errors or if any upgrade issues were found for your sites, you can review the full report to see the details. The report is named PreupgradeReport_uniqueID_Log.txt (where uniqueID is a number string) and it is located in the temp directory on the computer of the user who ran the tool (for example, %SYSTEMDRIVE%:\Documents and Settings\User1\Local Settings\Temp). There is also a prescan.log file in the same directory; this prescan.log file notes the time or times when the pre-upgrade scan tool was run.
After you run the pre-upgrade scan tool, you can review the reports to find and troubleshoot issues (search for "error" in the report to find the issues).
Please refer to https://support.microsoft.com/kb/937291 for details regarding some common errors reported by the pre-scan tool & how to fix them.
3. Take the backup of the STS_Content_TFS (the SharePoint content database that contains the content for the team project portals) again and restore it on the target server. To do so, please refer the following msdn article, which talks about in detail of taking and restoring backing of TFS Databases:
https://msdn.microsoft.com/en-us/library/ms253070(VS.80).aspx
4. Go to the target TFS 2010 server with WSS 3.0 Server installed and create a web application as part of upgrade steps by following the msdn article provided below:
https://technet.microsoft.com/en-us/library/cc287954.aspx
5. Open an elevated cmd & change to the %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\12\BIN folder path & run the following command to upgrade & attach the STS_Content_TFS database restored from Step #4:
stsadm-o addcontentdb -url https://localhost –databasname STS_Content_TFS
Author: Nitish Nagpal
Reviewed by: Wendell Phillips