Monday, January 27, 2014

BizTalk 2013 Installation Bug: Enterprise Single Sign-On Error

While Installing BizTalk I received the following Error that Enterprise Single Sign-On should be installed manually.

Well this had not occured while installing previous versions of BizTalk. So I was a little bit curious as to what am I missing on the Server.
So I started installing the redistributable prerequisites manually as this is what BizTalk installation does first.

What I noticed is 
After installing .Net Framework 4.5 from the .cab file I tried to run the BizTalk installation again as normal and selected the .cab file I downloaded.
And it worked fine and BizTalk 2013 was installed successfully with Enterprise Single Sign-On and all other features.
So seems Enterprise Single Sign-On  installation needs .Net Framework 4.5 to be in  place before it can be installed and BizTalk Installation is messing it up somewhere while installing the redistributable prerequisites.

BAM configuration failure in BizTalk 2013

Seems the BizTalk 2013 Installation software has not been tested properly.
I got many errors which I could google and fix it but this one was odd about BAM configuration failed with following error.

ERROR: Encountered error while executing command on SQL Server "".A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)The system cannot find the file specified (Microsoft.BizTalk.Bam.CfgExtHelper.Utility)
[ Error BAMConfigWizExt] 

Solution was to install the latest Cumulative update and try again without Server restart and it worked fine and BAM was configured correctly.
BizTalk Cumulative Update Link

Till now Core Product configuration(SSO,Group,Runtime) was not messed up by Microsoft in all versions (2004 till 2010) I installed/configured. I normally used to install Cumulative update after I am done configuring default BizTalk features or maybe it was a wrong way of doing it  :) .