Troubles installing a Db2 fixpack in windows?

You’ve already experienced this or you’re in the middle of it: You played around with your test workstation and installed and uninstalled db2 client products and scrapped the installation so that no client product can be installed anymore?!

Your installation abends with an error message like [german] „Fehler bei der Anwendung von Transformen. Stellen Sie sicher, dass die angegebenen Transformpfade gültig sind.“ [Englisch] „Error applying transforms. Verify that the specified transform paths are valid.“

These suggestions may help to solve the problem!

Take a look into you db2 installation log of the client. By default, Install log is created under the install users’s %USERPROFILE%\documents\DB2LOG folder, with file eg. C:\Users\Administrator\Documents\DB2LOG\DB2-SERVER-Tue Aug 04 19_08_12 2020.log.

Inspect a corresponding DB2 technote at https://www.ibm.com/support/pages/node/6256520

In my case I’ve copied the file 1031.mst from installation directory to c:\Windows\Installer, where no *.mst file existed. But Setup still failed with a problem accessing the 1031.mst from installation directory.

We then could try db2unins executable which will clean up the environment if we have issues. If you want to remove all db2 then we run db2unins -f from same directory as the setup.exe. This will remove information from the Windows directory for Db2 and some folders. You would still want to clean up some folders that may still be left in c:\Programdata\ibm\db2\. The configuration files are kept here like the db2dsdriver.cfg or db2cli.ini files.

In my case I followed your recommendations and executed everything and also deleted the remaining files from c:\programData\IBM\DB2. db2unins ran without errors. But unfortunately „setup“ still aborted.

I also had a look in the registry, but unfortunately did not find the section „HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\FD404AD299F118B49861AED46F25D5E8\“ as mentioned in the technote.

Then I’ve tried to find MST file using the Windows Registry query Tool:

C:\WINDOWS\system32>reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData /s /f
*db2\Windows\SERVER\1031.MST
Suchvorgang abgeschlossen: 0 übereinstimmende Zeichenfolge(n) gefunden.

C:\WINDOWS\system32>reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData /s /f *.MST
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1EBC37B671047D84C9CD8754712B7D9A
DCF681D2005E3D341B91F40A415F51F4 REG_SZ C:\Program Files (x86)\Novell\ZENworks\bin\AxInterop.MSTSCLib.dll
Suchvorgang abgeschlossen: 1 übereinstimmende Zeichenfolge(n) gefunden.

Then Windows Registry look as here there is some left overs.

Check „DB2 Windows Registry Clean-up“ section in link https://www.ibm.com/support/pages/uninstalling-and-removing-db2-windows

Remove as much as you can for removing some registries. But you would need {product code}. The {product code} can be located from the Windows registry under one of the following locations depending if you have a single or multiple product installation:

HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\\CurrentVersion
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\InstalledCopies\\\CurrentVersion

As you have removed above path, If you have another installation of this very version in some different env. please check the product code from there.

The {registry key} is derived from the {product code} by reversing the first three segments of the product code. Example: ProductCode for DB2 ESE v9.7 is {814D6DAC-E778-40EC-961E-312B354D12BC}. Reverse the first 3 segments individually (CAD6D418-877E-CE04), remove all dashes, and we are left with the following key:

CAD6D418877ECE0469E113B253D421CB

Be careful not to remove registry associated with other programs.

I followed the instructions in the article. But only after I really deleted every single registry entry that had anything to do with „sqllib“ or „db2“, a new DB2 Client installation was possible again.