Jul 14 2021 04:27 AM - edited Jul 14 2021 04:41 AM
ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1]
Microsoft.Exchange.Diagnostics.ExAssert.AssertInternal(String formatString, Object[] parameters) +241
Microsoft.Exchange.Clients.Common.HmacProvider.GetCertificates() +478
Microsoft.Exchange.Clients.Common.HmacProvider.GetHmacProvider() +143
Microsoft.Exchange.Clients.Common.HmacProvider.ComputeHmac(Byte[][] messageArrays) +16
Microsoft.Exchange.HttpProxy.FbaModule.SetCadataCookies(HttpApplication httpApplication) +826
Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.HandleFbaFormPost(BackEndServer backEndServer) +2776
Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.ShouldContinueProxy() +20
Microsoft.Exchange.HttpProxy.ProxyRequestHandler.BeginProxyRequestOrRecalculate() +229
Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon) +1379
Microsoft.Exchange.HttpProxy.<>c__DisplayClass3f.<OnCalculateTargetBackEndCompleted>b__3e() +311
Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +35
Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate, LastChanceExceptionHandler exceptionHandler) +121
Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(MethodDelegate method) +69
[AggregateException: One or more errors occurred.]
Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result) +416
System.Web.CallHandlerExecutionStep.InvokeEndHandler(IAsyncResult ar) +231
System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +172
Oct 20 2021 12:15 AM
Oct 22 2021 10:22 AM - edited Oct 22 2021 10:23 AM
Ran into the same issue with the October update. In our case, the Exchange Server Auth Cert was not expired, but it was never properly activated and published. The posted solution worked like a charm without any delays.
Nov 11 2021 03:35 AM
Nov 11 2021 06:16 AM
Nov 12 2021 02:04 AM
Nov 12 2021 03:46 AM
Dec 10 2021 10:09 AM
I did the renewal process, as my Auth cert was expired.
For me both OWA and ECP are not working.
After doing everything, it still doesn't work.
I suspect I need to wait 2 hours until GMT "reaches" my local timezone.
From the other posts I suspect that certificate checking is done in GMT and not the local timezone.
Dec 10 2021 10:53 AM
Jan 04 2022 11:37 AM
Jan 16 2022 10:31 AM
Feb 03 2022 06:55 AM
My certificate was valid till 2027 but my Windows 2019 Core server did updates (2 Feb 2022) and rebooted and after the reboot ecp and owa was broken. In the event log, i could see constant info messages to say that all the exchange items were either missing or corrupt. To fix this, i ran the commands to create a new OAuth certificate, removed the old one and then rebooted. I then re-ran the CU11 security update from January 2022 and rebooted again. It took a while but Exchange 2019 was happy again and both ecp and owa working fine. (Edward van Biljon - Office Apps & Services MVP)
Mar 01 2022 01:21 PM
hi, as you used you old CERT Thumbprint did this save you running the Hybrid Configuration Wizard again ? @SpadgingtonBear
Mar 24 2022 08:58 AM
Apr 19 2022 02:11 AM
Hi @Asterofus may you please share the working document for the link you provided here it doesn`t seem to work and after reading this conversation I think it`s what I need for my problem today. Thanks in advance.
Apr 29 2024 05:51 PM
May 01 2024 11:36 PM
installed exchange 2019 c11 error re certificate error.