Home > SharePoint, SharePoint 2010 > Sharepoint 2010 bug

Sharepoint 2010 bug


http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2009/12/09/Missing-Server-Side-Dependencies-_2D00_-8d6034c4_2D00_a416_2D00_e535_2D00_281a_2D00_6b714894e1aa.aspx

Excerpt;

Missing Server Side Dependencies – 8d6034c4-a416-e535-281a-6b714894e1aa

So what is this you ask? Well, I did a little digging, I watched the Timer Job and the query it sent ( to the content database of the central admin site):

SELECT tp_WebPartTypeId, COUNT(1), tp_Assembly, tp_Class
FROM AllWebParts (NOLOCK)
WHERE tp_WebPartTypeId IS NOT NULL GROUP BY tp_WebPartTypeId, tp_Assembly, tp_Class

You get back a result set that has a null for the tp_Assembly column for the web part. What is this web part you ask, well it is the Microsoft.Office.Server.Search.WebControls.SearchTopologyView web part in the Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c assembly.

If you do a query to see where these 6 instance are:

select *
from AllWebParts
where tp_WebPartTypeId = ‘8D6034C4-A416-E535-281A-6B714894E1AA’

You will see that the web part exists on two pages:

  • SearchAdministration.aspx
  • SearchFarmDashboard.aspx

Open those pages, notice…It DOES exist!

Now, here is the funny thing – rerun the queries. As soon as you open those pages, the databsae gets updated and the error will go away. Weird!!!

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: