Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have run a preupgrade check on a SP2007 database to identify issues prior to upgrading to SP2010. The report shows a lot of messages for missing webparts. The strange thing is that I cannot identify these webparts. The message looks like:

WebPart class [293e8d0e-486f-e21e-40e3-75bfb77202de] is referenced [11695] times in the database [sharepoint-3], but is not installed on the current farm....

When I run a TEST-SPCONTENTDATABASE command on the SP2010 environment I get similar output. I have also downloaded the SP2007Migration.console.exe from CodePlex which takes the output of the TEST-SPCONTENTDATABASE from the SP2010 environment and runs that on the SP2007 environment to fetch all the sites/pages/webpart names etc.

Still the referenced web part issues relate to many sites and have a blank title. I have checked the sites to see if they have errors on the SP2007 environment but there are none. I have even mounted the database to SP2010 and after the migration the sites are looking fine. (So what are we talking about? haha)

Question is: what is the easiest way of identifying the webparts name, title, assembly etc as I have no clue where the issues are coming from. I need to know if I can safely ignore those like old references in the database which are perhaps from SP2003?

Thanks!

share|improve this question

1 Answer 1

up vote 3 down vote accepted

This issue keeps cropping up.

To recap, the best way to do get a quick view of what is being used where in a given content database is with the stsadm command enumallwebs using the addtional parameters (supplied with the October 2009 Cumulative Update, if you are using SP2007):

stsadm -o enumallwebs -includefeatures -includewebparts -includeeventreceivers -includesetupfiles -includecustomlistview
share|improve this answer
2  
This is THE way to do it. The Guid cannot be used to backtrace the web part. –  Wictor Wilen MCA MCM MVP Jun 7 '11 at 9:35
    
Yes, this works. Apologies for not having discovered the other issue earlier. So I can now see the Type of the webpart which is a default Microsoft.SharePoint.WebPartPages.ListFormWebPart. Keeps me puzzled as why preupgradechecker is referring oob web parts as 'not installed on farm'. Thanks @SPDoctor @Wictor-SharePoint-MVP –  Serve Hermans Jun 7 '11 at 10:16
    
I used this and found the faulty webpart in the XML like this: <WebPart Id="96868c1b-d534-790b-45ed-6c4f2fe6efa0" Count="1" Status="Missing" /> But now what? What can I do to correct this? –  Jasper Jun 9 '11 at 14:49

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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