Exchange 2016 CU6 Released


Exchange 2016 CU6 has been released to the Microsoft download centre!  Exchange 2016 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously.    CUs are a complete installation of Exchange 2016 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 has the same servicing methodology.

Download Exchange 2016 CU6

This is build 15.01.1034.026 of Exchange 2016 and the update is helpfully named ExchangeServer2016-x64-CU6.iso which allows us to easily identify the update.  Details for the release are contained in KB 4012108.

.NET Framework 4.7 is not supported at the time of writing.

No Exchange 2010 updates were released today since Exchange 2010 is in extended support.  Updates will be released as per the extended support lifecycle policy.

Exchange 2007 is no longer supported, updates are not provided once a product has exited out of extended support.

Updates Of Particular Note

CU6 contains the latest time zone updates

There  is now improved support for TLS 1.2.  TLS 1.0 and 1.1 should not be disabled at this time.

As announced in the Exchange 2016 CU5 release post the .NET framework requirement has changed.  Exchange 2016 CU5 onwards require .NET framework 4.6.2.  Please see Exchange 2013 CU16 and Exchange 2016 CU5 .NET Framework Requirement for more details.

Two major features were added to Exchange 2016 with the CU6 release: Sent Items Behaviour Control and Original Folder Item Recovery.  The latter is a feature which has been requested for many, many years.  Admins, rejoice!!

Issues Resolved

KB4024658 FIX: The EAS web.config file is not updated on the CAFE server during a build-to-build upgrade

KB4024654 POP/IMAP clients can't log on with NTLM when Alias and SamAccountName are different in Exchange Server 2016

KB4024653 Active Monitoring probes fail when you use a new accepted domain as the default domain in Exchange Server 2016

KB4024652 Repeated IMAP SEARCH BODY requests may not return newly delivered messages in Exchange Server

KB4024651 The "MessageRetrievalMimeFormat" setting isn't honored for plain text-only email messages in IMAP in Exchange Server

KB4024650 Emoji is displayed as question marks in iOS clients in an Exchange Server environment

KB4024649 The Read or Unread flag isn't synchronized correctly after you turn off an ActiveSync device overnight in Exchange Server

KB4024648 FIX: A new contact created in OWA may be merged into an existing contact on Exchange Server 2016

Some Items For Consideration

Exchange 2016 follows the same servicing paradigm for Exchange 2013 which was previously discussed on the blog.  The CU package can be used to perform a new installation, or to upgrade an existing Exchange Server 2016 installation to this CU.  Cumulative Updates are well, cumulative.  What else can I say…

For customers with a hybrid Exchange deployment, must keep their on-premises Exchange servers updated to the latest update or the one immediately prior ( N or N-1).

  • Test the CU in a lab which is representative of your environment
  • Review this post to also factor in AD preparation which is to be done ahead of installing the CU onto the first Exchange server
  • Follow your organisation’s change management process, and factor the approval time into your change request
  • Provide appropriate notifications as per your process.  This may be to IT teams, or to end users.
  • After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2016. If you uninstall this cumulative update package, Exchange 2016 is removed from the server.
  • Place the server into SCOM maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
  • Place the server into Exchange maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
  • I personally like to restart prior to installing CU.  This helps identifies if an issue was due to the CU or happened in this prior restart, and also completes any pending file rename operations.  3rd party AV products are often guilty of this
  • Restart the server after installing the CU
  • Ensure that all the relevant services are running
  • Ensure that event logs are clean, with no errors
  • Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment.  This includes archive, backup, mobility and management services.
  • Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application.  FIM and 3rd party user provisioning solutions are examples of the latter.
  • Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed.  See KB981474.
  • Disable file system antivirus prior to installing. Do this through the appropriate console.  Typically this will be a central admin console, not the local machine.
  • Verify file system antivirus is actually disabled
  • Once server has been restarted, re-enable file system antivirus.
  • Note that customised configuration files are overwritten on installation.  Make sure you have any changes fully documented!
  • CU6 does contain new AD Schema updates for your organisation.

Please enjoy the update responsibly!

