When we run the BizTalk Configuration Wizard to configure BizTalk (2 BizTalk hosts, non-clustered remote SQL), it fails due to the Enterprise SSO configuration step failing with a SQL timeout on the Create Database SQL operation:

[2:53:26 PM Info SSOServerCfg] (ssoconfigobj2.cpp:5181) Returning error description: <Exception Message="Failed to create the SQL database 'SSODB' on SQL Server 'STG-BIZT-DB1' (with SSO Administrator account 'DEV\SSO_Admins_STG')." Source="SSO" HelpID=""><Exception Message="(0xC0002A21) An error occurred while attempting to access the SSO database.

" Source="SSO" HelpID=""><Exception Message="An error occurred while attempting to access the SSO database. See the event log (on computer 'STG-BIZT-APP1') for more details.

(SQL: 0xFFFFFFFE: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.)" Source="SSO" HelpID=""/></Exception></Exception>

What could be causing this and how can we resolve it? Is there any way to change the SQL command timeout for the BizTalk Configuration Wizard? Could it be related to MSDTC (although we used DTCPing to test and MSDTC connectivity test between all servers were all successful).

Thanks in advance.

Hi,

According to your Error code '0xC0002A21',

One odd reason of this exception is an old SSO database file in the database folder.

'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA'

This prevents the creation of SSO DB because a database file already exists at the same path. To resolve, just delete the old SSODB.mdf and SSODB.ldf files

In addition I would like to suggest please look at this support articl

There were no existing database files in there and the config still fails. We've tracked down the root cause is due to the CREATE DATABASE Sql operation for the SSO database timing out. In our environment, since the Model database is configured to start at 500 MB, creating a database takes about 90 seconds. It looks like the BizTalk Configuration Wizard times out at 60 seconds.

Is there any way to increase the SQL command timeout for the BizTalk Configuration Wizard?

Thanks.

In that case, what you should do is pre-create the database.  If Configuration detects an otherwise empty database, it will assume that's what you want to use and skit the actual CREATE step.

This is supported and actually then only way to use a database with non-default settings.

Thanks for the response.

So I'm assuming we have to do this for all the BizTalk databases the wizard's supposed to create including the two SSAS data stores for BAM (BAMAnalysis and BAMStarSchema)?

If the lengthy CREATE is due to something on the SQL layer, then yes, you will have to pre-create any affected databases.

In that case, what you should do is pre-create the database.  If Configuration detects an otherwise empty database, it will assume that's what you want to use and skit the actual CREATE step.

This is supported and actually then only way to use a database with non-default settings.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 5 hours 45 minutes ago

In that case, what you should do is pre-create the database.  If Configuration detects an otherwise empty database, it will assume that's what you want to use and skit the actual CREATE step.

This is supported and actually then only way to use a database with non-default settings.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Monday, August 24, 2015 1:20 AM

Are there any firewalls or IP/port restrictions between the BizTalk and SQL Server machines? It looks like it is trying to connect but for some reason it cannot connect to the SSO database. In some environments you have to enable IP addressing from BizTalk to the SQL box. Also, please make sure that the COM+ System Application Windows service is running.

Please check below configurations,
1. User DEV\SSO_Admins_STG have proper right to create database
2. check firewall
3. Windows services are running
4. try dtctester tool

Hi,Try configuring MSDTC as in the following article: http://bencode.wordpress.com/2008/01/27/dtc-and-biztalk/. This would explain why the database is having some problems being created completely.

During configuration of SSO the master secret is generated and is used for securing the credentials usually stored in the SSO database. Probably you are dealing with something about the master secret being out of sync with your SSO database. It is possible that the master secret was generated on the first install and when you create the SSO database again it is pulling the old master secret and its not working appropriately. Or perhaps it is trying to generate a new master secret and this is not working for some reason. Here is an article about generating the master secret: http://technet.microsoft.com/en-us/library/aa560212.aspx.

An alternate strategy would be to do a basic configuration run to get the BizTalk environment cleaned up (from the very first failed install) and then unconfigure everything and finally do an advanced configuration to specify specialized accounts and settings. It seems like you are trying to get back to a clean state on your BizTalk server so you can get things running again

The OP has already stated that the problem is on the SQL Server, specifically the CREATE operation.