Archive | Installation RSS for this section

Configuring the ESB Toolkit 2.2 for BizTalk 2013 – Exception Creating the ExceptionDb

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.
Advertisements

Delete of ApplicationNode Failed

 BizTalk deploys and undeploys have, in recent times, become much easier than they were back in the “bad old days.”  Especially with tools like the Deployment Framework to help us out, we can usually get through the process with only a little discomfort.

Once in a while, though, you run into something that makes things more difficult than they ought to be.  During a recent application removal on one of our development servers, this lovely message appeared as I attempted to remove the application from BizTalk:

Most of the help out there for the “Delete of  ApplicationNode Failed” message relates to competing resources, etc.  Since, those are pretty well documented, I won’t go into it here.  Here our solution is much simpler than those dealing with other flavors of the exception. 

For whatever reason… someway, somehow… the event log became corrupted and our message is pretty clear on that.

As expected there are a lot of ways to get around this, but FIRST, BEFORE YOU DO ANYTHING ELSE, just try a simple clearing of the Windows Application Log.  In our case, this is what fixed the problem.

BizTalk 2010 Adapter Pack on x64: Why the Adapters May Not Be Listed

Fellow BizTalker, Virtual TS, and Connected Systems Dude Extraordinare, Brent Anderson with RBA Consulting, recently drew my attention to an issue you might find when installing BizTalk 2010 WCF Adapters on 64-Bit systems.   If you install only the 64-bit versions of the adapters, they will not be listed as you go through the “Add Adapter” steps in the BizTalk Administration console.  If you install the 32-bit versions as well, they will show up as they should.

I’m not 100% certain why this is the case, but I suspect it’s because the BizTalk Admin Console and particularly ExplorerOM which the console uses to configure BizTalk artifacts is still 32-bit.  As such, it may not recognize your 64-bit adapters although the BizTalk Engine will use the the correct version when you’re running on a 64-bit Host.

BizTalk 2010 Prerequisite Redistributable CAB Files

These aren’t very well publicized yet, so if you’re doing a “disconnected” BTS 2010 install, you can find the prerequiste CABs at these locations beforehand:

CAB Files for 32-bit Editions (EN):
Windows 7: http://go.microsoft.com/fwlink/?LinkID=189403&clcid=0x409
Windows Vista: http://go.microsoft.com/fwlink/?LinkID=189406&clcid=0x409
Windows Server 2008: http://go.microsoft.com/fwlink/?LinkID=189407&clcid=0x409

CAB Files for 64-bit Editions (EN)
Windows 7:  http://go.microsoft.com/fwlink/?LinkID=189404&clcid=0x409
Windows Vista:   http://go.microsoft.com/fwlink/?LinkID=189405&clcid=0x409
Windows Server 2008: http://go.microsoft.com/fwlink/?LinkID=189408&clcid=0x409
Windows Server 2008 R2: http://go.microsoft.com/fwlink/?LinkID=189409&clcid=0x409

For languages other than English, check out the Installation Documentation at  http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b77d6a4f-8b41-470e-a58c-730dc5859b38&displaylang=en for the complete list.

%d bloggers like this: