- 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
Event ID: 10536Additionally, the following pop-up error may be logged when you open the BizTalk Server Administration MMC snap-in:
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.BizTalk Server Administration
Bad Data.
(WinMgmt)
Buttons:
OK
Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.