none
Could not start Enterprise SSO could not start RRS feed

  • Question

  • I have a BTS 2k13 running fine since 4 years (with remote SQL in my domain). Recently, I started having issues displaying information in the administration interface. I discovered that it was SSO not running. When I try to run it I get the following.

    In the event viewer I get the following 10503 error

         The SSO service failed to start.
          Error Code: 0xC0002A51, The specified SSO database is not configured.

    And a warning just before it

          This version of the SSO server is not compatible with the SSO database. The SSO server will upgrade your master secret          server.
           SQL Server Name: SQL2K12
            SSO Database Name: SSODB
           SSO Database Version: 0.0
            Required Version: 5.0

    I rerun BTS config, it seems that all is OK as follows

    but running the SSO admin console, I see an RPC error at the end 

    I tried to follow several threads at 

    https://social.msdn.microsoft.com/forums/en-US/f566c35c-093b-4ea6-9d46-aadbd8600b65/error-0xc0002a0f-could-not-contact-the-sso-server-servername-check-that-sso-is-configured-and

    https://support.microsoft.com/en-us/help/2252691/fix-0x80131700-error-code-when-starting-or-configuring-the-enterprise

    ...no way, SSO does not want to start

    Wednesday, November 27, 2019 11:51 AM

Answers

  • After other investigation, I came across a thread that time difference between sql server and domain controller might lead to not being able to connect to SQL. Indeed, I switched to sql server, found time is 10 minutes behind domain controller, configured it as the same time as the DC and everything started to work back again as usual.

    In fact I was not able to connect by RDP to sql server by name but by IP, this thread gave me the hint

    https://serverfault.com/questions/112352/remote-desktop-remote-computer-that-was-reached-is-not-the-one-you-specified

    So it was a question of not being able to connect to sql, so all error messages were misleading


    • Marked as answer by eliassal Wednesday, November 27, 2019 3:41 PM
    • Edited by eliassal Wednesday, November 27, 2019 3:43 PM
    Wednesday, November 27, 2019 3:41 PM

All replies

  • After other investigation, I came across a thread that time difference between sql server and domain controller might lead to not being able to connect to SQL. Indeed, I switched to sql server, found time is 10 minutes behind domain controller, configured it as the same time as the DC and everything started to work back again as usual.

    In fact I was not able to connect by RDP to sql server by name but by IP, this thread gave me the hint

    https://serverfault.com/questions/112352/remote-desktop-remote-computer-that-was-reached-is-not-the-one-you-specified

    So it was a question of not being able to connect to sql, so all error messages were misleading


    • Marked as answer by eliassal Wednesday, November 27, 2019 3:41 PM
    • Edited by eliassal Wednesday, November 27, 2019 3:43 PM
    Wednesday, November 27, 2019 3:41 PM
  • Nice to hear you found the Kerberos time skew limit to be the solution. Make sure to backup master secret and install KB3062831 also on BizTalk 2013 R2. 

    https://support.microsoft.com/en-us/help/3062831

    Friday, December 6, 2019 2:05 PM