SharePoint 2016 Upgrade: How to solve the “Feature is referenced in database but isn’t installed on the current farm” error
Tags: sharepoint2016, deployment, migration, sharepoint
Published: 2018-09-24 07:36:39

---
title: SharePoint 2016 Upgrade: How to solve the “Feature is referenced in database but isn’t installed on the current farm” error
published: true
tags: SharePoint 2016,Deployment,Migration,SharePoint
canonical_url: https://blogit.create.pt/miguelisidoro/2018/09/16/sharepoint-farm-update-how-to-solve-the-feature-is-referenced-in-database-but-isnt-installed-on-the-current-farm-error-in-a-sharepoint-2016-farm/
---

The post [SharePoint 2016 Upgrade: How to solve the “Feature is referenced in database but isn’t installed on the current farm” error](https://blogit.create.pt/miguelisidoro/2018/09/16/sharepoint-farm-update-how-to-solve-the-feature-is-referenced-in-database-but-isnt-installed-on-the-current-farm-error-in-a-sharepoint-2016-farm/) appeared first on [Blog IT](https://blogit.create.pt).

Hello,

Recently, I migrated a SharePoint 2010 farm to SharePoint 2016 and used an automated installation process using PowerShell and [AutoSPInstaller](https://autospinstaller.com/) to install the new SharePoint 2016 farm that ensured that the latest updates where applied, leaving the SharePoint 2016 farm updated and working properly (if you want to learn more about how to install a SharePoint farm in an automated way using PowerShell, I invite you to click [here](https://dev.to/mlisidoro/how-to-install-a-sharepoint-2016-farm-using-powershell-and-autospinstaller-part-1-54m5) and [here)](https://dev.to/mlisidoro/how-to-install-a-sharepoint-2016-farm-using-powershell-and-autospinstaller-part-2-5e36).

After installing the farm and migrating the web applications, new updates were installed in the farm (if you want to keep up with the latest SharePoint updates, click [here](https://buildnumbers.wordpress.com/sharepoint/)) but when I ran the SharePoint Products and Configuration Wizard to ensure the new updates were properly installed (to know more about the need to run SharePoint Products and Configuration Wizard after a SharePoint farm update, click [here](https://blogs.technet.microsoft.com/stefan_gossner)), I got an error that was preventing me to finish the update process.

**Important Note:** Both source SharePoint 2010 and target SharePoint 2016 farms have Standard SharePoint licenses.

# The Problem

After installing the updates and after running the SharePoint Products and Configuration, I was getting the following error:

![](https://i1.wp.com/blogit.create.pt/wp-content/uploads/2018/09/SP2016_PSConfig_Error.jpg?resize=621%2C536&ssl=1)

The error details:

_An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information:_

_Feature (Name = [SharePoint Portal Server Status Indicator List template], Id = [065c78be-5231-477e-a972-14177cc5b3c7], Description = [SharePoint Portal Server Status Indicator List template], Install Location =_ _**[BizAppsListTemplates]) is referenced in database [Content\_DB]**, **but isn’t installed on the current farm** __. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)_

_Feature (Name = [SharePoint Server Enterprise Site Features], Id = [0806d127-06e6-447a-980e-2e90b03101b8], Description = [**Features such as the Visio Services, Access Services, and Excel Services applications included in the SharePoint Server Enterprise License.**],_ _Install Location = **[PremiumWeb]) is referenced in database Content\_DB] but isn’t installed on the current farm**__. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)_

_Feature (Name = [SharePoint Portal Server Report Library], Id = [2510d73f-7109-4ccc-8a1c-314894deeb3a], Description = [SharePoint Portal Server Report Library], Install Location =_ **_[ReportListTemplate]) is referenced in database [Content\_DB], but isn’t installed on the current farm_**_. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)_

_Feature (Name = [InfoPath Forms Services Support], Id = [c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5], Description =_ _[InfoPath Forms Services Lists and Related Pages to Enable Presentation of Forms on the Server.], Install Location = [**IPFSSiteFeatures]) is referenced in database Content\_DB], but isn’t installed on the current farm**__. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)_

_Feature (Name = [Data Connections Feature], Id = [00bfea71-dbd7-4f72-b8cb-da7ac0440130], Description = [], Install Location =_ **_[DataConnectionLibrary]) is referenced in database Content\_DB], but isn’t installed on the current farm_**_. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)_

_Upgrade [SPContentDatabase Name=Content\_DB] failed.        (EventID:an59t)_

_Exception: **The upgraded database schema doesn’t match the TargetSchema** __ **  **       (EventID:an59t)_

_Upgrade Timer job is exiting due to exception:_ _Microsoft.SharePoint.Upgrade.SPUpgradeException: **The upgraded database schema doesn’t match the TargetSchema** _

There are two main problems here:

- There are references in the content database to SharePoint Enterprise Features (InfoPath Form Services, Visio Services, Excel Services, etc) – my guess here is that sometime along the way, the source SharePoint 2010 farm had an Enterprise SharePoint license and was downgraded to a Standard license, leaving behind however references to Enterprise features in the content database
- There is a mismatch between the content database schema version and the version of SharePoint updates installed in the farm

One additional symptom that confirms there is an upgrade issue is the Upgrade Status page in Central Administration that showed the upgrade status as Failed:

![](https://i0.wp.com/blogit.create.pt/wp-content/uploads/2018/09/SP2016_Upgrade_Status_Error.jpg?resize=696%2C206&ssl=1)

# The Solution

The solution to this problem was a two part solution, both applied in the target SharePoint 2016 farm:

- Fixing the missing Enterprise features references in the content database
- Fixing the content database schema version mismatch

For more details about the solution, click [here](https://blogit.create.pt/miguelisidoro/2018/09/16/sharepoint-farm-update-how-to-solve-the-feature-is-referenced-in-database-but-isnt-installed-on-the-current-farm-error-in-a-sharepoint-2016-farm/).

Happy SharePointing!

The post [SharePoint 2016 Upgrade: How to solve the “Feature is referenced in database but isn’t installed on the current farm” error](https://blogit.create.pt/miguelisidoro/2018/09/16/sharepoint-farm-update-how-to-solve-the-feature-is-referenced-in-database-but-isnt-installed-on-the-current-farm-error-in-a-sharepoint-2016-farm/) appeared first on [Blog IT](https://blogit.create.pt).