Today I had for specific reasons to install the older BizTalk 2006 R2 on a Windows 2008 R2 server. Now although this leads to an unsupported scenario; it is still valid for development environments (as in the case I encountered). Another issue that complicated the problem is that this server already had Visual Studio 2010 with .NET framework 4.0 installed on it.
I had already also installed SQL server 2008 on this server. So I started to follow the BizTalk 2009 installation guide. It went actually very smooth (to my surprise). The issues or notes I faced were as follows.
1- First the prerequisites file it downloaded was kind of strange for me. It downloaded a file called “BTSRedistVistaEn64.cab”. So this is a file that should be directed to Vista and not 2008 R2. But it was installed with no problems.
2- The MSDTC have to be configured as per the BizTalk 2009 guide to get it BizTalk to be configured properly. This is done as below image:
3- Since I also had SQL express installed on the same box I had to disable it to make sure it does not interfere with the configuration.
4- I installed VS 2005 with no noticeable issues.
5- I then installed BizTalk and had no issues there.
6- The main problem I faced was related to ENTSSO configuration. First I could not get it to start configuring it as it reported that the SSODB does not exist on the SQL server! So I am thinking; but I want to create it. Why does it need this DB although it will be created? After several hours of research I found the root cause. The problem was related to that the ENTSSO was using a wrong set of assemblies since its SQL communication COM+ component was registered using the REGASM utility of .NET4.0. The resolution was to re-register this assembly using the .NET 2.0 frameowork utility. To do so.
a. Open a command prompt.
b. Go to C:\Windows\Microsoft.NET\Framework64\v2.0.50727
c. regasm “C:\Program Files\Common Files\Enterprise Single Sign-On\win32\ssosql.dll”
d. regasm “C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll”
7- I also needed to disable the shared memory protocol on the SQL server.
8- For the BAM I was not yet able to get it to work or configured as it reported that the SSAS is not a supported version. I will do further investigation on how to configure BAM on this configuration.
Did you ever get this working?
The only way I got BAM to work in this configuration is to install SSAS on a separate instance using SQL 2005 and used only for SSAS and not even for the BAM databases (these works ok on SQL 2008).