[wix-users] Wix bundle failed to upgrade

Edwin Castro egcastr at gmail.com
Fri Dec 2 01:07:52 PST 2022 

This log shows the uninstall portion of a major upgrade. I did not see
anything wrong with it. After RemoveExistingProducts completes, which is
scheduled after InstallValidate but before InstallInitialize, we see that
the Windows Installer cannot access the original msi package.

MSI (s) (20:6C) [03:08:42:692]: Determining source type
MSI (s) (20:6C) [03:08:42:692]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi 3:
-2147287037
MSI (s) (20:6C) [03:08:42:692]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi
MSI (s) (20:6C) [03:08:42:692]: SECREPAIR: Error determining package source
type
MSI (s) (20:6C) [03:08:42:692]: SECREPAIR: Cleanup the Hash Value
MSI (s) (20:6C) [03:08:42:692]: SECUREREPAIR: SecureRepair Failed. Error
code: 52456C15FB8

Note 2203 is Database: [2]. Cannot open database file. System error [3].
https://errorco.de/msi/2203/

System error -2147287037 is The path %1 could not be found.
https://errorco.de/win32/winerror-h/stg_e_pathnotfound/-2147287037/

Note 1316 is A network error occurred while attempting to read from the
file: [2]
https://errorco.de/msi/1316/

All this tells us C:\ProgramData\Package
Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi could
no longer be found in the package path.

At the beginning of the upgrade we that C:\ProgramData\Package
Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi was
found and the Windows Installer created its own cached copy
at C:\Windows\Installer\9f1a53bf.msi which it used to run from.

MSI (s) (20:6C) [03:07:28:598]: Original package ==>
C:\ProgramData\Package
Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi
MSI (s) (20:6C) [03:07:28:598]: Package we're running from ==>
C:\Windows\Installer\9f1a53bf.msi

In any case, this log ends immediately after it fails to determine the
package source type. If the upgrade is hanging at this point, then perhaps
it is prompting the user for the location of the source package. That's
just a guess though. And not the root cause of the problems here. The root
cause is whatever is deleting the source package
from C:\ProgramData\Package
Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi.

Based on the previous bundle logs we investigated, I would have to guess
something is initiating one or two uninstall of the bundle while the bundle
upgrade is still running. It is hard to guess how that is happening but I
can say it does not appear to be the bundle upgrade itself.

I would guess the upgrade is initiated by a configuration management tool
of some kind and it is that tool that is also uninstalling the bundle
before it has completed the upgrade. This is a complete guess of course as
I don't know how you are starting the upgrade nor the uninstalls. As
previously suggested, Process Monitor would be a good tool to help root
cause what is starting these uninstalls.

https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

To summarize, as best as I can tell, the problem here is not with your msi
package, nor with your bundle, but rather with some other currently unknown
process that is uninstalling the bundle while it is still installing.

Something odd about all this is that the bundle, while listed in ARP and
enumerable as a related bundle, should not be uninstallable because the
bundle install session has not completed so its registration should
indicate it is not installed yet. This is a bit of a mystery but that is
more complicated than what can be troubleshooted via mailing list. If I
were troubleshooting this in house I would want to look in the registry to
see what is there before the upgrade begins as well as capture a trace with
Process Monitor to see how the registry changes in addition to figure out
what uninstalls the bundle.

--
Edwin G. Castro



On Fri, Dec 2, 2022, 00:19 Jackie Xu <jackie.xu at teradyne.com> wrote:

