This project has moved. For the latest updates, please go here.
1

Closed

SSO Ticket creation assembly version issue

description

SSO Ticket creation is throwing following error (Environment Biztalk 2013)
[17964] Timestamp: 13-02-2015 23:07:50.723
[17964] Assembly Full Name: BREPipelineFramework.Helpers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=83eab0b166470ebc
[17964] Assembly Version: 1.0.0.0
[17964] App Domain Name: DefaultDomain
[17964] Application Base Path: C:\Program Files (x86)\Microsoft BizTalk Server 2013\
[17964] Exception Information Details:
[17964] ======================================
[17964] Exception Type: System.IO.FileNotFoundException
[17964] Message: Could not load file or assembly 'Microsoft.BizTalk.Interop.SSOClient, Version=5.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
[17964] FileName: Microsoft.BizTalk.Interop.SSOClient, Version=5.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[17964] FusionLog: WRN: Assembly binding logging is turned OFF. 
[17964] To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. 
[17964] Note: There is some performance penalty associated with assembly bind failure logging. 
[17964] To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. 
[17964] 
[17964] TargetSite: Void Execute(Microsoft.BizTalk.Message.Interop.IBaseMessage ByRef, Microsoft.BizTalk.Component.Interop.IPipelineContext)
[17964] Source: BREPipelineFramework.SampleInstructions
Closed Feb 26, 2015 at 1:39 AM by jcooper1982
Issue was fixed by providing a custom build for BizTalk 2013 since the user wasn't able to make use of assembly redirection in their production environment.

comments

jcooper1982 wrote Feb 14, 2015 at 12:58 AM

Hi Secrets,

This was done by design to ensure that the framework is compatible with all versions of BizTalk 2010+. Microsoft chose to update the assembly version on this specific assembly, not the norm for most of their BizTalk assemblies. The framework targets the assembly version used by BizTalk 2010 but with a config change the version can be retargeted to make the framework compatible with later versions of BizTalk.

The best way to cater for this is to add an assembly redirect to your BizTalk config files which would fix the problem, take a look at the following article written by my colleague Mahindra for more info - https://connectedcircuits.wordpress.com/2013/06/19/could-not-load-assembly-microsoft-biztalk-interop-ssoclient-ver5-0-1-0-after-bts2013-upgrade/

If for whatever reason you are not keen to modify your BizTalk config files then let me know and I'll create an installer which specifically target BizTalk 2013 for you.

Cheers
Johann

secrets wrote Feb 14, 2015 at 7:45 AM

Hi Johann,
yup already using this assembly redirect on my dev machine.
But this is not possible for Production environment, please create the installer for BizTalk 2013.

jcooper1982 wrote Feb 15, 2015 at 12:03 AM

Hi secrets,

I've uploaded an installer that specifically targets BizTalk 2013 so you will not need to use any assembly redirections to get the BRE Pipeline Framework v1.5.4 to work. There are no differences between this build and the core build besides the reference to the Microsoft.BizTalk.Interop.SSOClient assembly.

Will you please download the installer from the below link and let me know if this fixes your problem

https://brepipelineframework.codeplex.com/releases/view/611688

Cheers
Johann

secrets wrote Feb 15, 2015 at 1:54 PM

Hi Johann,
I can't download it:

There are no downloads associated with this release.

jcooper1982 wrote Feb 15, 2015 at 6:52 PM

Hi secrets,

Sorry about that, I've uploaded the file again now. Can you please try again at the same link?

Cheers
Johann

jcooper1982 wrote Feb 21, 2015 at 12:28 AM

Hello secrets,

Can you please let me know if this has fixed your issue?

Cheers
Johann

secrets wrote Feb 25, 2015 at 3:50 PM

Hi Johann,
sorry for delayed response. it's working fine now.

wrote Feb 26, 2015 at 1:39 AM