Home / server / Questions / 23613
Accepted
Dave
Asked: 2009-06-11 11:39:23 +0800 CST

How to best diagnose Failure in loading assembly errors

  • 772

I'm seeing many occurrences of "Error: Failure in loading assembly: MyAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=Token#" in my sharepoint farm's web front end eventlog.

I've read this article: http://blogs.msdn.com/suzcook/archive/2003/05/29/57120.aspx but I am prohibited from installing any SDKs or utilities by our sys admins.

The assembly in question is in the bin folder of my app and is identical across the farm. The sharepoint log file (in the 12 hive) lists the same error as above without further information.

Any suggestions on how to diagnose?

sharepoint assembly

5 Answers

  1. In the past I've seen this error occur with custom dll's that i've written. I tried a lot of ways to get around things, such as add the code to the GAC, etc.

    I actually replied to a similar question, http://social.technet.microsoft.com/Forums/en-US/sharepointdevelopment/thread/ab43b645-77f9-44e1-8c50-c1e902f7d5b2

    My fix was that I added the DLL to the assemblies element of web.config

    <compilation batch="false" debug="true">
      <assemblies>
        <add assembly="MyCustomDLL, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

    Once I did that, I noticed that i no longer saw errors in the event logs of my front ends.

    • 1

  2. How to best diagnose it? Check the Event Log, the fusion loader writes its failures there.

    And use Process Monitor, looking for events that result in File Not Found.

    • 1

  3. I would add the assembly to the GAC on the servers. There are times when the assemblies could be loaded that are not involved with the web serving piece, such as when you have feature receivers. Is this something that is allowed by your sys admins?

    • 0
  4. Best Answer

    You can just turn on the Fusion log (through those registry settings using regedit) and just look at the logs with notepad.

    Take a look here for more info regarding bin deployed SharePoint dlls. http://msdn.microsoft.com/en-us/library/cc768621.aspx

    • 0

  5. I would try attaching a remote debugger, this will then show you in Visual Studio the exception when you hit the page that is using your custom assembly.

    I know you mention in your post that you're not allowed to install anything but frankly you're going to have a hard time diagnosing this without any utilities!

    • 0