Exchange 2013 cannot upgrade from CU9 to CU23 without the CU9 install media

AWIT 106 Reputation points
2021-03-06T05:51:50.93+00:00

I have inherited an Exchange 2013 CU9 server that urgently needs to be upgraded to CU23 for obvious reasons. I have already done this to another server in the exact same scenario (this one's partner in a DAG) and no issues, however this one is prompting for the CU9 install media in order to process the "uninstalling" stage. It's looking in C:\Temp\CU9, which does not exist, and the log reports

[ERROR] 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.

The other server, which upgraded fine, does NOT apear to have had the CU9 install media anywhere on it so I can't imagine why this one in particular must have it. Is there a way to bypass this, to force CU23 to perform the removal, or a way I can get my hands on the CU9 install media?

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,333 questions
0 comments
Accepted answer
  1. AWIT 106 Reputation points
    2021-03-06T10:01:48.22+00:00

    Solution

    • I extracted ALL of the files in c:\windows\installer from the backup of another CU9 exchange server.
    • Then moved them into a folder on EXCH01 (the one with the issues).
    • With File Explorer in Details view, I added the "subject" column.
    • Going through the registry: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\<user>\Products
    • In each entry, look at the "InstallProperties" key
    • Compare the "DisplayName" to the Subject column
    • Rename the msi according to the "LocalPackage" value
    • Move the renamed file into c:\windows\installer on the afflicted computer

    Once all the MSIs were put back in place, the installer ran through. There was only one other issue where I had to manually make a "grammars" folder.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. AWIT 106 Reputation points
    2021-03-06T06:30:03.977+00:00

    Some progress - I found the registry was looking for a particular MSI file in c:\windows\installer that does not exist, which is why it's now looking for the copy in c:\temp\cu9.
    I found the equivalent copy in a backup of the other cu9 server, renamed the MSI file and copied it across and the process moved all the way up to Installing Languages.

    At which point it started asking for individual language installers... all FIFTY SIX of them.

    Now I don't know if the installer will fail because I have to somehow deal with all of them before running it again.

    0 comments