Flexera
Flexera

Re: Invoke-Expression : Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'file:///C:\Program Files (x86)\ManageSoft\WebUI\bin\Ionic.Zip.dll'

Jump to solution
Aha, under
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft

please update the value for InstallDir to match ETAPInstallDir (where you have FNMS installed). Then you can try rerunning the config.ps1 script

View solution in original post

Active participant

Re: Invoke-Expression : Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'file:///C:\Program Files (x86)\ManageSoft\WebUI\bin\Ionic.Zip.dll'

Jump to solution

@Jell-O 

you are right, its trying to find the .dll file in C:
after making changes it ran successfully.

really appreciate your support on this case and help in fixing the problem

Thanks,
Sushant

Occasional contributor

Re: Invoke-Expression : Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'file:///C:\Program Files (x86)\ManageSoft\WebUI\bin\Ionic.Zip.dll'

Jump to solution
** Easy & universal fix provided by Microsoft **
Enable Windows to load files, such as the aforementioned (~Ionic.Zip.dll) from "remote" sources (different drives in this case).
--------------------------------------------------------------
Steps:
1. FIND `machine.config ` (*replace [VERSION] respectively see reference #1):
o 32-bit location: %windir%\Microsoft.NET\Framework\[VERSION]\config\machine.config
o 64-bit location: %windir%\Microsoft.NET\Framework64\[VERSION]\config\machine.config

2. UPDATE `machine.config` (see reference #2 for Microsoft verification):
<configuration>
<runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
</configuration>

3. SAVE `machine.config`

4. CLOSE (important) & RE-OPEN `powershell` (allows new changes to take place)

5. RE-RUN `Config.ps1` same way you did before
--------------------------------------------------------------
I recommend following this solution, as provided by Microsoft, because each environment is different. Also, there are a variety of reasons people would choose to have these items on another local drive or even a shared drive. In some cases, the other mentioned solutions worked for us, other cases they did not. In many cases, this issue will have nothing to do with Flexera/FNMS or there will be underlying reasons the config is setup the way it is. Additionally, you can always copy the original `machine.config` and plug it back in once you've completed your upgrade or installation.

References:
1. Find `machine.config`:
o https://stackoverflow.com/questions/2325473/where-is-machine-config
2. How to update `machine.config` appropriately (loadFromRemoteSources enabled="true"):
o https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/dd409252(v=vs.100)?redire...
Austin Raun, CSAM, CHAMP
IT Software Asset Manager, Engineering Lead