What do I mean by that?  Well, you need to ensure that you are fully informed about the caveats with the CU  and are aware of all of the changes that it will make within your environment.  Additionally you will need to test the CU your lab which is representative of your production environment.

Cheers,

Rhoderick

Comments (73)

  1. Steve says:

    Bottom or article says “CU5 does contain new AD Schema updates for your organisation.” but this is CU6. I assume no AD Schema updates for CU6?

    1. CU6 does contain schema updates – corrected the typo!

      Cheers,
      Rhoderick

      1. Evan Vincent says:

        Hi Rhoderick,

        Do you know what the schema updates are in CU6 or where I could find them?

        1. Bhaskar says:

          Apparently No Schema updates only the version number got increased. All Schema updates were pulled from CU6 and will include in the CU7 release. With that said because of the Schema version increment, you still have to run through the Schema Update/AD Prep.

  2. Christian Friedel-Jain says:

    Hello,
    What about the email address policy error from Exchange 2016 CU5? Is this error now solved?

    Regards
    Christian

      1. Christian Friedel-Jain says:

        Hello Rhoderick,
        yes that’s it. Thank you 🙂

        Regards
        Christian

  3. Ram says:

    Just finished lab upgrade. No issue. Will have to test the fixes in particular recover emails back to original location.

    Ram

  4. Douglas plumley says:

    Hi Rhoderick,

    What schema updates are made in CU6? The following URL still says “no schema updates since CU4…”

    https://technet.microsoft.com/en-us/library/bb738144(v=exchg.160).aspx

    Thanks!

    1. TobiasMa says:

      that’s what i’m also looking for

      1. Ellen Bogen says:

        Microsoft…are you kidding? That’s a poor Information process…

  5. Mario Hangjas says:

    Just finished lab testing, all is working except for owa access. (ASP.NET Event ID 1309 event code 3005)

    1. Spohn Daniel says:

      Same problem here.
      CU6 breaks OWA! ASP.NET error in application log. (1309).
      Sais something about Security certificate is absent.
      Found out that the Exchange Server Auth Certificate is missing after the Update.
      Recreating the Cert und reassigning with Set-AuthCertificate did not improve anything.
      Had this Problem last week on a brand new installation as well as on a upgrade from CU4 to CU6.

      I think that there must be something really wrong with CU6!
      Any others out there with the same problem?

      Daniel

      1. MSchueler says:

        Hi Daniel,

        I need the CU6 update because of the ‘Umlaut’ problem described here:
        https://support.microsoft.com/en-us/help/4019534/error-when-a-mailbox-name-includes-an-umlaut-in-exchange-server-2016

        After successfully CU6 Update, OWA access is not more possible!

        IE Error message is:
        “;-) Something went wrong. We can’t get that information right now. Please try again later.”

        ECP access is possible!

        Found on application event log also “ASP.NET 4.0.30319.0” warnings with Event ID 1309 and

        Event code: 3005
        Event message: An unhandled exception has occurred.
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
        Exception information:
        Exception type: TargetInvocationException
        Exception message: Exception has been thrown by the target of an invocation.
        Encryption certificate is absent
        at Microsoft.Exchange.Security.Authentication.Utility.GetCertificates() …

        Certificates are present and valid. Cert replacement does not fix the problem.

        Has anyone a solution or is it already a bug? 🙁

        Unfortunately I do not receive any answers from Rhoderick.

        1. Oh my. Back now after a couple or weeks of holiday, and I see this post went a bit crazy.

          Give me a few days to get back into work, and look into what I can find.

          Cheers,
          Rhoderick

          1. Dany says:

            Same problem here.
            CU6 breaks OWA me too, outlook is ok, please help me

      2. goahead says:

        hi there
        i have found out the following. changing the timezone of the machine so it matches the same time displayed on the errorpage “something went wrong”
        there was a 2 hours mismatch so i changed to a different timezone..
        and after that it worked.. what the hell….??

        1. TB_Tim says:

          goahead, you sir are a legend!

          This fixed our problem. Now do I risk changing the timezone back to normal?

  6. Hi Rhoderick
    I have a few questions for you.
    1. A while back a saw some articles on google NOT recommending installation of exchange 2016 on server 2016 OS. It was something about the IIS crashing constantly – or something related.

    What is recommended regarding installing Exchange 2016 CU6 on server 2016 with latest security updates and patches ?

    2. I´m about to start a migration from exchange 2010 SP3 -> exchange 2016 CU6 and I need to find out all clients and devices that uses smtprelay connector on the existing server ?

    Do you have a way or a tool that can help me identifying this ? (a list/log of ip-addresses, hostnames or something)

    Thanks in advance – and thank you for a good site and articles.
    BR
    Peter

  7. Peter says:

    Hi Again
    An addtional quistion is, the need for a seperate drive containing the OS Pagefile ?
    I have seen this in some guides when building a new Exchange 2016 server.

    Could anyone please reflect on this and maybe give an answer ?
    Thanks
    Peter

  8. MSchueler says:

    What exactly is changed on the schema?
    New attributes are probably not added, since I can not found any changes with the PS command?

    $ADSchemaPath = “CN=Schema,CN=Configuration,DC=contoso,DC=com”
    #
    Get-ADObject -SearchBase $ADSchemaPath -SearchScope OneLevel -Filter * -Property Name, objectClass, ObjectGUID, SchemaIDGUID, whenChanged, whenCreated | Select-Object Name, objectClass, ObjectGUID, whenChanged, whenCreated, @{name=”event”;expression={($_.whenCreated).Date.ToShortDateString()}} | Sort-Object whenCreated
    #

  9. Spohn Daniel says:

    Same problem here.
    CU6 breaks OWA! ASP.NET error in application log. (1309).
    Sais something about Security certificate is absent.
    Found out that the Exchange Server Auth Certificate is missing after the Update.
    Recreating the Cert und reassigning with Set-AuthCertificate did not improve anything.
    Had this Problem last week on a brand new installation as well as on a upgrade from CU4 to CU6.

    I think that there must be something really wrong with CU6!
    Any others out there with the same problem?

    Daniel

    1. Morten Moger says:

      Hi Daniel, could this fix t ‘1309 ASP.NET error’ problem ?
      ://support.microsoft.com/en-us/help/3099532/event-id-1309-and-you-can-t-access-owa-and-ecp-after-you-install-excha

      rgds Morty

      1. Daniel Spohn says:

        Hi Morton,
        thanks for your reply.
        I have checked that already. web.config exists and is alright.
        Tried also to copy it from the mention location (overwriting the existing one) but that did not help either.

        Regards
        Daniel

    2. MSchueler says:

      Hi Daniel,

      the (ASP.NET Event ID 1309 event code 3005) OWA Problem could be solved, if you check for the “OAuth Certificate” with friendly name “Microsoft Exchange Server Auth Certificate” and creates them again if is not present!?

      Check for Event Log Warnings:

      “MSExchange OAuth” mit der Event-ID 2004
      “Unable to find the certificate with thumbprint xxxxxxxxxxxxxxx in the current computer or the certificate is missing private key. The certificate is needed to sign the outgoing token.”

      See here (https://social.technet.microsoft.com/wiki/contents/articles/34914.exchange-troubleshooting-federation-or-auth-certificate-not-found.aspx)

      Apparently the Exchange 2016 CU6 update now checks for the existence of the certificate!?!

      After these changes OWA works and “AlertValue” for “HealthSet” – “OWA\OwaTooManyWebAppStartsMonitor” is now “Healthy” again.

      “Get-ServerHealth –Identity $env:computername -HealthSet OWA | ft -AutoSize -Wrap”

      All a nice week yet.

      1. Corey says:

        Thanks for this! I’ve been working on this since like June 30th or something, and the Set-AuthConfig Certificate stuff ended up being the answer. I imagine there are going to be a fair amount of angry people out there if this CU breaks their Exchange though.

  10. Spohn Daniel says:

    Here is the complete error message:

    Event code: 3005
    Event message: Es ist eine unbehandelte Ausnahme aufgetreten.
    Event time: 10.07.2017 12:55:16
    Event time (UTC): 10.07.2017 10:55:16
    Event ID: 247fec0a1fc74c1c87ccc08be013044c
    Event sequence: 2
    Event occurrence: 1
    Event detail code: 0

    Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-925-131441577093070328
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: EX2016

    Process information:
    Process ID: 11052
    Process name: w3wp.exe
    Account name: NT-AUTORITÄT\SYSTEM

    Exception information:
    Exception type: TargetInvocationException
    Exception message: Ein Aufrufziel hat einen Ausnahmefehler verursacht.
    bei System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    bei System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    bei Owin.Loader.DefaultLoader.c__DisplayClass12.b__b(IAppBuilder builder)
    bei Owin.Loader.DefaultLoader.c__DisplayClass1.b__0(IAppBuilder builder)
    bei Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup)
    bei Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup)
    bei Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
    bei System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
    bei Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context)
    bei System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
    bei System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
    bei System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
    bei System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

    Encryption certificate is absent
    bei Microsoft.Exchange.Security.Authentication.Utility.GetCertificates()
    bei Microsoft.Exchange.Clients.Owa2.Server.Core.notifications.SignalR.SignalRStartup.Configuration(IAppBuilder app)

    Request information:
    Request URL: https://localhost:444/owa/exhealth.check
    Request path: /owa/exhealth.check
    User host address: ::1
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: NT-AUTORITÄT\SYSTEM

    Thread information:
    Thread ID: 20
    Thread account name: NT-AUTORITÄT\SYSTEM
    Is impersonating: False
    Stack trace: bei System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
    bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
    bei System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    bei Owin.Loader.DefaultLoader.c__DisplayClass12.b__b(IAppBuilder builder)
    bei Owin.Loader.DefaultLoader.c__DisplayClass1.b__0(IAppBuilder builder)
    bei Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup)
    bei Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup)
    bei Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
    bei System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
    bei Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context)
    bei System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
    bei System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
    bei System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
    bei System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

    Custom event details:

    1. Morten Moger says:

      oboy, this is .net is waay above my nut <: ) -guess recreate thy owa/ecp vdir did'nt solve it either ?
      it's 'scared' me to stay @ cu4 for a while longer..
      -cheers morty

      1. Daniel Spohn says:

        Hi morty,
        recreating OWA / ECP virtual directories did not fix the issue.
        We even did a complete uninstall an reinstall of the exchange server. No luck.
        Finally we build up the domain from scratch (only 20 Users) and installed CU5 without any problems!
        This really sucks!

        1. MSchueler says:

          Hi Morton / Daniel,

          can confirm…

          Recreating the “SharedWebConfig.config” files (OWA + ECP) with “DependentAssemblyGenerator.exe” (https://support.microsoft.com/en-us/help/3099532) did not resolve the OWA issue!
          ECP works.

          A new Exchange environment or a new Excahnge server, I think is not appropriate.
          You always run from one problem to the other.

  11. Despringre Olivier says:

    Hello

    I just had the same problem as you, with a fresh installation of Exchange Server 2016 with CU6.

    OWA Breaks…….. ==> Resolution, I juste tried to reset from the ECP the OWA Virtual Directory, and it’s now OK

    Tried This

    1. Axel Duez says:

      Hello,
      I had the same problem, OWA and ECP breaks. It was both a problem of certificate deleted for the ssl part and a probleme with the authorizations of the virtual directories. You need to check that the backend ecp /Owa have the correct ones and default web site as well.

      1. Leacho says:

        Are you able to describe how you worked through these steps please? It seems that a lot of people are having this issue following the update to CU6

        1. Despringre Olivier says:

          I juste have done a reset in the control panel of the OWA Virtual Directory

          Best Regards

          Olivier

          1. Leacho says:

            Have tried the OWA reset – but to no avail – looks like the certificate trail might be my next port of call. I’m stuck without it!

          2. Jan Haarsma says:

            Are all the Server Components running? “get-servercomponentstate”

          3. Leacho says:

            Hi, Everything is running except for ForwardSyncDaemon and ProvisioningRPS.

            I have also re-done the local self-signed certificates, rebuilt the OWA virtual directory and run an iisreset /noforce – but I am still seeing this error when trying to log onto OWA:

            Encryption certificate is absent
            bei Microsoft.Exchange.Security.Authentication.Utility.GetCertificates()
            bei Microsoft.Exchange.Clients.Owa2.Server.Core.notifications.SignalR.SignalRStartup.Configuration(IAppBuilder app)

            Request information:
            Request URL: https://localhost:444/owa/exhealth.check
            Request path: /owa/exhealth.check
            User host address: ::1
            User:
            Is authenticated: False
            Authentication Type:
            Thread account name: NT-AUTHORITY\SYSTEM

            ECP is working fine.

            Thanks

          4. Daniel Spohn says:

            The problem has been solved.
            We had opened a support case at microsoft.
            They troubleshooted with one of our employees 2 times. Without a solution.
            After an internal escalation at microsoft they found the solution.
            The web.config file gets somehow corrupted or gets wrong entries.

            I have no further details so far but I will check out what the exact cause was.
            I’ll keep you updated.

            Regards
            Daniel

          5. Leacho says:

            Thank you Daniel – if you could share the solution that would be amazing – thank you.

  12. Victor Lambert says:

    I don’t dare install CU6 until we feel comfortable that LaggedCopies are fixed from CU5…
    Did anyone have this issue?

    Another CU installed (CU5), another issue with Lagged Copies…
    After installing CU5 (3 weeks ago), all 14day Lagged Copies are either ReplayQueue of 0 or Unhealthy with ReplayQueue of 10Ks
    I removed one 14day LaggedCopy, deleted the dir files and recreated with 14day Lag and Pref4, wait for reseed…ReplayQueue back to 0
    Any ideas?? We got burned on CU4 with LaggedCopies going into AutoSuspend (undocumented feature of CU4)

    Thanks

  13. Igor says:

    Is there any update ?
    I have same issue. Every suggested ways not helped me. Still Event 3005 and owa not working. ECP is working fine.

    1. Maxim says:

      I have same issue. After upgrade to CU 6 from CU 5 OWA go down… but ECP work fine. When MS give fix solution for this bug!?

      1. Igor says:

        After two days it finally started working. The reason really was in OAuth certificate.

        MSchueler saggest this
        https://social.technet.microsoft.com/wiki/contents/articles/34914.exchange-troubleshooting-federation-or-auth-certificate-not-found.aspx
        And its works for me.
        But it is strange that it did not work right away, but only the next day.

      2. Maxim says:

        Problem with OWA was resolved wonderfully.
        With Event ID 1305 (ASP.NET 4.0.30319.0 …Encryption certificate is absent…) i also have Event ID 2004 MSExchange OAuth (Unable to find the certificate with thumbprint ****** in the current computer or the certificate is missing private key. The certificate is needed to sign the outgoing token.).

        Get-ServerComponentState cmdlet showed two inactive components:
        ForwardSyncDaemon
        ProvisioningRps

        cmdlet “Get-ServerHealth –Identity $env:computername -HealthSet OWA | ft -AutoSize -Wrap” showed AlertValue status of OwaTooManyWebAppStartsMonitor
        – Unhealthy

        What I have made:
        1) By this (https://social.technet.microsoft.com/wiki/contents/articles/34914.exchange-troubleshooting-federation-or-auth-certificate-not-found.aspx) was solved problem with Event ID 2004
        2) Start two inactive components:
        (Set-ServerComponentState -Component ForwardSyncDaemon -Identity EXCHANGE-SERVER -Requester Functional -State Active
        Set-ServerComponentState -Component ProvisioningRps -Identity EXCHANGE-SERVER -Requester Functional -State Active)
        3) Restart IIS services (i have two EX2016 servers in DAG)
        After about 2 hours OWA began work fine. No more Event ID 1309 and 2004. May be after restart exchange servers OWA began to work immediately.
        OwaTooManyWebAppStartsMonitor now Healthy.

        1. Leacho says:

          I can confirm that this works a treat!! Good spot! – thank you for the solution!

          1. Those two components *should* not have bearing for on-premises. They are for Office 365. Have you tried it without touching them?

            Cheers,
            Rhoderick

  14. Jeff says:

    In my lab, I was running CU5. I had some early on issues with that so I decided against pushing that in my production environment. Going from CU5 to CU6 in my lab was seemless and without issue; however, attempting to go from CU4 to CU6 in production won’t get past the pre-req check. The installer tells me I don’t have a mailbox server installed and the AD schema is not up to date.

    After reading through all these comments, I have second thoughts about trying to patch my on-prem Exchange 2016 servers. Does anyone know if you can go straight from CU4 to CU6 or if you have to install CU5 first?

    1. Daniel S says:

      You can go directly to CU6, Exchange updates are cumulative and include all previous fixes.

  15. NotThatGuy says:

    How on earth can this still be available for download? One of the most basic user facing features of the software is broken with no fix available from MSFT…

  16. RecklessR says:

    Precisely why is this still available to download? It’s obvious from the posts it’s broke.

  17. Daniel Fischer says:

    Hello after Update to Exchange 2016 CU6 i have a Problem with my Outlook Clients (2013 fully Patched)
    The free Busy Information takes a very long time and sometimes i received no Information , the same for Out of Office here i get the “server unavailable”. Before the Update to CU6 i have no Problems ! Is it possible that the support for TLS 1.2 in cU6 has something to do with that ?

    1. Daniel Fischer says:

      Now i see in the Event Log :

      EventID:1325 Source: ASP.NET 4.0.30319.0

      An unhandled exception occurred and the process was terminated.

      Application ID: /LM/W3SVC/2/ROOT/EWS

      Process ID: 35548

      Exception: System.TypeLoadException

      Message: Could not load type ‘Microsoft.Exchange.WebServices.Data.OfficeExtension’ from assembly ‘Microsoft.Exchange.WebServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
      ………

      This looks very similar to the Problem with OWA can anyone confirm the Problems with “FreeBusy/OOF” because the Error has to do with the EWS Service and “FreeBusy/OOF” also use EWS

  18. Kyle says:

    I confirm having the same issue with event IDs 2005 and 1309. OWA would present a login screen, then give me the “something went wrong” dialog instead of showing me my inbox. When looking for the above event IDs, be sure to check in the event viewer under “Windows Logs” > “Application” (I had mistakenly looked for them under “Applications and Services Logs” > “MSExchangeManagement” and found nothing relevant).

    The solution for my environment ended up being this article referenced in other comments: https://social.technet.microsoft.com/wiki/contents/articles/34914.exchange-troubleshooting-federation-or-auth-certificate-not-found.aspx

    If you have the same event IDs, follow the above guide to the letter but don’t forget to substitute any references to “*.domain.com” with your environment’s domain. Restarting the IIS service after following the above guide fixed the issue for me without requiring a reboot or down time.

    I hope this helps anyone who ends up in my shoes; it was a frustrating issue to troubleshoot following a successful cumulative update.

  19. Maxim says:

    I find new bug of CU6, may be somebody help me. When i try enable transport rule witch curently disabled (Enable-TransportRule “xxxx”) i get warning:
    WARNING: An unexpected error has occurred and a Watson dump is being generated:
    SOFTWARE\Microsoft\MSIPC\CurrentVersion not found
    SOFTWARE\Microsoft\MSIPC\CurrentVersion not found
    + CategoryInfo : NotSpecified: (:) [Enable-TransportRule], Exception
    + FullyQualifiedErrorId : System.Exception,Microsoft.Exchange.MessagingPolicies.Rules.Tasks.EnableTransportRule
    + PSComputerName : ex2016_server

    Rule does not enabling…
    Recreating rules does not fix the problem
    Someone else has encountered such a problem?

    1. Daniel Fischer says:

      Have you installed .net 4.7 ? in my case this was the reason! Uninstall 4.7 fixed the Problem with the EWS Erros ! i know this is not supported but i installed it automatically because it didnt checked the windows updated before installing 🙁 maybe in your case its the same

    2. Daniel Fischer says:

      Iam Sorry this has nothing to do with .NET but i have the same issue , but i stay in contact with MS Support if i have a solution i will tell you

      1. Maxim says:

        Ok, thank you. Waiting for…

    3. Mario says:

      Same issue here.
      We do an export import of the transport rule to get it enabled agaiin.

      1. Daniel Fischer says:

        Microsoft says they can adjust the Bug .. they say there is a Problem with a Code limitation. The Developers are working on a solution but the MS Technican has no information how long does it take .. so we have to wait for a fix or a second revision of CU6

        1. MaddiN78 says:

          Hi Daniel,
          Hopefully there will be a fix soon. Same issue here with EWS not working after CU6 upgrade. In the test lab everything worked fine.

          Cheers,
          Martin

          1. ostandal says:

            We still have problems With EWS, Out-of-Office and freebusy after upgrading to CU6. We have not installed .net 4.7. Even tried the updatecas.ps1 script with no success.
            Seems like the EWS crashes all the time:

            Log Name: Application
            Source: ASP.NET 4.0.30319.0
            Date: 28.08.2017 19.02.32
            Event ID: 1325
            Task Category: None
            Level: Error
            Keywords: Classic
            User: N/A
            Computer: taco-exc05-vm.prd.tasp.tikt.no
            Description:
            An unhandled exception occurred and the process was terminated.

            Application ID: /LM/W3SVC/2/ROOT/EWS

            Process ID: 112072

            Exception: System.TypeLoadException

            Message: Could not load type ‘Microsoft.Exchange.WebServices.Data.OfficeExtension’ from assembly ‘Microsoft.Exchange.WebServices

          2. Steve Miner says:

            This has not been fixed, we still have an open case but no progress has been made on this, our symptom is that free/busy is randomly not available or extremely slow.

  20. Daniel Spohn says:

    Hello folks,

    as promised, here is the solution for the problem from July 9th (CU6 breaks OWA). 🙂

    ——————
    Symptom:
    Customer has an Exchange 2013 and Exchange 2016, when an exchange 2016 user tries to log in to owa, he gets to the authentication screen, can be authenticated, and then gets error 500 – internal server error

    Cause:
    most probable cause is web.config file corruption

    Resolution:
    did research, all cases that I can find were pointing to corruption of web.config file under %Exchangeinstallpath%\ClientAccess\OWA , but we have already recreated this.

    Decided to recreate it with a brand new file, and I copied the contents of it, created a new web.config file using notepad and pasted it in the new file. Ran iisreset. stll no go.

    Tried to run .\updatecas.ps1 so that we can restore files in front end, if there are any stale entries of the old corrupted files.

    ran iis reset and issue was resolved.

    1. itpadla says:

      Thank you Daniel!
      It is working!

    2. Chris says:

      This is the one that fixed mine!

      Thanks 🙂

    3. Andbonom says:

      Hi . the same problem. New domain 2012 r2 + new fresh installation exch cu6.
      OWA not open.
      asp.net error
      Encryption certificate is absent

      at Microsoft.Exchange.Security.Authentication.Utility.GetCertificates()
      at Microsoft.Exchange.Clients.Owa2.Server.Core.notifications.SignalR.SignalRStartup.Configuration(IAppBuilder app)

      test with this: .\updatecas.ps1
      nothing.
      Any help pls?
      thank u

  21. Faisal678 says:

    Can’t enable transport rules (Exchange 2016 CU6)

  22. Hi Rhoderick, I´m about to plan an upgrade of Exchange 2016 CU4 to CU6.
    Besides maybe a full VMM Clone of this virtual server, what would your best suggestion and advise be, to a Fall Back plan for me, in case something goes wrong, during or after til update to Exchange 2016 CU6 ?

    I know that the CU´s updates are different from I.e. the updates for Exchange 2010. The CU´s for both Exchange 2013 and Exchange 2016 are “fresh” or completely new installations, with the Exchange configuration applied after the CU. Unfortunately I´m not able to test the update for CU6 in a test environment, so I need a fall back plan when updating this exchange server in a production setup.

    Thanks
    BR
    Peter

    1. Hi Peter,

      Consider them the same as an Exchange 2010 service pack. Some slightly different aspects, but better to think of them like that and not a RU/UR.

      Consider updating one server, leaving the other alone. Then you can monitor the updated machine to verify.

      But you really should have a lab 🙁

      Cheers,
      Rhoderick

Skip to main content