locked
Exchange Server 2013 CU update fail from CU13 to CU22 RRS feed

  • Question

  • We want to update our exchange mailbox server from CU13 to CU20. We are facing below error:

    Error:
    The following error was generated when "$error.Clear(); 
        initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
     

    " was run: "System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateOrMoveEWPGroup(ADGroup ewp, ADOrganizationalUnit usgContainer)
       at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage taskStage, Action initFunc, Action mainFunc, Action completeFunc)
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()".

    We have 2 mailbox and a EDGE server in our environment. We have found that in mailbox 1, Exchange Server Service Host Service is not starting. It is showing an error 1067: The Process terminated unexpectedly.

    Saturday, June 13, 2020 6:49 PM

All replies

  • Hi,

    did you run schema update and organization preparation before starting the install? If not, do that and try again.

    What have you planned in regard to .NET framework versions? Even if you go the unsupported route and do the upgrade in one step, you should probably update the framework first. 


    Evgenij Smirnov

    http://evgenij.smirnov.de

    Saturday, June 13, 2020 7:02 PM
  • I updated .NET and run schema update and organization preparation. But no luck.
    Sunday, June 14, 2020 3:20 AM
  • Hi Rony,

    According to the error information you provided, this issue is related to Exchange Universal Groups.
    Please check whether the Exchange Universal Groups group is under the root domain as shown below.

    There is a similar case you could refer to:Organization Preparation Failes.

    Regards,

    Lucas Liu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, June 15, 2020 8:35 AM
  • Hi Rony,

    I am writing here to confirm with you how thing going now? If the above suggestion helps, please be free to mark it as an answer for helping more people.

    Thanks for your understanding.

    Regards,

    Lucas Liu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, June 18, 2020 9:53 AM
  • Hi Liu,

     Exchange Universal Groups group is already under the root domain. This issue is not solved yet. Do you have any other suggestion on this issue?

    Best Regards,

    Rony

    Tuesday, June 23, 2020 12:42 PM
  • Check services.  Make sure all exchange related services are not disabled.  Re-run the CU install if you find disabled services.  Make sure the CU upgrade is run from an elevated CMD prompt and not powershell or a GUI

    Being part of a DAG group, you'll definitely need to run the AD preps on a domain controller with .net 4.8 installed first.

    CU13 to 20 is a huge gap, bound to cause issues.  Make sure .Net 4.8 is installed on all servers and the latest VC runtimes.  Try dpaulson45's healthchecker to see if the base OS is ready for an Exchange install.

    Wednesday, June 24, 2020 4:25 AM
  • Hi Rony,

    According to the error information, I think your security group is missing some important role groups. The following screenshot is the security group in my environment. If it is missing in your environment or some of them were removed before, please add it to the security group.

    In addition, I agree with gettnmorebetter.

    Please check that your system and prerequisites are complete.

    For more information you could refer to:Exchange 2013 prerequisites and Exchange 2013 system requirements.

    Regards,

    Lucas Liu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, June 24, 2020 10:30 AM
  • Hi Rony,

    I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

    Thanks for your understanding.

    Regards,

    Lucas Liu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, June 30, 2020 8:39 AM