Recently, I migrated a SharePoint 2010 farm to SharePoint 2016 and used an automated installation process using PowerShell and AutoSPInstaller 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 and here).

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) 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), 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:

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:

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

Fixing the missing Enterprise features references in the content database

To fix the problem with references to Enterprise SharePoint features, I used the SharePoint Feature Administration and Clean Up Tool, which basically enables us to delete from the Farm, Web Application, Site Collection and sub sites any references to features that are not installed in the farm. The version I used was the version 2.4.8 that you can download here, that supports SharePoint 2016. The version 3.0, for some reason, didn’t detect the farm, which made it useless (maybe a beta version, not sure).

In this case, to remove the missing feature references, I used the SharePoint Feature Administration and Clean Up Tool to:

• Remove the missing features from the farm
• Remove the missing features from the sub sites

First, I removed the missing features from the farm, by removing the features marked as “Faulty” in the “Farm Feature Administration” tab, using the “Uninstall” button for each missing feature.

After that, I removed the features marked as ERROR in the “Remove / deactivate features in the selected sites” tab, by selecting all the site collection faulty features and using the “Remove from selected SiteCollection” button.

Finally, for each site, I selected the faulty site features and removed them by using the “Remove from selected Site (SPWeb)” button.

Fixing the content database schema version mismatch

To fix the version mismatch between the content database schema version and the version of installed SharePoint updates, I executed the following PowerShell command (executed with “run as administrator”):

Get-SPContentDatabase | Upgrade-SPContentDatabase

After this, I ran the SharePoint Products and Configuration Wizard again, and this time, it ran successfully:

To confirm if everything was OK, I checked the following pages in Central Administration in the target SharePoint 2016 farm:

• The Upgrade Status page
• The Database Upgrade Status page

In the Upgrade Status page, there is now a Succeeded upgrade status:

In the Database Upgrade Status page, there is an indication of “No action required” for all content databases in the farm, meaning that all databases were properly upgraded and the respective schema version is the same as the installed SharePoint updates:

Hope this helps!

Related Articles

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

In the meantime, SharePoint 2019 RTM is already out there! If you want to know all about the new features available in the new SharePoint Server release, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are involved in a SharePoint upgrade and want to learn more about the upgrade process, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

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 appeared first on Blog IT.

Today i’m going to talk about SharePoint Scenarios and what are the main difference between this three types of scenarios and what scenario should be the option for your environment…

So, the three types of architecture scenario that you can have on your SharePoint environment are the following:

What should you choose?! Well in fact there are so many question that you need answered before take an decision!?

It isn’t easy take a decision, let’s analyse what are the main benefits each architecture:

SharePoint On-Premises:

• Private Cloud
• Dedicated environment
• Internally hosted
• Internally managed
• Internal designed

• Migration Flow:

SharePoint Online:

• Public Cloud
• Partially or fully dedicated
• Externally hosted
• Externally or Internally managed
• Internally managed
• Minimal customization

Cloud benefits according to cloud users?

• Increase efficiency (55 %)
• Improved employee mobility (49 %)
• Increased ability to Innovate (32 %)
• Freed current IT staff for other projects (31 %)
• Reduce IT operation costs (25 %)
• Enabled us to offer new products/ services (24 %)

• Migration Flow:

SharePoint Hybrid Solution:

What is Hybrid SharePoint?

“Productivity services in SharePoint Online (Office 365) which are securely integrated with on-premises SharePoint Server 2016 to provide unified functionality and access to data.”

Why considering a Hybrid SharePoint Solution?

• Large existing investments (customized SP deployments w/lots of data and settings,custom solutions, LOB systems, etc…)
• Functionalities I can’t do in the Cloud that i can do on premises;
• Keep Sensitive Data on Premise
• Collaboration with External Partners
• Capacity Flexibility
• Intranet – Extranet
• Geo Location

Same Benefits of Hybrid SharePoint Solution?

SharePoint Business to Business Collaboration: Extranet for Partners with Office 365

“on-premises extranet site involves complex configuration to establish security measures and governance, including granting access inside the corporate firewall, and expensive initial and on-going cost….SharePoint Online, partners connect directly to a members-only site in Office 365, without access to the corporate on-premises environment or any other Office 365 site. Office 365 Extranet sites can be accessed anywhere…”

SharePoint hybrid sites and search

“A hybrid environment can help your company get started in the cloud, taking a first step to explore the cloud functionality at own your pace. It also enables enterprise users to be connected from almost anywhere to the resources and content they need… SharePoint hybrid features, you can consolidate search results between SharePoint Server and Office 365, consolidate user profiles in Office 365, and offload your users’ personal storage to the cloud…”

• Migration/Interactions Flow:

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint Scenarios – Online, On-Premises or Hybrid!? appeared first on Blog IT.

Today i will talk about SharePoint Migrations, a complex process that requires an extra efforts depending the version of SharePoint.

Why should I upgrade or migrate to SharePoint 2016?!

1.SharePoint Farm of company is old! If it’s SP2003, SP2007 or SP2010, Microsoft do not give more support and updates for that versions, so you can’t expect more features our updates for your infrastructure.

SharePoint Product Lifecycle

2.SharePoint 2016, it’s more stable and fast than the other version even is a version more close to the cloud, all the innovation and experience hosting SharePoint Online brought that knowledge and innovation to SharePoint 2016, also that, new version use MinRoles a significant improvement in terms of infrastructure.

3.FIM is no more a component of SharePoint, it was replaced by Microsoft Identity Manager (MIM).

4.Data Loss Prevention is now part of SharePoint.  You can now identify, monitor for, and protect sensitive data across SharePoint 2016, SharePoint Online, and One Drive for Business using SharePoint 2016.

5.Hybrid Solutions between SharePoint 2016 and Office 365,  now you can easily integrate with Office 365 using SharePoint 2016. Taking the advantage of Cloud Hybrid Search, Delve, Hybrid Sites, Groups, Profile Redirection and more running SharePoint in hybrid mode.

6.Durable Links,move files wherever you like and your link remains valid. It may seem like a small thing but to end users this is a big deal.

7.Cloud Hybrid Search in the cloud you can display all of your results from O365 and on-prem will be listed happily together, by relevancy, and it’s all encrypted by the crawler.

There are many other new features offered by SharePoint 2016 you can read more about in this link.

Which approach should I take, to upgrade or migrate?!

What questions should I ask before upgrading or migrating?

It’s important understand what is the main processes and data that you what migrate for your new version of SharePoint, this will be essential to define the process and success of the operation. Ask questions about the current solution and success criteria you can define the scope of the migration or upgrade, this type of process not is fast but is really importance is be precision.

Are you now ready to migrate or upgrade?

The  success of  migration or upgrade is planning, then some more planning, and organizational buy in. Moving to SharePoint 2016 will deliver better security, collaboration, content management, mobility, compliance and cloud connectivity features. But the migration or upgrade warrants a much more care and attention to detail in planning, you need to lay out every step needed to get there and  engage all the stakeholders in your organization in all aspects of the selected process.

New and improved features in SharePoint Server 2016

Create the SharePoint Server 2016 farm for a database attach upgrade

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint 2016 – Essential Migration Steps and Considerations appeared first on Blog IT.