none
BizTalk 2013 R2 - SSODB Issue RRS feed

  • Question

  •  @Team - We are having issue with one our BizTalk instance using BizTalk 2013 R2, we are seeing SSO issue with the following error message and when we check the transaction log on the SQL for SSODB its around 40 GB. When we shrink the log and restart the ENTSSO and BizTalk Service everything looks good for a while and again we see the SSODB went back to 40 GB in a week. We are using SSO App config to store custom config which we are doing on other instances too and the same applications are running on other BizTalk group and we haven't see any issue there. Any thoughts on why SSODB transaction logs are bigger than Message box?

    Log Name:      Application

    Source:        ENTSSO
    Date:          7/21/2017 12:47:19 PM
    Event ID:      10514
    Task Category: Enterprise Single Sign-On
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXXX
    Description:
    An error occurred while attempting to access the SSO database.
     Function: LookupXp
     File: lookupserver.cpp:296
     Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding..
     SQL Error code: 0xFFFFFFFE
     Error code: 0xC0002A21, An error occurred while attempting to access the SSO database.
     
    Friday, July 21, 2017 3:12 PM

All replies

  • Are you using only one or several SSO databases?
    Any SQL Server agent jobs taking care of the sso db and transaction log backup?

    /Peter

    Friday, July 21, 2017 5:11 PM
  •  @Peter - Only one SSODB, we don't have any custom SQL jobs other than BizTalk SQL jobs which we are running.

    Friday, July 21, 2017 5:18 PM
  • Please check that you do have SSODB backup files in the destination folder as configured in the Backup BizTalk Server (BizTalkMgmtDb) job

    Name is something like <dbserver>_SSODB_Log_BTS_2017_07_21_17_15_00_803.<ext>

    Only the log is growing?

    /Peter

    Friday, July 21, 2017 5:33 PM
  • Hi,

    You need to verify some things 

    1) Ensure that the BackUp BizTalk and other Biztalk  jobs are running fine

    2) Run a Full BHM report for the environment  and check if there are any critical warnings.

    Refer to following thread too.

    Biztalk sso db log file incresing in size (SSODB_log.ldf)


    Mandar Dharmadhikari

    Monday, July 24, 2017 5:24 AM
    Moderator