While applying a cumulative update I ran across the following error.
Warning: An unexpected error has occurred and a Watson dump is being generated: Could not find a part of the path 'C:\Windows\Temp\ExchangeSetup\bin\EnterpriseServiceEndpointsConfig.xml'.
The Exchange setup log essentially repeated this same error, without any additional clues. The C:\Windows\Temp\ExchangeSetup\ folder is a staging area used by setup to unpack temporary files. These files are copied to this temporary location during the ‘Initializing Setup’ and ‘Copying Files’ steps.
When navigating to this folder it became apparent that not only was the file in question missing but the entire parent folder too.
Comparing this temp folder to a server whose cumulative update applied successfully we spotted even more missing folders. The screenshot below is what the unpacked temporary setup folder should look like.
It’s unsure what caused this. Immediate suspicion could indicate an antivirus solution. However, we had completely unloaded the antivirus solution from memory prior to the start of setup.
Oddly running set up a second time, and allowing the temporary files to unpack again, fixed the issue. The folders all appeared and the cumulative update finished without incident.
This error is still a mystery to us. However, it seems simply rerunning setup resolves the issue. If you have encountered this error before and identified a root cause, let us know by dropping a comment below.
Have you seen this issue before? What did you do to fix it? Drop a comment below or join the conversation on Twitter @SuperTekBoy
Ludovic says
Is it safe to delete ExchangeSetup folder ?
Robert says
Thank you. I got this error too on CU15 (missing UnpackedVersion 15.1.466.34 PostSetupVersion 15.1.466.34 from HKLM\SOFTWARE\Microsoft\ExchangeServer\V15\EdgeTransportRole)
Carl Lee says
Not sure if yours was the same as what I ran into, but when installing Ex2016 CU12, I got the same error preceded by Incomplete Installation Detected. However, I hadnt attempted the upgrade yet.
Going into the registry. I saw a mismatch between the ConfiguredVersion/UnpackedVersion and PostSetupVersion. After making the version match the installed version, the installed wasnt seen as “incomplete.” The XML error did not occur after this.
Dave says
Thank you Carl Lee!! I was missing a few of those strings on my edge server. Once I added them and set all of the values to the same version the install kicked off.
Details for anyone that runs into this.
I searched the HKLM\SOFTWARE\Microsoft\ExchangeServer key for each of the strings “ConfiguredVersion, UnpackedVersion, and PostSetupVersion”. I found one or more of those strings missing inside of a few keys; AdminTools, EdgeTransportRole, etc… I made sure all 3 strings existed where I found at least one of the strings and all values were set to the same version number.
Thanks again Carl!
David says
Great find Carl. I had the same issue applying CU17.
In my case the regkeys were present but some of the values were mismatched – Configured Version/PostSetupVersion/UnpackedVersion. After a reboot the keys all matched and the patch went through fine.
Thanks!