|
Home > Archive > BizTalk Server > October 2006 > Exception accessing SSO database
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Exception accessing SSO database
|
|
|
| Good day all!
I have implemented the storing of database connections strings in the
SSO database per instructions on John Flander's web site (see
http://www.masteringbiztalk.com/blo...1eb6c4def.aspx.)
[BTW, thanks John!]
All has gone well on my local machine where BizTalk 2006 and SSO
database are running together in Windows Server 2003 SP1. When I try to use
John's config app in our staging environment ( with BizTalk 2006 and SSO
databases on different machines in the same domain), I get the following
exception:
System.Runtime.InteropServices.COMException (0x800706FC): The trust
relationship between the primary domain and the trusted domain failed.
Can anyone tell me what the problem is here? Better yet tell me what the
solution is.
Thanks for your attention.
Best regards --
David Lutz
Cross posted to: microsoft.public.biztalk.appintegration,
microsoft.public.biztalk.general and microsoft.public.biztalk.server
| |
| Ramkumar 2006-10-03, 7:23 pm |
| Hi Dlutz
We have come across this problem some time back on SSO and we have resolved
..What you need do is you should make the two domains trusted that is you can
make one way trusted or both ways depends upon how the security features
wants to be implemented.And also create unique user name on both domains for
SSO account or you can create local account with administrator previleges on
the both boxes(same name) and make the domains one way trusted.Hope this helps
Thanks
Ramkumar
"dlutz" wrote:
> Good day all!
>
> I have implemented the storing of database connections strings in the
> SSO database per instructions on John Flander's web site (see
> http://www.masteringbiztalk.com/blo...1eb6c4def.aspx.)
> [BTW, thanks John!]
>
> All has gone well on my local machine where BizTalk 2006 and SSO
> database are running together in Windows Server 2003 SP1. When I try to use
> John's config app in our staging environment ( with BizTalk 2006 and SSO
> databases on different machines in the same domain), I get the following
> exception:
>
> System.Runtime.InteropServices.COMException (0x800706FC): The trust
> relationship between the primary domain and the trusted domain failed.
>
> Can anyone tell me what the problem is here? Better yet tell me what the
> solution is.
>
> Thanks for your attention.
>
> Best regards --
> David Lutz
>
> Cross posted to: microsoft.public.biztalk.appintegration,
> microsoft.public.biztalk.general and microsoft.public.biztalk.server
>
>
>
| |
|
| Hello again --
The problem below has been solved. A deeper look at John's code revealed
the problem; no problem with his code, just an environment change on my
side.
The problem in a nutshell: the group names passed to the
ISSOAdmin.CreateApplication method in Helper.cs file of John's code were
valid in my dev environment.However, staging environment did not get the
default BizTalk groups created (domain groups were created instead) and so
the names in John's code were invalid in my staging environment. Passing the
group names valid for the staging environment fixed the problem.
What I find perplexing is the error message. I do not find that "The
trust relationship between the primary domain and the trusted domain
failed." tells me what the problem actually was. C'est la vie!
Anyway, I hope this proves of some use to you or some other future
Google'er.
Thanks,
David
"Ramkumar" <Ramkumar@discussions.microsoft.com> wrote in message
news:8401E7B6-D782-43AB-A94D-92C5CFC56BC8@microsoft.com...[vbcol=seagreen]
> Hi Dlutz
> We have come across this problem some time back on SSO and we have
> resolved
> .What you need do is you should make the two domains trusted that is you
> can
> make one way trusted or both ways depends upon how the security features
> wants to be implemented.And also create unique user name on both domains
> for
> SSO account or you can create local account with administrator previleges
> on
> the both boxes(same name) and make the domains one way trusted.Hope this
> helps
> Thanks
> Ramkumar
>
> "dlutz" wrote:
>
|
|
|
|
|