Khalids Technical Diary

[MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663]

[MissingWebPart] WebPart class [07f48b68-2e69-c86a-ebe4-16359e03ebc2]

[MissingWebPart] WebPart class [23091f6c-295d-4493-504c-1714a20d65a2]

[MissingWebPart] WebPart class [7d319bdd-d90e-7861-b7f0-2f9f4cec3004]

[MissingWebPart] WebPart class [888f7af5-05f1-4d07-1143-4b24c394b67b]

[MissingWebPart] WebPart class [c744e2b2-158c-c2f8-2f80-54bf046ff644]

[MissingWebPart] WebPart class [0a60f514-1dea-8537-b588-64ee5e224da3] 

MissingWebPart] WebPart class [b2b35bdf-5e78-ab22-5351-6639ca63203f]

[MissingWebPart] WebPart class [9f56656f-6aa3-0d55-a812-711bf65864ea]

[MissingWebPart] WebPart class [9637ed85-7d44-e135-35ba-73ce390ebf93]

[MissingWebPart] WebPart class [2fc2e287-55c9-b5d1-0d5c-7458bc3c9841]

[MissingWebPart] WebPart class [8acac35f-e9d3-95c3-76c7-76fe034cef50]

[MissingWebPart] WebPart class [f9c020f4-bcb2-3629-0460-9e5ec4c9de93]

[MissingWebPart] WebPart class [bc8768f7-7d8c-1d56-b5a5-bb19cca9c7b8]

[MissingWebPart] WebPart class [dc4f0aa3-bdd4-3394-6372-cd263a7a9cd0]

[MissingWebPart] WebPart class [83d7efb5-5a0a-0d4e-fc32-cf0eae4b6cb1]

[MissingWebPart] WebPart class [42b6d12b-947f-6ec4-9540-dc2f3e8f2425]

[MissingWebPart] WebPart class [3517e131-b02d-114b-1df2-dd9fa67b90c6]

[MissingWebPart] WebPart class [9afe11f2-9603-ac36-62a9-debeb61bcac0]

[MissingWebPart] WebPart class [d46a22f8-7373-12cb-4e07-e1b78e3dba96] 

[MissingWebPart] WebPart class [874f5460-71f9-fecc-e894-e7e858d9713e] 

[MissingWebPart] WebPart class [0ff9a0d5-1514-7a3b-fb97-fccbc902e380]

Upon inspection I noted that they were search web parts SHOCKING!!. So I set about the usual that would be viewing search pages etc then running the health analyser again but low and behold still no dice. I noted some were referenced in the Admin Content DB so I went and checked site settings and noted that the Search Server Webparts feature was disabled. I enabled it in Central admin and that took care of the admin content db errors however there were still a million of references in the other content DB's

I done some testing and some reading and noted that the health analyser job apparently is not smart enough to distinguish which servers are WFE servers and which are APP servers and would report the webparts as missing but they were infact on the farm. I then done some research further on the Health analyser and noted that it would look at the web.config on ever server for every SharePoint WebApp. This got me thinking why not just copy the inetpub folders from the WFE to each server in the same location and the same for the Central Admin folder as then the web.configs would be on all servers.

So I tested this and low and behold no more search dependency errors.