ENTSSO experiences a memory leak after you apply hotfix 3000847


  • Issue 1

    After you apply the hotfix from the following Microsoft Knowledge Base article, a memory leak is triggered in the Enterprise Single Sign-On (ENTSSO) service:

    This problem occurs because the SSOCSServer!CICSServer::GetConfigInfo function is called repeatedly. This causes the CPDeriveKey() Windows Crypt API to continually generate a new key. To resolve this problem, CryptDestroyKey() must be called to release its memory allocation after it uses the generated keys.
  • Issue 2

    Consider the following scenario:
    • You have installed the Enterprise Single Sign-On (SSO) version 5 component that's included in Microsoft BizTalk Server 2013 R2 or Host Integration Server 2013. 
    • In one of the following scenarios, you restore the master secret key from a backup file:
      • When you're setting up an Enterprise SSO cluster
      • During enterprise SSO disaster recovery
      • When you're promoting an Enterprise SSO server to the Master Secret Server (MSS)
      • During migration from an earlier version of Enterprise SSO
      • During an in-place upgrade from an earlier version of Enterprise SSO
      • When you're performing multiple Enterprise SSO V5 restore and backup sequences
    After you restore the master secret key in any of these scenarios, Enterprise SSO cannot decrypt the data that's contained in the Enterprise SSO database. In this situation, Enterprise SSO logs the following event in the Application log:
    Event ID: 10536
    Source: ENTSSO
    Level: Warning
    SSO AUDIT Function: GetConfigInfo ({11111111-6055-4cda-89CD-389E8A2B1640}) Tracking ID: b084f15b-43fd-474e-a075-398943753c91 Client Computer: computer name (executable name:PID) Client User: username Application Name: application name Error Code: 0x80090005, Bad Data.

    Additionally, the following pop-up error may be logged when you open the BizTalk Server Administration MMC snap-in:
    BizTalk Server Administration
    Bad Data.


Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


There are no prerequisite to apply this hotfix.

Restart requirement

If files to be updated are being used when you apply this update, you may have to restart the computer afterwards.

Installation information

This update also includes a SQL update. To make sure this update completes successfully, do the following:
  • Make sure that you run the update when you are logged in as a user who is an SSO administrator who has full access to the SSO database. For example, log on as a SQL System Administrator.
  • Verify that the SQL instance that hosts the SSO database is online and available.
  • Run the update on only one BizTalk/SSO server at a time to avoid a race condition between the SQL updates, which will be applied when you run the update.
  • If the SQL instance was inaccessible for some reason, run the update again when the SQL instance can be accessed.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

32-bit (x86) version
File nameFile versionFile sizeDateTimePlatform
Infocache.dll9.0.2266.2130,56005-May-201512:02Not Applicable
Msent.sso.systemmmc.dll9.0.2266.2198,65605-May-201512:02Not Applicable
Ssoconfigom.dll9.0.2266.2140,80005-May-201512:02Not Applicable
Ssoss.dll9.0.2266.2113,15205-May-201512:02Not Applicable
Ssox7.sqlNot Applicable13,70505-May-201512:02Not Applicable
64-bit (x64) version
File nameFile versionFile sizeDateTimePlatform
Infocache.dll9.0.2266.2151,55205-May-201512:02Not Applicable
Msent.sso.systemmmc.dll9.0.2266.2198,65605-May-201512:02Not Applicable
Ssoconfigom32.dll9.0.2266.2140,80005-May-201512:02Not Applicable
Ssoconfigom64.dll9.0.2266.2174,08005-May-201512:02Not Applicable
Ssoss.dll9.0.2266.2124,41605-May-201512:02Not Applicable
Ssox7.sqlNot Applicable13,70505-May-201512:02Not Applicable
Ssox7.sqlNot Applicable13,70505-May-201512:02Not Applicable

Because of file dependencies, the most recent fix that contains these files may also contain additional files.

आलेख ID: 3062831 - पिछली समीक्षा: 17/02/2016 - संशोधन: 1