I am trying to install BizTalk 2009 Developer Edition on my standalone machine running Sql Server 2008. When I run basic configuration I get the following message under Enterprise SSO validation: Message: Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' when I double-click on this message I get the following information in a popup: Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' 0x80131700 (Win32) No matter what I try, I can't get rid of this message and I can't get the rest of BizTalk to install without SSO. I've attached the relevant portion of my ConfigLog.log file if that helps at all... Any ideas? Thanks, Mike
Did you find any fix for this, running into same issue Windows server 2003 Sp2 SQL Server 2008 SP1 Visual Studio 2008 SP1 / 2010 2007 Sharepoint Server. Thanks for your help. "Michael Carr" wrote: > I am trying to install BizTalk 2009 Developer Edition on my standalone > machine running Sql Server 2008. When I run basic configuration I get the > following message under Enterprise SSO validation: > > Message: Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > when I double-click on this message I get the following information in a > popup: > > Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > 0x80131700 (Win32) > > No matter what I try, I can't get rid of this message and I can't get the > rest of BizTalk to install without SSO. > > I've attached the relevant portion of my ConfigLog.log file if that helps at > all... > > Any ideas? > > Thanks, > Mike > >
Hi, got the same issue atm. Additionaly im getting error saying "Failed to open the explicitly specified database" in event log. It's strange behavior since SSODB database should be created, not connected. Did you find any fix for this? Kind regards "KM" wrote: > Did you find any fix for this, running into same issue > > Windows server 2003 Sp2 > SQL Server 2008 SP1 > Visual Studio 2008 SP1 / 2010 > 2007 Sharepoint Server. > > Thanks for your help. > > > "Michael Carr" wrote: > > > I am trying to install BizTalk 2009 Developer Edition on my standalone > > machine running Sql Server 2008. When I run basic configuration I get the > > following message under Enterprise SSO validation: > > > > Message: Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > > > when I double-click on this message I get the following information in a > > popup: > > > > Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > 0x80131700 (Win32) > > > > No matter what I try, I can't get rid of this message and I can't get the > > rest of BizTalk to install without SSO. > > > > I've attached the relevant portion of my ConfigLog.log file if that helps at > > all... > > > > Any ideas? > > > > Thanks, > > Mike > > > >
Hi, I was getting the same error "Failed to connect to the SQL database ..." during config. I tried running : 'regasm SSOSQL.dll' as suggested at this blog : http://gloriousmonster.blogspot.com/ and then ran config and it worked just fine. Hope this helps. "Piotr Skorupski" wrote: > Hi, > > got the same issue atm. Additionaly im getting error saying "Failed to open > the explicitly specified database" in event log. It's strange behavior since > SSODB database should be created, not connected. Did you find any fix for > this? > > Kind regards > > "KM" wrote: > > > Did you find any fix for this, running into same issue > > > > Windows server 2003 Sp2 > > SQL Server 2008 SP1 > > Visual Studio 2008 SP1 / 2010 > > 2007 Sharepoint Server. > > > > Thanks for your help. > > > > > > "Michael Carr" wrote: > > > > > I am trying to install BizTalk 2009 Developer Edition on my standalone > > > machine running Sql Server 2008. When I run basic configuration I get the > > > following message under Enterprise SSO validation: > > > > > > Message: Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > > > > > when I double-click on this message I get the following information in a > > > popup: > > > > > > Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > > 0x80131700 (Win32) > > > > > > No matter what I try, I can't get rid of this message and I can't get the > > > rest of BizTalk to install without SSO. > > > > > > I've attached the relevant portion of my ConfigLog.log file if that helps at > > > all... > > > > > > Any ideas? > > > > > > Thanks, > > > Mike > > > > > >
Thanks a bunch NG, you saved my day. KM "NG" wrote: > Hi, > > I was getting the same error "Failed to connect to the SQL database ..." > during config. I tried running : 'regasm SSOSQL.dll' as suggested at this > blog : > http://gloriousmonster.blogspot.com/ > and then ran config and it worked just fine. > Hope this helps. > > > "Piotr Skorupski" wrote: > > > Hi, > > > > got the same issue atm. Additionaly im getting error saying "Failed to open > > the explicitly specified database" in event log. It's strange behavior since > > SSODB database should be created, not connected. Did you find any fix for > > this? > > > > Kind regards > > > > "KM" wrote: > > > > > Did you find any fix for this, running into same issue > > > > > > Windows server 2003 Sp2 > > > SQL Server 2008 SP1 > > > Visual Studio 2008 SP1 / 2010 > > > 2007 Sharepoint Server. > > > > > > Thanks for your help. > > > > > > > > > "Michael Carr" wrote: > > > > > > > I am trying to install BizTalk 2009 Developer Edition on my standalone > > > > machine running Sql Server 2008. When I run basic configuration I get the > > > > following message under Enterprise SSO validation: > > > > > > > > Message: Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > > > > > > > when I double-click on this message I get the following information in a > > > > popup: > > > > > > > > Failed to connect to the SQL database 'SSODB' on SQL Server 'MCARR' > > > > 0x80131700 (Win32) > > > > > > > > No matter what I try, I can't get rid of this message and I can't get the > > > > rest of BizTalk to install without SSO. > > > > > > > > I've attached the relevant portion of my ConfigLog.log file if that helps at > > > > all... > > > > > > > > Any ideas? > > > > > > > > Thanks, > > > > Mike > > > > > > > >