> Hi Edwin,
>
>
>
> I tried to capture the failure log before it was overwrite, I upload it to:
>
>
>
>
> https://github.com/xuxiushi888/Wix-logs/blob/main/second-upgrade-success/UpgradeFaile_OasisSetup_msi.txt
>
>
>
>
>
> Best Regards,
>
>
>
> Jackie Xu
>
> Teradyne HeFei | ADC
>
> Office: +86-551-63803346
>
>
>
> *From:* Edwin Castro <egcastr at gmail.com>
> *Sent:* Friday, December 2, 2022 11:13 AM
> *To:* Jackie Xu <jackie.xu at teradyne.com>
> *Cc:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>;
> wix-users <wix-users-bounces at lists.wixtoolset.org>
> *Subject:* Re: [wix-users] Wix bundle failed to upgrade
>
>
>
> *CAUTION - EXTERNAL EMAIL: *Do not open attachments or links unless you
> recognize the sender and the content is safe.
>
> The bundle was started to upgrade. Then it was started two more times to
> uninstall the bundle while the first was still running. Check the
> timestamps of the first and last lines of the bundle logs in
> first-upgrade-fail. These were not within a single bundle install but
> rather three separate invocations of the bundle. Based on the command lines
> used for the two uninstall attempts I would guess that a human tried to
> uninstall the bundle from ARP.
>
>
>
> --
>
> Edwin G. Castro
>
>
>
> On Thu, Dec 1, 2022 at 6:25 PM Jackie Xu <jackie.xu at teradyne.com> wrote:
>
> I never expect the installers in the bundle to install concurrently, I
> think they will install one by one, right? I have three installers in the
> bundle. And you are right, the OasisSetup.msi will wait the Excel.exe
> process terminated to continue. But when the issue happened, I didn’t see
> any Excel processes. I have one machine that can reproduce this issue every
> time, which means the first-time upgrade on that machine will always fail.
> Thanks for your help, I will check more about it.
>
>
>
>
>
>
>
> Best Regards,
>
>
>
> Jackie Xu
>
> Teradyne HeFei | ADC
>
> Office: +86-551-63803346
>
>
>
> *From:* Edwin Castro <egcastr at gmail.com>
> *Sent:* Friday, December 2, 2022 10:14 AM
> *To:* Jackie Xu <jackie.xu at teradyne.com>
> *Cc:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>;
> wix-users <wix-users-bounces at lists.wixtoolset.org>
> *Subject:* Re: [wix-users] Wix bundle failed to upgrade
>
>
>
> *CAUTION - EXTERNAL EMAIL: *Do not open attachments or links unless you
> recognize the sender and the content is safe.
>
> I don't believe there's any way to stop burn from retrying in these cases.
> That said, the cases in which it retries are typically cases where retrying
> makes sense. For example, the msi install fails because another msi was in
> progress.
>
>
>
> I'd recommend never running multiple installers concurrently. Certainly
> attempting to uninstall, twice, while the install was still in progress
> caused some issues. It is just unclear if it caused all the problems.
>
>
>
> If you have processes that must be terminated for the msi to continue,
> then it is very possible that the msi was waiting for those processes to
> stop. Or perhaps the installer was waiting for user input. In any case, you
> need a reproduction to troubleshoot further.
>
>
>
> --
>
> Edwin G. Castro
>
>
>
>
>
> On Thu, Dec 1, 2022 at 6:01 PM Jackie Xu <jackie.xu at teradyne.com> wrote:
>
> Hi Edwin,
>
>
>
> Thanks for your so detail explanations. Is there any way to let it do
> *NOT* retry so that we can keep the original failed log?
>
>
>
>
>
>
>
> Best Regards,
>
>
>
> Jackie Xu
>
> Teradyne HeFei | ADC
>
> Office: +86-551-63803346
>
>
>
> *From:* Edwin Castro <egcastr at gmail.com>
> *Sent:* Friday, December 2, 2022 1:15 AM
> *To:* Jackie Xu <jackie.xu at teradyne.com>
> *Cc:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>;
> wix-users <wix-users-bounces at lists.wixtoolset.org>
> *Subject:* Re: [wix-users] Wix bundle failed to upgrade
>
>
>
> *CAUTION - EXTERNAL EMAIL: *Do not open attachments or links unless you
> recognize the sender and the content is safe.
>
> In first-upgrade-fail/Teradyne_IG-XL_Oasis_Toolset_20221031020631.log we
> see burn start to apply OasisSetup.msi at 2022-10-31T02:06:35 and fail at
> 2022-10-31T02:08:34
>
>
>
> [41B0:123C][2022-10-31T02:06:35]i301: Applying execute package:
> OasisSetup.msi, action: Install, path: C:\ProgramData\Package
> Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi,
> arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
> [41B0:123C][2022-10-31T02:08:34]e000: Error 0x80070643: Failed to install
> MSI package.
>
>
>
> Both first-upgrade-fail/Teradyne_IG-XL_Oasis_Toolset_20221031020730.log
> and first-upgrade-fail/Teradyne_IG-XL_Oasis_Toolset_20221031020731.log run
> to completion before 2022-10-31T02:08:34
>
>
>
> [4078:4114][2022-10-31T02:07:30]i001: Burn v3.11.2.4516, Windows v10.0
> (Build 19042: Service Pack 0), path: C:\ProgramData\Package
> Cache\{6ea28c67-1f07-492c-9b16-4df7c98569b9}\OasisSetup_4.1.8442_BETA.exe
> [4078:4114][2022-10-31T02:07:30]i009: Command Line:
> '"-burn.clean.room=C:\ProgramData\Package
> Cache\{6ea28c67-1f07-492c-9b16-4df7c98569b9}\OasisSetup_4.1.8442_BETA.exe"
> -burn.filehandle.attached=536 -burn.filehandle.self=552 /uninstall /quiet'
>
> ...
>
> [336C:0810][2022-10-31T02:07:31]i351: Removing cached package:
> OasisSetup.msi, from path: C:\ProgramData\Package
> Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\
>
> ...
>
> [4078:4114][2022-10-31T02:07:31]i007: Exit code: 0x0, restarting: No
>
>
>
>
>
> [4170:0020][2022-10-31T02:07:31]i001: Burn v3.11.2.4516, Windows v10.0
> (Build 19042: Service Pack 0), path: C:\ProgramData\Package
> Cache\{c6227845-13d6-4987-9d47-c3c8f384a149}\OasisSetup_4.1.8262_ALPHA.exe
> [4170:0020][2022-10-31T02:07:31]i009: Command Line:
> '"-burn.clean.room=C:\ProgramData\Package
> Cache\{c6227845-13d6-4987-9d47-c3c8f384a149}\OasisSetup_4.1.8262_ALPHA.exe"
> -burn.filehandle.attached=540 -burn.filehandle.self=556 /uninstall /quiet'
>
> ...
>
> [4170:0020][2022-10-31T02:07:52]i007: Exit code: 0x652, restarting: No
>
>
>
> These uninstall attempts ran concurrently with the upgrade attempt and
> removed OasisSetup.msi from the package cache.
>
>
>
>
>
> first-upgrade-fail/Teradyne_IG-XL_Oasis_Toolset_20221031020631.log tried
> to install OasisSetup.msi again at 2022-10-31T02:08:34 and failed
> immediately.
>
>
>
> [2468:2594][2022-10-31T02:08:34]w348: Application requested retry of
> package: OasisSetup.msi, encountered error: 0x80070643. Retrying...
> [41B0:123C][2022-10-31T02:08:37]i301: Applying execute package:
> OasisSetup.msi, action: Install, path: C:\ProgramData\Package
> Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi,
> arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
> [41B0:123C][2022-10-31T02:08:37]e000: Error 0x80070003: Failed to install
> MSI package.
>
>
>
> In
> first-upgrade-fail/Teradyne_IG-XL_Oasis_Toolset_20221031020631_000_OasisSetup.msi.log
> we see the reason is OasisSetup.msi does not exist in the package cache
>
>
>
> MSI (s) (F0:54) [02:08:37:198]: Note: 1: 2203 2: C:\ProgramData\Package
> Cache\{28C39E9E-3C2E-45A4-B938-8BB2802BBB19}v4.1.8442\OasisSetup.msi 3:
> -2147287037
>
>
>
> Burn overwrote the log file of the initial install attempt of
> OasisSetup.msi as it reuses the same log file on each attempt.
> Unfortunately we no longer have any information on how far along that
> initial attempt got before OasisSetup.msi was removed from the package
> cache.
>
>
>
> --
> Edwin G. Castro
>
>
>
> On Wed, Nov 30, 2022 at 12:27 AM Jackie Xu <jackie.xu at teradyne.com> wrote:
>
> Hi Edwin,
>
>
>
> I uploaded the logs to GitHub, here is it:
>
> https://github.com/xuxiushi888/Wix-logs [github.com]
> <https://urldefense.com/v3/__https:/github.com/xuxiushi888/Wix-logs__;!!GenOTVeOfQ!T7U6aLwFVaWjzY9p1Rs6mWFcGPT4smSKVwiz0f2wng9w7w-hyg86BVt8pF-w3L0cblpoQ3X9TLV1Q8dkcA$>
>
>
>
> Many thanks for your help.
>
>
>
>
>
> Best Regards,
>
>
>
> Jackie Xu
>
> Teradyne HeFei | ADC
>
> Office: +86-551-63803346
>
>
>
> *From:* Edwin Castro <egcastr at gmail.com>
> *Sent:* Wednesday, November 30, 2022 10:52 AM
> *To:* Jackie Xu <jackie.xu at teradyne.com>
> *Cc:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>;
> wix-users <wix-users-bounces at lists.wixtoolset.org>
> *Subject:* Re: [wix-users] Wix bundle failed to upgrade
>
>
>
> *CAUTION - EXTERNAL EMAIL: *Do not open attachments or links unless you
> recognize the sender and the content is safe.
>
> > One more comment, after the upgrade failure, I run the bundle again, now
> it can install successfully.
>
> > So when upgrade the first time, it successfully uninstall the previous
> version but failed to install.
>
> > So when run again, it worked as a brand new installation since the
> previous version already removed.
>
>
>
> I'm not following your comment.
>
>
>
> Can you upload all the installer logs to pastebin or similar? Please
> include all the logs for the initial install, the first upgrade failure,
> and the second successful upgrade.
>
>
>
> --
>
> Edwin G. Castro
>
>
>
> On Tue, Nov 29, 2022 at 6:47 PM Jackie Xu <jackie.xu at teradyne.com> wrote:
>
> Thanks, I will check it.
>
> One more comment, after the upgrade failure, I run the bundle again, now
> it can install successfully. So when upgrade the first time, it
> successfully uninstall the previous version but failed to install. So when
> run again, it worked as a brand new installation since the previous version
> already removed.
>
>
>
>
>
>
>
> Best Regards,
>
>
>
> Jackie Xu
>
> Teradyne HeFei | ADC
>
> Office: +86-551-63803346
>
>
>
> *From:* Edwin Castro <egcastr at gmail.com>
> *Sent:* Wednesday, November 30, 2022 10:45 AM
> *To:* Jackie Xu <jackie.xu at teradyne.com>
> *Cc:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>;
> wix-users <wix-users-bounces at lists.wixtoolset.org>
> *Subject:* Re: [wix-users] Wix bundle failed to upgrade
>
>
>
> *CAUTION - EXTERNAL EMAIL: *Do not open attachments or links unless you
> recognize the sender and the content is safe.
>
> MSI (s) (5C:9C) [08:37:24:416]: Note: 1: 2203 2: C:\ProgramData\Package
> Cache\{EE1C9582-FA55-4E05-9E08-036385B32255}v4.1.8426\OasisSetup.msi 3:
> -2147287037
>
>
>
> Note 2203 is Database: [2]. Cannot open database file. System error [3].
>
>
>
> REF: https://errorco.de/msi/2203/ [errorco.de]
> <https://urldefense.com/v3/__https:/errorco.de/msi/2203/__;!!GenOTVeOfQ!QfH8T7Olb5RYYloGxpPJum2Ey8eU3_422Y5QF8cG2MguyZgvdPOc7eAq3p2pr3mKcFneJhlNxkiPwsC_Pw$>
>
>
>
> System error -2147287037 is STG_E_PATHNOTFOUND
>
>
>
> REF: https://errorco.de/win32/winerror-h/stg_e_pathnotfound/-2147287037/
> [errorco.de]
> <https://urldefense.com/v3/__https:/errorco.de/win32/winerror-h/stg_e_pathnotfound/-2147287037/__;!!GenOTVeOfQ!QfH8T7Olb5RYYloGxpPJum2Ey8eU3_422Y5QF8cG2MguyZgvdPOc7eAq3p2pr3mKcFneJhlNxkimM_LcFw$>
>
>
>
> This seems to indicate C:\ProgramData\Package
> Cache\{EE1C9582-FA55-4E05-9E08-036385B32255}v4.1.8426\OasisSetup.msi does
> not exist.
>
>
>
> Your best bet is probably to use ProcMon to determine why OasisSetup.msi
> is disappearing.
>
>
>
> REF: https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
> [learn.microsoft.com]
> <https://urldefense.com/v3/__https:/learn.microsoft.com/en-us/sysinternals/downloads/procmon__;!!GenOTVeOfQ!QfH8T7Olb5RYYloGxpPJum2Ey8eU3_422Y5QF8cG2MguyZgvdPOc7eAq3p2pr3mKcFneJhlNxkg9jBJSHA$>
>
>
>
> --
>
> Edwin G. Castro
>
>
>
>
>
> On Tue, Nov 29, 2022 at 6:05 PM Jackie Xu <jackie.xu at teradyne.com> wrote:
>
> Hi Edwin,
>
>
>
> Thanks for your reply, below is the log from msi when bundle upgrade
> failed. (*Please ignore the version number mismatch* ):
>
> === Verbose logging started: 10/20/2022  8:37:24  Build type: SHIP UNICODE
> 5.00.10011.00  Calling process:
> C:\WINDOWS\Temp\{4BBC1BC9-2704-494C-BC6A-6AA36DD1957B}\.be\OasisSetup_4.1.8426_BETA.exe
> ===
>
> MSI (c) (48:E4) [08:37:24:373]: Resetting cached policy values
>
> MSI (c) (48:E4) [08:37:24:373]: Machine policy value 'Debug' is 0
>
> MSI (c) (48:E4) [08:37:24:373]: ******* RunEngine:
>
>            ******* Product: C:\ProgramData\Package
> Cache\{EE1C9582-FA55-4E05-9E08-036385B32255}v4.1.8426\OasisSetup.msi
>
>            ******* Action:
>
>            ******* CommandLine: **********
>
> MSI (c) (48:E4) [08:37:24:375]: Client-side and UI is none or basic:
> Running entire install on the server.
>
> MSI (c) (48:E4) [08:37:24:375]: Grabbed execution mutex.
>
> MSI (c) (48:E4) [08:37:24:394]: Cloaking enabled.
>
> MSI (c) (48:E4) [08:37:24:394]: Attempting to enable all disabled
> privileges before calling Install on Server
>
> MSI (c) (48:E4) [08:37:24:394]: Incrementing counter to disable shutdown.
> Counter after increment: 0
>
> MSI (s) (5C:34) [08:37:24:414]: Running installation inside multi-package
> transaction C:\ProgramData\Package
> Cache\{EE1C9582-FA55-4E05-9E08-036385B32255}v4.1.8426\OasisSetup.msi
>
> MSI (s) (5C:34) [08:37:24:414]: Grabbed execution mutex.
>
> MSI (s) (5C:9C) [08:37:24:416]: Resetting cached policy values
>
> MSI (s) (5C:9C) [08:37:24:416]: Machine policy value 'Debug' is 0
>
> MSI (s) (5C:9C) [08:37:24:416]: ******* RunEngine:
>
>            ******* Product: C:\ProgramData\Package
> Cache\{EE1C9582-FA55-4E05-9E08-036385B32255}v4.1.8426\OasisSetup.msi
>
>            ******* Action:
>
>            ******* CommandLine: **********
>
> MSI (s) (5C:9C) [08:37:24:416]: Note: 1: 2203 2: C:\ProgramData\Package
> Cache\{EE1C9582-FA55-4E05-9E08-036385B32255}v4.1.8426\OasisSetup.msi 3:
> -2147287037
>
> MSI (s) (5C:9C) [08:37:24:416]: MainEngineThread is returning 3
>
> MSI (s) (5C:34) [08:37:24:418]: User policy value 'DisableRollback' is 0
>
> MSI (s) (5C:34) [08:37:24:418]: Machine policy value 'DisableRollback' is 0
>
> MSI (s) (5C:34) [08:37:24:418]: Incrementing counter to disable shutdown.
> Counter after increment: 0
>
> MSI (s) (5C:34) [08:37:24:418]: Note: 1: 1402 2:
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
> 3: 2
>
> MSI (s) (5C:34) [08:37:24:419]: Note: 1: 1402 2:
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
> 3: 2
>
> MSI (s) (5C:34) [08:37:24:420]: Decrementing counter to disable shutdown.
> If counter >= 0, shutdown will be denied.  Counter after decrement: -1
>
> MSI (c) (48:E4) [08:37:24:421]: Decrementing counter to disable shutdown.
> If counter >= 0, shutdown will be denied.  Counter after decrement: -1
>
> MSI (c) (48:E4) [08:37:24:421]: MainEngineThread is returning 3
>
> === Verbose logging stopped: 10/20/2022  8:37:24 ===
>
>
>
>
>
> Best Regards,
>
>
>
> Jackie Xu
>
> Teradyne HeFei | ADC
>
> Office: +86-551-63803346
>
>
>
> *From:* Edwin Castro <egcastr at gmail.com>
> *Sent:* Wednesday, November 30, 2022 9:54 AM
> *To:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> *Cc:* wix-users <wix-users-bounces at lists.wixtoolset.org>; Jackie Xu <
> jackie.xu at teradyne.com>
> *Subject:* Re: [wix-users] Wix bundle failed to upgrade
>
>
>
> *CAUTION - EXTERNAL EMAIL: *Do not open attachments or links unless you
> recognize the sender and the content is safe.
>
> What does the log for the upgrade of OasisSetup.msi say?
>
>
>
> --
> Edwin G. Castro
>
>
>
> On Tue, Nov 29, 2022 at 5:31 PM Jackie Xu via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
> Hi Experts,
>
> I am facing an issue that I failed to upgrade my bundle installer on some
> machines (On most machines, it worked fine).
> My bundle contains 3 installers, 2 msi installers and one EXE installer.
> When install a newer version I got an error pop-up said, "The Specified
> Account already exists".
> After clicking OK, and a few moments later, it shows "0x80070003 - The
> system cannot find the path specified."
>
> Here is the log:
> [1408:0F00][2022-09-29T10:51:37]i301: Applying execute package:
> OasisSetup.msi, action: Install, path: C:\ProgramData\Package
> Cache\{3FDC0824-4867-40DE-A1F0-390AA8575AC4}v4.1.8352\OasisSetup.msi,
> arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
> [1408:0F00][2022-09-29T10:51:48]e000: Error 0x80070643: Failed to install
> MSI package.
> [1408:0F00][2022-09-29T10:51:48]e000: Error 0x80070643: Failed to execute
> MSI package.
> [2D58:5174][2022-09-29T10:51:48]e000: Error 0x80070643: Failed to
> configure per-machine MSI package.
> [2D58:5174][2022-09-29T10:51:48]i319: Applied execute package:
> OasisSetup.msi, result: 0x80070643, restart: None
> [2D58:5174][2022-09-29T10:51:48]e000: Error 0x80070643: Failed to execute
> MSI package.
>
> I tried to remove the OasisSetup.msi from the bundle, then the bundle can
> upgrade correctly, but when I install the OasisSetup.msi separately and
> upgrade it with a new MSI, it also worked fine. So I just suspect somehow
> the msi failed to upgrade in a bundle, but can upgrade alone.
>
> Any suggestions would be appreciated, this really bugs me for a long time.
>
> ________________________________
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.<
> https://www.teradyne.com/privacy-statement>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
> [firegiant.com]
> <https://urldefense.com/v3/__http:/www.firegiant.com/__;!!GenOTVeOfQ!WneStD5AgygaFBs5F4b17p2sBNOmfG48c19GXqiWt6U0eZhMbkBxJqB56VFUyW1l2qItNEXbibs_yowiFQ$>
>
> ------------------------------
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.
> <https://www.teradyne.com/privacy-statement>
>
> ------------------------------
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.
> <https://www.teradyne.com/privacy-statement>
>
> ------------------------------
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.
> <https://www.teradyne.com/privacy-statement>
>
> ------------------------------
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.
> <https://www.teradyne.com/privacy-statement>
>
> ------------------------------
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.
> <https://www.teradyne.com/privacy-statement>
>
> ------------------------------
>
> Please note that this message may contain confidential information. If you
> have received this message by mistake, please inform the sender of the
> mistake, then delete the message from your system without making,
> distributing or retaining any copies of it. Although we believe that the
> message and any attachments are free from viruses and other errors that
> might affect the computer or IT system where it is received and read, the
> recipient opens the message at his or her own risk. We assume no
> responsibility for any loss or damage arising from the receipt or use of
> this message. When we process personal data relating to physical persons,
> such processing will meet the requirements of applicable data protection
> legislation and will be in accordance with our Privacy Policy.
> <https://www.teradyne.com/privacy-statement>
>

More information about the wix-users mailing list