Could not access the SSO database when configure Biztalk Runtime

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Could not access the SSO database when configure Biztalk Runtime

Viewing 1 reply thread
  • Author
    Posts
    • October 8, 2008 at 7:57 PM #20932
      community-content

         when configure Biztalk Runtime, error out “New transaction cannot enlist in specified transaction coordinator”.

        And in event log, warning:

        Event Type: Warning
        Event Source: ENTSSO
        Event Category: Enterprise Single Sign-On
        Event ID: 10603
        User:  N/A
        Computer: Event Type: Warning
        Event Source: ENTSSO
        Event Category: Enterprise Single Sign-On
        Event ID: 10603
        User:  N/A
        Description:
        Could not access the SSO database. If this condition persists, the SSO service will go offline.
         Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding..
         SQL Error code: 0xFFFFFFFE

         

        I already done lots of modification related to MSDTC to make sure its functionality. But same error persists.

         

        Does anybody have some tips?

         

        Thanks in advance

      • October 8, 2008 at 8:00 PM #20933
        community-content

           Additionally, Biztalk and SQL Server are on seperate machines.

          • October 9, 2008 at 2:14 PM #20939
            community-content

              It definately is a Distributed Transaction Coordinator (MSDTC) error – I blogged about this several months ago at http://www.modhul.com/2008/01/22/further-biztalk-msdtc-issues/

              If you’re still not having any luck, please post any error messages you receive on the SQL Server / BizTalk Side.

              Rgds, Nick.

              • October 12, 2008 at 5:29 AM #20958
                community-content

                   Thanks for your reply, Nickh!

                  I tried almost all the modification on MSDTC(Actually a lot of others) and DTCPing shows fine. But error still.

                  So I have to reinstall MSDTC on both servers. Worked!

                  I think that’s because OS were coloned on these 2 servers.

                  In addition, we’d better reinstall MSDTC strictly per http://support.microsoft.com/kb/279786

                   

                  • October 13, 2008 at 1:42 AM #20961
                    community-content

                      “I think that’s because OS were coloned on these 2 servers.”

                      That probably would be the problem, yes…!

                      Nick.

            • Author
              Posts
            Viewing 1 reply thread
            • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.