Tuesday, August 07, 2012 4:16 PMHi all, i am installing BTS 2009 in my system. During configuration, i am facing error. SSODB and all other DB's are failed to connect to the SQL server. I can clearly see this might be some logon error which prevent my biztalk to create DB's in server. First of all i was trying to make SSODB, as its the first thing in configuration. I ve tried all the mechanisms suggested in most articles(like SSOSQL.dll, regasm andd alll). But all my efforts was vain. i was nt configure successfully. I dont know how to resolve this issue. I need help to fix this asap.
Tuesday, August 07, 2012 4:22 PM
is the sql server in cluster?
Do you have dbo privilages in that instance?
Any further error info from log/event log?
Tuesday, August 07, 2012 4:26 PM
No message in event log. I hav privileages and it s nt cluster
Tuesday, August 07, 2012 4:33 PM
Is it possible to upload error screen shot, during configuration?
can u once check in sql event log as well. Also just check in Applciaiton,security,setup and system logs even.
Tuesday, August 07, 2012 4:37 PMrite now, am not having the screen shots. But i guess, it may be due to improper credentials given during SQL installation(since, i was not able to config SSO, i guess this). Is there any way to rectify it?
Tuesday, August 07, 2012 4:42 PM
can you configure SSO in SQL Server.
Login to SQL server and install SSO components in SQL through bizTalk setup and run the biztalk configuration.
Tuesday, August 07, 2012 4:53 PMhere's what i face the error, Haik. It says that the SSODB cannot be able to connect to my SQL server(NAME OF MY SERVER)
Tuesday, August 07, 2012 4:58 PM
Just one more try, Is the ping fine ? MSDTC configuration setting perfect in biztalk and sql?
Tuesday, August 07, 2012 5:00 PMsorry Haik, couldnt get you. can you explain the above one again?
Tuesday, August 07, 2012 6:08 PM
Is the SQL in same machine as in biztalk?
if not , ping the sql server from biztalk..,check the msdtc setting as defined in msdn...,
and if possible, re-installation could solve the issue
- Marked As Answer by LeoTangModerator Sunday, August 19, 2012 4:26 AM
Wednesday, August 15, 2012 4:12 AMModeratorTry to delete all databases (and ESSO database!) manually by SQL Server Management Studio.
Leonid Ganeline [BizTalk MVP] BizTalkien: Naming Conventions for the BizTalk Solutions
Thursday, August 16, 2012 12:10 PM
Try implement step 2 in article mentioned below on both BizTalk and SQL Box
Thursday, August 16, 2012 12:51 PMHave you installed SQL Server client tool on your BizTalk box?