Upgrade causes *.ipi database error - Advanced Installer Community
korr
Posts: 48
Joined: Tue Sep 09, 2014 3:13 pm

Upgrade causes *.ipi database error

We have ran into an interesting error case, the scenario is as follows :
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.
This happens consistently across multiple machines (though I haven't tested multiple products), installation type is per-machine, single msi (no bootstrap exe).

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...
korr
Posts: 48
Joined: Tue Sep 09, 2014 3:13 pm

Re: Upgrade causes *.ipi database error

The issue is with temporary files, I ran a couple more tests :
Blank MSI (just a registry value) upgrades no problem
Temporary File MSI (same registry value as above + random temporary file in Windows Volume -> Temporary) fails with same result as noted previously

/e : Probably safe to assume that the "Windows Volume -> Temporary" is misleading as being directed to C:\Windows\Temp and is actually environment variable for TEMP/TMP ?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Upgrade causes *.ipi database error

Hello,

I've tested the installation scenario, but I cannot replicate the issue. Can you please isolate this in a small buildable sample (AIPs + their referenced files) and send it us alongside a detailed step by step test case which we can follow?

Also, please let us know on which Windows version did you replicate the issue.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
korr
Posts: 48
Joined: Tue Sep 09, 2014 3:13 pm

Re: Upgrade causes *.ipi database error

Sent, thanks!
korr
Posts: 48
Joined: Tue Sep 09, 2014 3:13 pm

Re: Upgrade causes *.ipi database error

I may have forgotten the OS... but Window Server 2008 R2
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Upgrade causes *.ipi database error

Hello,

I've tested your sent sample on a Windows Server 2008 R2 machine, but everything installed just fine. I've used two admin users with the following temp locations:

Code: Select all

C:\Users\CaphyonA\AppData\Local\Temp
C:\Users\CaphyonB\AppData\Local\Temp
Can you please retest the scenario on multiple Windows Server 2008 R2 machine and see if the behavior consistently replicates?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
korr
Posts: 48
Joined: Tue Sep 09, 2014 3:13 pm

Re: Upgrade causes *.ipi database error

Had this happen at several production sites, recreated it in-house on multiple machines as well.


Taking an MSI with a temporary file located into "Windows Volume" -> "Temporary"
UserA installs the MSI
UserB _upgrades_ that same MSI (in a non-interactive session, for testing I had used runas, our production sites use a different method)

This "ipi" database error occurs consistently, even on a clean OS.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Upgrade causes *.ipi database error

Hello Kevin,

I'm very sorry for this, but I am unable to replicate the error. There must me something else specific only to your Server 2008 machines. I even tested this scenario with domain Administrators users. But the issue doesn't replicates neither with domain nor with local user account.

Here is the full test case I used:
1. log in under "CaphyonA" user account
2. run the following command:

Code: Select all

runas /user:CaphyonA cmd
3. run the following command:

Code: Select all

runas /user:CaphyonB cmd
4. in the CaphyonA cmd windows launched the following command:

Code: Select all

msiexec /i <pathToMsi V1>
5. in the CaphyonB cmd windows launched the following command:

Code: Select all

msiexec /i <pathToMsi V2>
If you have an antivirus software on your test machines, can you please turn off during this test and see if this helps? Also, for testing purposes can you add "Everyone -> Full Control" permissions on the non-accessible TEMP folder and see if this helps? Also, you may take a look on "Error 2203. An internal error occurred." MSDN article debating a similar issue.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
korr
Posts: 48
Joined: Tue Sep 09, 2014 3:13 pm

Re: Upgrade causes *.ipi database error

I am working to get a fresh (as opposed to just 'clean') install of 2008 R2 on a VM to do more testing. I will report back with what I can find.

Thanks for the article link, I will look into that as well.

Return to “Common Problems”