Re: BizTalk Server 2004 ConfigFramework.exe error

Hi Bryan,
I have problem to pass the SSO setup during the configuration process.
Here is the error I got: "Could not start Enterprise Single Sign-On service
on local computer."

Any idea and solution ?

Thank you in advance !

Nelson Xu


"Bryan E Fairchild" wrote:

> Hi Mariusz,
>
> Thanks for the suggestion. Yes I have a total of 5 Windows 2003 Ent Servers
> in this BizTalk environment. 1 SSO server, 2 BizTalk App servers, 2 Clustered
> SQL servers.
>
> I have since resolved this issue. I was getting errors for a couple of
> reasons. 1st is I was only installing the SSO component to the SSO server,
> and trying to configure this server 2nd. This is kind of a catch 22. Because
> the SSO server needs to be the first server configured in a BizTalk group.
> What I did was install all the components onto my SSO server (even the ones
> I'm only planning on using on my other two app servers). Then I was able to
> successfully run the ConfigFramework on the SSO and my other two app servers.
>
> Hope this made sense.
>
>
> --
> Regards,
> Bryan Fairchild
> -----------------
> NeotericIT.com
> Of recent origin; modern. The development, installation, and implementation
> of computer systems and applications.
>
>
> "Mariusz Borsa [MSFT]" wrote:
>
> > Bryan
> >
> > You said in the beginning that you're trying to install on multitier
> > environment. Do you mean that your SQL Server is on different box from the
> > one BizTalk is installed on? If yes, you might be running into the DTC
> > communication problems, which I think because of the timeout messages I see
> > in the log. See below, maybe this will help you to resolve the problem
> > (from BizTalk docs). Also, make sure that communication between your
> > machines (both for SQL and DTC) is not blocked by firewalls and new MSDTC
> > security settings, which are added and on by default in Win2k3 SP1.
> >
> > -----------------------------------------------
> > Multi-computer configuration using Windows Server 2003 or Windows XP
> > Problem: If you attempt to run the Configuration Wizard on Windows Server
> > 2003, or Windows XP, and point to a remote SQL server, the configuration
> > will fail.
> >
> > Resolution: You must enable network clients DTC access before configuring
> > BizTalk Server. This is required for the distributed transactions performed
> > by BizTalk Server components to work.
> >
> >
> > Important The following procedure must be run on each of the computers in
> > the multi-computer configuration.
> >
> > To turn DTC Access on
> >
> > 1. From the Start menu, double-click Control Panel, double-click
> > Administrative Tools, and then double-click Component Services.
> >
> > 2. Expand Component Services, and then expand Computers.
> >
> > 3. Right-click the computer you need to set, and from the
> > context menu select Properties.
> >
> > 4. In the Properties window, select the MSDTC tab.
> >
> > 5. In the Transaction Configuration area, click Security
> > Configuration.
> >
> > 6. In the Security Settings area, make sure the Network DTC
> > Access check box is selected.
> >
> > 7. In the Security Settings area, check the Network Clients
> > check box.
> >
> > 8. Click OK on each open dialog box.
> >
> > 9. Restart your computer to enable the remote DTC option.
> >
> >
> >
> > Warning This configuration could take up to 15 minutes.
> >
> > size=3 width="100%" align=center>
> > Problem: If you are using Windows Server 2003 for both client and server
> > computers, in a multi-domain or workgroup deployment, and the remote
> > computer is a member of a different domain, RPC security must be turned off
> > or configuration will fail.
> >
> > Resolution: The following registry key must be created on SQL servers, SSO
> > Master servers and anywhere else the BizTalk Engine is installed.
> >
> > HKLM\Software\Microsoft\MSDTC\TurnOffRpcSecurity = 1 (dword)
> >
> >
> >
> > After making sure that above is OK, it’ll be good to test DTC configuration
> > using the DTCTester tool from the following KB article:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;293799
> >
> >
> > Thanks
> > Mariusz Borsa
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > EBusiness Server Team
> > --------------------
> > >>Thread-Topic: BizTalk Server 2004 ConfigFramework.exe error
> > >>thread-index: AcWXhQZtqFfx82oWQxOYaonot0ZL0g==
> > >>X-WBNR-Posting-Host: 192.55.52.10
> > >>From: "=?Utf-8?B?QnJ5YW4gRSBGYWlyY2hpbGQ=?=" <Bryan@xxxxxxxxxxxxxx>
> > >>References: <107C33AC-65BF-42AF-AB80-5C1C30B2EB3E@xxxxxxxxxxxxx>
> > <ufi$s03lFHA.2920@xxxxxxxxxxxxxxxxxxxx>
> > >>
> > >>Hi Scott, Thanks for the comments. Yes there was a *previous installation
> > of
> > >>BizTalk on this server. However, I un-installed BizTalk server and
> > deleted
> > >>all associated databases. Then I re-installed BizTalk and started the
> > >>ConfigFramework script. It just doesn't make sense that ConfigFramework
> > is
> > >>complaining about old/new databases, when installing to a clean
> > environment.
> > >>
> > >>Excuse the long post, but here is the entire log output from the time
> > things
> > >>went south.
> > >>
> > >>[8:54:51 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btswmi.cpp(
> > 266): FAILED hr = c0c025b3
> > >>
> > >>[8:54:51 AM Error BtsCfg] Failed to deploy BizTalk system assembly
> > >>"C:\Program Files\Microsoft BizTalk Server
> > >>2004\Microsoft.BizTalk.GlobalPropertySchemas.dll".
> > >>Timeout expired. The timeout period elapsed prior to completion of the
> > >>operation or the server is not responding.
> > >> [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database
> > >>BizTalkMgmtDb on server sqlserver-nodeA.
> > >>
> > >> [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database
> > >>BizTalkMgmtDb on server sqlserver-nodeA.
> > >>[8:54:51 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btscfg.cpp(
> > 762): FAILED hr = c0c025b3
> > >>
> > >>[8:54:51 AM Info BtsCfg] Leaving function: CBtsCfg::ConfigureFeature
> > >>[8:54:53 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>
> > >>[8:59:16 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>[8:59:22 AM Info ConfigFramework] Showing MessageBox with text: Failed to
> > >>deploy BizTalk system assembly "C:\Program Files\Microsoft BizTalk Server
> > >>2004\Microsoft.BizTalk.GlobalPropertySchemas.dll".
> > >>Timeout expired. The timeout period elapsed prior to completion of the
> > >>operation or the server is not responding.
> > >> [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database
> > >>BizTalkMgmtDb on server sqlserver-nodeA.
> > >>
> > >> [Microsoft.BizTalk.Deployment.DeploymentException] Cannot open database
> > >>BizTalkMgmtDb on server sqlserver-nodeA. Return Code: 4
> > >>[8:59:22 AM Info BtsCfg] Entering function: CBtsCfg::ConfigureFeature
> > >>[8:59:22 AM Info BtsCfg] Configuring feature: WMI
> > >>[8:59:22 AM Info BtsCfg] Entering function: CBtsCfg::IsSelectedCreate
> > >>[8:59:22 AM Info BtsCfg] Leaving function: CBtsCfg::IsSelectedCreate
> > >>[8:59:22 AM Info BtsCfg] Entering function: CWMI::Connect
> > >>[8:59:22 AM Info BtsCfg] WMI is already connected
> > >>[8:59:22 AM Info BtsCfg] Leaving function: CWMI::Connect
> > >>[8:59:22 AM Info BtsCfg] Entering function: CWMI::CreateGroup
> > >>[8:59:22 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btswmi.cpp(
> > 266): FAILED hr = c0c02524
> > >>
> > >>[8:59:22 AM Error BtsCfg] Failed to create Management database
> > >>"BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases.
> > >>[8:59:22 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btscfg.cpp(
> > 762): FAILED hr = c0c02524
> > >>
> > >>[8:59:22 AM Info BtsCfg] Leaving function: CBtsCfg::ConfigureFeature
> > >>[8:59:27 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>[8:59:38 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>[8:59:49 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>[8:59:55 AM Info ConfigFramework] Showing MessageBox with text: Failed to
> > >>create Management database "BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases. Return Code: 4
> > >>[8:59:55 AM Info BtsCfg] Entering function: CBtsCfg::ConfigureFeature
> > >>[8:59:55 AM Info BtsCfg] Configuring feature: WMI
> > >>[8:59:55 AM Info BtsCfg] Entering function: CBtsCfg::IsSelectedCreate
> > >>[8:59:55 AM Info BtsCfg] Leaving function: CBtsCfg::IsSelectedCreate
> > >>[8:59:55 AM Info BtsCfg] Entering function: CWMI::Connect
> > >>[8:59:55 AM Info BtsCfg] WMI is already connected
> > >>[8:59:55 AM Info BtsCfg] Leaving function: CWMI::Connect
> > >>[8:59:55 AM Info BtsCfg] Entering function: CWMI::CreateGroup
> > >>[8:59:55 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btswmi.cpp(
> > 266): FAILED hr = c0c02524
> > >>
> > >>[8:59:55 AM Error BtsCfg] Failed to create Management database
> > >>"BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases.
> > >>[8:59:55 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btscfg.cpp(
> > 762): FAILED hr = c0c02524
> > >>
> > >>[8:59:55 AM Info BtsCfg] Leaving function: CBtsCfg::ConfigureFeature
> > >>[8:59:57 AM Info ConfigFramework] Showing MessageBox with text: Failed to
> > >>create Management database "BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases. Return Code: 4
> > >>[8:59:57 AM Info BtsCfg] Entering function: CBtsCfg::ConfigureFeature
> > >>[8:59:57 AM Info BtsCfg] Configuring feature: WMI
> > >>[8:59:57 AM Info BtsCfg] Entering function: CBtsCfg::IsSelectedCreate
> > >>[8:59:57 AM Info BtsCfg] Leaving function: CBtsCfg::IsSelectedCreate
> > >>[8:59:57 AM Info BtsCfg] Entering function: CWMI::Connect
> > >>[8:59:57 AM Info BtsCfg] WMI is already connected
> > >>[8:59:57 AM Info BtsCfg] Leaving function: CWMI::Connect
> > >>[8:59:57 AM Info BtsCfg] Entering function: CWMI::CreateGroup
> > >>[8:59:57 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btswmi.cpp(
> > 266): FAILED hr = c0c02524
> > >>
> > >>[8:59:57 AM Error BtsCfg] Failed to create Management database
> > >>"BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases.
> > >>[8:59:57 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btscfg.cpp(
> > 762): FAILED hr = c0c02524
> > >>
> > >>[8:59:57 AM Info BtsCfg] Leaving function: CBtsCfg::ConfigureFeature
> > >>[8:59:57 AM Info ConfigFramework] Showing MessageBox with text: Failed to
> > >>create Management database "BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases. Return Code: 4
> > >>[8:59:57 AM Info BtsCfg] Entering function: CBtsCfg::ConfigureFeature
> > >>[8:59:57 AM Info BtsCfg] Configuring feature: WMI
> > >>[8:59:57 AM Info BtsCfg] Entering function: CBtsCfg::IsSelectedCreate
> > >>[8:59:57 AM Info BtsCfg] Leaving function: CBtsCfg::IsSelectedCreate
> > >>[8:59:57 AM Info BtsCfg] Entering function: CWMI::Connect
> > >>[8:59:57 AM Info BtsCfg] WMI is already connected
> > >>[8:59:57 AM Info BtsCfg] Leaving function: CWMI::Connect
> > >>[8:59:57 AM Info BtsCfg] Entering function: CWMI::CreateGroup
> > >>[8:59:57 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btswmi.cpp(
> > 266): FAILED hr = c0c02524
> > >>
> > >>[8:59:57 AM Error BtsCfg] Failed to create Management database
> > >>"BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
> > >>"BizTalkMgmtDb" already exists and it cannot be re-used. Specify another
> > SQL
> > >>database. Also, see documentation regarding reusability rules for
> > BizTalk
> > >>databases.
> > >>[8:59:57 AM Error BtsCfg]
> > >>c:\depot4000\jupiter\source\private\mozart\source\setup\btscfg\btscfg.cpp(
> > 762): FAILED hr = c0c02524
> > >>
> > >>[8:59:57 AM Info BtsCfg] Leaving function: CBtsCfg::ConfigureFeature
> > >>[9:00:00 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>
> > >>[9:20:47 AM Info ConfigFramework] Waiting for configuration thread to
> > >>complete.
> > >>[9:20:51 AM Info ConfigFramework] Showing MessageBox with text: Failed to
> > >>create Management database "BizTalkMgmtDb" on server "sqlserver-nodeA".
> > >>The specified SQL database server "sqlserver-nodeA" / database name
.

Relevant Pages

  • Re: Security Connection Problem
    ... If I am in the SQL ... Server Enterprise Manager and I can't connect to the server using the ... Axapta does not seem to understand the entire DNS name. ... was an error in an Axapta Configuration File. ...
    (microsoft.public.sqlserver.security)
  • Re: Security Connection Problem
    ... If I am in the SQL ... Server Enterprise Manager and I can't connect to the server using the ... Axapta does not seem to understand the entire DNS name. ... was an error in an Axapta Configuration File. ...
    (microsoft.public.sqlserver.setup)
  • Re: BizTalk Server 2004 ConfigFramework.exe error
    ... one BizTalk is installed on? ... machines (both for SQL and DTC) is not blocked by firewalls and new MSDTC ... Multi-computer configuration using Windows Server 2003 or Windows XP ... >>all associated databases. ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk Server 2004 ConfigFramework.exe error
    ... SQL servers. ... and trying to configure this server 2nd. ... the SSO server needs to be the first server configured in a BizTalk group. ... If you attempt to run the Configuration Wizard on Windows Server ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk server Topology & scalibilty
    ... BizTalk itself is 'stateless' and so can run on any machine that has access ... host instances is unrelated to the distribution of databases across SQL. ... could have all dbs installed on a single SQL server, or each on its own SQL ... > configuration of hosts. ...
    (microsoft.public.biztalk.server)