Missing Feature - SharePoint 2010 to 2013 Upgrade

  • 26 September 2017
  • 2 replies
  • 9 views

Badge +3

Hi,

I am upgrading SharePoint 2010 to 2013, when try to perform Test-SPContentDatabase got following message, on my current SharePoint 2013 environment i have just install Nintex and have not yet perform further configuration for Nintex. Please guide what is an issue and how to fix it.

Thx

Category : MissingFeature
Error : True
UpgradeBlocking : False
Message : Database [WSS_Content_DB] has reference(s) to a missing
feature: Name = [Nintex Workflow 2010 InfoPath Forms], Id =
[80bf3218-7353-11df-af9f-058bddfd72085], Description =
[Allows Nintex Workflow to use start forms and task forms
designed with Microsoft InfoPath 2010.], Install Location =
[NintexWorkflowInfoPath].
Remedy : Feature (Name = [Nintex Workflow 2010 InfoPath Forms], Id =
[80bf3218-7353-11df-af9f-058bdfd72085], Description =
[Allows Nintex Workflow to use start forms and task forms
designed with Microsoft InfoPath 2010.], Install Location =
[NintexWorkflowInfoPath]) is referenced in database
[WSS_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.
Locations :


2 replies

Userlevel 7
Badge +11

Hi Irfan,

What I would suggest is that you configure Nintex Workflow to a point where the default configuration is done in your 2013 environment.

eg. Creating the configuration DB, uploading a license etc.

Then try that script again.

Vadim

Userlevel 5
Badge +8

Hi irfan mughal‌,

Vadim's advice is solid on this one.  I would recommend referencing the 2010 --> 2013 Migration Guide for the step-by-step instructions on migrating SharePoint with Nintex. 

For the particular error message you received around the 2010 features may mean you need to deploy the nintexworkflowbackwardcompatibilityui.wsp solution to the affected Web Application.  This solution will make all Nintex Features available for sites that may still be running in 2010 compatibility mode.

Reply