How do I clean up missing server side dependencies from a “dirty” installation?

Question

After a rather hasty (unavoidable) migration/reconfiguration of a SP 2010 Foundation box, I am left with an error in CA regarding a number of missing Features, SetupFiles, and WebParts. I redeployed and then retracted and uninstalled the two solutions that were the cause of the majority of the messages (they weren't being used, which is why they weren't migrated initially) and while the errors went away while the solutions were deployed (except for one regarding a missing template file that had been renamed), they came back after the removal and I'm not sure how to eliminate the references to the "Missing server side dependencies."

I ran WssAnalyzeFeatures to confirm the damage, and, sure enough, even after the removal of the solutions, the errors remain.

Any suggestions for tools and/or steps to remove these errors?

Answer 1

The two main tools for dealing with upgrade problems on your SharePoint 2010 farm are the Test-SPContentDatabase Powershell command and the stsadm command enumallwebs.

The Test-SPContentDatabase tool will check the content db against a specific site collection. It can be safely run either before or after the database is attached, as often as required. I would avoid running it against a live production database - take a copy.

Test-SPContentDatabase –Name dbame -WebApplication url

Use the enumallwebs stsadm command to work out which webparts, features, etc. are associated with which sites. You may discover orphaned sites that can be deleted and which may be the source of your problems.

stsadm -o enumallwebs -databasename dbname -includefeatures -includesetupfiles -includewebparts -includeeventreceivers -includecustomlistview

You would usually also want to review your upgrade error log, although it sounds as though you are beyond that point.

Answer 2

Well, I was able to solve my particular error, though it was only by means of a cumbersome process.

I loaded this stored procedure onto each affected database which allowed me to search the entire database for a given string. I searched though the database based on the error strings to finally identify the affected pages. One problem that was causing the error is that while I had emptied the main site Recycle Bin, I had never cleared out the Recycle Bin on the Admin site.

It was an ugly, ugly hack, but it worked. I wish I could share a step-by-step but it's a totally unique scenario for each system. Also, I imagine for a site with any degree of content, the searches through the databases might take aeons.

Answer 3

Detaching and reattaching the content db fixes the most obvious discrepancies between the config and the content db.