Health analyzer

by

Title Missing server side dependencies.


Title Missing server side dependencies.

Explanation

[MissingWebPart] WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa] is referenced [1] times in the database [WSS_Content_Intranet], 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 [WSS_Content_Intranet], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

solution

 

function Run-SQLQuery ($SqlServer, $SqlDatabase, $SqlQuery)

{
$SqlConnection = New-Object System.Data.SqlClient.SqlConnection
$SqlConnection.ConnectionString = “Server =” + $SqlServer + “; Database =” + $SqlDatabase + “; Integrated Security = True”
$SqlCmd = New-Object System.Data.SqlClient.SqlCommand
$SqlCmd.CommandText = $SqlQuery
$SqlCmd.Connection = $SqlConnection
$SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
$SqlAdapter.SelectCommand = $SqlCmd
$DataSet = New-Object System.Data.DataSet
$SqlAdapter.Fill($DataSet)
$SqlConnection.Close()
$DataSet.Tables[0]
} 

Once you have loaded the function in a PowerShell console, you can run it by using the Run-SQLQuery command with the options relevant to your deployment. For [MissingWebPart] errors, you need to run a SQL SELECT query on the “AllDocs” table in the content database exhibiting the problem, joining to the “AllWebParts” table in order to find details about the missing web part. For example, you would type the following command to find details of the web part with the class ID “4575ceaf-0d5e-4174-a3a1-1a623faa919a”, as reported in the error above:

Continue reading →

Advertisements
by

Title Missing server side dependencies


Title Missing server side dependencies.

Explanation
[MissingWebPart]WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa] is referenced [1] times inthe database [WSS_Content_Intranet], but is not installed on the current farm.Please install any feature/solution which contains this web part. One or moreweb parts are referenced in the database [WSS_Content_Intranet], but are notinstalled on the current farm. Please install any feature or solution whichcontains these these web parts.

solution

function Run-SQLQuery ($SqlServer, $SqlDatabase, $SqlQuery)
{
$SqlConnection = New-Object System.Data.SqlClient.SqlConnection
$SqlConnection.ConnectionString = “Server =” + $SqlServer + “; Database =” + $SqlDatabase + “; Integrated Security = True”
$SqlCmd = New-Object System.Data.SqlClient.SqlCommand
$SqlCmd.CommandText = $SqlQuery
$SqlCmd.Connection = $SqlConnection
$SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
$SqlAdapter.SelectCommand = $SqlCmd
$DataSet = New-Object System.Data.DataSet
$SqlAdapter.Fill($DataSet)
$SqlConnection.Close()
$DataSet.Tables[0]
}

For this I am going to reuse the Run-SQLQuery PowerShell script that I introduced in my article on MissingSetupFile errors:

Read more »

by

Databases running in compatibility range, upgrade recommended


Explanation:The following databases have versions that are older than thecurrent SharePoint software, but are within the backwards compatible range:
User Profile Service Application_SocialDB_cdd2f43ca1c9467abdd0e58c5e3751e5,
Search_Service_CrawlStoreDB_b2dbbbdfbf514a4e96868cec02583d1f,
Search_Service_PropertyStoreDB_daf09cfc46fe4e1cb79b403c44d3ff19,
SearchAppPropertyDB1,
WSS_Content,
WSS_Content_Intranet,
WSS_Content_MYSITE-2011,
Search_Service_Application_DB_fd3133ce2e6f4e46b158a15ce06cada3,
Search_Service_DB_aeaf5a1c95db46e1a73f8f8cd9f0221d,
Managed Metadata Service_c81e807f1ee3477193467cf2d05c2d9d,
User Profile Service Application_ProfileDB_fa386a74a1754112b9baa69d50c816e3,
WSS_Logging.
Thiscooures when you run new bathces to the Spoint or to the Microsoft Projectserver
You canfind the following
In thestatus field
How to solve it
First, try to run this command
C:Program FilesCommon FilesMicrosoftSharedWeb Server Extensions14BINpsconfigui.exe
This is the product configuration wizard if it succeed thenyou are done if not then go to the following
Open the Sp powershell

Powershell commands that are useful during SharePoint 2010Upgrade