Bootstrapper Fails on Lync 2010 Front Ends

I ran into a significant issue that I found no reference to anywhere on google or bing, or even within MS internal notes.  The issue was that I couldn’t run bootstrapper.exe on many different Lync 2010 Front End servers within multiple environments.  This issue occurred on FE’s that had either CU7 or CU9 applied.  When running Step 2: Setup within the Lync Deployment Wizard the following error occurs:

bootstrapfailure

When viewing the logs the primary error was:

Error: The given key was not present in the dictionary.
▼ Details
└ Type: KeyNotFoundException
└ ▼ Stack Trace
└   at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Microsoft.Rtc.Management.Deployment.Core.MsiFeatureFactory.GetFeature(String featureName)
at Microsoft.Rtc.Internal.Tools.Bootstrapper.BootstrapperTask.RemoveUnusedFeatures(Boolean scorch)
at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action, T arg)

After much troubleshooting, logging and compare and contrast between some functional servers and non functional the failing ones appeared to have “Microsoft Lync Server 2010, Front End Server” version 4.0.7577.707 installed.

FEversion

 

The fix for this issue was to uninstall installed patches KB2982385 (and KB2982388).  From my research it appears that KB2982385 was originally released in September of 2014 and then re-released in November of 2014 to fix some bugs within it.  After first uninstalling KB2982385 and confirming that Bootstrapper.exe completed successfully, I re-installed the November release of this patch however that broke Bootstrapper.exe again for me.  Due to this, I simply kept them off and Setup was happy to run.  Some further notes on these patches can be found at: https://technet.microsoft.com/library/security/ms14-055

After removing this patch the Front End Server component version changed to 4.0.7577.203.

Hopefully this saves someone else out there a significant amount of time if you run into the same issue.

Lync on.

 

Leave a Reply