I was working on a feature last week that would add some event receivers to a specific list instance. (Blogged sum a frenum album, ut hic Receptorem).
Usura order versus, Possem install pluma cum nihil erroris (Pellentesque sed qui absconditus est errare). When I tried to deploy the feature on the site, MOSS complained of a "FileNotFoundException" error. This blog entry describes how I solved it.
Quod est error ostendit mihi in textus pasco quod MUSCUS:
Feature ‘b2cb42e3-4f0a-4380-aaba-1ef9cd526f20’ could not be installed because the loading of event receiver assembly "xyzzyFeatureReceiver_0" defecit: System.IO.FileNotFoundException: Could not load file or assembly ‘xyzzyFeatureReceiver_0’ aut unum viculis. Ratio non reperio lima nuncupati.
File name: ‘xyzzyFeatureReceiver_0’
at System.Reflection.Assembly.nLoad(AssemblyName filename, String codeBase, Testimonium assemblySecurity, Coetus locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Testimonium assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Testimonium assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
WRN: Vincientes logging est verto off contione.
Ut ligemus cœtus defectum logging, statuet pretium registry [HKLM Software Microsoft Fusion!EnableLog] (DWORD) ad 1.
Note: Aliqua poena est effectus coniungitur cum contione ligáveris defectum logging.
Convertere off pluma, tollere valorem registry [HKLM Software Microsoft Fusion!EnableLog].
Scio quia de industria causam erroris: don’t install the assembly in the GAC. Sed, it was in the GAC. I normally install assemblies into the GAC by dragging them into the c:\windows\assembly folder using windows explorer. I’ve never felt 100% faciens quod consolatoria quia ego semper existimavi fuisse ex causa quia gacutil … so I tried that. It made no difference.
Rimarer Internets invenit locum istum: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2243677&SiteID=1
Poster contigit eadem usus radicis frenum of code (a intus ex WSS libro hoc album) so that was a hopeful sign. Autem, suggerentibus tegerent cum contione [conventu: ] directive didn’t make sense to me. I tried it anyway and I was right. It made no difference.
Then I noticed that my class definition was not public. I made it public and that made no difference.
Postero, I went to the trouble of enabling the "assembly bind failure log" (iuuabit sequi et mandata accurate provisis) and this is where things started to get interesting. That log shows me that the runtime is searching everywhere on that server for my assembly. It even appears to be searching for it in my medicine cabinet. Sed … non inveniri in GAC.
I put on my winter jacket and go searching the Internets again and find that someone has had this problem too. The lengthy discussion in that posting peters off into nothing and I can’t find a solution.
I move my assembly into one of the places the log claims it’s searching and I make a little more progress. I’m rewarded with a new error in the browser when I try to activate the feature:
Failed to create feature receiver object from assembly "xyzzyFeatureReceiver_0", type "Conchango.xyzzyFeatureReceiver" quia pluma-b2cb42e3 4f0a-(IV)CCCLXXX-aaba-1ef9cd526f20: System.ArgumentNullException: Valorem non potest esse nulla.
Nomen modularis: typus
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
Uno tempore enim ultimi itineris usque ad Internets!
Hoc tempore invéniam, Satis praevisam, that MOSS issues this error because the assembly is not in GAC.
Lorem ipsum dolor sit conantur positionem et ex hoc quod ego creavi superbos Fugacissimo MSIL cœtus, but it’s not working. I’m just plain annoyed. I find myself muttering "chicken or the egg" sub lingua mea.
I finally decide to punt. I create an entirely new project and copy/paste the code from the incredible-cloaked-from-the-GAC-assembly non-working project over to this new project. (I look for a build flag called something like "hide from assembly binding if installed in the GAC" sed non potest invenire).
Ego install ipsum et eu eam et … Operatur! Ita, post omnes,, I had to basically ‘reboot’ my project. Hae altera causa est cur oderim computers.
I did learn something useful from this. I had been installing features using the stsadm command line all day long and been using the "-force" option out of habit. Propter aliquam causam,, I did not use the -force option when I installed the new project. Hoc tempore, Ego actu, truly forget to copy this new project’s assembly into the GAC. Ut ex, I received that "FielNotFoundException" error. Hoc tempore, Possedi a stsadm, not when I tried to activate the feature via the web browser. Ita, -force actually plays two roles. It allows you to re-install an existing feature. It also allows you to install a buggy feature that cannot work at runtime by suppressing the error. It probably says as much in the help somewhere but I never noticed it.
</finem>
Quoque, I had my 2 hours of hysteric nintendoSIXTYFOURRRR-in-a-bad-way moments when I renamed the Namespace on the Feature Receiver, to help track where yours or anyone else’s began.
The root of the problem lies on the deployed wsp in the sharepoint database. I read your post and while it does indeed fix the problem we have a huge solution with several projects and dozens of files so moving everything was not an option.
No matter how much you update your GAC or your assembly, what is giving you trouble is the assembly in the current WSP installed on sharepoint.
You can easily noticed that by trying to only retract the solution (which is where the error happens). Everything happening on "Retracting Time" should be considered "deployed wsp"-only not the project itself.
My workaround was:
– Central admin: Cancel solution
– stsadm: deletesolution
– Visual Studio => Project => Package
– stsadm: addsolution -file Project\bin\Debug\Project.wsp
– stsadm: deploysolution -name project.wsp -immediate -allowgacdeployment -force
– Visual Studio => Deploy
I also deleted the bin and debug folders from the project before running Deploy again, might not have any effect but worth commenting.
This works for both
"Feature … could not be installed because the loading of event receiver assembly"
et
"Failed to create feature receiver object from assembly"
Gratias!
Francisco
Just spent a couple of hours trying to fix this same issue and found a better solution than simply recreating the project.
It turned out that for some reason Visual Studio had set the build target to x86 instead of x64 or MSIL – the assembly was in the GAC, just not the same GAC that 64 bit SharePoint was looking in.