SharePoint 2010 Sandbox solution 2 – Architecture and Execution Model

In my previous blog, I took up overview of Sand boxed solutions. Now the time is to take a lift and peek into the architecture and execution model

Architecture

Sandbox solution is often called as user solution. The primary API for sandbox solution is Microsoft.SharePoint.UsserCode and the service that takes care of it is SharePoint 2010 User Code Host.

Now the first question arises is where the assemblies are deployed – The assembly is packaged in wsp file and the wsp is uploaded in the solution gallery. When, for the first time, the assembly is required – e.g. a page is accessed which contains a webpart of the sandboxed solution, then the assembly is extracted from the gallery and copied to the file system (C:\ProgramData\Microsoft\SharePoint\UCCache) of the server that is handling the request (this may not be web front end server as it is handled by User Code Host Service).

But who copies the assembly to the file system as SPUCWorkerProcess.exe can’t write to file system. The answer is SharePoint 2010 User Code Host service

Once the user session, which accessed the assembly, ends, the assembly stays in the cache for a short time. If the same assembly is required by some other session it can be accessed from the cache, if present. Otherwise again it needs to be extracted from the solution. Following is the detailed execution process

This chronicles the process of using a custom  Web Part and solution in a particular site.

1. The SPSite admin uploads a new solution package (*.wsp) into the Solution Gallery of the SPSite.
2. The SPSite admin "activates" the solution.  This activates the features within the solution.  Web Part files are copied into the Web Part gallery.

•       As part of the activation, solution is validated using the validation framework. Custom validator can be added for example to check that only solutions signed with certain key can be activated. Customers and partners can develop their own validators based on their needs.

3. Sometime later, a user decides to add a Web Part to their home page.  They go into Web Part edit mode, and click "Add a Web Part".  They notice the additional Web Part options, and click Add.
4. SharePoint now checks to see if the custom webpart.dll file, which backs this Web Part, is installed into the assembly cache.  It is not.
5. The assembly is faulted into the assembly cache; it is extracted and copied from the solution file to temporary folder in disk and loaded to memory (disk is cleaned immediately). Now the Web Part is about to be used. 
6. It is loaded into Sandbox Code service host.
7. Processes deliver the Web Part to be executed to the service.

 

Execution Model

We’ll see the same execution from the perspective of execution model

 

1. An incoming request comes in for a page with a Web Part from a partial trust assembly.   This is delegated to a Web Part proxy.  The Web Part proxy then in turn calls the worker process manager, and tells it to execute the Web Part
2. The worker process manager queries the configuration database to figure out which machine and process it should send the request to
3. The worker process then sends the request to the user code manager on that machine
4. The user code manager needs to ensure that the assembly backing the Web Part is locally deployed.  To do this, it reaches back into the Web Part solution package, extracts the assembly, and places it into the assembly cache
5. Now, the SPUserCodeManager (SPUserCodeHostService.exe) delegates the request to execute the code to SPUserCodeWorkerProcess.exe. The full trust Web Part wrapper works with the instantiated process to simulate the Web Part lifecycle
6. The Web Part itself calls into the SharePoint OM to retrieve some set of data
7. The resulting HTML and viewstate changes are bubbled back to the hosting process, which has been synchronously waiting for this infrastructure to complete
8. The resulting page is sent back to the user
9. Rendered results sent back to the requester

 

So, that’s it. Hope this blog served the purpose. I’ll be back with the next part of this series soon J

 Please note that I orignally posted this on http://aspe-it.com/blog/2013/sharepoint-2010-sandbox-solution-2-architecture-and-execution-model/

 

SharePoint 2010 Sandbox solution 1 – Overview of Sandboxed solution

Please note that I have posted this blog orginally on http://aspe-it.com/blog/2013/sharepoint-2010-sandbox-solution-1-overview-of-sandboxed-solution/

SharePoint aims at reducing the involvement of IT team in solution lifecycle. Deployment and monitoring of custom solution is one area where Farm administrators (IT team) are still putting lots of their efforts. This effort can be reduced (I would use the word REDUCED effort instead of no effort because of the concept of Solution Validation) if the business needs can be fulfilled by Sandboxed solution.

In this series of blogs, I’ll be covering following topics in each block

