Typically, the actual installation goes through smoothly and once the base product is laid down, all is well until the BizTalk configuration wizard tries to perform it’s final steps.  Just to keep things in perspective, here are the typical steps taken in configuring a new installation of BizTalk Server leading up to the error.

Start the BizTalk Configuration Wizard

The first step is simply launching the BizTalk Configuration Wizard after the installation is complete.

Many situations would allow for using the “Basic configuration” to be used, but I’m a control freak when it comes to what and how every module is installed on my servers, so naturally, I pick the “Custom configuration” option and then click on “Configure” to start the process.

For the sake of demonstration, I’m going to simply install everything on a single server.  Typically, and resource limitations aside, I’d split the install among several servers, but the issue I’m covering is not typically install location specific.

Configure BizTalk Group

Given the fact that the root issue typically pops up during the configuration of the BizTalk Group feature, I’ll focus on this step for now.  Obviously a typical installation of BizTalk Server may not just consist of a running BizTalk Group, but again, I don’t want to waste your time with things that are not affecting you for this challenge.

Note: If you haven’t performed a custom configuration before, you must install the Enterprise Single Sign-on feature before you are allowed to install the BizTalk Group, otherwise, you’ll be slapped with this beauty:

I’ll write up an entire installation guide a bit later on that will cover such details, so keep an eye open for that once I have it ready.  For the time being, accept the defaults of the SSO feature installation and include your Master Secret backup password and location.  Next, click on the “Group” option in the navigation tree.

Select “Enable BizTalk Server Group on this computer” and then opt to “Create a new BizTalk Group”.  The Data stores and BizTalk Administrative Roles will populate automatically for you.  Again, simply for the sake of demonstrating the error, that’s all I’m going to include in this configuration process.  Click on “Apply Configuration” and click on “Next” to see the faulty magic…

Unfortunately, and one thing that Microsoft is really good at, is not typically exposing the actual error right there on the screen.  So, let’s dig in to that Logfile that has been created in the temp directory to see what’s up.

I’ve cleaned up the configuration log and highlighted the location of where the BizTalk Configuration Wizard logged the error.  As plainly demonstrated, the wizard was unable to create the necessary database, “BizTalkMgmtDb” on the target SQL Server.

The Problem

I hate to label this particular error as a, “problem”, but it does frustrate several folks.  However, the root issue is more of a comparability issue more than anything else.  Technology is constantly improving, err…upgrading to different versions, and not all versions of different software will be guaranteed to play well with one another.

In this case, the issue is that the installation of Microsoft BizTalk Server 2009 is attempting to create databases on SQL Server 2008 R2.  There is a compatibility gap between the R2 release of SQL Server 2008 and BizTalk Server 2009.  BizTalk Server 2009 does not support SQL Server 2008 R2 , whereas BizTalk Server 2010 will communicate as desired with SQL 2008 R2.

The Solution

Of course, the solution may require you to throw money at the issue in order to ensure that the correct versions of server platforms are in use.

I hope this helps!