When performing a SharePoint farm upgrade, you might see the message “Farm upgrade completed with errors.” This means the upgrade process finished, but some components encountered issues. Below is a detailed step-by-step guide to troubleshooting and resolving this issue.
Step 1: Understand the SharePoint Farm Upgrade Process
A farm upgrade involves:
- Upgrading databases – Ensuring schema and data consistency.
- Upgrading web applications – Migrating settings, services, and features.
- Upgrading site collections – Ensuring compatibility with the new SharePoint version.
- Verifying configuration settings – Ensuring services and applications are running properly.
If any of these steps encounter an issue, you will see “Farm upgrade completed with errors.”
Step 2: Check SharePoint Upgrade Logs
- Navigate to the Upgrade Logs at:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS - Look for error messages or warnings in the logs.
- Alternatively, run PowerShell to check upgrade status:
Get-SPUpgradeSession | Select-Object Id, StartTime, EndTime, Status
Step 3: Use PowerShell to Identify Errors
Run the following command to view a summary of upgrade issues:
Get-SPUpgradeStatus -All
- This provides a detailed report of what failed.
For a specific service or component, run:
Get-SPContentDatabase | ForEach-Object { Upgrade-SPContentDatabase -Identity $_.Id }
Step 4: Resolve Feature and Solution Issues
Missing or outdated features can cause errors.
- Check for missing features:
Get-SPFeature | Where-Object { $_.Scope -eq "Farm" } | Sort-Object DisplayName - Activate missing features:
Enable-SPFeature -Identity "FeatureName" -Url "http://YourSiteURL" - Remove deprecated features:
Uninstall-SPFeature -Identity "FeatureName" -Confirm:$false
If missing solutions (WSP files) caused the error, redeploy them:
Install-SPSolution -Identity SolutionName.wsp -GACDeployment
Step 5: Upgrade Content Databases
Ensure all content databases are properly upgraded:
Upgrade-SPContentDatabase -Identity "YourDatabaseName"
- If errors persist, check the ULS logs for database-related messages.
Step 6: Verify Timer Jobs
A stuck or failed timer job can cause an incomplete upgrade.
- Navigate to:
Central Administration → Monitoring → Timer Jobs - Look for stuck or failed jobs and restart them.
- Restart the SharePoint Timer Service using PowerShell:
Restart-Service SPTimerV4
Step 7: Check Service Applications
Certain service applications may not upgrade correctly.
- Go to Central Administration → Manage Service Applications
- Check for any stopped or failed services.
- Restart problematic services:
Restart-Service -Name SPAdminV4
Step 8: Reattempt the Upgrade
Once all issues are fixed, run the upgrade again:
psconfig.exe -cmd upgrade -inplace b2b -wait -force
This reprocesses any previously failed components.
Final Thoughts
The “Farm upgrade completed with errors” message indicates that some parts of the upgrade did not succeed fully. By systematically checking logs, verifying databases, fixing feature issues, and ensuring all services are running, you can resolve these errors and complete the upgrade successfully.
Would you like help interpreting specific errors from your upgrade logs?