Failed to connect to the SQL database 'SSODB'


hi,

have dev biztalk environment (vm) of windows server 2003 (64 bit) machine. when try configure biztalk 2006, getting error "failed connect sql database 'ssodb' on sql server 'xxxxxxxxx'. (sso)".  i need join existing sso db.

trying workarounds like:  running esso hotfix which update entsso assembly registration correct version of .net framework, but failed with below error:

"esso v4 x64 gdr not found or package not contain compatible patch"

tried  regasm “c:\program files\common files\enterprise single sign-on\win32\ssosql.dll”
and regasm “c:\program files\common files\enterprise single sign-on\ssosql.dll” still getting same error.

can please suggest solution?

hi,

i removed .net frameworks till 2.0 , able configure sso db.  when configuring ruleengine db getting below error: 

""the specified rules engine database not match pre-configured database biztalk server group. pre-configured database group server: xxxxxxxxxx, database: biztalkruleenginedb"

any suggestions resolve error?


hi juhi,

thank posting in msdn forum.

seems first issue has been resolved of below article,

http://msbiztalk.blogspot.in/2010/07/sso-problem-failed-to-connect-to-sql.html

for second issue first please check configured database name using below script,

select ruleenginedbservername, ruleenginedbname biztalkmgmtdb.dbo.adm_group id = 1

thanks,

if reply helpful please mark answer or vote helpful.

my blog | twitter | linkedin

this post own opinion , not reflect opinion or view of microsoft, employees, or other mvps.



BizTalk Server  >  BizTalk Server General



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more