SSOSettingEditor and BizTalk 2013

Topics: Bindings File, Settings Management and SSO
Jul 18, 2013 at 12:55 PM
The SSOSettingsEditor returns an error stating that Microsoft.BizTalk.Interp.SSOClient Version= can't be loaded. This appears to be a version that came with an earlier version of Biztalk, and targets the .NET 2.0 runtime. Is there a newer version of this tool built againts the version of this assembly which comes with BizTalk 2013, which targets .NET 4.0 runtime, and its version number is 9.0.1865.0? Thanks
Jul 18, 2013 at 3:47 PM
Nov 7, 2013 at 6:33 AM
Edited Nov 7, 2013 at 6:49 AM

we installed the latest Beta 2 but still faced with the error when deploying to production environment.

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.BizTalk.Interop.SSOClient, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.BizTalk.Interop.SSOClient, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' at SSOSettingsFileManager.SettingsFileImport.Main(String[] args)

Production environment was upgraded to BizTalk Server 2013 Std. but we did not so on our build-environment. Could this be the cause?

Build & Bundle on/via:
BTDF 5.1 Beta 2
Visual Studio 2008 Addin
BizTalk Server 2009 Developer x64

Install & Deploy on/via
BTDF 5.1 Beta 2
MSI-Installer package
BizTalk Server 2013 Standard x64

Unfortunetly we cannot upgrade our build-environment due to operating system-support. We need to have a deploy-strategy for our current scenario. Could you help us?
Nov 7, 2013 at 3:05 PM
When you install the Deployment Framework on a BizTalk 2009 machine it installs a number of files specific to BizTalk 2006-2009. When you install on a BizTalk 2010 or 2013 machine it installs a number of files specific to BizTalk 2010-2013. There is no way around having different files for the different versions of BizTalk. As a result, you cannot build a BizTalk 2013 MSI on a BizTalk 2009 machine.

Since you say it is a build server, I assume that it never actually runs the apps, just builds the code and MSI. In that case, on the build server, you can overwrite the contents of the <BTDFInstall>\5.1\Framework\DeployTools folder with the contents of the same folder from a BizTalk 2013 workstation. That should get you the desired result.