Skip to main content

BizTalk : Runtime assembly loading issue , Could not load file or assembly

By


BizTalk : Runtime assembly loading issue , Could not load file or assembly



If you require a specific version of  assembly to be loaded at runtime when your BizTalk application run. This requirement could be implemented by adding a required assembly setting in BTSNTSvc.exe.config. In biztalk config file you need to specify the old and new version of assembly that need to be loaded at runtime.



Following setting could be added in your BTSNTSvc.exe.config file with proper assembly details.



Using this Binding Policy in config, we can load the any required assembly at runtime..



<runtime>

                                <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

                                                <dependentAssembly>

                <assemblyIdentity name="BTSales.DataAccess" publicKeyToken="89b653f429c47342" culture="neutral" />

                    <bindingRedirect oldVersion="2.111.7.0" newVersion="4.112.1.2"/>

            </dependentAssembly>

                                </assemblyBinding>

                </runtime>


After implementing the above changes in BtsntSvc.exe.config file, if you are still getting this error while using  BTAdmin console then  update the BTSMMCLauncher.exe.config  file same as above. This will resolve your design time assembly loading issue.
Added following  thing in BTSMMCLauncher.exe.config , Reopen your BTS Admin console.
<runtime>

                                <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

                                                <dependentAssembly>

                <assemblyIdentity name="BTSales.DataAccess" publicKeyToken="89b653f429c47342" culture="neutral" />

                    <bindingRedirect oldVersion="2.111.7.0" newVersion="4.112.1.2"/>

            </dependentAssembly>

                                </assemblyBinding>

                </runtime>
Labels:

Comments

Post a Comment

Popular posts from this blog

WCF MaxReceivedMessageSize max value in .config

By
MaxReceivedMessageSize parameter in binding config   file:   For max file size in WCF, we need to set following parameter in binding files. <binding name="MyService"        maxReceivedMessageSize="2147483647"        maxBufferSize="2147483647" transferMode="Streamed" >        <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"      maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/> <!-- other binding info here, such as security --> </binding> Max possible size: MaxReceivedMessageSize to 2147483647 (i.e. Int32.MaxValue), which is 2GB For our case, as we are using WsHttpBinding. <wsHttpBinding>         <binding name="wsHttpBindingSettings" maxReceivedMessageSize="2147483647">      ...
Post a Comment
Read more

Deploying Custom Pipeline Component on BizTalk Server (PROD)

By
Deploying Custom Pipeline Component on BizTalk Server: ·         Deploying BizTalk Custom Pipeline Component   on BizTalk Server 2006 or Older Version : To deploy the custom Pipeline component on BizTalk server 2006 or older version. We need to add the Custom Pipeline component in GAC as well as “ C:\Program Files (x86)\Microsoft BizTalk Server 2006\Pipeline Components ” folder.   At design time it will access the Pipeline component dll located in “….. Microsoft   BizTalk Server 2006\Pipeline Components ” folder and show the component in pipeline toolbox. At runtime the BizTalk will use the Custom Pipeline component from GAC. ·         Deploying BizTalk Custom Pipeline Component   on BizTalk Server 2006 R2 or New Version : To deploy the custom Pipeline component on BizTalk server 2006 R2 or later version. We need to add the Custom Pipeline component only in “C:\Pr...
12 comments
Read more

biztalk schema remove ns0 prefix

By
We can remove ns0 prefix simply by set the schema elements property or both elements and attributes properties to be qualified. To do that follow my steps: 1-       Open your schema 2-       Right Click <Schema> and select properties 3-       Use schema property editior and Set [Element FromDefult] to Unqualified , and then set [Attribute FromDefault] to Unqualified if you are using attributes in your schema. After applying the steps above, both XML instances below will be valid: Instance 1 (with ns0) < ns0:Root xmlns:ns0 = " http://RandomBizTalkProject.Schema1 " >   < Field1 > Field1_0 </ Field1 >   < Field2 > Field2_0 </ Field2 > </ ns0:Root > Instance 2 (without ns0) < Root xmlns = " http://RandomBizTalkProject.Schema1 " >   < Field1 > Field1_0 </ Field1 >   < Field2 >...
Post a Comment
Read more