/build/static/layout/Breadcrumb_cap_w.png
09/17/2018 192 views
After uninstalling Microfocus Reflection 14.1 on some clients it will now no longer reinstall and now will only install on a per user basis which the software is not designed to run as.

Some key lines in the logs are below - 

MSI (s) (38:30) [06:19:24:016]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-user.
MSI (s) (38:30) [06:19:24:016]: PROPERTY CHANGE: Deleting ALLUSERS property. Its current value is '2'.
MSI (s) (38:30) [06:19:24:016]: Product {DDC418E9-C130-4726-A956-17720BDB0EF7} is admin assigned: LocalSystem owns the publish key.
MSI (s) (38:30) [06:19:24:016]: Product {DDC418E9-C130-4726-A956-17720BDB0EF7} is managed.

I have trawled through the registry for related keys with no luck.






2 Comments   [ + ] Show comments

Comments

  • I had a similar issue with a different software package. I was only able to resolve it through the publisher. I would contact Microfocus directly.
    • Yeah I have engaged MicroFocus but they are stumped as the issue seems to lie in our specific upgrade scenario and is very much deep down in Windows Installer technology.
  • The line that caught my eye is:

    "Deleting ALLUSERS property. Its current value is '2'."

    If you can set this value to "" (an empty string), the software should install in the 'per-machine' context. I found this article that might explain better: https://docs.microsoft.com/en-us/windows/desktop/msi/allusers
    • Actually setting "this value to "" (an empty string)" causes a per-user installation :) ALLUSERS=1 means a per-machine installation.

      You can try to find a copy of the old MsiZAP and perform a cleanup of the Windows Installer registry keys for this particular product code ({DDC418E9-C130-4726-A956-17720BDB0EF7}) and remove the Application files and registry keys manually or via script.

      If this does not help, you can try to dig manually through the registry and find all keys containing "DDC418E9" (first part of the MSI GUID) or "9E814CDD" (first part of the compressed GUID), but MsiZap should do this automatically...
      Here are the Windows Installer keys you should look into:
      HKEY_CLASSES_ROOT\Installer\Products\9E814CDD....
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9E814CDD....
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-<Users'sSID>\Products\9E814CDD....
      • How did you find the "compressed GUID"? UPDATE: Oh it's the MSI GUID backwards...interesting to know.

        SO, I revisited MSIZAP and determined that I was actually running the commandline wrong! I was using TWA! which only updates the ACL on the registry and does not actually delete.

All Answers

1
Fixed using MSIZAP command - 

“MsiZap.exe TW!{DDC418E9-C130-4726-A956-17720BDB0EF7}”

Answered 09/19/2018 by: Davooo
Orange Belt