1.       Overview of Sandboxed solution

2.       Architecture and Execution Model of Sandboxed solution

3.       Sandbox Proxy

4.       Solution Validation

Overview of Sandboxed solution

If I try to define sandboxed solution technically then the easiest way is — It runs under context of SPUCWorkerProcess (instead of w3wp) which has limited access to the resources

Before you decide on Sandboxed solution for your application, you need to be aware of the following

1.       It has access to only a subset of SharePoint object model. So limited operations can be performed

2.       It has no access to file system. So you cannot create Visual Web Parts or read/ write web.config file or log exceptions into log files

3.       No support to external web services

4.       No Email support using SPUtility.SendMail

5.       Impersonation is not allowed. So you cannot use SPSecurity.RunWithElevatedPrivileges

6.       Scope of the solution is limited. You can access only site collection level resources in which it is deployed

7.       Performance is another concern. If sand box worker process runs for more than 30 seconds then the UserCodeHosting service terminates the process

Oh my god! There are so many restrictions.

Don’t worry there are ways to perform full trust operation even after these restriction. I’ll show it in further blogs (3. Sandbox Proxy)

Now we are aware of, on high level, what we can’t do. Let’s see what we can do. We can create

1.       Web Parts (normal, not visual web part)

2.       Lists

3.       List Templates

4.       Custom Actions

5.       Event Receivers

6.       Content Types

7.       Site Columns

8.       Workflows

9.       Event Receivers

And many more…

 

Now we’ll look at the lifecycle of a Sandboxed solution at a very high level (as I’ll be diving deep in subsequent episodes)

 

1.       Deployment – The Site Collection Administrator (SCA) gets a solution as wsp file and uploads it into Solution Gallery. Once it is uploaded she needs to activate it. On activation the solution is validated against validation logic (either OOB or custom). IIS reset/ Web App pool recycling required. Great huh?

2.       Activation – If the validation is passed then the solution is activated which activates all the features contained in the solution. The SCA doesn’t need to activate the features separately(But cross checking is always good :P). If we assume that a feature contains a web part then on activation the web part would be populated into web part gallery

3.       Deactivation – On deactivating the solution, the web part no longer executes but still be present in the web part gallery

4.       Deletion – The solution is deleted. The web part, obviously, doesn’t executes but still it remains in the web part gallery

By now you would be aware of WHAT IS SANDBOXED SOLUTION, WHAT WE CAN AND CAN’T and LIFE CYCLE OF SANNDBOXED SOLUTION. Here I am concluding this episode of Sandboxed solutions and will take up Architecture and Execution model next

Form Library template is not displayed while creating new library

Problem Scenario:

While creating InfoPath form library, form library template is not available in templates.

Solution:

Form library template is not displayed in library templates when Team collaboration feature is not enabled in site features. By default site collaboration feature is disabled and you need to manually activate it from site features. Refer below for details on how to enable team collaboration feature:

1. From site actions menu click on site settings

2.  In Site settings, under Site actions section click on Manage Site features

3.  In site features, click on activate Team collaboration Lists feature

4.  Now go to view all site contents page, Click on create and then click on Library in left panel
5.  Form library template would be visible now

SharePoint overview for layman

Health Analyzer showing “missing server side dependency” after performing In-Place upgrade

