Failed to load receiver assembly

Question

Hi I´m working with 3 WFE, I´m, trying to deploy a solution with 2 master pages, also with a feature that will help us to change the master when we active it or de acitvate it.

The solutions has been updated, so the way I´m deploying the solution is with powershell using install-spsolution command.

The solutions deploys to 2 out of 3 WFE, the Solution management display error message:

WFEXXXXX : Failed to load receiver assembly "MySharePointProject Feature, Version=1.0.0.0, Culture=neutral" for feature "Custom Master Page_MPChangeFeature1" (ID: 9d71c1af-f03f-473b-a2a7-f8037af369c5).: System.IO.FileNotFoundException: Could not load file or assembly 'MySharePointProject Feature, Version=1.0.0.0, Culture=neutral' or one of its dependencies. The system cannot find the file specified.

File name: 'MySharePointProject Feature, Version=1.0.0.0, Culture=neutral' at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

NDHWQ50077 : Failed to load receiver assembly "MySharePointProject Feature, Version=1.0.0.0, Culture=neutral" for feature "Custom Master Page_MPChangeFeature1" (ID: 9d71c1af-f03f-473b-a2a7-f8037af369c5).: System.IO.FileNotFoundException: Could not load file or assembly 'MySharePointProject Feature, Version=1.0.0.0, Culture=neutral' or one of its dependencies. The system cannot find the file specified. File name: 'MySharePointProject Feature, Version=1.0.0.0, Culture=neutral' at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

I´ve brwose into the servers looking for this Registry Value "HKLM\Software\Microsoft\Fusion!EnableLog" but none of the servers has the value, I mean the entrie is not even there what means the value is turned off.

My frist option will be to turn it on in 3 WFE, but the wierd thing is the error only pops in 1 WFE.

We have deploy this very same solution in QA server and it works just fine.

After all this my specific questions "how come I got this error in only 1 WFE server in none of the 3 has the value activated?"

WIll this error could be caused for something else?

Tks in advance!!

Answer 1

The first step would be to verify that the SharePoint Timer service is running properly on all servers in the farm. Beyond that, you would need to look at Central Admin and see if the deployment of the solution generated unusual errors for the other servers.

If that all looks good then you probably need to understand the nature of the update. Did the Strong Name change on the DLL in any way? Even a single digit difference would make a different name. If that changed, they you should do a full retraction of the solution followed by a redeployment of it.

It is also possible that the solution itself is relying on a reference to another file that is either not in the solution or is not installed on your production servers.