I have content deployment (using database snapshots) configured between an authoring and production SharePoint 2010 environment.

I have a feature called PublishingContent_ContentTypes which I upgraded to version (from to add a new field to a content type. I upgraded the containing WSP on each environment and used Chris O'Brien's Feature Upgrade Kit to upgrade the feature on the sites.

After that, in each environment, I confirmed that version of the PublishingContent_ContentTypes feature is deployed to the site.

enter image description here

However, my content deployment job is failing with the following error:

Feature 'PublishingContent_ContentTypes' is deployed but its version '' is below the minimum required version of ''.

This appears to be happening in the import phase of content deployment. That is, after the snapshot of the source content database has been taken and when the job begins importing content into the destination environments.

Does anyone have any thoughts about why this would be happening? Thank you

1 Answer 1


I would recommend you to deactivate and uninstall the feature using stsadm/PowerShell on destination environment first, the retract and delete the WSP containing the feature. Now, try to add and deploy the WSP containing correct feature version, but DON'T activate/deactivate the feature. In fact let this feature activation/deactivation should be done using Content Deployment (i.e. from Source to Destination).

  • Falak, thanks for your response. I'm comfortable deactivating/reactivating features in an environment, however, uninstalling and reinstalling a WSP is pretty drastic in that it can actually take an application down. Commented Feb 16, 2012 at 22:41
  • 1
    Is there any possibility to Upgrade Solution because you need to do it anyway, if Feature versions are actually different on Source and Destination? I wonder if there is any maintenance window schedule to perform such tasks? Commented Feb 16, 2012 at 22:47
  • The strange thing is that I did actually upgrade the solutions and the feature and verified that the version numbers matched. We just rebooted the servers and all of a sudden the error no longer happens - I love SharePoint :) Commented Feb 16, 2012 at 23:00
  • 2
    Great, to know it works. Perhaps, you might have forgot to perform the IISReset after the upgrade? Commented Feb 16, 2012 at 23:07
  • Interesting point, I thought the Update-SPSolution recycled the application pool. Maybe I should have tried an IISRESET before rebooting. Good suggestion. Commented Feb 16, 2012 at 23:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.