Problem
After migrating site in MOSS 2007 to SharePoint 2010, health analyzer is showing “Missing server side dependency”. Migration of the site was done using In-Place upgrade. Following logs are logged in the log file:

 [MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [3fbd49d6-a25a-4f2f-89d6-1b0fd979435b]. The feature with Id 3fbd49d6-a25a-4f2f-89d6-1b0fd979435b is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [03ccceb8-6c39-4b02-870a-41ef6a93979d]. The feature with Id 03ccceb8-6c39-4b02-870a-41ef6a93979d is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [747755cd-d060-4663-961c-9b0cc43724e9]. The feature with Id 747755cd-d060-4663-961c-9b0cc43724e9 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [859ca45b-3943-4a01-a3d0-e5d7f0048e34]. The feature with Id 859ca45b-3943-4a01-a3d0-e5d7f0048e34 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [0158480c-bff0-4231-93c5-f0f37598b2a2]. The feature with Id 0158480c-bff0-4231-93c5-f0f37598b2a2 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [fb3233f6-235a-11dd-b0a8-fcc255d89593]. The feature with Id fb3233f6-235a-11dd-b0a8-fcc255d89593 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingSetupFile] File [Features\ExcelServerSite\Microsoft.Office.Excel.WebUI.dwp] is referenced [1] times in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. Please install any feature/solution which contains this file. One or more setup files are referenced in the database [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these files.

[MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [40] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [c17f9896-5c01-bf29-48af-096fd218184e] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [a6b1b233-477c-36d4-e0f2-0b79876b67b9] is referenced [6] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [d55b3b6b-6281-707b-73d0-0c49581475ad] is referenced [26] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [f94b483e-dc6e-f8a2-2867-10bd9897f35f] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [bc877bd0-b48e-3165-7c9e-1e2f98c2a42a] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [e265a361-507e-136e-ceb3-20d04a556a22] is referenced [7] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [ddbfb079-d77d-89c8-cb82-213960b44379] is referenced [4] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [b620591f-ce04-2efb-7b19-256f5fd94ca7] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [a2e08067-888b-2ca1-4b3d-2bb33bdc3b37] is referenced [3] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [2f1510c7-75d5-921f-b120-2ce98fe3afe3] is referenced [74] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts. [MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [3fbd49d6-a25a-4f2f-89d6-1b0fd979435b]. The feature with Id 3fbd49d6-a25a-4f2f-89d6-1b0fd979435b is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [03ccceb8-6c39-4b02-870a-41ef6a93979d]. The feature with Id 03ccceb8-6c39-4b02-870a-41ef6a93979d is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [747755cd-d060-4663-961c-9b0cc43724e9]. The feature with Id 747755cd-d060-4663-961c-9b0cc43724e9 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [859ca45b-3943-4a01-a3d0-e5d7f0048e34]. The feature with Id 859ca45b-3943-4a01-a3d0-e5d7f0048e34 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [0158480c-bff0-4231-93c5-f0f37598b2a2]. The feature with Id 0158480c-bff0-4231-93c5-f0f37598b2a2 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingFeature] Database [Intranet_WSS_Content_Corporate_11000] has reference(s) to a missing feature: Id = [fb3233f6-235a-11dd-b0a8-fcc255d89593]. The feature with Id fb3233f6-235a-11dd-b0a8-fcc255d89593 is referenced in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.

[MissingSetupFile] File [Features\ExcelServerSite\Microsoft.Office.Excel.WebUI.dwp] is referenced [1] times in the database [Intranet_WSS_Content_Corporate_11000], but is not installed on the current farm. Please install any feature/solution which contains this file. One or more setup files are referenced in the database [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these files.

[MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [40] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [c17f9896-5c01-bf29-48af-096fd218184e] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [a6b1b233-477c-36d4-e0f2-0b79876b67b9] is referenced [6] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [d55b3b6b-6281-707b-73d0-0c49581475ad] is referenced [26] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [f94b483e-dc6e-f8a2-2867-10bd9897f35f] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [bc877bd0-b48e-3165-7c9e-1e2f98c2a42a] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [e265a361-507e-136e-ceb3-20d04a556a22] is referenced [7] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [ddbfb079-d77d-89c8-cb82-213960b44379] is referenced [4] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [b620591f-ce04-2efb-7b19-256f5fd94ca7] is referenced [2] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [a2e08067-888b-2ca1-4b3d-2bb33bdc3b37] is referenced [3] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

[MissingWebPart] WebPart class [2f1510c7-75d5-921f-b120-2ce98fe3afe3] is referenced [74] times in the database [Intranet_WSS_Content_Corporate_11000], 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 [Intranet_WSS_Content_Corporate_11000], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

Solution:

This generally happen when a feature deployed in MOSS 2007 environment is not deployed in SharePoint 2010 after migration. Following steps can be performed to resolve the errors:

• Before starting of it would be better if name of web part corresponding to web part id which is causing this issue could be figured out. For determining this tool called WssAnalyzeFeatures can be used. First run it on MOSS 2007 environment and check for the feature name corresponding to the Id in the error log. 
• If the referenced pages come out to be related to help pages then "SharePoint Foundation Help Search" need to be configured, which will crawl all the SharePoint Help files
• If the missing feature is SharePoint OOB feature then simply activate the feature
• Or SharePoint 2010 manager can be used; it’s an object model explorer that helps  to see what’s going on in SharePoint environment. Installation and activation of the features can be done through this. It can be downloaded from here 
• Finally if all above steps did not work then try deactivating the features using WssAnalyzeFeatures tool

Health analyzer showing error “Missing server dependency" in content databases

Problem Statement:

In a newly installed SharePoint farm sometime health analyzer shows error “Missing server dependency” in the content databases. Following errors are logged:

[MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [23] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9eba9c17-3b89-a2e7-a3cf-0ee3d7c2adb1] (class [Microsoft.Office.Server.Search.WebControls.SearchTopologyView] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [07f48b68-2e69-c86a-ebe4-16359e03ebc2] (class [Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [23091f6c-295d-4493-504c-1714a20d65a2] (class [Microsoft.Office.Server.Search.WebControls.PeopleRefinementWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [7d319bdd-d90e-7861-b7f0-2f9f4cec3004] (class [Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [2] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [c744e2b2-158c-c2f8-2f80-54bf046ff644] (class [Microsoft.SharePoint.Portal.WebControls.PeopleSearchBoxEx] from assembly [Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [b36f9dfe-325a-1b44-e6bb-645dcf79c770] (class [Microsoft.Office.Server.Search.WebControls.FarmSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [0a60f514-1dea-8537-b588-64ee5e224da3] (class [Microsoft.SharePoint.Portal.WebControls.SearchBoxEx] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [2] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9f56656f-6aa3-0d55-a812-711bf65864ea] is referenced [149] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9637ed85-7d44-e135-35ba-73ce390ebf93] (class [Microsoft.Office.Server.Search.WebControls.SearchPagingWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [2] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [2fc2e287-55c9-b5d1-0d5c-7458bc3c9841] (class [Microsoft.SharePoint.Portal.WebControls.ContactFieldControl] from assembly [Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [8acac35f-e9d3-95c3-76c7-76fe034cef50] (class [Microsoft.Office.Server.Search.WebControls.SearchSummaryWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [926a1a3e-d1ff-f58f-8b3a-854974660703] (class [Microsoft.Office.Server.Search.WebControls.ContentSourcesStatus] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [f9c020f4-bcb2-3629-0460-9e5ec4c9de93] (class [Microsoft.Office.Server.Search.WebControls.QuerySuggestionsWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [de8c8afc-7c6e-e9fc-91c2-aa4a291c3623] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [bc8768f7-7d8c-1d56-b5a5-bb19cca9c7b8] (class [Microsoft.Office.Server.Search.WebControls.FederatedResultsWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [83d7efb5-5a0a-0d4e-fc32-cf0eae4b6cb1] (class [Microsoft.Office.Server.Search.WebControls.SearchStatsWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [2] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [42b6d12b-947f-6ec4-9540-dc2f3e8f2425] (class [Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [2] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [3517e131-b02d-114b-1df2-dd9fa67b90c6] (class [Microsoft.Office.Server.Search.WebControls.TopFederatedResultsWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [d46a22f8-7373-12cb-4e07-e1b78e3dba96] (class [Microsoft.Office.Server.Search.WebControls.RefinementWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [5cc5df3a-29a8-a713-5898-e52e2dce72a8] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationShortcutsList] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [874f5460-71f9-fecc-e894-e7e858d9713e] is referenced [81] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [ff79cbb5-48cf-96ee-3f74-f22cc1b00fbd] (class [Microsoft.Office.Server.Search.WebControls.FarmSearchApplicationList] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [0ff9a0d5-1514-7a3b-fb97-fccbc902e380] (class [Microsoft.Office.Server.Search.WebControls.HighConfidenceWebPart] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [Sharepoint_AdminContent], 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 [Sharepoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

Solution:

These errors generally appear on a cleanly installed SharePoint farm in the Health Analyzer Reports until anyone visit the following pages:

·         SearchAdministration.aspx

·         SearchFarmDashboard.aspx

These pages are located at following location:

Central Administration à General Application Settings à Farm Search Administration àSearch Service Application.

Browse to these pages and the error will no longer appear in the Health Analyzer Report.