Skip to Content
0
Sep 14, 2023 at 11:58 AM

BI 4.2 SP9 Patch 16 installation does not work, and corrupted system

310 Views Last edit Sep 15, 2023 at 12:04 PM 2 rev

Today I attempted to install BI 4.2 SP9 Patch 16, which was only released this week, on an existing BI 4.2 SP9 Patch 14 system, running Windows Server 2016. This server has been patched several times before with no issues.

I ran the executable. The files were extracted without issue, the wizard ran, default options were selected, and the installation began. It failed with the message "Failed to update cache for execution". I've never seen this particular message before; I followed the advice in SAP Note 2091076.

The following was found in setupengine.log:

09:49:53.430 Error: Could not move temp dest folder to dest folder.
09:49:53.430 Error: Temp dest folder: D:\BI4\InstallData\tmp\product.boe64one.patch-4.2.9.16-core-32
09:49:53.430 Error: Dest folder: D:\BI4\InstallData\InstallCache\product.boe64one.patch-4.2.9.16-core-32\14.2.9.4691\

So, as per the advice, I created the subfolder 14.2.9.4691 in the "product.boe64one.patch-4.2.9.16-core-32" folder.I then ran the installation process again. This time it got through the "caching deployment units" stage, stopped Tomcat, stopped the SIA, and set about uninstalling the existing version.I came back and looked a short while later, and the process appeared to be near the end, far too quickly. I noted that there was no SIA, no web applications in tomcat (though they were in tomcat.old), and there was an error message hidden behind the installation dialog:
"The set of DUs marked as installed does not match the set of DUs in the target install state".The only SAP note I can find with this error is 1838662, relating to the same error occurring many years ago with Crystal Server 2011. I followed the same principle, finding an sqlite database browser, removing the last row (I had to move the database to a different folder that wasn't read only to achieve this), and then tried running the installation wizard again. On doing so, it asked for the licence key and destination folder of the new installation. At that point, I quit fearing more damage, and have requested that the server is restored from a snapshot.I have done hundreds of installations, upgrades and patches in the past, it's not a difficult process.

EDIT: I've now attempted to run Patch 16 on another system (this one was previously on 4.2 SP7) and it appears to have completed successfully with no issues.

This clearly shows (a) the importance of having snapshots to revert to, and (b) that sometimes, it seems a system just doesn't want to upgrade. Very odd! I'm not looking for any further answers here, looks like it is just one of those things.