Failed to update Ex2013 from CU13 to CU23

Cosmic Storm 21 Reputation points
2021-03-17T14:03:58.577+00:00

We have DAG1 with two nodes Ex 2013 CU13 & DAG2 also with 2 Node Ex 2013 CU13 all hosted on Windows 2012 R2.

We successfully updated the two nodes in DAG 1 from Ex 2013 CU13 to CU23.

But while updating the Node1 in DAG2, we encountered the following error during 3/15 progress stage of the GUI wizard.
" Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. The installation source for this product is not available. Verify that the source exists and that you can access it. Error code is 1612."

With this error the node is stuck in Maintenance mode. We cannot Set ServerComponentState ServerWideOffline to Active.
The command "Set-ServerComponentState EXNode12 -Component ServerWideOffline -State Active -Requester Maintenance" executes without any error but the state of the component does not change to Active.

Help much appreciated.

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,345 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eric Yin-MSFT 4,386 Reputation points
    2021-03-18T02:21:11.247+00:00

    Hi
    It might result from an old package, try the following steps:
    Searched for GUID "4934d1ea-be46-48b1-8847-f1af20e892c1" in registry, took backup of Key and deleted IT key from the location.
    Ran MsiExec.exe/X{ 4934d1ea-be46-48b1-8847-f1af20e892c1 } to uninstalls the package.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Cosmic Storm 21 Reputation points
    2021-03-18T09:11:00.457+00:00

    EricYin-MSFT, thanks for your revert.

    I tried your suggestion. It did not help directly but gave me a cue to how i could overcome the issue i was facing.

    Ultimately it boiled down to manually replacing some file the setup prompted & /or pointing to the path of CU13 extract during the update to Ex2013 CU23.