Recently I had to configure a BizTalk 2006 multi-server environment that someone else had built out (installed BizTalk, SQL, prerequisites, etc.)  When running the BizTalk configuration tool I would get the following error:


"BizTalk 2006 Configuration: Microsoft SQL Server 2005 Data Transformation Services (DTS) for BAM Archiving is not installed on the local machine.  Please install Microsoft SQL Server 2005 Integration Services.  (Microsoft.BizTalk.Bam.CfgExtHelper.ToolsHelper" … Additional information: “Could not load file or assembly ‘Microsoft.SqlServer.ManagedDTS, Version=”…


I assumed that the SQL Client Tools weren’t installed, which is a requirement per the installation guides.  I also found this post on the same problem,


This hunch (which the post confirmed) turned out to be correct so I tracked down the SQL Server DVDs; however, when installing the required SQL Client Tools I would get this error message when the setup package was trying to install OWC11:


"Error 1706.  Setup cannot find the required files.  Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM"


Since it was failing on the OWC11 portion of the installation I had a hunch that it was the already installed OWC11 (11.0.8003.0) (likely from the BizTalk 2006 pre-requisites .cab file) that was causing the SQL Client Tools setup program problems so I uninstalled OWC11 and then tried to install the SQL Client Tools again.  They installed successfully this time (and they installed OWC11 (11.0.6558.0).


I decided to repair BizTalk since things we’re being installed in an odd order; additionally, I extracted the owc11.exe (installer) from the BizTalk prerequisites cab and installed it to be safe.  Now the OWC11 version is back to (11.0.8003.0)


I ran the BizTalk configuration tool again it worked smoothly.


So, please follow the installation guides carefully to avoid having to troubleshoot your installation/configuration – or at least to avoid increasing the chances of having to troubleshoot J.