Resume upgrade (SharePoint Foundation 2010)
Applies to: SharePoint Foundation 2010
Topic Last Modified: 2011-09-17
In some cases, you might have to restart upgrade to finish upgrading your sites from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010. For example:
During an in-place upgrade, if the server restarts or the upgrade fails, you must restart the upgrade process by using Psconfig.exe to upgrade the remaining sites.
During a database attach upgrade, any sites that cannot be upgraded will be skipped. After you have corrected any issues in the sites (such as a missing template or language pack, or the site being set to read-only or having exceeded its quota), you can restart upgrade by using a Windows PowerShell command to upgrade just the skipped sites.
|One frequent cause of failures during upgrade is that the environment is missing customized features, solutions, or other elements. Be sure that any custom elements that you need are installed on your front-end Web servers before you begin the upgrade process. You can use the pre-upgrade checker — and, for a database attach upgrade, the test-spcontentdatabase Windows PowerShell cmdlet — to identify any custom elements that your sites might be using. For more information, see Identify and install customizations in the article "Use a trial upgrade to find potential issues."|
In this article:
If you determine that upgrade stopped or failed before the SharePoint Products Configuration Wizard was completed, you can restart the upgrade from that point by running the SharePoint Products Configuration Wizard again or by using a command line operation. This process is also known as forcing a software upgrade. Be sure to research and address the problem that caused the failure or stoppage before you restart upgrade.To restart upgrade for the server farm
Verify that you have the following administrative credentials:
To use Psconfig.exe, you must be a member of the local Administrators group on the server.
Open a Command Prompt window and navigate to the following directory:
%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\14\Bin\
Type the following command:
psconfig -cmd upgrade -inplace v2v -passphrase <passphrase> -wait
Where <passphrase> is the passphrase that was specified when SharePoint Products Configuration Wizard was run. The passphrase is used to join the server farm. The passphrase value must be the same on all servers in the farm if the farm is to function correctly.
There is an optional parameter, -force, that can force the upgrade to continue if the command does not work. Add -force to the end of the command string to force the upgrade process to continue.
|You can enable Windows Installer logging before you start the software upgrade installation again. To enable logging for Windows Installer, see Microsoft Knowledge Base article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/p/?LinkID=99206).|
If the upgrade skipped any site collections during in-place upgrade or database attach upgrade, you can restart the upgrade process for the database that contains that site collection by using a Windows PowerShell cmdlet.To restart upgrade for a database by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
At the Windows PowerShell command prompt (PS C:\>), type the following command:
upgrade-spcontentdatabase -id <GUID>
Where GUID is the identifier for the database. You can run the following cmdlet to find the GUID for a content database:
Get-SPContentDatabase -Identity <content_database_name>
For more information, see Upgrade-SPContentDatabase.