Issue after ContentDB migration from 2007 to 2010

Question

I have migrated Content Db from 2007 to 2010 . Taken the backup and restored in 2010 and mounted with power shell script

Problem is I have 7 custom list in migrated 2010 environment with data from 2007. While browsing one any of this list showing an error like  “Possible mismatch between the reported error with code = 0x8107058a and message: "Feature 'b77c9e5c-cfba-4ef6-84d6-b8de940fe108' for list template '100' is not installed in this farm.  The operation could not be completed." and the returned error with code 0x80070002.    95db0f72-f6e4-4462-870f-f22fba2dfbbf”

Failed to determine the setup path of the list schema for feature {B77C9E5C-CFBA-4EF6-84D6-B8DE940FE108}, list template 100.    95db0f72-f6e4-4462-870f-f22fba2dfbbf

 Whenever I install the wsp in CA (wsp used to create this custom list in 2007 and not activating the feature), this list will start working with data with out issue.Is there any alternate solution for this issue ?

---

alancejacob

Answer 1

Probably not, the list is expecting the feature to exist for some reason and needs to be deployed to the farm.

Perhaps the list needs a custom content type that is deployed by the solution. There could be other reasons, the point is there is some sort of dependence on the solution (oh the joys of upgrading).

This requirement would have been identified by the preupgradecheck stsadm operation when run in the 2007 farm, the Test-SPContentDatabase cmdlet that is typically run before adding the content database with Mount-SPContentDatabase, and you will have likely seen errors in the upgrade log mentioning this feature not existing in the farm.

---

Jason Warren

Infrastructure Specialist

Habanero Consulting Group

habaneroconsulting.com/blog

Answer 2

Yes exactly. So how can I resolve this issue with new source code. For part of migration I’m developing new source code (VS 2010) for custom application. I have created the same replica for my custom list with schema.xml and same feature Id. But issue is still pursuing.

I have not done Visual Upgrade in Migrated site !

---

alancejacob