BizTalk Server 2013 R2: Installation of Microsoft hotfix KB3062831 failed

Hello BizTalk-Friends&Fans,

I have a problem by installing the necessary Microsoft hotfix KB3062831 for the SSO service on my BizTalk 2013 R2 server and I need your qualified help.

Our infrastructure
==================

BizTalk-Applicationserver 1
– OS: Windows Server 2012 R2 Standard german 64bit with all actual patches
– BizTalk-Version: BizTalk Server 2013 R2 german 64bit with CU8 installed
– Master secret server for SSO

BizTalk-Applicationserver 2
– OS: Windows Server 2012 R2 Standard german 64bit with all actual patches
– BizTalk-Version: BizTalk Server 2013 R2 german 64bit with CU8 installed
– Tracking Host and cold standby server for BizTalk system

SQL-Server 1
– OS: Windows Server 2012 R2 Standard german 64bit with all actual patches
– Microsoft SQL Server 2014 Enterprise (64-bit) german
– Hosts all of the BizTalk and customer databases, except the BizTalkMsgBoxDB

SQL-Server 2
– OS: Windows Server 2012 R2 Standard german 64bit with all actual patches
– Microsoft SQL Server 2014 Enterprise (64-bit) german
– Hosts the BizTalkMsgBoxDB

Problem details
===============
I checked our BizTalk system with the BizTalk Health Monitor tool (v4.2), with actual collect framework (9.3) and Queries/rules repository version (4.74). One critical warnings shows, that the following Microsoft hotfix was missing:

“KB3062831 not installed on FOX02SV160185: Master secret key cannot be restored and/or memory leaks can occur in SSO”
So I downloaded the hotfix and try to install the Application “ESSOv5-KB3062831-x64-ENU.exe”, but a dialog window with the following error occured:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

Following you find the output of the installation log (translated by me, cause the output content was in german … ;-):

MSI (s) (CC:54) [13:28:52:011]: Product: Microsoft Enterprise Single Sign-On — Installation failed.
MSI (s) (CC:54) [13:28:52:012]: The product was installed by Windows Installer. product name: Microsoft Enterprise Single Sign-On. product version: 9.0.2096.0. product language: 1031. Hersteller: Microsoft Corporation. State of success or failure of the installion: 1642.
MSI (s) (CC:54) [13:28:52:013]: Closing MSIHANDLE (1) of type 790542 for thread 9300
MSI (s) (CC:54) [13:28:52:013]: Attempting to delete file C:\Windows\Installer\8737614b.msp
MSI (s) (CC:54) [13:28:52:013]: MainEngineThread is returning 1642

My tries
=====

It seems I’am the only one on this planet who have this problem … 🙂 Cause an extensive google/DuckDuckGo search don’t bring any entries or useful help about that issue.

I considered the following recommendation (https://support.microsoft.com/en-us/help/3062831/entsso-experiences-a-memory-leak-after-you-apply-hotfix-3000847) without having success:

– 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.
I tried to install the older Microsoft hotfix KB3000847 and than the actual KB3062831, but the installation of KB3000847 failed with the same error message.

So I tried to find out the version of our sso service on the BizTalk server (Master secret server):
– In the SSO Administration tool the version 9.0.2096.0 is displayed.

– The file- and productversions of the SSO files in directory C:\Program Files\Common Files\Enterprise Single Sign-On are as follows:
* Infocache.dll
==> File- and Product-Version 9.0.2096.0
* Ssoss.dll ==> File- and Product-Version 9.0.2096.0
* Ssoconfigom.dll
==> File- and Product-Version 9.0.2096.0

I searched the registry about the sso versions and I found a weird entry in the Wow6432Node:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ENTSSO]
—————————————————————————————–
“Server”=”9.0.2145.0”
“ConfigFrameworkHelperPath”=”C:\\Program Files\\Common Files\\Enterprise Single Sign-On\\Win32\\ConfigFrameworkHelper.dll”
“Administration”=”9.0.2145.0”

The entry in the 64bit section is the version I expected:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ENTSSO]
———————————————————————
“InstallPath”=”C:\\Program Files\\Common Files\\Enterprise Single Sign-On\\”
“ProductCode”=”{F89B22BC-2768-4237-B300-5CFA52D9AC84}”
“ProductName”=”Microsoft Enterprise Single Sign-On”
“ProductLanguage”=”1031”
“ProductVersion”=”9.0.2096.0”

My suspicion
========

Could this be the problem of the Windows installer, that he found different sso versions in my registry and: why there are different versions in my registry … :-)??

When I installed the BizTalk Runtime and the CUs I started with CU5 and then CU7 and CU8. Could this be the problem, that the hotfix expected an earlier CU version like CU4, CU3, …?

Can anyone help me? Thanks a lot in advance for your answer!

Best Regards,
Alexander