UserA installs product
UserB upgrades product (that UserA installed) but gets the following error if the environment variables TEMP/TMP are different than that of UserA
This snip-it of the failure is a part of the uninstall of the current product (from UserA) before the install of the new version (order is set to uninstall old first, then install new version)
Code: Select all
MSI (s) (9C:84) [19:00:52:897]: Doing action: InstallInitialize
Action start 19:00:52: InstallInitialize.
MSI (s) (9C:84) [19:00:52:928]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (9C:84) [19:00:52:928]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (9C:84) [19:00:52:943]: BeginTransaction: Locking Server
MSI (s) (9C:84) [19:00:52:943]: SRSetRestorePoint skipped for this transaction.
MSI (s) (9C:84) [19:00:52:959]: Server not locked: locking for product {GUID-HERE}
MSI (s) (9C:84) [19:00:52:975]: Note: 1: 2203 2: c:\Windows\Installer\a44326bf.ipi 3: -2147287037
MSI (s) (9C:84) [19:00:52:975]: Product: ScriptPro Secure Payment Service -- Error 2203. Database: c:\Windows\Installer\a44326bf.ipi. Cannot open database file. System error -2147287037.
Action ended 19:00:52: InstallInitialize. Return value 3.
Action ended 19:00:52: INSTALL. Return value 3.In researching I found a few other items from other areas that cause this that I have ruled out :
Anti-virus getting in the way -- not our case here
SQL Server has a KB about not being able to install with a space in TEMP/TMP -- not our case here
TEMP/TMP arent being translated to proper paths (ie : %UserProfile% doesnt translate to C:\Users\{youruser}) -- not the case here
There are a couple of temporary files in the installer (set to be placed in Windows Volume -> Temporary)
No special launch conditions / pre-requisites
There should not be any privilege issues (UserB is administrator, as is UserA)
No special upgrade rules
I am stumped...
FOLLOW US
Get the latest news in Application Packaging