One of the great things about BizTalk 2013 is the improvements made in the installation of the ESB Toolkit. However, we’ve found lately, that there are still some issues that you should be watching for during configuration.
One issue, which I’ve seen twice now, has shown up while completing the very first configuration step in the ESB Toolkit 2.2’s configuration utility–creating the Exception Management database. Our configuration failed with this exception:
Exception Calling “create” with “0” argument(s) “Create failed for database esbExceptiondb’.”
Generally the first thing we do is figure out if there are security issues. In particular, we need to make sure that the account we are logged in with has all the correct rights on the SQL Server. In my opinion, it’s probably best to have SA privileges while completing the configuration, but I’m sure there are plenty of DBAs who would argue with me on that. We were able to verify that, in fact, we were operating under such an account.
That led us into the configuration tool’s log file, which gave us a much more helpful hint:
The primary file must be at least 100 MB to accommodate a copy of the model database.
The source of the problem seems to be a powershell script, embedded into an .exe, that sets the size of the DB. Because the value is “hard-coded” into the uneditable script, the other option is to shrink the model db. Once you connect to the SQL server, you can find the model db under System Databases in SSMS.
First, before you go any further, BACK UP THE DATABASE.
You can use SSMS to perform the shrink. We found that running a shrink script didn’t work as well. So in SSMS, you just right-click the database and select Tasks -> Shrink -> Database. Then configure the options to get the DB down to a more manageable size. You can find an MSDN article on using SSMS to shrink a database here
This worked for us right away and configuration of the ESB Toolkit was able to be continued.