|
|
|
Error Running .NET Web Application: "Could not load file or assembly..."
Technical Note 40034
Last Reviewed 15-Jul-2008
Applies To
Verastream Host Integrator version 6.0 or higher
Summary
Technical Note 40034
Last Reviewed 15-Jul-2008
Applies To
Verastream Host Integrator version 6.0 or higher
Summary
When attempting to run a .NET web application built with Web Builder, you may see a Server Error "Could not load file or assembly AppConn.Interop." This technical note describes the error and solution.
Problem Symptom
When attempting to run a .NET web application built with Web Builder (in the Verastream Host Integrator [VHI] Development Kit), an error may be displayed in the web browser such as the following.
Server Error in '/<applicationname>' Application.Could not load file or assembly 'AppConn.Interop, Version=6.0.94.0, Culture=netural, PublicKeyToken=e3faaeefc1a40698' or one of its dependencies. The system cannot find the file specified.The Exception Details section indicates System.IO.FileNotFoundException with the above error repeated.
The Source Error section may indicate the exception occurred when executing the following line:
_session = new HostIntegratorSession(); |
Explanation
The issue cause depends on your product version.
Version 6.5
This problem may occur if you installed a hotfix (version 6.5.707 or higher), uninstalled the product from Add/Remove Programs, and then re-install the shipping release (version 6.5.683).
Version 6.0
This problem occurs if Microsoft .NET Framework version 1.1 was not installed before Verastream Host Integrator 6.0.
This problem occurs even if .NET Framework version 2.0 has been installed. VHI 6.0 Setup expects .NET Framework version 1.1 to be present.
During VHI 6.0 installation, DLL components are normally registered using the Global Assembly Cache Tool provided with Microsoft .NET Framework 1.1 (C:\Windows\Microsoft.NET\Framework\v1.1.4322\gacutil.exe). If the tool is not found in this location, the DLL files are not registered.
Solution
You can manually register the Verastream DLLs, using either the Control Panel Method or Command Prompt Method.
Note: If you uninstalled and re-installed the product after applying a version 6.5 hotfix, refer to the hotfix ReadMe for instructions on using VHI_GAC_Upgrade.zip.
Control Panel Method
Follow the steps below to resolve this issue using the graphical configuration utility:
- In Control Panel, open Administrative Tools.
- Open Microsoft .NET Framework (1.1 or 2.0) Configuration.
- Click Assembly Cache in the left pane, or the "Manage Assembly Cache" link in the right pane.
- Before proceeding, view the list of assemblies in the Assembly Cache and verify that AppConn.Interop is not listed.
- Click "Add an Assembly to the Assembly Cache" link in the right pane (or, in the Assembly Cache right-click menu, click Add).
- In the "Add an Assembly" browse dialog, go to C:\Program Files\VHI\lib\dotnet and select the two or three DLL files that are present:
- AppConn.Interop.dll
- WRQ.Verastream.HostIntegrator.dll
- policy.X.X.AppConn.Interop.config.dll (present if you generated .NET applications with a prior version of VHI, where X.X represents the version)
Use Ctrl+click or Shift+click to select multiple files at once. Click Open.
- View the list of assemblies in the Assembly Cache and verify that the added files are present.
Note: You may need to restart the aspnet_wp.exe process from Windows Task Manager.
Command Prompt Method
Instead of using the Control Panel configuration utility above, you can register the VHI DLL files using the command line to run gacutil.exe (installed with .NET Framework SDK 2.0, or .NET Framework 1.1). For example,
cd c:\Program Files\VHI\lib\dotnetC:\Windows\Microsoft.NET\Framework\v1.1.4322\gacutil.exe /i AppConn.Interop.dllC:\Windows\Microsoft.NET\Framework\v1.1.4322\gacutil.exe /i WRQ.Verastream.HostIntegrator.dllNote: You must have administrative privileges to run gacutil.exe.
To verify that the files are successfully added, examine the C:\Windows\Assembly directory, or run gacutil /l.
