integrating your business

BizTalk can be installed using command line such as this:

"Setup.exe /quiet /addlocal all /IGNOREDEPENDENCIES /INSTALLDIR D:\program files\Microsoft BizTalk Server 2010 /s D:\Install\biztalk2010/configBiztalk2010.xml"

But we had an issue with the INSTALLDIR flag. Using the above path, the installation was failing with an error "Unable to load xml file: c:\users\insUser\AppData\Local\Temp\EBZ39051.tmp\1033\Autorun.xml"

After quite a lot of investigation the developer realised that the INSTALLDIR path with spaces in the name was the culprit. Using quotes around the path did not work either. Instead, the path should be its DOS short name. In order to do that, do the following:

1) Create the destination folder using the commande MKDIR on the destination drive
2) Get the DOS path using the command DIR /X from the destination drive
3) Run again using now the command such as in this example using the new path: "Setup.exe /quiet /addlocal all /IGNOREDEPENDENCIES /INSTALLDIR D:\PROGRA~2\MICROS~2\ /s D:\Install\biztalk2010/configBiztalk2010.xml". It should work fine!

Vincent ROUET, CODit

When installing the 64-bits version of the BizTalk LOB Adapter Pack, you may experience that the bindings (sqlBindings, SAPBinding etc...) do not show in the Binding Type drop down list when using a WCF-Custom Transport Type.

MSDN explains that the installation package only updates the 64-bits version of the machine.config. But the administration console runs in a 32-bits process and will not pick-up the installed binding types.

The solution is:

Up to BizTalk 2009 and the .Net Framework 3.5: Install both the 32-bits and 64-bits versions of the BizTalk Adapter Pack on top of the 64-bits WCF LOB Adapter SDK installation. This way, both machine.config (32 and 64-bits) will be updated. Note: only the 64-bits version of the LOB Adapter SDK must be installed.

From the 4.0 version of the adapter pack compatible for BizTalk 2010, this is not enough. Since the 32-bits version of the Adapter Pack only update the machine.config of the .Net 2.0 version, you must edit yourself the 32-bits version of the .Net 4.0 machine.config file (C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config). Refer to To register the adapter binding for the "how to". Then everything will work fine!

This might get fixed in the RTM version of the .Net 4.0 version of the adapter pack.

Vincent Rouet, CODit