title: SSIS use of JSON.NET in GAC for Script Component
body: <p>I have built a Scopus Library (dll) which I load into the GAC for use by an SSIS package's script component.
  This Library is based on the .Net framework 4.5 and utilizes the Json.Net Lib which I have also loaded into the GAC.</p>
  
  <p>When run the package through the SSISDB in SSIS Catalogue on my loacal &amp; Dev machines it works fine, When I have run it on the test machine in the same manner it fails with the following error.</p>
  
  <blockquote>
    <p>DFT - S_SCOPUS_PUBL_META_EXTRACT: Error: System.TypeloadException:
    Could not load the type System.Collections.Generic.IReadOnlyDictionart
    '2' from assembly mscorlib, version 4.0.0.0 Culture=neutral,
    PublicKeyToken=b77a5c661934e089.</p>
  </blockquote>
  
  <p>at</p>
  
  <pre><code>Microsoft.SQLServer.Dts.Pipeline.SciptComponentHost.HandleUserException(Exception(e)
  </code></pre>
  
  <p>at </p>
  
  <pre><code>Microsoft.SQLServer.Dts.Pipeline.SciptComponentHost.
  </code></pre>
  
  <p>ect ect.</p>
  
  <p>Box Setups:
  SQL Server 2012, Server 2012 for Dev and Test and SQL Server 2012 &amp; Windows 7 for Local.</p>
  
  <hr>
  
  <p>Things I have attempted to fix the issue</p>
  
  <ol>
  <li>Checked the Scopus Library, Json.Net and SSIS Script Component all use the 4.5 version of the .Net Framework.</li>
  <li>Double checked that the Scopus and Json.Net Libraries are in the GAC correctly</li>
  <li>Made sure I had the latest version of the Json.Net Library </li>
  <li>Checked the version of the mscorlib.dll on each machine <br>
  LOCAL, DEV Machines are File Version 4.0.30319.18052<br>
  TEST Machine is&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;File Version 4.0.30319.1008 <br></li>
  <li>Ran a scan for updates on the TEST machine to see if it required any additional patches to update the mscorlib.dll file (it told me it was up to date - keep in mind I am not a sys admin so they might be holding back).</li>
  </ol>
  
  <p>Does anyone have any additional idea's about how to get around this error ? </p>