Deena Abbas Ali on Sat, 17 Dec 2016 03:34:37
I have sharepoint environment, which has previously K2 however currently it's removed. I would like currently to clean all k2 references in the content database. I am receiving the below error in the central administration
[MissingWebPart] WebPart class [334d10fa-a50a-5f79-ffbb-2e1d5e80c15a] (class [SourceCode.SharePoint.ProcessPortal.WebPartPages.SchedulesWebPart] from assembly [SourceCode.SharePoint.ProcessPortal, Version=126.96.36.199, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d]) is referenced  times in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
I have followed the article "http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html" to locate the references. I have found the LeafName in the database however in the site collection the page is not exist. I have checked it using designer and other sharepoint management tool but no luck to found that page. I have delete the item from the database in AllDocs table and in AllDocsStream tables. But still I m receiving the error in the central administration.
Is there any SQL query to clean the references and remove the effected item from the content database.
Trevor Seward on Sat, 17 Dec 2016 04:53:06
No, direct database access is unsupported with (most) SharePoint databases. Instead, use the object model. You can also use http://featureadmin.codeplex.com/ to try to rid sites/webs of features.
Deena Abbas Ali on Sat, 17 Dec 2016 09:11:03
Thanks for reply , I have tried featureadmin.codeplex.com with no luck to remove the error. I follow the http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html article and the script return empty result ; no data in return result i.e. siteId, webId, ...etc.
Any other suggestion plz.
Victoria Xia on Wed, 21 Dec 2016 11:40:13
Please re-check if you have used the right web part GUID in PowerShell command.
And make sure that the command you are running are correct.