Feb 17, 2014
  3866
(2 votes)

Using VppMigrationTool returns exception (Could not load file or assembly..)

This is migth be a bit too specific, but when using the VppMigrationTool to migrate files to EPiServer 7.5 I got this error when trying to connect to the site:

Capture

Could not load file or assembly 'file:///C:\Users\pa_hemo\Downloads\EPiServer_7.5_VppMigrationTool\VppMigrationTool_20140107.1\VppMigrationTool.exe' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

At the bottom of the exception you get a little hint, but it took me

some minutes to figure it out. The solution is to add the config settings below in to your Machine.config-file:

<configuration>
   <runtime>
      <loadFromRemoteSources enabled="true"/>
   </runtime>
</configuration>

This did the trick for me :)

You can also change the VppMigrationTool.exe.config  to look like this:

<?xml version="1.0"?>

<configuration>

   <startup>

        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>

   </startup>

   <runtime>        

        <loadFromRemoteSources enabled="true"/>

   </runtime>

</configuration>

PS: You should also be aware that VppMigrationTool removes the config-settings from web.config for the folders you choose migrate.

Feb 17, 2014

Comments

May 22, 2014 12:26 PM

Thank you!! :)

Ted
Ted Oct 30, 2014 03:25 PM

Saved me some headache - thanks Henrik!

Please login to comment.
Latest blogs
Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely CMS 11 Is Out of Support — and the Hard Part of the Upgrade Isn't the CMS

On 10 April 2026, Optimizely formally announced that CMS 11 was out of support — CMS 13 had reached GA on 31 March, and by policy only the two most...

Allan Thraen | May 6, 2026 |