As we’ve seen, there is a little problem with the Install MSI action after importing an BizTalk application in the BizTalk Application Console. (remember this post)
Today I’ve discover a new little issue…
I tried to Import the MSI of the ESB Toolkit in the Biztalk Administration Console, the result is good. Then I tried to install the MSI and I get an error :
So, I decided to check my Application Event Log and I’ve got the two following Errors :
An error occurred while attempting to install the BizTalk application: A file load exception occurred while attempting to install the assembly into the Global Assembly Cache. This error may occur if the assembly is delay signed, or if assembly was renamed after creating/signing.
The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.BizTalk.ApplicationDeployment.ApplicationDeploymentException
at Microsoft.BizTalk.ApplicationDeployment.ApplicationInstallerHelper.Install(System.Configuration.Install.Installer, System.Collections.IDictionary)
The interesting element is this one : Framework Version : v220.127.116.119.
Indeed, in my MSI, all my assembly have been build with the Framework Version : v2.0.50727 and before exporting my MSI from the BizTalk Administration Console, all my Assembly had this configuration :
The Problem seems to be the following : when you check this box, the executable use the Gacutil of the framewok .Net 4 so when it try to gac a .Net 2 dll, it failed…
The Importer of the BizTalk Administration Console seems to be able gac the DLL in the good place.
(Info : In the normal installation of the ESB toolkit 2.1, this case is not check, I think we check this case before preparing the deployment for an other platform…)