Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1611
  • Last Modified:

Sharepoint2010 Health Analyzer: Missing server side dependencies.


We have a warning in Sharepoint Health Analyzer indicating a missing server side dependency:
Title Missing server side dependencies.  
Severity 1 - Error  
Category Configuration  
Explanation [MissingAssembly] Assembly [PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17] is referenced in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this assembly. One or more assemblies are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these assemblies. 

Remedy  For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142689". 
Failing Servers    
Failing Services SPTimerService (SPTimerV4) 
Rule Settings View  

Open in new window

I have followed the instructions on this blog and found that this is what's causing the error (found in the CSV file generated by the script originating from the mentioned blog):

Windows PowerShell Transcript Start	
Start time: 20130116003044	
Username  : DOMAIN\sp_farm 	
Machine	  : SERVER (Microsoft Windows NT 6.1.7601 Service Pack 1) 
Transcript started, output file is MissingAssemblyOutput-2013-01-16_12-30.csv	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteA/Documents;UpdateVersionColumnsItemAdded;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteA/Documents;UpdateVersionColumnsItemUpdated;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteA/Documents;UpdateVersionColumnsCheckedOut;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteB/Workbook;UpdateVersionColumnsItemAdded;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteB/Workbook;UpdateVersionColumnsItemUpdated;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteB/Workbook;UpdateVersionColumnsCheckedOut;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteC;UpdateVersionColumnsItemAdded;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteC;UpdateVersionColumnsItemUpdated;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
PAC.SharePoint.VersionInfoInDocs2010, Version=, Culture=neutral, PublicKeyToken=60365f8db63e4b17;https://sharepoint.com/siteA/subsiteC;UpdateVersionColumnsCheckedOut;PAC.SharePoint.VersionInfoInDocs2010.UpdateVersionColumns.UpdateVersionColumns	
Windows PowerShell Transcript End	
End time: 20130116003047	

Open in new window

How do I fix this problem? Will deleting the Event Receiver Reference as mention in the blog be enough or is it just removing the Health Analyzer Warning? I.e will I have problems when upgrading Sharepoint 2010 to the lates version?

All help greatly appreciated!
  • 2
  • 2
2 Solutions
Mohit NairSenior AssociateCommented:
The log itself shows that the solution is missing in the farm.You need to download the wsp file and install it in the farm.
Please find the link below to download it.

Before installing check whether you have used this solution in your previous versions or another farm.

Second thing is that you wont face any upgrade issues in future if this doesnt get fixed. The workaround to upgrade sharepoint is to detach the database WSS_Content and then run the upgrade wizard. Once done attach the database back.
cegelandAuthor Commented:
Thanks for your quick reply. Unfortunately the wsp file available for download is v.1.1, but my error seem to indicate that version 1.0 is missing. I can't seem to find the old 1.0 version anywhere.

Is there any other way to get rid of this error? The lists/libraries triggering the error contain lots of data so I would prefer not to delete the whole list/library...
You can remove the eventreceivers with powershell:


The article shows how to remove them all. You can change it to target just a specific list.
cegelandAuthor Commented:
Thank you. What happens when I do this- will files be deleted or is it just the reference to the columns mentioned that will be removed?
No, what happens when you deploy a custom event handler to a list is that it attaches itself to that list. So that it can execute when an item is added to that list. What the powershell does, is detach the event handler from that list. It won't affect the items in that list.

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now