Paul Galvin's (old) SharePoint space [SharePoint

Just another WordPress.com site

Solution to Problem: “FileNotFoundException” With My Feature Receiver.

I was working on a feature last week that would add some event receivers to a specific list instance.  (I blogged a bit about that list receiver here).

Using the command line, I could install the feature with no error (but see below for the hidden error).  When I tried to deploy the feature on the site, MOSS complained of a "FileNotFoundException" error.  This blog entry describes how I solved it. 

This is the error that MOSS showed me in the web browser:

Feature ‘b2cb42e3-4f0a-4380-aaba-1ef9cd526f20’ could not be installed because the loading of event receiver assembly "xyzzyFeatureReceiver_0" failed: System.IO.FileNotFoundException: Could not load file or assembly ‘xyzzyFeatureReceiver_0’ or one of its dependencies. The system cannot find the file specified.
File name: ‘xyzzyFeatureReceiver_0’
   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].

Troubleshoot issues with Windows SharePoint Services.

I know how to deliberately cause that error: don’t install the assembly in the GAC.  But, 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% comfortable doing that because I always thought that gacutil existed for a reason … so I tried that.  It made no difference.

I searched the Internets and found this post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2243677&SiteID=1

The poster happened to be using the same root bit of code (from the Inside WSS book from this list) so that was a hopeful sign.  However, the suggestion of decorating the assembly with an [assembly: ] 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.

Next, I went to the trouble of enabling the "assembly bind failure log" (following the helpful and accurate instructions provided) 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.  But … it won’t search for it in the 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" for feature b2cb42e3-4f0a-4380-aaba-1ef9cd526f20: System.ArgumentNullException: Value cannot be null.
Parameter name: type
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.Activator.CreateInstance(Type type)
   at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

Troubleshoot issues with Windows SharePoint Services.

Time for one last trip to the Internets!

This time I find out, predictably enough, that MOSS issues this error because the assembly is not in GAC. 

I want to get something positive out of this and try to feel a little proud that I’ve created the Fugitive of MSIL assemblies, but it’s not working.  I’m just plain annoyed.  I find myself muttering "chicken or the egg" under my breath.

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" but can’t find one).

I install the feature and activate it and … it works!  So, after all that, I had to basically ‘reboot’ my project.  This is another reason why I hate 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.  For some reason, I did not use the -force option when I installed the new project.  This time, I did actually, truly forget to copy this new project’s assembly into the GAC.  As a result, I received that "FielNotFoundException" error.  This time, I got it from stsadm, not when I tried to activate the feature via the web browser.  So, -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.

</end>

Advertisements

2 responses to “Solution to Problem: “FileNotFoundException” With My Feature Receiver.

  1. Francisco February 20, 2009 at 11:51 am

    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 => DeployI 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"and "Failed to create feature receiver object from assembly" Thanks!Francisco

  2. Francisco February 20, 2009 at 11:57 am

    Also, 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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: