When a SharePoint upgrade fails, it can be due to several reasons, such as database issues, missing features, or configuration problems. Below is a detailed step-by-step guide on how to troubleshoot and resolve a failed SharePoint upgrade.
Step 1: Understand the SharePoint Upgrade Process
SharePoint upgrades involve multiple steps, including:
- Backing up existing data – Ensuring no data is lost.
- Running the SharePoint Products Configuration Wizard – Applying necessary updates.
- Upgrading databases – Ensuring schema and data consistency.
- Upgrading site collections – Ensuring compatibility with the new SharePoint version.
When an upgrade fails, it usually occurs during one of these steps.
Step 2: Check Upgrade Logs
- The first place to look when an upgrade fails is the SharePoint upgrade logs.
- These logs are typically located at:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS - Look for entries containing “Upgrade failed” or “Error”.
Step 3: Use PowerShell to Check Upgrade Status
Run the following command to check the upgrade status:
Get-SPContentDatabase | ForEach-Object { Upgrade-SPContentDatabase -Identity $_.Id }
This will help identify which content databases might be causing the failure.
Step 4: Check for Missing or Corrupted Features
- SharePoint upgrades can fail if certain features are missing or not activated.
- Run the following PowerShell command to check for missing features:
Get-SPFeature | Where-Object { $_.Scope -eq "Farm" } | Sort-Object DisplayName
- If any missing features are found, install them using:
Install-SPFeature -Path "FeatureFolderName"
Step 5: Validate and Upgrade the SharePoint Databases
- Check for orphaned databases
Run:Get-SPContentDatabaseIf a database appears but is not attached, reattach it using:Mount-SPContentDatabase -Name "DatabaseName" -DatabaseServer "ServerName" -WebApplication "http://YourWebApp" - Manually upgrade content databases
If automatic upgrade fails, try manually upgrading the databases:Upgrade-SPContentDatabase -Identity "YourDatabaseName"
Step 6: Check Timer Jobs
- Some SharePoint timer jobs might get stuck, causing an upgrade failure.
- Navigate to: Central Administration → Monitoring → Timer Jobs
- Look for any stuck jobs and restart them.
Step 7: Ensure Services Are Running
Make sure these critical SharePoint services are running:
- SharePoint Timer Service
- SharePoint Administration Service
- SQL Server (MSSQLSERVER)
Check services by running:
Get-Service | Where-Object { $_.DisplayName -match "SharePoint" }
If any of these services are stopped, restart them.
Step 8: Verify IIS and Application Pools
- Open IIS Manager (inetmgr)
- Ensure that:
- SharePoint web applications are running.
- Application pools are not stopped.
- The identity running the app pools has sufficient permissions.
Restart IIS:
iisreset /noforce
Step 9: Run SharePoint Configuration Wizard
If the upgrade is still failing, rerun the SharePoint Configuration Wizard:
- Open “SharePoint Products Configuration Wizard”.
- Follow the prompts and apply any necessary updates.
- Monitor for errors.
Step 10: Check for Missing Updates
Sometimes, a failed upgrade is due to missing SharePoint patches.
- Check installed updates:
- Go to Control Panel → Programs and Features → View installed updates.
- Download and install the latest Cumulative Update (CU) and Service Packs from Microsoft.
Step 11: Manually Update Site Collections
If site collection upgrades are failing:
- Run:
Get-SPSite -Limit All | Start-SPSiteUpgrade - Monitor the progress.
- If a site fails, check the ULS logs for specific errors.
Step 12: Restart and Reattempt Upgrade
- Reboot the SharePoint and SQL servers.
- Run upgrade commands again:
psconfig.exe -cmd upgrade -inplace b2b -wait -force
Step 13: Restore from Backup (If Needed)
If all else fails:
- Restore from a backup before the upgrade.
- Use the SharePoint Backup and Restore tool or SQL Server backups.
Final Thoughts
A SharePoint upgrade failure is usually due to database inconsistencies, missing features, or configuration issues. By following the steps above carefully, you can troubleshoot and resolve the issue effectively.
Would you like assistance with a specific error message from your upgrade logs?